Acrobat, Reader, Adobe Reader, Enterprise Administration, Acrobat Products, registry, plist, deployment, configuration, wizard, GPO, AIP, Citrix, AppV. Philip Flint Blog Archive Install and Configure MDT 2. Part 2In Part 1 of this series we walked through installing and configuring MDT 2. In this part Ill show you how to globally automate the deployment. In terms of automation there are two types of automation, global automation settings that are applied by default to all machines and then those that are directed at individual machines. Firstly I will explain and demonstrate the global settings and then I will run through how to centrally apply individual settings to different makes and model of machines. If we right click our deployment share we can access the configuration settings properties used for that share. Under the rules tab we can access two sets of settings, customesettings. Bootstrap. ini the settings accessed by clicking the button. These settings are held on the hard drive in the deployment share. Boot. Strap. ini is used at boot time to provide basic configuration to the machine and allow it to connect to the deployment share. Because of this, changes to bootstrap. Win. PE image by updating the deployment share whenever changes are made to bootstrap. Once the machine is booted custom. Settings. ini takes over and controls the rest of the deployment process typically automating entries in the MDT GUI to drive the deployment. Lets deal with bootstrap. If we click on the button above to open the ini file we see that, by default, its settings look like the below The Settings section is read in first and the process then follows the value in the priority field. Here it loads up the section Default which only has one value, the location of the deployment share to read data from. In Part 1 of this series we walked through installing and configuring MDT 2013 for the first time. In this part Ill show you how to globally automate the deployment. Integrate UDI with your SCCM task sequence for optional software deployments and other cool features. The latest version of System Center Custom Updates Publisher 2011 is released and ready for download. SCUP 2011 is a freeware tool from Microsoft that can assist you. The other day I had an issue at a customer, where the installations of new computers ran without any errors, but once logging in, it was obvious that everything was. Complete Technical Acronyms, Glossary Definitions for PC, SAN, NAS, QA, Testing, HDTV, Wireless, Linux, Embedded, Networks, Video, Digital, pharma, Unix, Video. By default, all installations will use the same deployment share in this location. We can add additional item to bootstrap. The typical values we may want to add are User. IDAdministrator. User. DomainExample. User. PasswordPaw. Keyboard. Localeen GBSkip. BDDWelcomeYESI have highlighted the values to be changed in RED. A word of caution though, the username and password are held in plain text in the boot. If you were to use your domain administrator account in a production environment users could possibly have access to this high privilege level account Instead, I prefer to create a new account and grant access to that account to that share at the NTFS levek. I also remove the account from the Domain Users group and add it to a No Access group. This prevents the account being used to access information shared to domain users. It does not prevent it being used to access data shared to everyone or authenticated users though so the amount of protection this strategy supplies will depend on your internal environment. For those shares, access can be denied to the No Access group securing the environment once more. He account is granted read access to the share and the built in users group removed. In this way admins still have access to the share but standard users do not and so the likelihood of someone seeing any user names or passwords in the customsettings. Applying these settings, my boostrap. Sccm 2007 And Microsoft Deployment Toolkit Setup And Configuration' title='Sccm 2007 And Microsoft Deployment Toolkit Setup And Configuration' />Once the boorstrap. Win. PE boot. iso and. Angry Birds Star Wars Repackaging. DVD USB sticks or to WDS as needed. That is, we run the Update Deployment Share as below and once that is completed after 1. Sccm 2007 And Microsoft Deployment Toolkit Setup And Configuration' title='Sccm 2007 And Microsoft Deployment Toolkit Setup And Configuration' />D Deployment. ShareBoot location to wherever we will be using them to boot our endpoints. Once the boot. ini file has been updated, we can re test out deployment and ensure that the keyboard set to be used is the correct language in my case, British English and that we are not asked for a user name and password to connect to the deployment share. If you prefer you can leave out the line that passes the Password through. In that case anyone accessing the setup screen will not be able to reuse your image without first entering the password. However, if you would like remote users to self service their rebuilds then this would mean you would need to tell them the password so its a little bit of swings and roundabouts and how you configure this will, to an extent, depend on your circumstances. Assuming that the test passes, you can now move on to customizing your customsettings. By default, the customsettings. The Information Center provides detailed information on which settings can be applied to the customsettings. This information can be found by clicking on the Planning MDT Deployments link. This will open a PDF file and under the Toolkit Reference Properties Providing Properties for Skipped Deployment Wizard Pages node you will find listed the values you need to enter into customsettings. Accessing the Properties Definition item 1 level up allows you to get a fuller explanation of each property together with examples of how to configure it. So, for example, If we want to automatically select the Task Sequence name to be run and just build 2. R2 servers we enter the two lines below. Skiptask. SequenceYes. Task. Sequence. IDWIN2k. R2 0. 01. To automate the complete process you may want to consider using the settings below as well as setting the pre set items to Yes Skip. Computer. NameYESSkip. Domain. MembershipYESSkip. User. DataYESSkip. CaptureYESDo. CaptureNOSkip. Locale. SelectionYESSkip. Task. SequenceNOSkip. Time. ZoneYESSkip. ApplicationsYESSkip. SummaryYESTime. Zone0. Time. Zone. NameGMT Standard Time. The Time Zone values for all regions are listed at http msdn. The above settings will allow you to select a task sequence to be run but will assign a random name to the computer and, unless your task sequence adds the computer to the domain, will add the computer to a workgroup. If you want to pre set any of the values you add the corresponding entry from the right hand column of the above table and assign a value to it as demonstrated by the task sequence example above. A completed basic customsettings. Booting using our boot media now results in a single screen asking us which task sequence we would like to run. The only thing is, configuring MDT as above means that ALL of your deployments must be identical other than the contents of the task sequence. Now, this may or may not be OK. For example, if we want to use MDT to refresh workstations and laptops as well as build new servers it could be that, when we are booting to a client machine we want to preserver or be asked to preserve user data whereas if we are booting to a server machine then we will not want to be given this option. This can be achieved by detecting gathering information about the endpoint at boot time and then applying different settings based on characteristics of the endpoint. Luckily, this isnt as different as it may sound. When the boot process runs, MDT runs a gather script named ZTIGather. This script is located in the Scripts folder of the deployment share meaning we can run it ourselves against an existing client and inspect the output of the script quite easily. We can then use those discovered values to drive our deployment proves using customsettings. If we run the script it creates a folder called MININT in the root of the operating system drive. Drilling down inside that folder we eventually get to the ZTIGather. This can be opened in notepad or you can download the SCCM 2. System Center Configuration Manager 2. Toolkit V2 from http www. This will allow you to install the Trace. Common Tools only. An example of the type of information gathered is displayed below.