Tripredacus

I am looking to do my first capture of a multi-partition image, but I have encountered one problem. Can Imagex capture a hidden partition?

We get this if the NIC uses a different driver than is included in the PE.

Since Windows XP has something like 14 different HALs, the IMage you use needs to be machine specific. Unless your WIM is actually an install ISO, then that case is different. Windows PE, I hear, has full support for HTA scripting (also likly other tools as well). There is a Windows PE section on this forum. You can capture an image with imagex to a network drive. The computer you are using to store the boot images does not need any WDS software installed unless you are using it for PXE Booting.

I would say try to go into Safe Mode and make a new profile, the try logging in with that one to see if the same thing happens. Make sure to give this new user admin rights tho.

I am pretty sure you need to install the Windows AIK as well.

IIRC, if you do not to extensive configuration, sysprep will blow away all accounts on the machine, as well as regen your SID unless you tell it otherwise. You may also encounter drivers that need to be reinstalled after you go through the welcome screen.

I am now wondering if there is a way to create a standardised XP image that does not capture the drivers for the motherboard and HDDC for example. Because I can't use an image captured from a Shuttle onto a different motherboard, or else Windows will just reboot constantly.

I have experienced this same issue. My question is if your DS runs DHCP or not. I have this problem when the DHCP server is not the DS. If the DS runs DHCP, it all works properly and I can do a network service boot. Unfortunately in my case, the network segment will not function properly if the DS runs DHCP. So I need to figure out how to resolve this as well.

Do you get an error after you run the initializenetwork command?

Good start! I was going to say corrupted profile!

I have found instructions that allows me "To Delegate ability to authorize DHCP servers to a non-enterprise administrator" on Tech Net. The Domain Controller has its DHCP disabled (but will only use it for network service boots) and the Proxy Server is running DHCP for the LAN. The Proxy Server is not a member of the domain, so I can't ever find it to authorize it properly. Is there a way to create an alias to a non-domain computer so that I can give it security permissions? Is making the Proxy Server log into the domain the only way to do this?

This worked out very well for me. We got an order in for a machine that we could not get Ghost to recognise the drivers in DOS. So I imaged the machine using the PE. All said and done, I was able to load a 1.5GB XP Pro image on a computer in 100 seconds (it was about 1% per second). Now if I could only get it so my WDS doesn't take down the network I would be using it for everything.

I am having this proble also. On Intel 965 Chipset on a Shuttle board. The NI is a Broadcom 5789 GigaBit. I have added the driver to the PE but then an ipconfig -renew comes back with "Interface is Unknown" but an ipconfig -all does display the correct device name, but the IP address is 169.x.x.x. Also the DNS Servers are displayed ie fec0:0:0:ffff::1%1....

Bump and cross-posted

This looks really cool. I will look at it on Monday to see if we can implement it into the Deployment Server I am working on.

It was OK. I'll probably like it more if I went to see it again.

On a couple of different Vista installs (both in Factory and after sysprep) we have encountered times when the Control Panel won't open, or will CTD less than a second after opening. We can still get to the Control Panel by going through My Computer. This behaviour seems to occur quite often. Anyone know what causes it or have experienced it before?

Thanks for that information. I am slowly but surely figuring this out. I have been able to make 1 successful boot to PXE, but then the network went down. I have found that I cannot boot from the PXE unless the Deployment Server (DS) is running DHCP. Here is a layout for what is involved in the network. 1. DHCP/Proxy Server (192.168.0.5) serves IP addresses from 192.168.0.10 - 192.168.0.250. It runs MS ISA Server 2004 and acts as a router/webproxy from the LAN to the ISP connection. It exists within WORKGROUP workgroup. It is configured to look to an Exchange server for DNS and to the DS for PXE Bootloaders. 2. Exchange Server (unsure as to exact IP, but exists within 192.168.100.x) runs DNS as far as we are concerned. It exists within the WORKGROUP workgroup. 3. DS/AD Domain Controller (192.168.0.8) runs Deployment Server and has the capability of being a Ghost server as well. DHCP is currently authorised to itself, but the scope is disabled. It resides within the subnet of WORKGROUP, but operates a domain of zero members. AD is only running because DS requires it to be active. The DNS and DHCP Servers are NOT members of the domain. The idea is that when an interface requests an IP address, it goes to the DHCP Server to get its address. If the interface wishes to do a network boot, the DHCP Server tells the interface to use the DS. Then the computer would boot from the network that way. The problem is that in the current configuration, this does not occur. I receive Errors E35 and E39 from PXE. In my infinite wisdom, I changed the DS scope to 192.168.0.249 - 192.168.0.249 (thus only 1 IP could be leased). When this was done, I booted a computer to PXE, it got an IP address from the DS and not the DHCP server. Then it successfully booted into a Vista Business Setup WIM (used for testing). Then the DS reported "scope full" errors and DHCP dropped across the LAN. The Proxy Server suddenly declared that it was no longer authorised to serve IP addresses. After some running around I managed to put both servers back to their initial states where it did not work. So it would appear that DHCP needs to be actively running on the DS in order to do a PXE boot. My only concern is that the DS would not give outside network access such as the DHCP server would. I was also authorised to allow the DS to server IPs 192.168.200.200 to 192.168.200.250 but Windows reported that this was an invalid IP range and it was not a valid scope. Questions: 1. Is there hope for this configuration of servers on the network? 2. Is there a workaround to enabling DHCP on the DS to boot off PXE? 3. Why was that address range invalid? I should also note, that the DHCP server could not see the DS by the complete domain name. In fact, it cannot see it if any part of the domain name was used, likely because the DHCP Server is not a member. It can see it fine based solely on the computer name itself.

Greetings, I was given the task to setup a Windows Deployment Server onto our network. I am going through the Configuration of the server and I have some questions. I am at the DHCP Option 60 screen right now and it concerns me. We wish to use this server to hold our WIMs for deployment through a PE PXE environment. But I have a concern about that. I was able to set a static IP for the server, and make it an AD Domain Controller. But it is NOT the DHCP Server for the network segment it is on. Is it possible for other computers on the LAN to PXE Boot to this server if it isn't the DHCP Server? Is there any good documents regarding this type of setup?

Try setting the boot order to Floppy, Hard Drive then CD. Or put the hard drive first.

I do with some productivity software, but not games. I buy those for sure. Music I can't say that really counts. That is such a fine line there. The problem is that a lot of bands actually bootleg their own stuff so I can't even count that.

I would say that "custom build" is not a valid "pc make". Unless you own your own company that makes custom builds...

Yes it is a popular discussion. A hacker breaks into systems to learn things. No damage is to be done. After successful entry and information retreival, the owner of the system is to be reported and notified of the vulberability. Anyone who does not follow these rules are not deserving of the term "hacker".

deal

BUt don't try transparent windows on Windows 98. It tends to lock up the computer.