- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- smart start scripting toolkit issue (systype/guicm...
ProLiant Deployment and Provisioning
1753797
Members
7277
Online
108799
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
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
тАО08-26-2003 09:37 AM
тАО08-26-2003 09:37 AM
smart start scripting toolkit issue (systype/guicmd)
Hi,
i am new to smart start scripting. I have managed to do the installation for dl360g2 with compaq smart start scripting. but as i had few different compaq machines I was implementing this in autoexec.bat
s:\cpq\systype ssstksys.ini
if errorlevel 53 goto DL580
if errorlevel 50 goto DL380
if errorlevel 49 goto ML530
if errorlevel 47 goto ML350
if errorlevel 71 goto DL360g2
but with this it correctly identifies the machine (if u run it on command line for dl360g2 it says system id: CPQ0724) but does not goto the section for the particular machine like dl360g2.bat in the autoexec.bat.
Another issue i was having was with guicmd.exe. If i have this line in cmd.txt
C:\ntcsp\setupex.exe /smartstart:C:\ntcsp\mgmtpwd.txt
Manully it runs ok but with guicmd it gives a install error.
i am new to smart start scripting. I have managed to do the installation for dl360g2 with compaq smart start scripting. but as i had few different compaq machines I was implementing this in autoexec.bat
s:\cpq\systype ssstksys.ini
if errorlevel 53 goto DL580
if errorlevel 50 goto DL380
if errorlevel 49 goto ML530
if errorlevel 47 goto ML350
if errorlevel 71 goto DL360g2
but with this it correctly identifies the machine (if u run it on command line for dl360g2 it says system id: CPQ0724) but does not goto the section for the particular machine like dl360g2.bat in the autoexec.bat.
Another issue i was having was with guicmd.exe. If i have this line in cmd.txt
C:\ntcsp\setupex.exe /smartstart:C:\ntcsp\mgmtpwd.txt
Manully it runs ok but with guicmd it gives a install error.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2003 06:05 AM
тАО08-27-2003 06:05 AM
Re: smart start scripting toolkit issue (systype/guicmd)
Try moving the "if errorlevel 71..." line above the "if errorlevel 53..." line.
DOS return codes (errorlevels) will return "true" if the return code was equal to or higher than the specified errorlevel.
DOS return codes (errorlevels) will return "true" if the return code was equal to or higher than the specified errorlevel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2003 10:42 AM
тАО08-29-2003 10:42 AM
Re: smart start scripting toolkit issue (systype/guicmd)
Hi,
Try using the following two commands in your cmd.txt file:
c:\ntcsp\setupc.exe /silent c:\ntcsp\bp000128.xml
waitonprocess SETUP50.EXE 120
Each time you change to a new SS package, just change the name of the xml file to match the one that came with the new SS package.
Jeff
Try using the following two commands in your cmd.txt file:
c:\ntcsp\setupc.exe /silent c:\ntcsp\bp000128.xml
waitonprocess SETUP50.EXE 120
Each time you change to a new SS package, just change the name of the xml file to match the one that came with the new SS package.
Jeff
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP