This is how to easily install ADK and MDT in Windows Server 2016 for Windows Deployment. The current version of Microsoft Deployment Toolkit is MDT 2013 update 1. MDT is a solution accelerator for operating system and application deployment. MDT supports the deployment of client operating systems and server operating systems. In this post, we are going to show you how to install and configure MDT and ADK for Windows 10 in Windows Server 2016 which works the same as Windows Server 2012 R2.

The methods of installation and configuration of all Microsoft Deployment Tool kits are the same. So don’t worry, just download the MDT required components ADK for Windows 10 or for older Windows and start installing.

You might need to read for Windows deployment Services:

1. How to install Windows Deployment Service WDS In Windows Server 2012 R2?
2. Configure Windows Deployment Services on Server 2012 R2
3. Deploying Windows 10 Using WDS Server 2012 R2

Download and Install ADK and MDT

The first kit we need to download is the Windows ADK for Windows 10. The second one is the latest update of the Microsoft deployment tool kit. Download the Microsoft deployment tool kit update 1 files from the Microsoft website. Always try to download the latest version of MDT.

In our practicing lab, we are using MDT 2013 update 1 which supports Windows 10 and Windows Server Server 2016. You can download Windows ADK for Windows 10 with two methods. Download and Install at the same time or download all components in a separate Windows and move it to Windows Server. So I have selected the second one. First, download all Windows ADK for Windows 10 and now try to install it.

1. Let’s download all components of Windows ADK for Windows 10 and then install it.

• • Download the Windows ADK for Windows 10 and run the setup.

2. Select the Download the Windows Assessment and Deployment Kit – Windows 10 for installation on a separate computer and Browns to specify the path then click Next.

3. It’s a test lab so select No and click Next. On the license terms and agreement page click Accept to accept the Windows Kits privacy.

4. It is almost 3 and a half GB in size. When the download is complete successfully, move or copy files to Windows Server 2016 then run the adksetup file to install it.

5. Specify a location or click Next to select the default location. Then on the Windows Kits privacy page select No and on the license terms and agreement page Accept.

6. Now select the features you want to install. Don’t select unnecessary features. Click Next to install it.

7. It will take a few minutes to complete. When it is finished, close the page.

Now the Windows ADK for Windows 10 is installed successfully in Windows Server 2016. The next step is to install the Microsoft Deployment tool kit.

How to Download and Install MDT?

So the installation of Windows ADK for Windows 10 has finished successfully. Now try to download and install Microsoft Deployment tool kit update 1.

• Microsoft Deployment Toolkit (MDT) 2013 Update 1 and run the setup.

1. Run the downloaded Microsoft deployment tool kit setup file and click Next.

2. Select I accept the terms in the license agreement and click Next.

3. Click Next and do nothing on this page because we need tools and documents.

4. For testing lab select I don’t want to join the program at this time and click Next.

5. Click Install to start the installation. Let the installation will be finished. Finally, click Finish to close the page.

Yes, that’s it. The Microsoft deployment tool kit was also installed successfully. If you are faced with some errors or problems during the installation, try to search for the title on Google or comment to us through this post.

6. Now go to Windows Server 2016 start menu and run the Deployment Workbench.

Here is the Windows deployment Workbench. It is ready for Windows Deployment and Application Deployment.

Now the Microsoft Deployment Toolkit is ready for configuration and deploying new operating systems and Applications.

It’s time to configure the MDT and start deploying Windows 10 with MDT. Continue the article about deploying Windows 10 using MDT in Windows Server 2016. So that’s all you need to install ADK and MDT for your Windows Deployment Server in Windows Server 2016.

The post How to Install ADK and MDT in Windows Server 2016? appeared first on TECHNIG.

Windows PowerShell has cmdlets that help you manage files with PowerShell easily within Servers and client machines. The following PowerShell articles provide a brief introduction to carrying out file system management tasks by using Windows PowerShell. These tasks include such things as creating, renaming, copying, verifying, and deleting files and folders with PowerShell.

Manage Files with PowerShell

As Sysadmin you already should know the basics of PowerShell command-line structure. Here I’m trying to manage files using PowerShell with some File management cmdlets. So follow the PowerShell articles to learn more.

#1. Listing Files and Folders with PowerShell

The old dir command would list the files and folders contained within the specified directory within command prompt (cmd.exe). PowerShell has “Get-ChildItem“ cmdlet.

1. Open PowerShell on your Windows system. It’s better to run it as an administrator when you manage files and folders with PowerShell. Type “Get-ChildItem” to display the current directory files and folders.

The “ls” command will list your files also, so the topic focuses on PowerShell File management cmdlets. Basically the Get-ChildItem works like dir command.

That’s not all, you can do more with Get-ChildItem such as “Get-ChildItem -Recurse” command. It will show all folders, sub-folders and files inside the folders.

You might want a list of all the files and folders in the sub-folders. Just simply add the -recurse parameter at the end like an above command. Read more about Get-ChildItem. It’s pretty good for sysadmins to do manage files with PowerShell.

#2. Creating Folders with PowerShell

The New-Item cmdlet will create a file or folder in a directory. You can specify the directory rather than the current directory you are located.

1. To create a folder, simply type “New-Item” folder name. For instance, I have created a folder named helpline.  The full command “New-Item helpline -ItemType directory“.

You must assign the item type in order to create a folder or and exact file type. The “-ItemType directory” is used for creating a folder with PowerShell.

#3. Create Files with PowerShell

Just like creating a folder, you can simply use -Type file” option to create a file. Do not forget to mention the file type or extension as well. Let’s create a text file on the helpline folder using PowerShell.

1. Type New-Item filename.extension. For example, to create a text file withing helpline folder. Type “NewItem c:\NetworkFiles\helpline\Helpme.txt -ItemType file“.

Yes, the file has been created successfully and you can check it with get-child item command. So good, let add some data or text to new file. The value parameter will help you add data to your files.

To add data to a text file, type “NewItem c:\NetworkFiles\helpline\Helpme.txt -ItemType file -Force -Value “Hello Jungle!”.

It will add the Hello Jungle word inside the helpme.txt file. The –Force parameter will replace the current file if it already exists.

#4. Rename Files with PowerShell

If type the files or folders wrong, the Rename-Item can be used to rename the files. Try to use and rename some files and folders.

1. Let’s rename a file, the Helpme.txt to Readme.txt. Type “Rename-Item c:\NetworkFiles\helpline\Helpme.txt Readme.txt” then press enter.

It will change the file without any prompt. So try to run the ls command to list the files inside the directory to see the changes.

#5. Move File and Folders with PowerShell

Related to manage files with PowerShell, like another command, moving files with PowerShell is also easy. The task will be accomplished with the Move-Item command.

1. Let’s move the Readme.txt folder from helpline folder to the Sales folder. Type “Move-Item c:\NetworkFiles\helpline\Readme.txt c:\NetworkFiles\Sales\” then press enter.

It will move the file without any prompt. So try to run the ls command again to see the files inside the Sales folder. The -Force parameter will overwrite the existing files.

#6. Delete Files and Folders with PowerShell

Deleting files and folder will be done with Remove-Item. It’s the main command to delete files or folder with PowerShell. Let’s delete the Readme.txt file and Helpline folder.

1. To delete the Readme.txt file, type “Remove-Item Readme.txt” and press enter. It will delete the file.

To delete a folder type “Remove-Item FolderName” and press enter. It will delete only the folder that doesn’t have any sub-folders. If you want to delete a folder with sub-folder or everything inside a folder, type “Remove-Item FolderName -Recurse” then press enter.

Yes, everything deleted successfully. The Remove-Item cmdlet also has many useful parameters that help you manage files with PowerShell better. Read more on Remove-Item.

#7. Verify the Existence of a File or Folder with PowerShell

Is my files or folder exist on the shared folder? Yep, this command will help you to verify the existence of files and folders with PowerShell.

1. To verify the existence of a folder, type “Test-Path c:\NetworkFiles\Sales” and press enter. Previously we have deleted the Sales folder and the result must be False.

Yes, the Sales folder does not exist on NetworkFiles but the Products folder already exist. Let’s verify whether do we have any text files on the products folder. Type “Test-Path c:\NetworkFiles\Products\*.txt” and press enter.

Yes, the result is True, it means we have text files on Products folder. It will verify the Windows Registry keys as well. For instance “Test-Path HKCU:\Software\Microsoft\Windows\CurrentVersion” and press enter.

That’s are not all but enough for managing files and folders with PowerShell on Windows servers and Clients operating system.

Hope you have got something new about managing files and folders with PowerShell. If you have any questions, feel free to ask and comment us your helpful suggestions and feedback.

The post How to Manage Files and Folders with PowerShell? appeared first on TECHNIG.

This article “configure DHCP failover on Windows Server” is apply-able on Windows server 2012 and higher for DHCP High Availability. The DHCP server failover feature provides the ability to have two DHCP servers provide IP addresses and option configuration to the same subnet or scope, providing for continuous availability of DHCP service to clients. The two DHCP servers replicate lease information between them, allowing one server to assume responsibility for servicing of clients for the entire subnet when the other server is unavailable. It is also possible to configure failover in a load-balancing configuration with client requests distributed between the two servers in a failover relationship.

The DHCP failover in Windows Server enables administrators to deploy a highly resilient DHCP service to support a large enterprise without the challenges of the options discussed earlier. The main goals of the feature are the following:

• Provide DHCP service availability at all times on the enterprise network.
• If a DHCP server is no longer reachable, the DHCP client is able to extend the lease on its current IP address by contacting another DHCP server on the enterprise network.

Read the Understand and Deploy DHCP Failover article on Microsoft technet.

Configure DHCP Failover on Windows Server?

You need to have two DHCP servers to configure DHCP failover on Windows Server. Install DHCP on both servers and don’t create scope on the second one. Just create a scope on the primary DHCP server.

1. On Windows server type “dhcpmgmt.msc” on Run and press enter to open DHCP Manager.
2. On the DHCP console right click the DHCP and click Add Server. Select the second DHCP server and add it to current DHCP console.

3. To configure DHCP Failover on Windows Server, right click on IPv4 of primary DHCP and select Configure Failover. On the welcome page of Configure Failover select Select all and click Next.

4. Add the second DHCP server and click Next.

5. On the Create a new failover relationship page, select Load balance mode and type a password then click Next.

6. Finally click Finish to set up failover between two servers. Make sure the process should be finished successfully. Close the page and to to see the changes on DHCP management console.

7. Once refresh the DHCP console or reconnect the server to see the final result. Now the DHCP servers are ready to work as DHCP load balancing service and your clients never fail to obtain IP address.

That is all about DHCP High Available or configure DHCP Failover on Windows Server 2016. The same configuration works on Windows Server 2012 also.

The post How to Configure DHCP Failover on Windows Server 2016? appeared first on TECHNIG.

The NIC Teaming feature is now the builtin feature to Configure NIC Teaming in Windows Servers. NIC Teaming is provide network availability and network performance. It act as a bonding network adapters to form one logical network adapter. It provides useful features such as load balancing across individual links and failover for network connections.

NIC Teaming Features and Modes

Currently Windows Server support two modes of NIC Teaming configurations. The firs once is Switch dependent mode and the second one is Switch independent mode.

Switch dependent mode is connecting all network adapters to the same switch. It requires to configure on the physical switch with Generic teaming mode and LACP for Dynamic mode. These two Generic 802.3ad and Dynamic 802.1ax are the features of Switch dependent mode.

Switch Independent mode is connecting network adapters to different switches and configuration is not required on physical switches.

Configure NIC Teaming in Windows Server

In this article I’m going to configure NIC Teaming in Windows Server 2016 using a Hyper-v lab. All network adapters are logical and just created for testing the functionality of NIC teaming in Windows Server 2016.

To configure NIC Teaming, at least you need to have two Network adapters. Before configuring NIC teaming, create some virtual network card for your virtual hyper-v servers.

1. On Windows server open Server Manager and select Local Server. It shows all network adapters with their IP configurations. The screenshot shows the network adapters configured with static IP address.

2. Just click Disabled in front of NIC Teaming to open NIC Teaming configuration window.

3. From TEAMS section click TASKS and select New Team to create and new NIC Team from existing network adapters.

4. Select the adapters you want to team with each others and type a name. Then select the appropriate settings from Additional properties. and click OK to create the first NIC team.

5. Finally you see the created NIC Teams on TEAMS section of NIC Teaming window. If you want to change the settings of NIC Teams, select and right click a NIC team then select Properties.

Yes, you have successfully created and configured NIC Teaming in Windows Server. To see the NIC Teaming is enabled, once refresh the Server Manager then see the result.

6. Now, once check the Network Connections to see the NIC Teams connections created after NIC Teaming configuration.

That’s all. Hope you clearly understand to configure NIC teaming in Windows Server. In case of any issue related to NIC Teaming, comment us please.

Configure NIC Teaming – Video Tutorial

The post How to Configure NIC Teaming in Windows Server 2016? appeared first on TECHNIG.

This article is going to explain the process of install and configure DirectAccess VPN in Windows Server 2016. In Windows Server 2016 and Windows Server 2012, you can deploy both DirectAccess and Routing and Remote Access Service (RRAS) on the same server. These allowing you to provide DirectAccess connectivity to supported clients as well as providing VPN access to remote clients that do not support.

The clients which support DirectAccess are Windows 10 Enterprise, 10 Enterprise 2015 Long Term Servicing Branch (LTSB), Windows 8 Enterprise, Windows 7 Ultimate and Windows 7 Enterprise.

Install and Configure DirectAccess VPN

I’m going to install DirectAccess-VPN with PowerShell command. You can install it from server manager dashboard using GUI. As a system administrator, improving your command line skill is necessary.

1. From your Windows Server open Windows PowerShell and type “Get-WindowsFeature RemoteAccess” then press enter. It shows the Remote Access is status. Also to see the DirectAccess, type DirectAccess-VPN.

2. Now, for installing DirectAccess-VPN, type the “Install-WindowsFeature DirectAccess-VPN -IncludeManagementTools” command and press enter.

Note: This command will install Remote Access Management and Routing and Remote Access. In order to configure a traditional VPN server, you should configure with Routing and Remote Access. But to configure DirectAccess VPN server, you need to configure it through Remote Access Management.

3. Type “ramgmtui” on Windows run and open the Remote Access Management to configure DirectAccess VPN Server.

4. On Remote Access Management console, click Run Getting Stared Wizard. This wizard will configure DirecetAccess and VPN server quickly.

5. On Configure Remote Access page, click Deploy both DirectAccess and VPN (recommended). This option will configure DirectAccess VPN server. This will allow remote client computers that not supported for DirectAccecss to connect over VPN.

The second option will only deploy DirectAccess, and the third option will configure a traditional VPN server with Routing and Remote Access.

6. On the Remote Access Server Setup page, select Behind an edge device (with a single network adapter) and type IP address used by client to connect to the remote access server, then click Next.

7. Now click Finish to apply remote access settings. If you want to bring changes or review the configuration settings of GPO settings, Remote clients settings, Remote Access Server settings and Infrastructure Server, click on Click here link to open the Remote Access Review page.

8. Finally the configuration of DirectAccess VPN will be completed successfully.

Try to navigate Remote Access Management console, to see more settings and find out he new features you need to understand. See the VPN section relevant to this article.

8. On Remote Access Management Console, click Open RRAS Management under VPN.  Select the ports on Routing and Remote Access to see the active and inactive VPN connections.

That’s all bout configure DirectAccess VPN in Windows Server 2016. This configuration works for Server 2012 R2 also. So don’t worry, just configure on Server 2012.

How to Test DirectAccess-VPN?

To test the DirectAccess-VPN whether it’s work or not. Create a VPN connection on a client machine and connect to DirectAccess. From Windows 7 and newest version support DirectAccess. But the older versions are non supported DirectAccess devices.

The post How to Configure DirectAccess VPN on Server 2016? appeared first on TECHNIG.

Dynamic host configuration protocol (DHCP) is providing IP addresses to network client workstations and server machines. The DHCP High Available role acts as load sharing and fault tolerance. So in this article we explain and configure DHCP high available to an step by step manner guide.

Before applying DCHP high available role in your production environment, once test it in a testing lab. For configuring dhcp high availability you need two Windows Server and a client for testing. I have a DC server installed Active directory, DNS Server, and DHCP Server. My second server is only DHCP installed.

The DHCP Failover Architecture

The two features of DHCP role for high availability are Hot Standby, and Load Sharing. In hot standby mode the primary server is responsible for providing IP addresses to clients and the secondary server is watching the primary server failure . When the primary DHCP server failed or not servicing properly, the secondary server start works to provide IP address instead of primary server.

If you are new with DHCP server, I recommend you to read the following article about DHCP Server.

1. Install and configure DHCP role in Windows Server 2012 R2
2. How to Configure DHCP in Cisco Routers?

I assume you know the basics of Dynamic Host Configuration Protocol.

Configure DHCP High Available

Now let’s start to configure DHCP high available in Windows Server 2012 R2 or Windows Server 2016. Both works the same.

1. Login to DC server and type “dhcpmgmt.msc” in Windows run to open the DHCP management console.

2. Add the second DHCP server to this primary DHCP management console. In order to do this right click the DHCP and select Add Server. Now select the secondary DHCP server from the list or browse and type the name of server you want to add it. Then click OK to add the second server.

Here is the result, the two servers are now have a Central access.

3. To configure DHCP high available, right click on IPv4 on primary server and click Configure Failover. On the Configure Failover page read the introduction to DCHP failover then click Next.

4. Click Add Server and select the server form list. or simply specify the partner server to use for failover then click Next.

5. On the Create a new failover relationship page, select Load balance mode and type a password then click Next.

6. Finally click Finish to set up failover between two servers. Make sure the process should be finished successfully. Close the page and to to see the changes on DHCP management console.

7. Once refresh the DHCP console or reconnect the server to see the final result. Now the DHCP servers are ready to work as DHCP load balancing service and your clients never fail to obtain IP address.

It is the easiest way using DHP high availability in Windows Servers 2012 and Windows Server 2016. I hope it has been informative for you and appreciate you to comment us the DHCP relevant problems.

The post How to Configure DHCP High Available in Server 2012 R2 appeared first on TECHNIG.

In a Enterprise network, directly upgrading the network operating systems are difficult task. But upgrade to Windows 10 using MDT is the easiest way to upgrade the old machines. As network admin you already know the importance of OS and application deployment rules in a enterprise network. And also must be familiar with Microsoft Deployment Toolkit, Windows Deployment Services and deployment operations.

In this practice lab I will show you how to upgrade to Windows 10 using MDT and refresh old machines with new operating system. You need to be familiar with MDT installation and creating deployment share with MDT. If you are beginner and don’t know the basic of deploying Windows with MDT and WDS, I recommend you to read the below article before continuing this post.

1. How to install MDT and ADK in Windows Server 2016?
2. How to Deploy Windows 10 using MDT?

Try to create your own test lab and continue this article. In the final stage I had faced with an error, hope it will not issue that for you.

Step 1: Import Windows 10 full source to MDT

Adding Windows 10 full sources to MDT will be done through MDT Deployment Workbench. I already have my deployment lab which installed and configured MDT as deployment Server in a Windows Server 2016. So go to open deployment workbench and import Windows 10 and create an upgrade task sequence.

1. Open Deployment Workbench from start menu in your MDT machine. Create a folder for Windows 10 on Operating system section.

2. Simply right click Windows 10 folder and select Import Operating System to open the OS Type page.

3. On the OS Type page select Full set of source files and go to the next page.

4. Put the Windows 10 disc to DVD ROM or mount the Windows 10 Image and select the directory drive then click Next.

5. On the Summary page read details and click Next to start importing Windows 10. Finally on Confirmation page click Finish to close the page and the Windows 10 should be ready.

Step 2: Create an Upgrade Task Sequence in MDT

On the Task Sequence section of Deployment workbench, create a folder relevant to upgrade to Windows 10 using MDT.

1. Right click the Task Sequence and create a folder, so do right click the folder and select New Task Sequence. Now on the General Settings page fill out the task id, name and comments then click Next.

2. Select the Standard Client Upgrade Task Sequence for task sequence template then click Next.

3. Select the previously imported Windows 10 as operating system and click Next.

4. Select the first option Do not specify a product key at this time for now on the Specify Product Key page and click Next.

5. Enter the Full name, Organization and Internet Explorer Home Page correctly on OS Settings page then go to next page.

6. If you like the local Admin account with a password, enter the password, otherwise select Do not specify and Administrator at this time on the Admin Password page and go to Summary page.

 7. On the Summary page read the detail and click Next to being creating the upgrade task sequence. Finally on the Confirmation page of Task Sequence close the page.

8. Now expand the Upgrade Windows 10 folder and right click the created task sequence then click Properties. See the options on the Task Sequence tab that everything is okay.

Close Task Sequence properties and go to update the MDT deployment share.

Step 3: Update the Upgrade MDT Deployment Share

The final step before performing upgrade to Windows 10 using MDT, try to update the MDT deployment share.

1. Right click MDT Deployment Share and click Update Deployment share then select Optimize the boot image updating process and click Next. 

2. Read the Summary details and click Next to begin updating MDT Deployment share. Finally the update should be done successfully.

Close the page and go to begin Windows upgrading from Windows 7 or 8 to Windows 10.

Step 4: Upgrade to Windows 10 Using MDT

Lets begin with a Windows 8.1 to upgrade to Windows 10 using MDT in our lab. I hope you could perform all above steps successfully.

1. Login to your old machine such as Windows 7 or Windows 8. Then run the Lite Touch script form Windows run like the screenshot. Click Yes to run the script.

The Lite Touch script is a vb script that load the Windows Deployment Wizard from deployment server, where the MDT is installed.

2. When the Lite Touch script will load, select the upgrade task sequence and click Next.

3. Specify a product key if you have, otherwise select No product key is required then click Next. In a production environment you can activate your machine from KMS Server.

4. Do you need to install or update applications also? If you don’t click Next and go to the next page. You can install or updated the applications from this section also. But I don’t want to update or install any software to testing lab.

5. Specify a strong password for Administrator for security reason then click Next.

6. Type the appropriate deployment share domain account for connecting to network share then click Next. I’m using the domain admin user for this lab.

7. On the Ready to begin page, read the details and click Begin to start upgrade to Windows 10 using MDT form a network shared.

8. Let the Windows deployment perform the upgrading from Windows 8 to Windows 10 successfully.

When the upgrade complete, the system will restart and finalizing the upgrade process. So don’t push it to restart or shutting down while installing new OS.

Ops! I don’t know why installation progress page disappeared? OK… Let me troubleshoot this error and find the problem. Try to your lab and share the result. I hope it work perfectly for you on your production environment.

The post How do Upgrade to Windows 10 Using MDT? appeared first on TECHNIG.

This is the second part of Microsoft deployment toolkit article to deploy Windows 10 using MDT. To simply understand the tasks in this article, you need to read the first part “How to Install ADK and MDT in Windows Server 2016?“. Also as a network admin, you should already know about Microsoft Deployment toolkits and Windows deployment. So I assume you have read the first part of deploy Windows 10 using MDT which talk about installing ADK and MDT in Windows Server 2016.

For this Windows deployment lab, I’m using Hyper-v, Windows Server 2016, and Windows 10 to deploy Windows 10 using MDT. The MDT is installed on Windows Server beside Active directory and DHCP Server. You can install MDT separately on a Windows client or Server.

Step 1. Create a New MDT Deployment Share

I know you are ready after reading and doing the tasks of the first part, and now continue the step by step guide to MDT. When you are ready to deploy Windows 10 using MDT  in a testing lab or production environment, you will first create a new MDT deployment share. Let’s do it step by step.

1. Open the Deployment Workbench from Microsoft deployment toolkit in Windows server 2016 start menu. Then right-click Deployment Share and click New Deployment share.

2. Select the deployment share path, where you want to keep operating system files, applications, drivers and scripts then click Next.

Don’t store the MDT deployment share files in system drive in a production environment.

3. For the Share, page specifies a short and meaningful share name to access it easily and quickly through the network then click Next. I have named DepShare. The complete UNC path is \\DC16\Depshare$.

4. On the Descriptive Name page, leave the default MDT Deployment Share or rename it to whatever you want and click Next.

5. On the Options page, select the customize-able options when performing deployment and click Next.

6. Read the Summary page and click Next to create the new deployment share.

7. Finally, the progress should be done without errors. Otherwise, you need to troubleshoot the errors. Click Finish on the Confirmation page to close the page.

The New Deployment share has been created successfully. Now try to add Windows images to deploy Windows 10 using MDT.

Step 2. Import Operating System to MDT

the second step is importing operating system to MDT. Put Windows 10 disc to DVD Rom or mount the Windows 10 Image within Hyper-v virtual machine.

1. Open MDT Deployment Workbench and expend MDT Deployment Share. Now right click on Operating system and create a New Folder. Specify a name and click Next then click Finish to create the new Windows 10 folder.

2. Now right click the Windows 10 folder and click Import Operating System.

3. Select a Full set of sources files on OS Type page and click Next. You can select a customized Windows image or connect to Windows Deployment Services images also.

4. Select the DVD drive and click Next. You can select Windows files from a folder and easily move it with selecting the Move option. So anyway…

5. On the Destination page, type a name for the directory where MDT create it for Windows files. When you specified a name click Next.

6. On the Summary page read the details and click Next. It will take a few minutes to import the Windows 10 files to Operating System folder of MDT.

7. On the Confirmation page, the Windows 10 should be imported without any errors. If you have faced with any error try to troubleshoot it by searching google or comment us the error titles.

Click Finish to close the page and go to step 3, add some application to MDT.

Step 3. Deploy Applications using MDT

When you configure your MDT deployment share, you will also add any applications to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the MDT deployment share using Microsoft Office 2013.

1. On the Deployment Workbench, Deployment Share, right-click Applications and create a New Folder for Microsoft Office 2013.

2. On the Applications Type page, select Application with source files then click Next. Before doing this task you should put the Microsoft Office 2013 to DVD Rom or insert it to Hyper-v virtual machine.

3. Write the application details and click Next. Try to fill out the application form with correct software information.

4. Specify the source directory of the application and click Next. The drive D: is the DVD drive of Office 2013.

5. On the application Destination page click Next. Leave it with default name or changed it with a related name to the application.

6. On the Command Details page, just type the exact setup name of application setup file with executable extension and click Next.

7. On the application Summary page, read the details and click Next to import it.

8. The importing process should be done successfully with any error. If 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. So the next step will be creating Task sequences.

Step 4. Create a New Task Sequence in MDT

In this section, we will explain to you how to create the task sequence used to deploy Windows 10 using MDT.

1. So right click the Task Sequence and click New Task Sequence. It is better to create a folder for your task sequences.

2. On the General Settings page type the task sequence id, task sequence name and comments then click Next.

3. Select the Standard Client Task Sequence from Template page and click Next.

4. 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.

5. Select Do not specify a product key at this time on Specify Product Key page if you don’t have a product key then click Next.

6. Type to OS settings like name, organization and internet explorer default homepage URL and click Next.

7. Enter the admin password on the Admin Password page and click Next. This password will be used as administrator user 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 should set a password for local admin.

8. 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 it is ready to create PE image by updating the deployment share.

Step 5. Update Deployment Share to Create Boot-able PE image

The final steps before deploying Windows 10 using MDT is to update the Deployment Share. This section is going to create Boot-able PE media to boot the client systems in order to deploy Windows 10 using MDT.

1. So, on the Deployment Workbench right click MDT Deployment Share and click Update Deployment Share.

2. On the Options, page select Optimize the boot image updating process and click Next.

2. On the Summary page click Next to apply the update to MDT deployment share. It will take a few minutes because it will create PE image and prepare the MDT for Windows deployment.

3. Finally, the Update Deployment Share will be accomplished successfully. Click Finish to close the update deployment share page.

Good news, till now everything is going on perfectly and I’m very happy with creating and sharing this long step by step article with you. So hope you would find it helpful.

4. Go to Boot folder in Deployment share directory on E: drive and copy or move the Lite Touch PE to a network location or somewhere else.

Later we will use the Lite Touch image to boot the new computer and deploy Windows 10 using MDT with the help of this PE image.

Step 6. How to Deploy Windows 10 Using MDT?

Now the deployment server is ready to deploy Windows 10 using MDT and deploy applications. Try to boot a new system where you want to install the new operating system.

Here I’m going to test on a new virtual machine by creating a new virtual machine in Hyper-v. So you can do both hyper-v or a physical machine.

1. Boot the new system with Lite Touch PE image. You can boot the physical computer with USB Boot-able or boot through Network.

2. On the Microsoft Deployment Toolkit, Wizard page click Run the Deployment Wizard to install ad new Operating System.

2. Specify the network address of MDT Deployment Shared folder and click Next then type user, password and domain name.

Remember; the user you enter must have full shared permission and modify NTFS permission to MDT deployment share folder on drive E. Otherwise it will not work.

3. Select the Windows 10 on Task Sequence page and click Next to execute to your new computer.

4. Type the computer details such as name and join to a domain if you want to join it. In this section, if you select Join to Workgroup, you will be able to capture an image also. But it’s not related to Windows 10 deployment using MDT. So we will discuss creating a reference computer and capture image in a separate topic.

5. On the Move Data and Settings page, select Do not move user data and settings and click Next to continue.

6. Select Do not restore user data and settings on User Data Restore page and click Next.

7. Enter the Windows product key or select No product key is required and click Next.

8. Select Windows local and time and click Next. Select the correct time zone and language.

9. On the Application, page select the applications you want to deploy on this machine at this time and go to the Next page.

10. Enter the local Administrator password twice and go to Next page.

11. Check everything should be ready to begin on the Ready page and click Begin to start deploying Windows 10 using with MDT.

It will deploy and take too much time. Go to do your other jobs at this time and come back when the deployment task is finished.

12. After finishing deploying Windows, the system will restart and ask to you deploy software. In this section simply accept the terms and agreement of Office 2013 and click continue then click Install Now to begin the installation.

13. When the Office 2013 installation has finished close all pages and once restart your computer to see the result.

It’s good to deploy Windows 10 using MDT in order to create the master image and then deploy it to other machines. Directly deploying with this method is a time-consuming process and is not a good practice for Windows and Application Deployment.

Conclusion

The MDT is a perfect toolkit to deploy software and operating system or creating a master image from a reference computer. To get more from MDT for lite touch level, you must combine MDT with WDS to create a flexible Deployment environment and using consistently in your network.

I hope it will help you to create your own deployment lab for your production environment with Windows Deployment Toolkit and can simply deploy Windows 10 using MDT or Windows Deployment Services. If you have any question, feel free to ask your question about Windows and Application Deployment.

Related Search Queries:

Deploy Windows 10 using MDT and WDS
Deploy Windows 10 using MDT and WDS
MDT download
Sysprep and capture windows 10
How to deploy Windows 10 image over the network
Capture windows 10 image MDT
Deploy windows 10 WDS
Windows 10 ADK

The post How to Deploy Windows 10 Using MDT in Windows Server 2016? appeared first on TECHNIG.

It is a best chances for MCSE holders to get free MCSE recertification trough MVA. Now Microsoft is offering a free, self-study way for IT professionals to recertify their expiring MCSE certifications through online courses from the Microsoft Virtual Academy.

The Microsoft Virtual Academy (MVA) has long been known as a good source for online training and information, much of it certification related. In what I hope is the start of a soon-to-be pervasive trend across all Microsoft certifications.

How to Get Free MCSE Recertification?

MVA is offering  MCSE recertification “paths” for two MCSE credentials: the MCSE: Data Platform (normally achieved by passing exam 70-469 Recertification for MCSE: Data Platform) and the MCSE: Business Intelligence (normally achieved by passing exam 70-470 for free  MCSE Recertification: Business Intelligence).

In a recent Born to Learn blog post, Microsoft Learning Senior Product Manager for Certification, Larry Kaye, describes how completing a prescribed “skills path” at MVA can lead to recertification on the two MCSE credentials (Data Platform and Business Intelligence) for which such coverage is available.

 Here’s what’s involved in re-certifying your expiring certifications through MVA:

• Find the appropriate skills path for your expiring Microsoft MCSE certification.
• Pass all of the self-study assessments for each MVA course in the path.
• Email Microsoft when you’ve completed step 2 with your MVA username and Microsoft Certification ID: certquest@microsoft.com.

Once Microsoft verifies your completed MVA courses, they will update your MCP transcript with a new expiration date for your MCSE.

That same blog post goes on to add that Microsoft Learning plans to add more recertification paths for MCSE and MCSD credentials over the next 12 months or so. Gosh! I’d like to see them add coverage for the various MCSA credentials, too, at which point they’d have the vast majority of certs covered, including all of the popular ones.

This will really help IT professionals maintain their Microsoft credentials, and also make it much easier for them to focus on topics they need to learn and master to keep tracking current certifications in the MS program(s). And unless Microsoft changes its delivery for MVA content, all this stuff should remain free and available to the general public, too.

For more information on this program, please take a look at the details in the Re-certify with Microsoft Virtual Academy page on Microsoft Learning. There you’ll find the list of MVA courses to take for each credential covered, and their availability status. Microsoft Learning also promises to keep this page updated with new credentials covered as they are added to the collection. You’ll also find the e-mail address through which to communicate your status when you complete all the assessments for a credential there, too.

Good stuff! Glad to see Microsoft is providing a free, self-study means for IT pros to keep up their MS certifications.

Source: TomsITPro

The post Get Free MCSE Recertification From Microsoft Virtual Academy appeared first on TECHNIG.

A new, free eBook is available from Microsoft Press. Titled, Microsoft System Center Software Update Management Field Experience, the 160 page eBook compiles accounts from Microsoft Premier Field Engineers and Consultants who have worked through issues in a multitude of different Configuration Manager environments.

Focused technical guidance from System Center experts

Part of a series of specialized guides on System Center–this book walks through the tools and resources used to manage the complex task of tracking and applying software updates to client computers in the enterprise using Windows Server 2012 R2 and System Center 2012 R2, or later. Written by experts on the Microsoft System Center team and with Microsoft MVP Mitch Tulloch as series editor, this title focuses on maintaining operational efficiency, minimizing security issues, and maintaining the stability of the network infrastructure.

The book software updates contains the following 5 chapters and each section includes guidance and troubleshooting.

• Architecture
• Client
• Management
• Monitoring
• Automation

Download the Free eBook Manage Software Updates:

• PDF
• EPUB
• MOBI (Kindle)
• Companion Files

Source: Microsoft Press Store

The post Free ebook Manage Software Updates Using ConfigMgr 2012 R2 appeared first on TECHNIG.

Online virtual Lab is a virtualized environment for testing new features of a product. Here you see the virtual Lab for Windows Server 2012 R2 which offered by Microsoft Windows Server team. You can test all new features of Server 2012 R2 within this Lab without creating or installing a local Lab.

Log in to your Microsoft account and go to Virtual Lab: Getting to Know Windows Server 2012 R2 and click start then the log in page will open which ask you to log in with your Microsoft Account.

This Lab is compatible with Internet Explorer. So it’s better try it with IE. If ask do you let this app access your info? click Yes and click Lunch lab to start the Lab server.

When ask you whether you test Windows Client or Web Client? Click Windows Client

S small app name holSystems LaunchPad Online will be download and installed.

On the Application Run – Security Warning page click run.

When the installation has complete, the system may need to restart once. After restarting the system open the virtual lab page again and click launch lab and continue. It take a few minutes to prepare lab.

The post Free online virtual Labs for Windows Server 2012 R2 appeared first on TECHNIG.