GreenLake Administration
ProLiant Deployment and Provisioning
1846938
Members
5707
Online
110257
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
Forums
Discussions
Discussions
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
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
03-04-2004 08:14 AM
03-04-2004 08:14 AM
Menu
I am looking for some advice on best practice to implement a menu based system to deploy OS's to different hardware platforms.
I have created a number of unattended install jobs (based on different hardware) and several modular based configuration, application install and security jobs to modify the default Windows install.
My question:
How can I distribute the unattended install as well as the appropriate jobs to a new server based on the hardware platform.
e.g. New HP BL20p running Windows 2000 - User chooses "BL20p (win2000)" config from a menu system and the appropriate jobs start executing in sequence.
I have seen that Altiris doesn't recommend the "Initial Deployment" method for systems above 10 computers.
I have also had a bit of a play with Virtual PCs but my first attempt seemed to put the client into a infinite reboot cycle after running the first job (unattended install).
Any thoughts/ideas/recommendations?
Regards,
Geoff.
I have created a number of unattended install jobs (based on different hardware) and several modular based configuration, application install and security jobs to modify the default Windows install.
My question:
How can I distribute the unattended install as well as the appropriate jobs to a new server based on the hardware platform.
e.g. New HP BL20p running Windows 2000 - User chooses "BL20p (win2000)" config from a menu system and the appropriate jobs start executing in sequence.
I have seen that Altiris doesn't recommend the "Initial Deployment" method for systems above 10 computers.
I have also had a bit of a play with Virtual PCs but my first attempt seemed to put the client into a infinite reboot cycle after running the first job (unattended install).
Any thoughts/ideas/recommendations?
Regards,
Geoff.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2004 11:09 PM
03-04-2004 11:09 PM
Re: Menu
Look at the SYSTYPE utility. It's documented in ssstkug.pdf in the deploy\tools\ssst directory on your RDP server.
Ken Henault
Infrastructure Architect
HP
Infrastructure Architect
HP
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP