Installing and Configuring Microsoft Deployment Toolkit MDT 2. Windows Server 2. R2. Last week I gave a presentation at the local Citrix Users Group in Santa Clara on Microsoft Deployment Toolkit MDT 2. Windows Server 2. R2.   During the session, I had a 2. I went through the basic installation and configuration of MDT 2. Introduction. There is presently a potential issue in setting language settings using unattend. Windows 10 1703 Enterprise x64. One drawback of the User State Migration Tool USMT is that it needs to run locally on the source and destination machines to migrate user state data. Luckily. o deploy this application using the Application method as used by Configuration Manager 2012, please see my StepbyStep Howto in this blog post. Microsoft Deployment Toolkit 2012 Documentation Library Documentation Home. Whats New in Microsoft Deployment Toolkit. Introduction to Whats New in MDT. Best Practices to Capture an Image for Deployment Alexandr May 15, 2015. Thanks for your article Nice information for deployment specialistsThis topic outlines the general process that you should follow to migrate files and settings. Plan Your Migration. Depending on whether your migration scenario is. Windows Server 2. R2. I enjoyed presenting the demo so much that I have decided to capture it into a blog post to help those new to the Microsoft Deployment Toolkit  If you want a quick overview and primer on MDT, go check out my presentation and previous blog post here Bay Area Citrix Users Group October 2. Presentation Microsoft Deployment Toolkit MDT 2. Primer In this post we are going to be covering slides 1. Lets get started  For this demo, I will be using two systems, the first is my MDT 2. Windows Server 2. R2. The second is my MDT clienttarget, to which I will be deploying Windows Server 2. R2 from a volume license ISO. On the MDT server, I will start by downloading the Microsoft Assessment and Deployment Kit ADK for Windows 8. Click Download Click Run I would always recommend downloading the ADK to a local folder or network share, since these files take a while to download and are commonly used in many Microsoft products, including System Center. Select a local or network path and click Next Click Next Accept the license agreement After many minutes or even hours, the 3. GB files will finish downloading. When complete, re launch the ADK setup wizard by executing adksetup. Yes, only two steps Now that Windows 10 is available, I want to demonstrate how easy it is to deploy using System Center Configuration Manager. The User State Migration Tool USMT is a Microsoft command line utility program intended to allow advanced users, comfortable with Scripting languages, to transfer. Displays several methods to get TPM enabled on Toughbook laptops and tablets. It also discussing best practices for enabling BitLocker and storing the Recovery. Portals/0/Images/blog%20images/7-10image1.PNG' alt='Usmt Example Xml Files' title='Usmt Example Xml Files' />If the installation files are detected, the installer will simply prompt for an installation directory. Click Next Click Next Accept the license agreement Uncheck all features except Deployment Tools, Windows Preinstallation Environment Windows PE, and User State Migration Tool USMT. These are the only features required for the MDT Server. Click Install After a couple minutes, the installation will finish. Click Close Next, well download the MDT 2. Click Download Select all files and click Next Click Save for each file, putting the files in an MDT folder Once each of the five files have been downloaded, launch Microsoft. Deployment. Toolkit. Click Next Accept the license agreement and click Next Click Next Click Next Click Install Click Finish On Windows Server 2. R2, click the Start menu As with many newly installed applications, youll find the app shortcuts are a bit buried in Windows Server 2. R2 until you get used to it. From the Start interface, click the Down arrow in the bottom left for all programs A new Microsoft Deployment Toolkit section is created. Launch the Deployment WorkbenchNew The first time launched, youll see a nice overview of MDT 2. Right click Deployment Shares in the left navigation and select New Deployment Share Change the deployment share path or leave defaults and click Next Change the deployment share name or leave defaults and click Next Change the deployment share description or leave defaults and click Next Review and uncheck each of the default options and click Next Review and click Next Click Finish Open Computer Management. Expand Local Users and Groups and right click Users to select New User A local user account with rights to the MDT share will be very beneficial for deployments. Create a local user, set password never expires, and enter a password that can be safely stored in plain text without much risk not a super secretive password By default the deployment share is created with Everyone Full Control permissions. To review, find the deployment folder, right click and go to the Sharing tab. Click Advanced Sharing Click Permissions Note Everyone is added by default with Full Control security is controlled by NTFS permissions on the folder On the Security tab of the share, note that Users have Read Execute, List Folder Contents, and Read NTFS permissions. This is perfect for our newly created MDT user to access the share during deployments Back in the Deployment Workbench, right click the new deployment share and select Properties Under the Rules section, drop the following block of options at the end of the Default section Skip. Computer. NameYESSkip. Domain. MembershipYESSkip. User. DataYESSkip. CaptureYESDo. CaptureNOSkip. Locale. SelectionYESSkip. Task. SequenceNOSkip. Time. ZoneYESSkip. ApplicationsYESSkip. SummaryYESSkip. BDDWelcomeYESTime. Zone0. 04. Time. Zone. NamePacific Standard Time. After youre fairly experienced with MDT, you can read up and review all of the Custom. Settings. ini options in various documentation articles and blogs online. Once each option has been added, click Edit Bootstrap. Under the Default section, drop the following block of options User. IDMDTUser. DomainWS1. R2. MDT0. 1User. PasswordPssw. Keyboard. Localeen USSkip. BDDWelcomeYESClose the Notepad document and you will be prompted to save changes Click Save Click Apply to save changes to Custom. Settings. ini for the deployment share Click OK Next, well import the Operating System images WIM for Windows Server 2. R2. To do this, I will very handily double click to Mount the volume license ISO The next drive letter available for my MDT server was E so the installation media is now mounted using that drive In the Deployment Workbench, right click Operating System and select Import Operating System Select Full set of source files and click Next Type E to use the recently mounted ISO. Click Next Enter a destination directory name I typically just clean up the default name that was detected. Click Next Click Next Upon completion typically a couple minutes click Finish Typically, I do some cleanup since I wont need most of the WIM files imported. For now, Ill delete the three WIM files and leave Server Datacenter. To do so, select each file, right click and select Delete Ill select Completely delete and click Next Click Next Click Finish Next, Ill rename to clean up the WIM file name to Windows Server 2. R2 Datacenter. wim Right click Task Sequence and select New Task Sequence Enter DEPLOY WS2. R2 for the Task sequence ID and a name to be selected using the deployment wizard, Deploy Windows Server 2. R2 for example. Click Next Select Standard Server Task Sequence from the drop down and click Next Select the Operating System from the list and click Next Your choice to enter a product key, or do this later. Click Next Enter a name, organization, and home page. Click Next Enter a password that you dont mind having stored in plain text as this is kept within the Unattend. The administrator password can always be changed post deployment. Click Next Click Next Click Finish Next, well modify the task sequence to enable Windows Updates. Right click the new task sequence and select Properties Under the State Restore section, there are two entries for Windows Update which are both disabled by default. Highlight each of these tasks and click the Options tab Uncheck Disable this step to enable the step. Repeat for the second Windows Update entry Uncheck Disable this step and both tasks should now be enabled. This will come in hand later when we start slipping in applications to the task sequence. Step By Step How To Migrate users and user Data from XP, Vista, Windows 7 or 8 TO Windows 1. Using Microsoft Tool USMT User State Migration Toolkit. Windows Assessment and Deployment Kit ADK for Windows 1. Windows 1. 0.   What you collect with USMT Scan. State is customizable through modifying the XML configuration files. For more information on the defaults, see What Does USMT Migrate  The USMT tools can be used to migrate data from a 3. The User State Migration Tool USMT Technical Reference can be found at https technet. Migrating data from your old computer source to your new computer destination is basically a four step process which includes Step 1 Download and Install USMT tools. Step 2 Gather Backup data using the USMT Scan. State tool Step 3 Install Windows 1. Unpack New computer with OS already loaded Step 4 Apply Restore data using the USMT Load. State tool. What you will need Access to this step by step guide Access to Internet to download tools from Microsoft. Network or USB drive to store USMT tools tiny, about 7. Network or USB drive to store Backup data and settings very large, big enough for all user dataAccess to the Source Machine the one you will be migrating FROM BackupAccess to the Destination Machine the one you will be migrating TO Restore n this post, I will dive into these Steps breaking it down to a click by click guide. Before we get started, I will give a bit more detail about what USMT is and does. The User State Migration Tool USMT 1. IT engineer can automate and precisely define migrations using the USMT. In this blog post we will not be modifying any of the configuration files. You do not need to make any changes for a default migration. USMT provides the following sample scripts that can be easily modified for customization if needed Mig. App. XML. Rules to migrate application settings. Mig. Docs. XML. Rules that use the Mig. Xml. Helper. Generate. Doc. Patterns helper function, which can be used to automatically find user documents on a computer without the need to author extensive custom migration. Mig. User. XML. Rules to migrate user profiles and user data. Psp 6.31 Cfw. Mig. User. xml gathers everything in a users profile and then does a file extension based search of most of the system for other user data. If data doesnt match either of these criteria, the data wont be migrated. For the most part, this file describes a core migration. The following data does not migrate with Mig. User. xml Files outside the user profile that dont match one of the file extensions in Mig. User. xml. Access control lists ACLs for folders outside the user profile. To migrate ACLs, you must specify the directory to migrate in the Mig. User. xml file. Using file patterns like The source ACL information is migrated only when you explicitly specify the directory. For example, lt pattern typeFile c test docslt pattern. Step 1 Download and Install USMT tools You can download the Windows Assessment and Deployment Kit ADK for Windows 1. Link. Id5. 26. 74. Learn more about whats in the Windows ADK for Windows 1. Launch adksetup. exe to install tools onto your administrative workstation or your source computer. This is an automated downloader and installer. It only has the install bits, not all the bits for the tools,  the tool will download the bits needed during installation. Click Next a couple times, Accept the license agreement. Select the options you want to install or just keep the defaults to install USMT click Install. We will not be using all of the tools so you can turn everything off except USMT for the purposes of copying data off of a machine. If you install PE or other components, they will need to be downloaded so it can take quite some time hour depending on Internet connection for the large download. Notice you will need elevated privileges. If you Add the ACT, you will need to have SQL server also which can be installed if you do not already have it. You should be able to view the files using. Program Files x. Windows Kits. Assessment and Deployment Kit. User State Migration Toolx. If you want to scancopybackup files on a different computer user computer instead of your administrative workstation you will need to copy the USMT tools to a thumb drive or network share so you can run the tool from the source computer. Where F is your Network drive or USB drive egxcopy c Program Files x. Windows Kits. 10. Assessment and Deployment Kit. User State Migration Toolx. F USMTx. 86xcopy c Program Files x. Windows Kits. 10. Assessment and Deployment Kit. User State Migration Toolamd. F USMTx. 64. You are now ready to proceed to the scanstate to backup the from the source computer. Step 2 Gather Backup data using the USMT Scan. State tool Now that you have the tools saved to a USB thumb drive or Network Share, you can run the USMT Scan. State Tool in an elevated command prompt from the location saved the files to in Step 1 above x. F USMTx. 86x. 64 F USMTx. Note You should run USMT from an account with administrative credentials. Otherwise, some data will not migrate. When running the Scan. State and Load. State tools you must run the tools in Administrator mode from an account with administrative credentials. If you do not run USMT in Administrator mode, only the user profile that is logged on will be included in the migration. In addition, you must run the Scan. State tool on Windows XP from an account with administrative credentials. Otherwise, some operating system settings will not migrate. To run in Administrator mode, click Start, click All Programs, click Accessories, right click Command Prompt, and then click Run as administrator. From the Windows XP, Vista, Windows 7, or Windows 8 machine SOURCE Login to source computer as administrator, Attach USB drives or connect network drives for USMT files and for destination for files and settings backup. Assumptions for this post is the USMT tools drive is F and the USMTData drive is G Note that the Destination Drive should allow for very large files eg. NFTS instead of FAT. The. MIG file that is created with all the user data in it can be massive depending on the amount of data being backed up. Run elevated Command Prompt click Start then type Command then Right Click on Command icon and select Run as Administrator. Note Understanding the switches we need to run scanstate to package our files and settings. You will need to run Scan. State F USMTx. 64 is the location on your source computer where you have saved the USMT files and tools. G USMTData. Dan. Stolts is the full path to a folder on a network server or USB drive where you can create the migration store. Overwrite  c Continue on non fatal errors i miguser. Read in this user configuration file i migdocs. Read in this documents configuration file Default configuration files come with the USMT. Stor. Path  By default the log will be created in the defaultcurrent folder. For more information about what is excluded when you specify localonly, see Scan. State Syntax. NOTE I strongly suggest you look at the syntax and in particular the auto and the genconfig. NOTE Note, once the. MIG file is created, you can manually extract individual files using the usmtutils command https technet.