Hi all, Just a quick one to give something back - we wanted to automatically name our stations to the service tag when provisioning. Here's a simple PowerShell script which you can save as rename.ps1 or something and then just add as a PowerShell distribution package and set as a provisioning step. Specifies the computer name used to access the computer from the network. If ComputerName is empty or missing, the user must Why the Hell don't microsoft admit they stuffed up with Windows 7 sysprep compared to XP, and left out any way to prompt for a computer name in a sysprep pass.

My first time as an actual poster here! Apologies if this is in the incorrect forum - but it sounded somewhat reasonable:) Our DR site service provider requires us to provide a reference image which they will clone via a basic Ghost capture and then deploy to 500 odd PC's in the event of a DR scenario. I would be most grateful for any guidance with regards to the following: Can we run sysprep on Windows 10 with an answer file which will automatically rename the machine (perhaps based on the service tag?) and automatically add it to the domain? American eurocopter ec 145. The ideal is to make this as automated as possible and require as little interaction as possible. Perhaps a better idea with as minimal setup as possible. We do have an onsite SCCM distribution point as well if that helps with an alternative solution. Thanks in advice for any guidance on this.

Basically, use MDT 2013. It is the bigger umbrella which encompasses the other components.

Being MSFT, there is no shortage of information, and it can take a while to pare things down to just what is needed. Aim on using Powershell for pre-, mid-, and post- imaging tasks. Check the link list— • Also, keep in mind the Deployment MVPs— • Johan Arwidmark, • Mikael Nystrom, • Michael Niehaus, • etc TechEd's Channel9 site has *lots* of sessions to go through to pick up tips & tricks— • • •.and more broad 'MDT' based searches Should books be your forte, try— • Deployment Fundamentals, Vol 1, (only one really needed) • Deployment Fundamentals, Vol 2, • Deployment Fundamentals, Vol 3, • Deployment Fundamentals, Vol 4, Experiment lots to see how well it works out for you. Maybe 3-6 months down the line, try a SmartDeploy trial. They have frequent webinars (bring questions, problems, and concerns to test their mettle and make them earn your business).

Should give an honest feel for free vs commercial, and best ascertain the value thereof. First I would not connect the 'mother' machine to AD before cloning. You want a clean, minimum system for cloning. Also set the mother machine name to something generic, like 'mother' and not use that name for your production system. You will be much happier with the results if you do it this way. Other than that it sounds like a process I have used before. We used clonezilla to make the mother image and deploy it that way.

• Open MioMore Desktop. • Connect your device to the PC and turn it on. • Go to Unlock features > Enter the Activation Key sent to you by email > click Continue > Finish. Mio. • If you are offered any updates via MioMore Desktop please download and install these.

For anything larger than just a few machines I would use FOG (or WDS) instead of doing it the clonezilla way. Lastly I do have to comment about licensing. Windows OEM licenses doesn't support cloning. Make sure you understand your EULA before moving forward with the project. (end of legal announcement) Other than the licensing thing, it can be done as you have outlined. First of of thanks for taking the time to respond guys, I really am grateful!