none
How to deploy Operating system using MDT RRS feed

  • Question

  • I have created, MDT server, with Operating system , drivers, application etc,

    Now, how would I deploy this particular Operating system on machine in network?

    What else I require?

    how does WinPE file get created for deploying and get linked to this MDT?

    I have checked on step by step guide, some video's but none of them explaining in details , about first step, where to get WINPE file from, which can deploy my OS from MDT?

    I have refer below links, but not helping

    http://systemscenter.ru/mdt2012.en/creaandimpothedeplworkwindpeimag.htm

    Can anyone help with step by step from scrach?


    P Dave

    Thursday, February 14, 2013 7:35 PM

Answers

  • MDT can be a little daunting if you are new to it, but it can also be a surprisingly powerful system for automated (or very near automated) system and application deployment. to make the best possible use of MDT you should use the MDT database to store records about your computers, make/models, roles, and network locations. really it all comes down to how big the environment is and how much money you want to spend on the deployment infrastructure. in a smaller business MDT alone is fine, but in a larger business you may want to use it with SCCM.

    to use MDT you generally (off the top of my head) follow these steps:

    • install MDT and create your distribution share
    • populate the operating system, applications and drivers folders
    • configure customsettings.ini and/or database records so computers can be targeted with the correct operating systems, drivers and applications
    • configure a task sequence which will install the OS and applications
    • update the deployment share which will generate the WinPE file, the WinPE file contains the correct data about finding the deployment share in your environment and pulling down the bits to install, coupled with a correctly configured customsettings.ini file and a bootstrap.ini file
    • you need to boot from that WinPE file which you can either do from a USB stick, DVD, or my favourite is from the network using Windows Deployment Services (you import the WinPE image into WDS)
    • boot the appropriate client, and you should find a fairly automated deployment experience

    MDT is so powerful for a free product I have managed to make it do the following in my environment

    • I have not had to make a capture of a preconfigured OS with applications, my deployment can run more dynamically by adding applications during deployment time - this largely depends on the frequency of OS deployments and the network bandwidth you have and the level of customisation you require, my environment is fairly straight forwards in this regard
    • a client boots to the WDS, pulls down the Win PE image and installs the correct OS, drivers and applications because I populated the database records with roles, location, computer and make/model records - every machine in my environment knows exactly what it should receive - all completely hands off
    • I have even gone as far as making MDT deploy software separately from the OS deployment, weeks or even months after the original deployment took place, this allows me to eliminate most of the need for group policy software installation or a product like SCCM to deploy applications
    • all of this is completely hands off with the exception of pressing F12 at the client to boot from the network, there is no further manual input at all required!

    perform a search for my posts in the MDT forum, you may find answers to many of questions you may also have. It's thanks to the expertise of many others in these forums I have managed to make a rather cool automated deployment solution. you might also want to investigate the use of ADK to allow you to deploy Windows 8, it also provides you with tools for performance testing, application compatibility, and volume license activation and monitoring.

    http://social.technet.microsoft.com/Search/en-US/Technet?query=steve%20mills&rq=meta:Search.MSForums.ForumID(d950aa1b-0da4-4ee4-831b-a4b23267f394)+site:microsoft.com&rn=Microsoft+Deployment+Toolkit+Forum

    http://www.microsoft.com/en-gb/download/details.aspx?id=30652

    feel free to ask me anything further if you want to know more. hope this has helped you. unfortunately I can't help you with using SCCM alongside MDT as this is a bit beyond my current level of experience, but if your environment is small enough SCCM might be overkill anyway.

    Steve


    • Edited by Milkientia Thursday, February 21, 2013 1:17 PM
    • Marked as answer by Soh.M Thursday, October 3, 2013 5:41 AM
    Thursday, February 21, 2013 1:13 PM

All replies

  • aare you planning to use SCCM to deploy ?

    Guowen Su
    Cisco Certified Network Associate
    Cisco Certified Internetwork professional - MPLS
    Certified Information Systems Security Professional
    Microsoft Partner Network 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator:Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Certified Ethical Hacker
    Computer Hacking Forensics Investigator
    Certified Sonicwall Security Administrator
    Microsoft Geeks

    Thursday, February 21, 2013 6:16 AM
  • MDT can be a little daunting if you are new to it, but it can also be a surprisingly powerful system for automated (or very near automated) system and application deployment. to make the best possible use of MDT you should use the MDT database to store records about your computers, make/models, roles, and network locations. really it all comes down to how big the environment is and how much money you want to spend on the deployment infrastructure. in a smaller business MDT alone is fine, but in a larger business you may want to use it with SCCM.

    to use MDT you generally (off the top of my head) follow these steps:

    • install MDT and create your distribution share
    • populate the operating system, applications and drivers folders
    • configure customsettings.ini and/or database records so computers can be targeted with the correct operating systems, drivers and applications
    • configure a task sequence which will install the OS and applications
    • update the deployment share which will generate the WinPE file, the WinPE file contains the correct data about finding the deployment share in your environment and pulling down the bits to install, coupled with a correctly configured customsettings.ini file and a bootstrap.ini file
    • you need to boot from that WinPE file which you can either do from a USB stick, DVD, or my favourite is from the network using Windows Deployment Services (you import the WinPE image into WDS)
    • boot the appropriate client, and you should find a fairly automated deployment experience

    MDT is so powerful for a free product I have managed to make it do the following in my environment

    • I have not had to make a capture of a preconfigured OS with applications, my deployment can run more dynamically by adding applications during deployment time - this largely depends on the frequency of OS deployments and the network bandwidth you have and the level of customisation you require, my environment is fairly straight forwards in this regard
    • a client boots to the WDS, pulls down the Win PE image and installs the correct OS, drivers and applications because I populated the database records with roles, location, computer and make/model records - every machine in my environment knows exactly what it should receive - all completely hands off
    • I have even gone as far as making MDT deploy software separately from the OS deployment, weeks or even months after the original deployment took place, this allows me to eliminate most of the need for group policy software installation or a product like SCCM to deploy applications
    • all of this is completely hands off with the exception of pressing F12 at the client to boot from the network, there is no further manual input at all required!

    perform a search for my posts in the MDT forum, you may find answers to many of questions you may also have. It's thanks to the expertise of many others in these forums I have managed to make a rather cool automated deployment solution. you might also want to investigate the use of ADK to allow you to deploy Windows 8, it also provides you with tools for performance testing, application compatibility, and volume license activation and monitoring.

    http://social.technet.microsoft.com/Search/en-US/Technet?query=steve%20mills&rq=meta:Search.MSForums.ForumID(d950aa1b-0da4-4ee4-831b-a4b23267f394)+site:microsoft.com&rn=Microsoft+Deployment+Toolkit+Forum

    http://www.microsoft.com/en-gb/download/details.aspx?id=30652

    feel free to ask me anything further if you want to know more. hope this has helped you. unfortunately I can't help you with using SCCM alongside MDT as this is a bit beyond my current level of experience, but if your environment is small enough SCCM might be overkill anyway.

    Steve


    • Edited by Milkientia Thursday, February 21, 2013 1:17 PM
    • Marked as answer by Soh.M Thursday, October 3, 2013 5:41 AM
    Thursday, February 21, 2013 1:13 PM
  • Hello steve

    Could you please explain after installing OS using MDT whether we need to join the systems into Domain or any custom settings to join the PC in domain in the installing time itself.

    Waiting for your response.

    Regards

    Raj karthick.V

    Wednesday, July 9, 2014 10:41 AM
  • You do not have to join the client machine to the domain if you dont want to. the best way to control MDT settings is by configuring a database, I would suggest using a location record to blanket cover the settings you require across every deployment, in here you would enter the settings to join the domain, or create a role record for example "domain computers" and add the settings in there, then associate the role record with a computer or model record.

    if your not using a database then edit the customsettings.ini file to include domain join settings. for example the lines to join domain in customsettings.ini would be 

    JoinDomain=mytestdomain.LOCAL
    DomainAdmin=administrator
    DomainAdminDomain=mytestdomain
    DomainAdminPassword=password

    if you are doing a small deployment (handful of PC's) then use the customsettings.ini file, if you are doing a medium sized deployment (say around 30-40 PC's and above use a database, you have more control over the deployment

    if your doing a larger deployment say around 100 or more, you should look at integrating MDT with system center configuration manager, you will possibly find the MDT database a bit too complicated to manage as the deployment size grows.

    hope this helps

    Wednesday, July 9, 2014 11:19 AM