When machines run through the 4 steps of the setup process they communicate with the OSD database via tftp file transfers.
On machines with multiple network cards this process might get interrupted after the setup was successfully finished.
The machine therefore stays stuck in the "InstallationProcessRunning" status.
Why? .....
After the setup plus all pending NI scripts completed, there is a system script that excutes a finalize.exe from the local harddrive.
This executable generates a temporary file and transfers it to the OSD server under the following name %MAC_Addr%.se.
(the se stands for "setup ended")
On machines with multiple NICs the Mac Address gathered by this little tool does not necessarily catch the MAC of the NIC that was used for the PXE boot. Therefore the file that is transferred to the server has the wrong file name.
Fix
Perform the following steps to fix the problem:
1.
Capture the correct MAC in during the execution of the the prosetup.bat by generating a ini file with this information:
echo [OSDNIC] > c:\osdnic.ini
echo MAC=#@caa########## >> c:\osdnic.ini
2.
Modify the EndInstallationProcess Script in NI to gather the correct OSD MAC with a simple ReadIni Statement
and instead of executing the finalize.exe, execute the following command
"tftp.exe <OSD-Server> PUT <local Dummy-file> <OSDMAC>.se"
© www.prodeploy.com
Wednesday, May 16, 2007 11:59 AM
hweeres