Image DHCP servers from the console
Updated: 23 May 2010 | 2 comments
This issue has been solved. See solution.
ok heres my scenario:
34 schools each with their own DHCP server, all with their own set of VLAN's
Ghost server centrally located, sites connected between 45-100mb connections
i want to use the ghost console to image these DHCP servers
i have imaged other servers at the same sites using the console before but not the DHCP machines
problem- the console kicks off a task, client boots to pre-os and attempts DHCP but theres no server feeding dhcp into the system
solution?- make the pre-os use a static ip address
how do i make the pre-os use a static IP of my choosing?
discussion Filed Under:
Comments
In general, as part of
In general, as part of building the preOS, if the network adapter being used by the machine to talk to the GSS server has a static IP setting on it then that setting should get propagated into the preOS.
That process is pretty simple and thus robust if the preOS is DOS since only a single network interface is brought up. For Windows PE it's potentially more complicated ensuring that the settings from host OS get applied to the right network adapter, since Windows tries to detect all the hardware and; the Virtual Partition building code is set up to edit the unattend.xml file inside Windows PE to propagate static IP settings from the host OS into the preOS and apply it to the same network adapter.
So, provided that your machines acting as DHCP servers have a static IP address set on the network interface on which they communicate to the GSS console, in principle that network address should be what is picked up in the preOS. If that doesn't happen, then in the preOS the first port of call is the wattcp.cfg or unattend.xml file in which the static IP settings would be being passed down to the preOS.
thanks Nigel, thats the
thanks Nigel, thats the information i needed! last night i kicked off the image without anything special just to see what happened. this morning i checked the logs and it happened just like you said it would. i guess i didnt realize the system was already set up for that, i just assumed the pre-os pulled a DHCP address. thanks again, im glad i can count on getting my questions answered here
Would you like to reply?
Login or Register to post your comment.