What Is Your Imaging Process

R

rosco

Gawd
Joined
Jun 22, 2000
Messages
722
I am looking to create a image for our new Windows 7 machines. It's been a while since I created an image so I'm looking for some pointers.

This is for a small school with a Windows Server 2008 box (x 2) and these computers will be going in a shared media center. So, different students will be logging on each day.

So, take me through your procedure if you would for creating your ultimate image for your workstations.

I'm looking to streamline the process each user goes through when they login also. We end up with each user sitting at "setting up personal settings" and also our MS Office 2007 asks them for their name and initials and whether or not they want to install updates. I would like info on how to eliminate that as well.

Thanks for the help.
 
Use the Microsoft Deployment Toolkit (a new version was just released a few days ago). You can use it to make an automated build. Once you have your build, you will be able to push it out to machines.

You can also make task sequences to install software. I recommend not installing software into your base image, and instead, use a task sequence to install it. That way, when you have to patch office or install the next version of the app, you can just update the task sequence to deploy it and you won't have to worry about opening up that base image and unintentionally corrupting it.

Most application settings are in the registry. Using Group Policy Preferences, you can push a registry setting to all machines, all machines with criteria, all machines a specific user or group logs into, etc, etc. Instead of baking those settings into the base image, you should use Group Policy to push them.

In regards to users sitting at the "setting up personal settings" stage of the login -- that is your profile loading. Could be anything from a slow profile store to a user dropping a large file on their desktop. You'll have to look at the User Environment Debug logs to see what it's doing. If I recall correctly, there is actually an event log for that now -- I don't remember if you have to turn on logging or if it's on by default. Either way, that is what you will need to do to figure out that problem.



This method has a steep learning curve and can be hard to comprehend at first. It actually isn't that bad, just a different way of thinking. I highly recommend finding some proof of concept tutorial and setting something up as a test at first. Then you can move it to your production and modify it.
 
Microsoft Deployment Kit is the bulletproof way to do it. If you have volume licensing and the school already has a local KMS server, you have way more flexibility and can easily use Acronis/Ghost/Clonezilla images. As far as personal settings go, just join the machine to the domain/AD and use remote profiles. The user should only have to set up their desktop and MS Office preferences the first time they log in.
 
Part of my concern is I'll be using Win 7 pro oem licenses that came with the computers.

I have looked into the deployment toolkit and it seems like a LOT to figure out.

Another question, do I have to use sysprep? I'm used to imaging a XP workstation in workgroup mode. Deploying the image, renaming the machine, then joining it to the domain. I have never ran into issues that way. I heard it could be a bigger problem with Win 7 though.
 
In XP you should be sysprepping as well! Lots of things can break if you don't sysprep in XP.

MDT is the way to go with Windows 7.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Is there a MDT for dummies you guys could point me to? I'm sure it's because the toolkit is so flexible, but it seems like there are a TON of options.

I have an Acronis Workstation boot cd that lets me change the SID as part of the restore process. I'll probably use that until I get this figured out.
 
rosco said:
Part of my concern is I'll be using Win 7 pro oem licenses that came with the computers
Click to expand...

I hate to be the bearer of bad news -- but if your desktop isn't under an SA with Microsoft, you're not legally allowed to deploy your desktops with *ANY* sort of imaging process. This means Ghost, Acronis, MDT, etc.

This was just brought to my attention the other day during our licensing talks with Microsoft. I wasn't actually aware of it.
 
Install Windows 7
At welcome screen ctrl+shift+f3 (reboots to audit mode)
Install all drivers and software
Sysprep shutdown with unattend.xml
Boot to cloning medium
Manually Delete Page File
Clone disk or copy to image file

The unattend.xml file I use just inputs products key, creates a local default admin account, copies administrator to defaultprofile, and tweaks a few minor things on the system. Basically when the computer boots back up (since it has been sysprepped) it acts like a new installation of Windows, then runs through the unattend and changes what I want and the system winds up at the logon screen ready to go for users.
 
Demon10000 said:
I hate to be the bearer of bad news -- but if your desktop isn't under an SA with Microsoft, you're not legally allowed to deploy your desktops with *ANY* sort of imaging process. This means Ghost, Acronis, MDT, etc.

This was just brought to my attention the other day during our licensing talks with Microsoft. I wasn't actually aware of it.
Click to expand...

While this is true. Its not like MS will take legal action against it.

You can always talk to a MS representative, IME they are very understanding. I'm sure they'll come out with a solution that will benefit both parties.
 
It sounds to me as though you need assistance in creating an unattended installation.

The integrated Sysprep utility is perhaps one of the more commonly used options to automate a successful deployment. The official Sysprep utility is located in the folder C:\Windows\System32\Sysprep of the Windows 7 environment.

In addition to Sysprep there a few more tools you could use to create images and simplify your imaging and deployment process in the future. Perhaps the best place to start would be to check out the Deliver and Deploy Windows 7 page on the Springboard site on TechNet so as to familiarize yourself with Windows 7 deployment. For now, there are some tips that I can give you to assist you both with the use of the Sysprep utility and creating unattend.xml files and then proceeding from there.

The first tip is to use the Windows Automated Installation Kit (Windows AIK), which includes WSIM (Windows System Image Manager) to create unattend.xml files, or an answer file. The Windows Automated Installation Kit or Windows AIK includes several utilities that can help make using the official Sysprep utility easier than ever. Windows AIK also includes ImageX, which is the Microsoft cloning utility that creates file-based images (.wim) allowing the images to be modified after their creation to apply updates, new drivers, or applications. You can even automate the process of joining a domain.

The second tip is to use Audit Mode to customize the system and perform customizations to the default profile. By allowing you to log into the system as Administrator, Audit Mode can significantly simplify the customization process. In order to customize the default profile in both Windows Vista and Windows 7 you will need to make your customizations in Audit Mode, and then run Sysprep with an answer file that has the copyprofile setting enabled.

The final tip I will leave you with is to use the Microsoft Deployment Toolkit (MDT) as Demon10000 and CEpeep suggested. MDT combines all of the official tools above into a single workbench interface that can help automate the entirety of the process. Additionally, it is compatible with Windows XP, Windows Vista, Windows 7, and Windows Server 2003, 2008, and 2008 R2, which means learning one utility to do all of your deployments. Furthermore, it is exceptionally useful in creating “universal” images as it can easily add or remove drivers or applications from the deployment images. MDT can also be used in conjunction with Windows Deployment Services (WDS).

For a step-by-step guide to deploying Windows 7 I recommend this step-by-step guide from the Springboard Series on TechNet and the Build a better desktop image resource as it is a great article with additional detailed information on desktop image management.
One last thing! There is an upcoming Webcast from TechNet that might be of interest to you:

The TechNet Webcast series is coming up on May 15th and 17th – Everything You Wanted to Know and Ask about Windows Deployment (Part 1 & 2) – Register here.

Last but not least, regarding the licensing question: While I work with the Microsoft Windows Outreach team for IT Pros, I cannot comment on licensing do's / don'ts. When we offer our advice we assume that the author has ascertained the legal right to do what he or she is about to do.

Jessica
Windows Outreach Team – IT Pro
 
winoutreach5 said:
Last but not least, regarding the licensing question: While I work with the Microsoft Windows Outreach team for IT Pros, I cannot comment on licensing do's / don'ts. When we offer our advice we assume that the author has ascertained the legal right to do what he or she is about to do.

Jessica
Windows Outreach Team – IT Pro
Click to expand...
i like the way you roll ;)
 
winoutreach5 said:
It sounds to me as though you need assistance in creating an unattended installation.

The integrated Sysprep utility is perhaps one of the more commonly used options to automate a successful deployment. The official Sysprep utility is located in the folder C:\Windows\System32\Sysprep of the Windows 7 environment.

In addition to Sysprep there a few more tools you could use to create images and simplify your imaging and deployment process in the future. Perhaps the best place to start would be to check out the Deliver and Deploy Windows 7 page on the Springboard site on TechNet so as to familiarize yourself with Windows 7 deployment. For now, there are some tips that I can give you to assist you both with the use of the Sysprep utility and creating unattend.xml files and then proceeding from there.

The first tip is to use the Windows Automated Installation Kit (Windows AIK), which includes WSIM (Windows System Image Manager) to create unattend.xml files, or an answer file. The Windows Automated Installation Kit or Windows AIK includes several utilities that can help make using the official Sysprep utility easier than ever. Windows AIK also includes ImageX, which is the Microsoft cloning utility that creates file-based images (.wim) allowing the images to be modified after their creation to apply updates, new drivers, or applications. You can even automate the process of joining a domain.

The second tip is to use Audit Mode to customize the system and perform customizations to the default profile. By allowing you to log into the system as Administrator, Audit Mode can significantly simplify the customization process. In order to customize the default profile in both Windows Vista and Windows 7 you will need to make your customizations in Audit Mode, and then run Sysprep with an answer file that has the copyprofile setting enabled.

The final tip I will leave you with is to use the Microsoft Deployment Toolkit (MDT) as Demon10000 and CEpeep suggested. MDT combines all of the official tools above into a single workbench interface that can help automate the entirety of the process. Additionally, it is compatible with Windows XP, Windows Vista, Windows 7, and Windows Server 2003, 2008, and 2008 R2, which means learning one utility to do all of your deployments. Furthermore, it is exceptionally useful in creating “universal” images as it can easily add or remove drivers or applications from the deployment images. MDT can also be used in conjunction with Windows Deployment Services (WDS).

For a step-by-step guide to deploying Windows 7 I recommend this step-by-step guide from the Springboard Series on TechNet and the Build a better desktop image resource as it is a great article with additional detailed information on desktop image management.
One last thing! There is an upcoming Webcast from TechNet that might be of interest to you:

The TechNet Webcast series is coming up on May 15th and 17th – Everything You Wanted to Know and Ask about Windows Deployment (Part 1 & 2) – Register here.

Last but not least, regarding the licensing question: While I work with the Microsoft Windows Outreach team for IT Pros, I cannot comment on licensing do's / don'ts. When we offer our advice we assume that the author has ascertained the legal right to do what he or she is about to do.

Jessica
Windows Outreach Team – IT Pro
Click to expand...

Tnx for the info, I just registered.
 
Stoly said:
Tnx for the info, I just registered.
Click to expand...

You are quite welcome! Please feel free to PM me directly if you have any questions on the information provided in the webcast after it airs.

Jessica
Windows Outreach Team -- IT Pro
 
You must log in or register to reply here.
Back
Top