Socky

IcemaND, Thanks for the input. I will fire up a Hub tomorrow to see if that may be the source of my trouble. will report my results. bj-kaiser, I will try your suggestion as well, but i have a question: If your suggestion is the case (disabling the firewall), I will need it disabled each time i Boot a PC to WinPE. I will need a way to disable the firewall by default. In PE 1, there was a /nowf switch required prior to compilation. Is there such a thing with winpe2 or should i add a line to PE2's startup script? Thanks in adavnce.

Hello All, This post may be out of place because it may have nothing to do with WinPE. However, I'm sure people using PE for Ghost deployment have run into a similar situation as mine. Any help is appreciated: I'm having trouble getting multicast to work with Symantec Ghost 11. CLIENT: I boot to PE 2.0 (stock wim with Ghost32.exe added), run ghost32.exe, select multicast, enter session name, choose automatic ip detection and yes to overwrite... Server: Running Server2003 with DHCP scope of 192.168.0.1-192.168.0.50 enabled. Ghost server 11 -default settings running and accepting clients. I can see computers join the session but when i click send, the multicast hangs. Has anybody had this problem? Could this be an issue with my switch? is there a multicasting setting on most switches? I don't deal with switches, routers or telephones so wouldn't know these answers. Should i have the multicast range entered as a scope on my server box? anything would be great. thanks in advance.

Hello All, I have been adding network drivers to a custom PE image for all of the systems supported by our infrastructure. The idea is to use the custom build disk to connect to a network location for automated master installations or ghost imaging. I have used the following script to inject network drivers to my image, as per Microsoft's documentation. I have been getting very unpredictable results -espeically with Dell systems, and since we run about 1200 Dells, this is a large problem. After using the script, I get a message that the INF has been added to the image but when i test it and fire up an ipconfig i get this IP: 0.0.0.0. If i do a release renew, i then get a 169.x.x.x IP. Any information somebody could provide which would remedy this problem would be hugely appreciated. Thanks in advance, Socky ----InjectInfToPE.bat----- set build_x86=%c:\WinpeStage\build_x86% set driverLocation=%C:\Share\Drivers\Ins6400\WinXP\b44win.inf% set customPE=%C:\winpe% cd\ cd %build_x86% drvinst.exe /inf:%driverLocation% %customPE% pause ------EndOfScript------