jwall

I'm just wondering what peoples practices are for deploying new Win7 or XP images to client machines. How do you prepare the master image, what do you use to image and what processes happen after imaging? I'm coming from an eDir / ZENworks shop, with very little AD experience (as strange as that sounds) with 100% XP machines, where I currently run a vbs script on my master machine before uploading the image, which continues running after the image is downloaded to configure the image for a particular school. Now we'll be deploying Win7 and XP together. I've read that one way to create the master is to put the machine in audit mode, but that just logs me into the local Administrator account, I think I'll need at least a domain user account (if not domain admin) to install apps or make config changes, is this correct? Thoughts on this? Currently we make limited use of group policies, the vbs scripts set everything from homepage to screensaver to Novell client settings to timezone (we have schools in 2 timezones) for a specific local Windows user account to which ZENworks logs our users into. It's kind of like setting up the Default user profile in the AD world. How to other organizations handle this problem?

Got the mapping working, that's one thing out of the way. Looks like the dsadd computer command will allow me to add the computer to OU I want so I should be off to the races

Thanks Jack, I'll look into that. Question, what happens if I rename a workstation after it's been added to the domain? Does it cause problems or would the computer object just end up being different than the computer name?

We are migrating our network from Novell eDirectory / ZENworks 7 to Active Directory and I am grappling with Sysprep for the first time and having some trouble doing what I want. It might help to know how we deploy workstations with eDir / ZEN now so: I create the workstation image with apps and configs I want, then run a vbs script that that enables AutoAdminLogin for a specific local Windows user account, copies 4 more vbs files (Phase 1 thru 4) to C:\, and creates a runonce to run Phase1 on the next boot. Then I restart and upload my master image. When this master image boots up on the destination machine it logs in as the user I specified and runs Phase1.vbs. The first thing Phase1 does is determine its IP (to know which school it's at), names the machine as specified in a txt file on the schools server, then set Phase2.vbs to runonce, followed by Phase3 and so on. When Phase4 runs it disables AutoAdminLogin, reboots and we have a local Windows account configured for that particular school, ie homepage, screensaver, Novell client settings etc, ready for our users. Using ZENworks, when our users log in with thier eDirectory credentials they are automatically logged into this local Windows user account so they have the homepage, screensaver etc that we have configured. The problem I'm having right now with sysprep is naming the machines according to a txt file on the server. I have set my answer file to do an AutoAdminLogin to the local Administrator account but do I need to login as a domain user in order to get a txt off the server? If this is the case then the next problem becomes how do I login as a domain user when the machine is not in the domain yet? I'd like to be able to script / automate the computer object creation as well and specify where to put it in the tree (ie not the Computers container). I should add that we are thinking of using FOG (I haven't looked into WDM, are there any benefits over FOG?) for imaging until we get around to looking at System Center. Any help would be appreciated.