ProLiant Deployment and Provisioning
1820294 Members
3313 Online
109622 Solutions
New Discussion юеВ

Win2k3 post install processes

 
Sean Cook
New Member

Win2k3 post install processes

I am using the 2.2 version of the smartstart scripting toolkit with supportpack 6.4, and when Server 2003 finishes installing it should run the postinstall task of GUICMD, but it appears to fail and then reboots without installing any of the HP drivers or utilities. I have noticed in the BestPractices guide that the CMD.TXT sample is different than the one found in the 6.4 SupportPack CD (Compaq\Install\wnet\). Which one is correct, if any?
3 REPLIES 3
Sean Cook
New Member

Re: Win2k3 post install processes

Has anyone else had this issue? If not, what does your command.txt look like?
Jeff Mathews
Respected Contributor

Re: Win2k3 post install processes

Hey Sean, I actually quite using the guicmd.exe tool in favour of the dos setup command line for Support Packs. The only thing with doing that, you can no longer launch other tasks from the cmd.txt file, but you can launch anything from the unattend.txt [GuiRunOnce] section. If you're interested in doing that, try running the following command:
c:\$oem$\ntcsp\setupc.exe /f /silent /use-first-csp:1989

Of course your location of the support pack may differ from mine as I'm using the deployment server now. This line is executed from the GuiRunOnce.

The last time I used the GUICMD.exe utility, my cmd.txt file looked like this:

Jeff's Installation Utility
Updating with the latest Compaq Drivers. Go have a coffee, this could take awhile...
C:\ntcsp\setupc /f /silent C:\ntcsp\bp000128.xml
waitonprocess SETUP50.EXE 120

C:\CMSISU.EXE

delfile C:\CMSISU.EXE

Of course the first two line only modify the title bar and message displayed in the guicmd.exe window.

Hope this helps....

Jeff

Re: Win2k3 post install processes

I used also the toolkit 2.2 with the guicmd to automate some installation and configuration tasks. I had the same issue (i.e. guicmd showed an error message indicating that the file cmd.txt could not be found).

So, in the server.bat file, during the step where files are copied to the system disk I also copied the cmd.txt and the guicmd.exe at the root of the system disk. I was able to run any command I wanted by specifiying it in the cmd.txt.

Extract of my .bat (State 3):
copy s:\CpqW2k3\$OEM$\$1\guicmd.exe c:\
copy s:\CpqW2k3\$OEM$\$1\cmd.txt c:\

Hope that helps.