- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Win2k3 post install processes
ProLiant Deployment and Provisioning
1820294
Members
3313
Online
109622
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2003 12:00 AM
тАО09-24-2003 12:00 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2003 11:07 PM
тАО09-24-2003 11:07 PM
Re: Win2k3 post install processes
Has anyone else had this issue? If not, what does your command.txt look like?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2003 05:13 AM
тАО09-26-2003 05:13 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2003 02:39 AM
тАО11-12-2003 02:39 AM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP