Automatically Configure New Computers

Solution 1:

Don't bother with uninstalling or fixing bloatware. Just reimage the computers. In fact it's pretty easy to setup a reference image, sysprep, capture, and deploy it using WDS + MDT. See the aforementioned for various driver packages: trust me you're not the first person to think of this stuff, it's been solved already.

Profiles can be transferred with USMT. Mapped drives are best done with a logon script. Outlook 2007+ with Exchange 2007+ can use Autodiscovery. Install updates with WSUS (fully automated at install with a simple script). Keys and Activation can be managed with scripts or VAMT.

Fair warning that if you don't know about any of this stuff already you've got one heck of a learning curve to get through and you're way behind the times. If you really only have a handful of computers it probably isn't worth the time to set this stuff up now, but if it's more than a dozen it's worth the time. Also future hardware refreshes aren't nearly so painful. Bonus that many of these skills allow you to be more efficient in your routine tasks and help prevent problems.

Solution 2:

Solution that would work:

Install following applications

1. WDS (windows deployment services)

   • Use WDS to provide PXE boot. All laptops can boot via PXE into WDS server.
   • WDS will host MDT boot images

2. MDT (Microsoft Deployment Tool)

   • Create task sequences to capture your default Windows 7 install
   • Create task sequences to install your captured Windows 7 image
   • Create task sequences to install Applications
   • Automate the installation of HP drivers

3. WAIK (windows automated installation kit)

   • Required to automate the Windows 7 Install
   • Provides USMT and allow integration from within MDT

All of the above sits inside MDT boot images that is hosted within WDS. Thus during the boot into WDS server you are provided with all of these task sequences.

Create default Windows 7 Image and Capture for re-deployment

1. Install Windows 7 as normal
2. Uninstall bloatware using PC decrapifier software
3. Install Windows updates
4. Create MDT task sequence to sysprep and capture image
5. Boot into WDS and choose task sequence created and capture Windows 7 Image

When you sysprep a machine it strips the machine back to a state where it can effectively be re-instated with different Product Keys, different drivers, different machine name, differernt SID , etc…. It also boots the machine back to Audit mode – the state a newly bought machine is usually in (U know that Welcome screen you see to complete the final steps of a new PC install).

Configuring MDT Rules to automate yor requirements

1. Licensing - I MDT you can specify a VLM key or use the rules to request a product key to be asked during every deployment. Example of the rule to always ask to provide product key.

   SkipProductKey=NO
   

2. Add to domain with different machine name - This can be done with MDT rules. Rules settings below

   SkipComputerName=NO 
   SkipDomainMembership=NO  
   JoinDomain=domain.co.uk  
   DomainAdmin=username  
   DomainAdminDomain=domain.co.uk  
   DomainAdminPassword=password 
   

USMT & saving user data

I have not done this before, but in theory you create a standard replace task in MDT, run this on the existing Windows XP PC and USMT will allow you to save the user settings to a network location. You then boot into WDS and run a standard install task for Windows 7 and during the wizard phase specify that you want to restore user settings.

Install applications and pre-configure office & outlook

• Applications can be automatically installed via MDT - you will need to ensure you identify the silent install options for the application so that it does not interrupt MDT during ddeployment phase.
• Office 2007 or 2010 settings (default templates, product keys, etc...) can be configured and installed via MDT (to automatically detect user settings upon first run of outlook you will need exchange 2007 & outlooked 2007)

Upgrade Windows XP to Windows 7

• Again using MDT you need to create a task sequence to deploy the Windows 7 image you captured.
• Set USMT to ensure user settings are saved
• Choose which applications to install during deployment
• Set MDT to re-run windows updates after install
• MDT can also run any scripts or bat files yuo speicfy for any additional functionality (to map drives etc...) Although you are probably better to map drives using AD and group policy

Solution 3:

You know. I find the easiest way is to use Symantec Ghost, which essentially means you configure one machine how you want it, snap an image, and then use that image on all the other machines.

If you need the user profile on the old machine, then you can run a free tool called Transwiz on the old machine, save the profile on an external, and then use Transwiz on the new machine, select the profile, and it does all the work. It will transfer documents, profile, application settings, etc, etc. http://www.forensit.com/move-computer.html

At the very end of the day, I use SCCM for my re-imaging needs. I find working with packages easier than working with ghost because they are easier to alter if you need to make subtle changes between machines.