Fully Automated Windows XP Scripted Install - Rename and Join Domain Best Practice
I've got our Sysprepped Images deploying fully automated to near perfection. It's a thing of beauty.
I am now looking at the Scripted install side of things as the driver feed makes it far more flexible than Images.
The actual installs are working perfectly but I'm finding the scripts that I used for the Images do not work as well for the Scripted install.
For my Images is used the scripts from - http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=763&artlang=en
I find that it if I use this script on a Scripted Install it tries to do all the steps in one go rather than waiting for the reboot to happen.
I've tried Naming Rules, they work fine, but I can't use a Naming Rule AND a Join Domain script at the same time due to the rename needing a restart.
The Pre-Installation scripts will not work for all of our installs as not all of our machines get rebuilt with the same name each time. We need the control that wsname and it's external data file gives us.
While I know I can use wsname to rename/delete the AD account, we require the machine to go into the correct OU on it's own so I need to machine to have to correct name BEFORE it joins the domain.
I just wondered what it the Best Practice method for achieving this?
Is there a way to run wsname as a Pre-installation task? Maybe using the /UNATTEND switch?
Or as a Post Installation Task but before Reboot (Exit Boot Environment)?
For now I'm toying with using the following method...
K2000 Post Installation:
Naming Rule
(reboot)
K1000:
Install Agent
Join Domain Script
Install Distributions configured for that machine (via Breadcrumbs, Labels etc...)
I am now looking at the Scripted install side of things as the driver feed makes it far more flexible than Images.
The actual installs are working perfectly but I'm finding the scripts that I used for the Images do not work as well for the Scripted install.
For my Images is used the scripts from - http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=763&artlang=en
I find that it if I use this script on a Scripted Install it tries to do all the steps in one go rather than waiting for the reboot to happen.
I've tried Naming Rules, they work fine, but I can't use a Naming Rule AND a Join Domain script at the same time due to the rename needing a restart.
The Pre-Installation scripts will not work for all of our installs as not all of our machines get rebuilt with the same name each time. We need the control that wsname and it's external data file gives us.
While I know I can use wsname to rename/delete the AD account, we require the machine to go into the correct OU on it's own so I need to machine to have to correct name BEFORE it joins the domain.
I just wondered what it the Best Practice method for achieving this?
Is there a way to run wsname as a Pre-installation task? Maybe using the /UNATTEND switch?
Or as a Post Installation Task but before Reboot (Exit Boot Environment)?
For now I'm toying with using the following method...
K2000 Post Installation:
Naming Rule
(reboot)
K1000:
Install Agent
Join Domain Script
Install Distributions configured for that machine (via Breadcrumbs, Labels etc...)
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
cblake
13 years ago
Posted by:
Arcolite
13 years ago
Posted by:
cblake
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.