• Choosing a Deployment Strategy
• • High-Touch with Retail Media. A hands-on, manual deployment, where you installing the Windows operating system on each client computer by using the retail installation DVD, and you manually configure each computer. This strategy can save your organization time and money by helping you automate portions the installation process. We recommend this strategy if your organization does not have dedicated information technology (IT) staff, and it has a small, unmanaged network with fewer than 100 client computers.
    
    
   
  •   High Touch with Standard Image. This strategy is similar to the High Touch with Retail Media strategy, but it uses an operating system image that includes your customizations and application configurations. We recommend this strategy if your organization has at least one IT pro (with or without prior deployment experience) on staff, and a small or distributed network with 100–200 client computers.
    
    
   
  •   Lite-Touch, High-Volume Deployment. This strategy requires limited interaction during deployment. Interaction occurs at the beginning of the installation, but the remainder of the process is automated. We recommend this strategy if your organization has a dedicated IT staff, and it has a managed network with 200–500 client computers. Prior deployment experience is not required, but it is beneficial for using this strategy.
    
    
   
  •   Zero-Touch, High-Volume Deployment. This strategy requires no interaction during deployment. The process is fully automated through Configuration Manager 2007 R2. We recommend this strategy if your IT organization has experts in deployment, networking, and Configuration Manager 2007 R2 products, and it has a managed network with 500 or more client computers.
    

• Lite-Touch, High-Volume Deployment
• creating a file server for the distribution shared resource.
• . Install MDT 2010 on the file server along with additional components, including the USMT.
• 200–500 client computers and at least one location with more than 25 users.
• Using MDT 2010 for a Lite-Touch deployment requires no more infrastructure than most medium-sized organizations already have (a file server is the only infrastructure requirement).
• answer files, scripts, the Windows Automated Installation Kit
• Microsoft Deployment Toolkit (MDT) 2010
• One of the following:
  
• Media with which to start client computers during deployment
• Microsoft Deployment Workbench Imaging Guide
• distribution share that contains operating systems, applications, device drivers, and updates.
• A server configured with the Windows Deployment Services role
  
• Modifying Task Sequences
• Preparing the Deployment Environment
• Updating a deployment point creates Windows PE images that you use to start client computers during deployment.
• Create a device to start the Windows PE image by preparing a removable storage device with the images created by MDT 2010 when you update a deployment point.
• Optionally, add the Windows PE image to Windows Deployment Services
• Start each client computer by using the Windows PE image
• log on to the distribution shared resource, choose a task sequence, and install Windows.
• Running the Windows Deployment Wizard

18 more annotations...

• Microsoft Deployment Toolkit (MDT) 2010 Update 1
• MDT uses Windows deployment tools for Lite Touch Installation deployments.

• Windows 7 as a virtualization-aware operating system
• streamline your Windows 7 desktop delivery
• Windows 7 Enterprise Edition.
• disk alignment issues
• section 3.3 of the Virtuall (PQR) whitepaper on VDI storage
• http://virtuall.eu/download-document/vdi-storage-deep-impact.

4 more annotations...

• Don't page to disk unless there's extreme memory pressure

• Multiple Activation Key (MAK)
• Activate remote systems using Key Management Service (KMS
• Perform disconnected proxy activation and reactivation of systems without each system having to connect with Microsoft activation services individually.

1 more annotation...

• rform MAK, KMS host, KMS client, and retail activations

• I have Office 2010 clients with legit keys expiring because they can't activate :

• 2. Expand the Computer Config > Policies > Windows Settings > Security Settings > Windows Firewall with Advanced Security > Windows Firewall with Advanced Security > Inbound Rules node.
• Predefined option, and select Windows Management Instrumentation (WMI) from the drop-down list
• (WMI-In) option with the Domain profile value

1 more annotation...

• Article ID: 973289 - Last Review: December 23, 2010 - Revision: 11.0

  How to customize the default local user profile when you prepare an image of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2
• When the default user profile is customized in the manner that is described in this article, it reconstructs the source profile in a format that is appropriate for use by multiple users. This is the only supported method of customizing the default user profile for the Windows operating system. If you try to use other methods to customize the default user profile, it may result in extraneous information being included in this new default user profile. Such extraneous information could lead to serious problems with applications and system stability.
• Note Previously it was possible to copy profiles by using the System Control Panel item. This copy to default profile option is now disabled as it could add data that made the profile unusable.

1 more annotation...

• , we lowered VDI licensing costs by making desktop access rights a Software Assurance (SA) benefit.
• Windows Thin PC (WinTPC), an upcoming SA benefit. WinTPC is a smaller footprint, locked down version of Windows 7, designed to allow customers to repurpose their existing PCs as thin clients.

• *To access the Release Candidate (RC) build of Windows Thin PC, please go to the Microsoft connect site and join the Windows Thin PC RC program. You must be a registered user of Connect to access the program.