My previous articles cycle called the Vista installation described the Windows Vista SP1 Enterprise installation process using Microsoft Deployment Toolkit (MDT) 2008 Update 1, as well as Windows Automated Kit (Windows AIK).one. In this cycle of articles on the installation of Windows 7, we consider the process of installing Windows 7 Enterprise using MDT 2010 and Windows Aik 2.0. Later we will also consider how to use Windows Deployment Services in Windows Server 2008 R2 for various tasks, and after that we will consider how to use MDT 2010 together with Microsoft System Center Configuration Manager 2007 SP2. But we will not run ahead.
In part 24 of my previous cycle of articles on the installation of Vista, we learned about:
- Stories of solutions to the Microsoft installation process
- Differences between Light-Touch Installation (LTI) and Zero-Touch Installation (ZTI) installations
- Four possible installation scenarios: new computer, computer update, computer replacement and computer upgrade
- How to install MDT 2008
- Deployment Workbench
If you forgot about it, you can turn to the previous parts of the cycle. Before continuing.
Improvements in MDT 2010
MDT 2010 is a new version of MDT, and many changes were made to it compared to the previous version of MDT 2008 update 1. Let’s look at some changes.
First of all, now you can install Windows 7 and Windows Server 2008 R2. The previous version of MDT (MDT 2008 Update 1) could not install Windows 7. You need to use MDT 2010 for this purpose. Using MDT 2010, you can install the following Windows operating systems:
- Client OS: Windows 7, Windows Vista SP1 and Windows XP SP3.
- Server OS: Windows Server 2008 R2, Windows Server 2008 and Windows Server 2003 R2.
In MDT 2008 Update 1, it was necessary to create and configure general distribution resources and installation points. You remember that the overall distribution resource was a folder containing the source files of the operating system, such as Windows Vista, which you planned to install using MDT 2008 Update 1. The distribution resource also contained all packages, drivers or applications that you wanted to include in the installation. The installation point, on the other hand, was a folder containing all the files necessary for installing the Vista image along with drivers, packages and applications necessary for installation. A big change in MDT 2010 is that these two things (general distribution resources and installation points) are now combined into one thing called the General Resource of installation (Deployment Share). This change simplifies the process of preparing and using installation infrastructures based on MDT.
Here are some additional improvements in the general installation resource:
- Installation resources can be placed on local disks, in network resources or on separate DFS namespaces
- Several installation resources can be opened simultaneously at Deployment Workbench
- Installation resources can be controlled from any machine on which Deployment Workbench is installed if NTFS and general resolutions are configured for the resource accordingly
- Installation resources can be connected so that when the contents of one resource are updated, the contents of another resource are also updated
Another significant change in this version of MDT is that the internal logic of working with command scenarios was moved from VBScript to Windows PowerShell. In other words, most of the tasks that you perform using Deployment Workbench are actually performed through Windows PowerShell commands. In addition, you can use Windows PowerShell commands directly to perform various configuration and control tasks and automate them; What was difficult to do in the previous version of MDT, since it required difficult work with command scenarios. In other words, everything that you can do using Deployment Workbench can now also be done using Windows PowerShell commands and scripts. Watch this post on Michael Nihaus blog for information about some powerful MDT 2010 capabilities using Windows PowerShell.
Deployment Workbench, integrated into the workspace from which you perform all installation tasks, was also improved in MDT 2010. For example, now you can create a hierarchical tree of folders in each installation resource for a more convenient organization of elements such as OS, devices drivers and tasks of this resource. Plus, you can cut/copy/insert and drag/release the elements in this line of folders. You can also use the choice profiles to manage groups of similar elements (such as devices for a certain type of machine), as one element. All these changes simplify the management of resources and installation tasks.
Finally, there are a number of improvements in the MDT 2010 related to safety, stability and performance. For example, now you can update a computer that is protected using Windows Bitlocker Drive Encryption without the need to decipher and re.encrypt a protected volume. This makes this specific update scenario safer and faster. MDT 2010 has added many more different features and functions. See Michael Nihaus blog, where he published a cycle of articles about new functions and capabilities of this version of MDT.
Performing MDT 2013 Configuration to Deploy Windows 10
We are Ready to MDT 2013 Start Configuring. Launch Deployment Workbench Console, Right Click on Deployment Share and Create New Once (New Deployment Share).
Using Deployment Share Wizard Select Deployment Share Path (C: \ DeploymentShare.
Change the Deployment Share Name Or Leave it as Default (DeploymentShare) and Click on Next.
Tip. CharACTER “” In the Name of Share Means that Network Shared Folder Is Hidden from Network Users.
After the End of the Wizard, Open The Folder C: \ DeploymentShare.
This Directory Stores The Images of Oprating Systems, Drivers, Settings, and Application Packages. This Folder Is Portable and It Cansferred to Other Mdt Server.
Consider The Main Directories in MDT Deployment Share:
- Applications. Application Installation Files are Stored Here (MS Office, Adobe Reader, ETC.) Which Will be Installed on the Deployed System;
- Operating Systems. Operating System Image Files;
- Out-OF-BOX Drivers-Directory with Device Drivers;
- Packages. Update Packages Packs;
- Task Sequences. Task Directory;
- Tools. A Typical Directory with Various Utilities that Can Be Used in the Deploying Process.
Tollow all Network Clents to Connect to the Creed Network Share, You Need in Share Permissions of Folder DeploymentHare, Add Evene Group With Read Accessionsions.
NEXT WEENED To IMPort Image of Windows 10. MDT Allows You to Import System Image from the Windows Source Files, Wim File Or Wds Image.
Expand Branch Deployment Shares Mdt Deployment Share. Right Click on Operating Systems Item and Select Import Operating System.
Select Full Set of Source Files and Choose Drive with Mounted Windows 10 ISO IMAGE.
Wizard Will Copy Windows 10 Source Files to the Folder C: \ DeploymentShare \ Operating Systems \ Windows10prox64.
Now in Operating Systems Section You Will See now the Image of Windows 10 Pro X64.
Creating MDT Deployment Task Sequence
At the next step you must create new Task Sequence, which represents a bunch of instructions needed to be performed when deploying Windows (installation of drivers, applications, system settings, apps updates, run custom scripts etc.).
Right Click on Task Sequences Item and Select New Task Sequence.
Enter Deloywin10x64 for The Task Sequence Id and “Deploy Windows 10 X64” as Task Sequence Name.
Select from the Drop-Down List One of Predefined Sequence Template. This Time We are Choosing Standard Client Task Sequence.
Select OS to Deploy Using this Task Sequence (Windows 10 Pro X64).
Specify Product Key. YOU CAN EITHER SKIP Entering Windows Key Or Specify Gvlk, Mak Or Retail Windows Key.
Specify Local Administrator Password for the Operating System Being Deployed.
Tip. Keep in Mind, That the Password Is Stored AS A Plain Text in the Unattted.XML File.
Open Properties of the Creed Task and Check That is Enabled and Avainable to Run Ony Platforms.
At Task Sequence Tab You Can Sequence of Steps for Deploying Operating System On the Client (Steps Based On the Previousy Selected Sequence Template). This Time We Will Leave it All by The Default.
Next Run Update Deployment Share. MDT Will Generate Boot Images and Configuration for Deploying Operating System.
At first time (Directory C: \ DeploymentShare \ Boot Is Empty) Choose Completely Regeneate the Boot Image and Wait Till the Image Generation Will Be Finishedes.
Adding Device Drivers to the MDT
With MDT, YOU CAN Install Any Device Drivers on Your Computers During the Deployment of a Windows 10 Image. Right-Click The Out-Of-Box Drivers Folder and Select New Folder.
Specify The Folder Name (You CAN CREATE DRIVER Folders by OS Version Or by the Computer Model). The Right-Click on the Creed Folder and Select Import Drivers. In the Window That Appears, Specify The Source Directory, Which Contains The Driver Files (Its Important that Drivers are Needed in Unpacked Form, I.E., In the Form of A Folder in Which.Inf Files Are Located in). Click Next Next Finish.
PerForm Thor Steps for All Devices for Which Windows 10 Cold Not found the Driver (Do Not Forget there ARA 32 and 64-bit DRIVERS For Different Versions of Windows 10).
After the Drivers are Added, It Remains to update the Deployment Share. Drivers Will Be Installed on the Deployed Windows 10 Computer Automatically. There is Nothing Extra to Do Do. The Default Simple PNP ID Drivers Detection Method Is Used.
If a large number of drivers for various devices are added to your MDT server, then in order to speed up the OS deployment, it is advisable to link the hardware drivers to different device models and/or OS versions.
To do this, in mdt 2013 You Need to Use Filtering with Selection Profiles. After Importing the Drivers, You Need to Create A Selection Profile for Each Driver Folder. Then (Advanced Configuration Selection Profiles New Selection Profile Windows 10 X64 and Select the Appropriate Directory with Drivers in Box Drivers Folder).
Add a Custom Task Sequence in the PreinStall Stage to Your Deployment Task Sequence with the Type Inject Drivers.
The in the Task Sequence Settings at the Preinstall Stage, Select the Correct Profile and Enable The Install Matching Drivers from the Selection Profile Option Option.
When Booting Over the Network, The Computer Boots Using the Boot Image Obtained from the Wds Server. If the Image sodaesn’t content Network Card Drivers, The Computer Won’s to Connect to the Wds Server to Select and the Windows 10 Instillation IMage. TheFore, For COME COPUTER MODELS, You Need to Inject An Additional Network Drivers Using The MDT Management Console (to the Litetouchpe_x64.WIM and LITETOUCHPE_X86.wim images).
In Addition, You Can Integrate Drivers Into A Wim Image File or Copy Them Into the Oem Subfolder, and Specify the Path to it in the Autunattten.XML File.
It’s Important to Mental that unattted.XML Answer File Can Be Added to the Wim Image Itself, By Putting it in the %Windir %\ Panther \ Unattend Folder, BUT FOR MDT YOU Will NEED A SEPARETE EXTERNAL TEASIDLE RUNERNENECELE.
Testing Windows 10 Deployment Over Network
We are now ready to test the boot of Network clips from Wds Server Over Lan (PXE Boot). For this test We uce a virtual Machine Running on Vmware Esxi Hypervisor. RUN VM and Press F12 Several Times to Begin Network Boot from PXe.
Tip. Because Boot Screens on VMS Appear Very Quickly, It is Almost Impossible to have Time to Press F12. So we need to set the Highest Priority to Boot Device Network Boot from Intel E1000 in BIOS of VM.
Machine Will Connect to Wds Server and Show You a List of Available Windows PE Boot Media. In Standard Windows Boot Manager Dialog Select Desireed Operating System to Boot From. Select To Boot Lite Touch Windows PE (X86).
The System Will Load Over The Network Wim Image of Winpe Environment and Offer to Begin The Installation of Windows 10 Using Microsoft Tool Wizard.
Click on Run The Deployment Wizard to Install AW Operating System Button to Start The Step by Step Wizard of Windows 10 Image Installation on the Client Computer.
In OUR Example it was Also Necessary to Specify Unc Path to the Network Folder Deployment MDT Server (\\ 10.one.one.170 \ DeploymentShare) and User Crediential to Access IT.
It Remains to Choose Desireed Task Sequence that Your Creed Earlier in Your MDT 2013 (Deploy Windows 10 X64) and Start A Network Deployment OF Windows 10 IMAGE ON THIS.
In this article we show you how to combine MDT 2013 and wds server in order to Create Deployment Infrastructure to Deploy Windows 10 With MDT 2013.
I Enjoy Technology and Developing Websites. SINCE 2012 I’M Running A Few of My Own Websites, and Share Useful Content on Gadgets, PC Administration and Website Promotion.
How to Configure the Task Sequence
You have Create the Task Sequence. But Now You must configure the Task Sequence to Add the Applications that You Want to Install
- IF You Want to Install Another Application Click in Add from the Top Menu.
- Select General and Install Application.
- Click Install Application that Create
- Select Install Single Application. Click Browse and Find Any Application That You Install. Click OK
After Finish with the Task Sequence Go in Deployment Shares with Right Click and Select Update Deployment Share.
Use Offline Image to Deploy Windows 10
In Case that You Don ‘in Yor Environment You Can Configure Image in the MDT (Microsoft Deployment Toolkit) Inter Read the Article Create Assble USTH MDTH MDTH MDTH
With WDS or Offline Image I Can See The Progress of the Installing Application After Finish The Setup of Windows 10
You can Send Me an Email at Info@Askme4Tech.com or do your Комментарии и мнения владельцев and opinions of owners in or
I Invite You to Follow ME OR IF YOU HAVE ANY QUESTIONS, SEND email to me at info@askme4Tech.com.
STEP 3. Deploy Applications Using MDT
When You Configure Your Mdt Deployment Share, You Will Also Add Applications to the New Deployment Share Creating Your Task Sequence. This Secation Walks You Through The Process of Adding An Application to the Mdt Deployment Share Using Microsoft Office 2013.
- On the Deployment Workbench, Deployment Share, Right-Click Applications and Create aw Folder for Microsoft Office 2013.
On the Applications Type Page, Select Application with Source Files The Click Next. Before Doing this Task You Shoup Put the Microsoft Office 2013 to Rom orrt Its to Hyper-V Virtual Machine.
Write the Application Details and Click Next. Try to Fill Out the Application Form with Correct Software Information.
Specify the Source Directory of the Application and Click Next. The Drive D: Is the DVD Drive of Office 2013.
On the Application Destination Page Click Next. Leave it with Default Name Or Changed it with a Related Name to the Application.
On the Command Details Page, Just Type The Exact Setup Name of Application Setup File with Executable Extension and Click Next.
On the Application Summary Page, Read the Details and Click Next to Import Its.
The Importing Process SHOULD Be Done Successfully with Any Error. Run it Issues an error? Try Different Software Or Fix The Problems.
Finally, Click Finish to Close The Page. Now the office has been imported and Windows 10 is Also. SOT NEXT STEP Will Be Creating Task Sequences.
STEP 4. Create a New Task Sequence in MDT
In this space, we Will Explain to You to Create the Task Sequence Used to Deploy Windows 10 Using MDT.
- SO Right Click The Task Sequence and Click New Task Sequence. It is better to Create A Folder for Your Task Sequences.
On the General Settings Page Type the Task Sequence ID, Task Sequence Name and Комментарии и мнения владельцев and Opinions of the Owners of The Click Next.
Select the Standard Client Task Sequence from Template Page and Click Next.
On the Select OS, Page Select the Windows 10 Image and Click Next. This is the windows 10 Image Which Previously We Had Imported from Operating System.
Select Operating System for Task Sequence
Select Do Not Specify a Product Key At this Time on Specify Product Key Page If You Don’t have a Product Key the Click Next.
Type to OS Settings Like Name, Organization and Internet Explorer Default Homepage Url and Click Next.
Enter The Admin Password on the Admin Password Page and Click Next. This password Will BE Ussed Account Password. You can set the Blank Password by Selecting Do Not Specify An Administrator Password at this Time Option. BUT For Security Reason, You Shoup Set a Password for Local Admin.
On the Summary Page, Read The Details and Click Next To Complete the Task Sequence. Finally, Click Finish on the Confirmation Page to Close The Window.
Now EVERYTHING IS DONE and Its Ready To Create Peage by Updating The Deployment Share.
NEXT STEP: Create a Task Sequence
Task Sequence Is Set of Steps What Will the System Look for. The Template to Start with (W10, W11, SRV2019 OR SRV2022 etc). Theen Product Key (If Any), Admin Password etc.
Let’s have a look. You have to Select Template. Pick The Default “Standard Client Task Sequence”.
The Look for Your W11 Files (Here it is, My ISO of W11 WAS Recognized as W10 Partly, But it’s OK).
Next, product key is not mandatory at this moment, but if you have, you’re a Volume License (VL) within your organization, then it allows you to enter it here and you won’t be bothered afterwards.
Do not Specify a Product Key at this Time
NEXT, WE HAVE SOME OS Settings and Default Browser Home Page Settings. Just leave as is for now.
Enter Some Settings ABOUT THIS TASK Sequence
Confirm and Click Finish to Close The Wizard
We can have a look at the properties and we can see each of the Single Steps. Just Double Click the Task Sequence To See. Nice and Clean.
When You Click the Deployment Share, You’ll Get All the Details. By Default, Both Are Checked. You cano uncheck the x86 as you won’s need data films.
The Winpe Tab, If You Prefer To Boot Via ISO You Canerate One. That’s What I DID. I LEFT The Box “Generate a Lite Touch ISO IMAGE” Checked Generated the ISO Right-Clicking The Deployment Share Completely Regeneate the Boot Images.
Your’re Done. The Boot Screen Looks Like This When Starting the Installation of the Windows 11 OS. YOU CAN EASILY BOOT from an USB Stick Which You Can Prepare with Tools Like Rufus, The Finish The Rest of the Installs Via The Network. This avoids you setting up wds and booting over Network.
The You’re Walked Through Several Screens (Ad Join Domain or not, User Date to Restore, Locale etc).
The System Starts The Deployment and All You’ll See is Window Like this.
Microsoft Deployment Toolkit Work in Progress
The Lab Deployment took Just a Couple of Minutes SO it shall be similar in a work deployment.
The Installer Finishes Installing the Windows 11 OS
Vsan from Starwind is Software-Defined Storage (SDS) Solution Creed with Restricted Budgets and Maximum Output in Mind. It Pulls Close to 100% of IPS from Existing Hardware, Ensures High Uptime and Fault Tolence Starting with Just Nodes. Starwind VSAN IS Hypervisor and Hardware Agnostic, Allowing You To ForGet Hardware Restricts and Crazy Expensave Physical Shared Storage.
Build Your Infrastructure with Off-The-Sheelf Hardware, Scale Howver You Like, Increase Return (ROI) and Enjoy Enterprise Virtualization Features A!
This Has Been Quite Difficult to find out that Winpe Add on Break and Does Not Allow Me to Continue (I’m not the only one). The Workaround I Found Working Is That You Must Get the Win 10 Adk Pe Add-on-on Instead.
The Things Sometimes Works and Sometimes Not. One must always look for Solutions Online, But All I Can Say Is That The Deployment Via Microsoft Deployment Toolkit (MDT) NOT OFTOPS, BUT AlSO SERVER OS, CAN BE DONE. The Advantage is That From One Central Location You Manage All the Necessary Patches and Updates When It Come To Deploying Orinstalling OS Whathin Your Organization or.
Instaad of Carrying Around USBS with Up-to-Date ISOS, YOU TONED THEED FOR BOOTING THE SOLUTION, The REST of the Installation Is Carried on Across the Lan Lan.
The Microsoft Deployment Toolkit is a Unified Collection of Tools, Processes, and Guidance for Automating Desktop and Server Deployment. In Addition to Reducing Deployment Time and Standardizing Desktop and Server Images, MDT ENABESY YOU to MORE EASILY Manage Security and ONGOVING Configurations. MDT builds on top of the core deployment tools in the Windows Assessment and Deployment Kit (Windows ADK) with additional guidance and features designed to reduce the complexity and time required for deployment in an enterprise environment. MDT Supports The Deployment of Windows 10, As Well as Windows 7, Windows 8, Windows 8.1, and Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, Windows Server 2016. IT ALSO Includes Support for Zero-Touch Installation (ZTI) WITH Microsoft System Center 2016 Configuration Manager.
For this demo, I Will Be Using My New Dedicated MDT and WDS Windows Server 2016 (WDS-SERVER).
There are A Few Things We Need to Prepare Before We Deep Dive Into the Process.
- Download Windows Assessment and Deployment Kit (Windows Adk) For Windows 10
- Download Microsoft Deployment Toolkit (MDT)
- Windows Deployment Services (Windows Server Role, Used to Boot and Deploy Operating Systems Image Through The Network)
- Windows 10 Distribution (ISO Image Or Installation DISC). Windows 10 Source Files
Once You Prepared All the Necessary Component, Let’s Get Started
1-On the WDS-SERVER, Install Windows 10 Adk
On the Windows Kits Privacy Click Next
On the License Agreement, Proced with Next
On the Select the Features You Want to Install, Click
- Deployment Tools
- Windows PreinStallation Environment (Windows PE)
- User state migration tool (USMT)
And The Click Install (It Might Take a While for the Features to Download)
Wait for the Download Installation Process to Complete
Once The Process Complete, Click Close
Next Weeed to Install Microsoft Deployment Toolkit, On the Wizard Click Next
Accept The License Agreement and Click Next
On the Custom Setup, Click Next
On the Customer Experience Improvement Program Interface, Click Next
Once The Process Completed, Click Finish
Start Menu Open Deployment Workbench
14-Deployment Workbench Console Right-Click Deployment Shares Folder and the Click New Deployment Share
On the Path Interface, Verify the location of the Deployment Share (by Default it Will to C: \ Deploymentsshare), The Click Next
On the Share Interface, Verify the Name of the Share (by Default the Name Is DeploymentShare), The Click Next
On the Descriptive Name Interface, Proced with Next
On the Options Interface, Please Untick All the Box and then Next
On the Summary Interface, Verify All the Information and then Click Next
On the Confirmation Interface, Click Finish
On the Deployment Workbench Console, Right Click Operating System Folder and the Click Import Operating System
Make Sure You Attach Windows 10 Distribution (ISO Image Or Installation Disc) Before Proceding with Next STEP
First of all, you need to create a directory where all images and installation files will be stored. To do this, click on the mouse at the Deployment Shares item and select the New Deployment Share item. A window will appear where you will need to make some settings. First we indicate the path to the Directory (I indicated D: DeploymentShare), click NEXT and indicate what to name the general resource (deploymentShare. I remind you that the sign at the end of the name means that the folder will not be visible when viewing the general resources of the server. This is useful, t.to. In fact, ordinary users do not need access. Click Next, enter the description (MDT Deployment Share), click Next, remove the box in the next window and then click Next everywhere. If you look into the created folder, you can see that many other folders were created there. You can also see them if you open on the left to the menu item Deployment Share. MDT Deployment Share:
Applications. applications that will be placed on the installed system (MS Office, Adobe Reader and T.D. if necessary) Operating Systems-the operating systems of theout-off-box Drivers-drivestask sequences-these are the tasks (for example, the installation of Win 7, may consist of the installation of the system itself, then installing all the necessary drivers and updates and installation of MS OFFICE- This is all one task) Advanced Configuration. more detailed settings
Creation of the first task
Let’s try to create the first task that (in my case) will set the Microsoft Windows XP system on the old Dell Optiplex 320, put the missing drivers, software and update the system.
Add the operating system
Click the mouse button on Operating Systems and select the Import Operating System. In the window that appears, select the Full Set of Source Files item (these are files and folders from the XP installation disk), press NEXT and indicate this folder (or disk), NEXT, indicate how to name this OS (I have Windows XP Professional SP3), Next, Next, Next Next, Finish 🙂 That’s it, after these actions we will have this operating system in the Operating Systems list.
Add the drivers
It often happens that after installing the system there is not enough some other driver. It’s good when they are available through Windows Update. But it happens that there are not even network drivers. How I solve this issue in MDT. In Out-OF-BOX Drivers, I create folders with computer models (Dell Optiplex 320, Dell Optiplex 755 and T.D.), and then in these folders I load the missing drivers.
It is important to remember such a thing. drivers are needed in a unpacked form, t.e. The folder in which.Inf files.
Consider an example for Dell Optiplex 320. Click the right mouse button on Out-OF-BOX Drivers and select the New Folder item. Enter the name of the folder and all. Next, click on the created folder and select the Import Drivers item. In the window that appears, we indicate the folder that contains drivers for, say, video cards. Click Next, Next, Finish. We make this action for all devices for which the drivers were not found.
All. Drivers are added. They will be put in the system automatically. Nothing additional for this should be done.
There are several options for installing software. I choose a method with MSI and EXE files. I will show now how it is done. Click the Applications mouse with the right mouse button and select the New Application. Click Next. We fill out the table (for example Adobe Reader 10.2, downloaded from Adobe): Publisher: (Optional): Adobeapplication Name: Readersion: (Optional): 10.2language: (Optional): Englishzhme Next and indicate the directory with EXE file. You must first create a folder and place a installation file there there. Next. Here it is necessary to indicate with what parameters the file installation will be launched. For MSI files, this is usually the MSIEXEC /I command.MSI /Quiet “. And for EXE files you need to look. In our example with Adobe, the flags will be as follows: “File.exe /msi eula_accept = Yes /Qn »click Next. Next. Finish.
We create a task
Click on the Task Sequences with the right mouse button and select the New Task Sequence item. In the window that appears, you need to enter the ID tasks (well, for example, 001), the name of the task (Dell Optiplex 320. Windows XP) and, if desired, Комментарии и мнения владельцев on the task. Next. Choosing the type of assignment for our purposes Suitable Standard Client Task Sequence. Next. Choose OS. Next. Indicate the key for XP (or do not indicate). Next. We indicate who to register a copy of the XP and a page that will be opened in IE by default. Next. We set the administrator password. Next. Next. Finish. Everything, the task was created.
Creating WIM-image Windows 10 with installed software using Microsoft Deployment Toolkit and deploying the image over the network
Hello, dear readers of the site Remontcompa.Ru. My name is a novel of a wrap, and I present to your attention an article in which we will consider the process of creating a WIM-image of the Windows 10 1809 operating system with installed software. And for this we will use the Microsoft Deployment Toolkit (MDT) version 8456. The created WIM-image will further be deployed into the computer’s hard drive on the network of Windows deployment services (WDS). To work, we will need a computer with the Windows 10 operating system and the programs installed in it. Let’s start.
First of all, it is necessary to prepare the Windows 10 operating system using the Sysprep utility. We cross the path:
And start the SYSPREP file.EXE. In the window that opens, select “Transition to the System Greetings Window”, put the “Preparation for use” checkbox, select “Completion of work”. And click “OK”.
We expect the completion of the SYSPREP utility work. The preparation of the Windows 10 operating system is completed.
Next, start the Deployment Workbench and move on to Task Sequences. Create a new folder by selecting in the context menu “New Folder”.
Indicate the name of the created folder (in our case, it is “Capture Windows 10”) and click “NEXT”.
We highlight the “Capture Windows 10” folder and select “New Task Sequence” in the context menu.
Indicate the ID and the name of the created task sequence. Click “Next”.
From the drop.down list, select the Sysprep and Capture template.
Indicate the operating system, in our case it is Windows 10 Pro (x64).
Indicate the name of the owner of the system and the name of the organization.
Indicate the password of the built.in accounting administrator.
The sequence of tasks “Capture Windows 10” has been successfully created. Click “Finish”.
And here is our created sequence of tasks “Capture Windows 10”.
We highlight the created sequence of tasks and select “Properties”.
Winpe environment setting up and updating the deployment resource
It is at the stage of updating the deployment resource that the real work of MDT begins. When updating the deployment resource, MDT, along with other actions, creates two configurated Winpe environments. But before updating the deployment resource, which can take quite a lot of time, consider the settings and components that can be changed by controlling the creation and contents of the Winpe media.
Winpe settings are located in the section of the deployment resource in the DW equipment. To change the properties of the deployment resource, open the Deployment Shares assembly, click on the deployment resource and select Properties. In the Properties window, we see six tabs: General, Rules, Windows PE X86 Settings, Windows PE X86 Components, Windows Pe X64 Settings and Windows Pe X64 Components. As shown on the screen 3, on the General tab, there are fields for describing, Комментарии и мнения владельцев, UNC paths, local paths and supported platforms. The values in all these fields can be changed, but two are recommended to be left: Network (UNC) Path and Local Path. If you need to open another deployment resource, you can click the Deployment Shares Knot in the DW equipment and select Open Deployment Share, and then go to the deployment resource that needs to be opened.
|Screen 3. General tab of the Properties dialog box of deployment resource|
By default, the General tab shows supported platforms X86 and X64. The choice of the platform determines which Winpe media will be created, and on what other tabs it is necessary to configure the parameters. Winpe customizable parameters are on Windows PE X86 Settings and Windows PE X64 settings tabs. And the components that can be added to Winpe environment are on the Windows PE X86 Components and Windows PE X64 Components tabs. Two settings tabs are similar as two components tabs. If both platforms are selected on the General tab, 32- and 64-bit files will be formed. wim and. ISO.
The 4 Windows PE X86 Settings tab is shown on the 4th screen, on which you can give the ISO file created by the MDT when updating the deployment resource, select the background image (if you do not like the picture of Solution Accelerators) and set the temporary data storage in RAM during deployment.
|Screen 4. Windows PE X86 Settings tab The Properties Detail Resource Window Window Window|
On the Components tab, you can choose drivers and packages introduced into Winpe. MDT components (drivers and packages) can be grouped according to signs called the profiles of choice. The steps of creating a choice profile are described in the article mentioned above the article “Creation of a medium for deploying Windows 7”. Specify the profile of the choice in the Driver Injection Field or use the default profile, All Drivers and Packages. By assigning a choice profile, you can turn on all the drivers from the specified profile or only certain types of drivers. There are four types of drivers: a network, a general repository, video and SystemClass. The only expansion package that can be added (and selected by default) is Ado support for the MDT database. Description of the MDT database goes beyond this article; It will be considered in the following articles. You can also add fonts for Winpe, in particular Chinese, Japanese and Korean.
Rules tabs settings determine the behavior of the deployment wizard, for example, which pages are displayed during the deployment process and how the master receives information if this page is not displayed. Table 2 shows the parameters that will act in case of acceptance of default settings when creating a deployment resource. Also on the Rules tab, in the left right corner, is the Edit Bootstrap button.ini. By clicking on it, you can see the root catalog of the deployment server, to which target customers will connect to deploy the operating system.
|table 2. Standard settings for the rules on the general deployment resource|
After the platform is selected and the parameters and components are configured, it is necessary to update the deployment resource to create new Winpe Winpe MDT tools. In the DW equipment, expand the Deployment Shares node. Click the deployment resource with the right mouse button and select the Update Deployment Share item to launch the master Update Deployment Share Wizard. Perform the following actions in the master.
On the Options page, install the Optimize The Boot Image Updating Process. You could choose the Completly Regenerate The Boot Images mode; With the first update of the deployment resource, the selected option does not matter, the result will be the same.
On the Summary page, see the designated parameters and make the necessary changes, and then press the NEXT button. On the confirmation page, click Finish to complete the work of the master.
After the first renewal of the deployment resource, new Winpe environments will be obtained in the \ DeploymentShare \ Boot folder. These Winpe environments are not displayed in DW equipment; Find them using Windows conductor. At the next updates of the deployment resource inside the DW equipment, the parameters assigned to the Update Deployment Share Wizard are more significant. Install the Optimize The Boot Image Updating Process, if you need to change the existing Winpe environments. If the Winpe environment is damaged and you need to create a new one, select the Completly Regenerate The Boot Images option.
Deployment of the operating system on the client computer
Now you can deploy the first Windows 7 operating system on the target computer. Make sure the target computer is connected to the network and has access to MDT deployment resource. Download the target computer using one of the Winpe (Litetouchpe_x86, prepared using MDT media.ISO or LITETOUCHPE_X64.ISO) that must be written to disk or saved on an external hard drive or USB flash drive. Perform these actions in an automatically launched Windows deployment master.
The Welcome Windows Deployment page provides three options: Operating System, Run The Windows Recovery Wizard and Exit to Command Prompt. There is also the Configure with Static IP Address button. Before proceeding to deployment, we will consider how the IP address receives the target computer. By default, the target computer is a DHCP client, so it needs to assign an IP address, subnet mask and parameters configured in a DHCP server. If the DHCP server is unavailable, you need to set a static IP information by pressing the configure with static IP Address button. To confirm the statically assigned IP information, press the F8 button, opening the command line, and view the settings using the IPConfig command; Do not use Exit to Command Prompt, as this command completes the deployment. The choice of the option Run The Windows Recovery Wizard launches a special Winpe environment that searches for all the files necessary to download the target computer after deploying the operating system; In this case, all spoiled and missing files are replaced. Select Run The Deployment Wizard to Install a New Operating System to start the process of deploying the image on the target computer.
On the User Credentials page, indicate the user name, password and domain for accounting, which will provide permits for deployment resource, and then click Ok.
The previously created sequence of tasks, Windows 7 Bare Metal Installation, is displayed on the Select a Task Sequence to Execute on this Computer. If the sequence of tasks is not on the list, make sure that the correct Winpe platform is loaded. In the 32-bit Winpe environment, only 32-bit sequences of tasks are displayed, and in the 64-bit Winpe only 64-bit sequences of tasks will be shown. Select a sequence of tasks and press the Next button.
On the Configure the Computer Name page, enter the name of the target computer, and then click Next.
On the Join The Computer to a Domain Or WorkGroup page, you can attach the target computer to the working group or domain. To join the domain, the domain data with the right to attach new computers to the domain is necessary. In this example, the computer will join the working group. Press the NEXT button.
On the SPECIFY COMPENSIA to the Restore User Data page, you can restore user data and settings, in particular the “Favorite” folders of the IE browser, the Outlook folders from the existing computer if user data and settings are already collected and saved on the server. To restore this information, select Specify A Location and enter the UNC path to the storage site. After Windows 7 is installed, the settings and user data will be copied to the target computer. I chose Do Not Restore User Data and Settings. Press the NEXT button.
On the Language and Other Preferences page, select the tongue, time, monetary unit and layout of the keyboard from the opening list, and then click Next.
Select a time zone on the Set the Time Zone page, then click Next button.
If applications have been added to the DW equipment, then the next will be the Select One Applications to Install. Select from the list of the application that you need to install. If there were no applications to the DW equipment, then the page is not displayed. Press the NEXT button.
On the Specify Capture An Image page, you can form the image of the target computer after the successful completion of deployment. In the Prepare to Capture the Machine mode, the files necessary for starting Sysprep on the computer are copied, but Sysprep is not launched and the image of the target computer is not formed. Select the DO not Capture An Image of this Computer option, and then press the Next button.
On the Specify The Bitlocker Configuration page, you can activate Bitlocker on the target computer and indicate the place of storage of the BitLocker encryption key. Take the default value, do not enable bitlocker for this Computer, then click the Next button.
Finally, the Ready to Begin page is displayed. Press the Details button and view the selected parameters. If you need to make changes, click the blue arrow indicating back in the lower left corner to return to the corresponding page; If everything is in order, press the Begin button. The installation stages will be displayed on the Installation Progress indicator. Warning: If the Installation Progress indicator freezes, move it to the side to see errors. Error messages during deployment are sometimes hidden under the Installation Progress indicator. As shown on the screen 5, under the Installation Progress indicator, the Installing Windows page is displayed for convenient tracking the deployment process.
|Screen 5. Installing Windows page and Installation Progress indicator during installation|
The described steps will help expand Windows 7 along with applications, drivers and packages. carefully, without unnecessary trouble and expenses, except for some time spent.
Ronda Leafield (Rhonda@Deploymentdr.com). consultant, teacher and specialist in product deployment. Has a Setup and Deployment MVP certificate
The problem is required to expand the operating system along with applications, drivers and packages on a computer connected to the company’s network. The decision to use the Microsoft Deployment Toolkit (MDT) 2010 tools to prepare a deployed and easy to manage the image. Necessary resources of MDT 2010, deployment resource prepared as described in the article “From XP to Windows 7 Migration using MDT 2010”. Stages of solution 1. Import the operating system in MDT 2010. 2. Create folders to organize DW. 3. Add MDT components. four. Create a sequence of MDT tasks. 5. Configure Winpe and update the deployment resource. 6. Expand the operating system on the client. Complexity level 3 out of 5