The process of install and configure Active Directory in Windows Server 2016 is the same as Windows Server 2012 and R2. If you already know the installation and deployments of Active Directory with old Windows Server, you can install and deploy Active Directory Windows Server 2016 as well.

Before you begin to deploy Active Directory Windows Server 2016, you must know the basic requirements for Active Directory. First of all, install a clean Windows Server and set static IP address, assign the server name and enable or disable Windows features you need to have on Windows server.

• Windows Server Initial Configuration: It shows and demonstrates all necessary configuration that requires an Active Directory Server.

Deploy Active Directory Windows Server 2016 – Technig

This is the Windows Server 2016 Server Manager Dashboard. I have installed ADDS, DHCP, DNS and other services.

Install and Configure Active Directory in Windows Server 2016

To install and configure Active Directory Domain Services in Windows Server 2016, try to read the below step by step guide to install and configure active directory. It is a clear pictorial guide to deploy active directory Windows Server 2016.

• Install and Configure Active Directory in Server 2012 R2: It’s work the same for Windows Server 2016.

If you don’t like to read the article, just watch the below short video tutorials about installing active directory domain services in Windows Server 2016.

That’s all, short and simple guide to install and deploy active directory in Windows Server 2016. If you have any question, don’t hassle yourself, try to ask us through the comments section. And follow the below topics to know more about Windows Server and Active Directory Domain Services.

MCSA Complete Lab Manual Guide:

You might need to know more about Windows Server and MCSA certification. Follow this “MCSA Lab Manual Articles For Windows Server 2012 R2” article.

What’s New in Windows Server 2016:

The content in this section describes what’s new and changed in Windows Server® 2016 Technical Preview. The new features and changes listed here are the ones most likely to have the greatest impact as you work with this release. Read more on what’s new in Windows Server 2016.

What’s New in Active Directory Domain Services Windows Server 2016:

The following new features in Active Directory Domain Services (AD DS) improve the ability for organizations to secure Active Directory environments and help them migrate to cloud-only deployments and hybrid deployments, where some applications and services are hosted in the cloud and others are hosted on premises. Read more on what’s new in Active Directory Domain Services Windows Server 2016.

The post Install and Configure Active Directory in Windows Server 2016 Step by Step Guide appeared first on TECHNIG.

Installing Windows OS is not a complicated task. You can easily install Windows 10 from ISO image file using a DVD or USB drive. The Windows upgrade option is also an excellent choice to install Windows 10. But you can not directly install Windows from ISO file on a computer. Here we just explain the method you must know to install Windows 10 from an ISO file.

Install Windows 10 from ISO Image File

You must know that you can’t install Windows 10 from ISO image file directly. It’s not impossible, but you can do it with Windows deployment services. The Windows Deployment Services (WDS) enables you to deploy Windows operating systems over the network, which means that you do not have to install each operating system directly from a CD, DVD or USB.

Benefits of Windows Deployment Services

• Allows network-based installation of Windows operating systems, reducing the complexity and cost compared to manual installations.
• Supports deploying images for mixed environments including Windows 7 and Windows Server 2008 R2 through Windows 10  and Windows Server 2016.
• Uses standard Windows Setup technologies including Windows Preinstallation Environment (Windows PE), .wim files, and image-based setup.
• Transmits data and images by using multicast functionality.
• Allows you to create images of a reference computer using the Image Capture Wizard, which is an alternative to the ImageX tool.
• Allows you to add driver packages to the server and configure them to be deployed to client computers along with the install image.

The below articles are about Windows deployment services, which explain the WDS usage on Windows servers. With these step by step articles, you can learn the best way to deploy Windows 10 images in the network environment.

1. Install Windows deployment services on Windows Server.
2. Configuring Windows Deployment Services.
3. Install and Configure WDS on Windows Server 2016.
4. Deploying Windows 10 with Windows deployment services.
5. How to Capture Windows 10 Reference Image using WDS?

On the final note, installing or deploying Windows operating systems with WDS is a perfect option for the network environment. For installing Windows on a single machine, you must use a DVD or a Windows Bootable USB. The following article helps you make a Windows 10 bootable USB with Diskaprt utility and Windows PowerShell.

• How to Create a Bootable USB Using Diskpart Utility?

Tools for Managing Windows Deployment Services

The following are tools that you can use to manage your server:

• Windows Deployment Services MMC snap-in – Provides an easy way to manage images, computers, and common server settings. You can perform almost all tasks from the MMC snap-in (for example, you cannot prestage client computers). Note that the snap-in is not available when you install only the Transport Server role service.
• WDSUTIL command-line tool – enables you to manage the full functionality of the server. WDSUTIL also enables you to script common tasks.
• Windows PowerShell cmdlets for WDS – enables you to manage and monitor the WDS server using Windows PowerShell scripts.

How to Install Windows 10 ISO from USB?

To install Windows 10 ISO from USB, create a Windows 10 bootable USB with Diskpart or PowerShell. When you have created a bootable USB drive, then boot your computer with USB and follow the Windows 10 installation process. It works the same as installing Windows 10 from Windows 10 DVD.

•  Make Windows 10 Bootable USB with PowerShell.

And anymore question you have about installing Windows operating systems, feel free to ask as from comment box under the post.

The post How to Install Windows 10 from ISO Image File? appeared first on TECHNIG.

Microsoft Windows deployment services (WDS) helps you for Windows deployment of the client computers on your business network environment. The WDS is a server technology from Microsoft for network-based installation of Windows operating systems. It is the successor to Remote Installation Services an old OS deployment service. Here you can learn to configure WDS on Windows Server 2016 for Windows Deployment.

Microsoft WDS is intended to be used for remotely deploying Windows Vista, Windows 7, Windows 8, Windows 10, Windows Server 2008, Windows Server 2012 and Windows Server 2016, but also supports other operating systems because unlike its predecessor RIS, which was a method of automating the installation process, WDS uses disk imaging, in particular, the Windows Imaging Format (WIM).

Install WDS in Windows Server 2016

The above video tutorial explains you to install WDS in Windows server 2016 quickly. For Installing Windows deployment services, you need a virtual server or a physical server.

Install and configure Windows deployment services:

1. Prepare Virtual Server.
2. Installing Windows Deployment Services.
3. Configure WDS.
4. Add OS Image.
5. Deploy Client OS.

Using WDS is the best way to deploy Windows 10 images on network client machines and network servers.

After watching this video, you must be able to install the WDS server on a virtual server or a physical dedicated server.

Configure WDS on Windows Server 2016

The next step, after installing Windows Deployment, you need to configure WDS on Windows Server 2016 for Windows deployment. Just watch the WDS configuration video tutorial.

Good, your Windows Deployment server must be configured accurately. The next step using WDS as the best way to deploy Windows 10 images you have added to WDS.

You can find a step by step configuration of Windows Deployment Services here: Step by step guide to configure WDS.

Best Way to Deploy Windows 10 Images

Here you find the best way to deploy Windows 10 image to the client machines on your business network environment. If your Windows Deployment server configured properly, you can deploy Windows 10 without any problems. Otherwise, you must troubleshoot the Deployment server configuration. Find out the issue and try to solve it or share with us to help you.

No matter, if you faced some Windows deployment issue, just comment us under this post.

How to Capture Windows 10 Reference Image with WDS?

Create and capture Windows 10 reference image is important because that image serves as the foundation for the devices in your organization. In this topic, you will learn how to capture Windows 10 reference image using WDS.

This video is a short lab manual. If you need to know more about capturing an image with Windows Deployment Services read the article “Capture Windows 10 reference image using WDS“.

The post Configure WDS on Windows Server 2016 for Windows Deployment appeared first on TECHNIG.

Create and capture Windows 10 reference image is important because that image serves as the foundation for the devices in your organization. In this topic, you will learn how to capture Windows 10 reference image using WDS.

This image is the core operating system you need on your network environment. The image require all needed software for your Windows 10 clients to be installed. So before capturing Windows 10 image, make sure you update Apps and Windows with latest updates.

Capture Windows 10 Reference Image with WDS

Capture a Windows 10 image with Windows Deployment Services is easy if you would be familiar with Windows Deployment. Before applying this article, you need to have installed WDS on Windows Server. If you lab is ready for deploying Windows follow the article, otherwise read and apply the below articles to create your Deployment Server first.

• How to Install and Configure WDS In Windows Server 2012 R2?
• Configure Windows Deployment Services on Server 2012 R2
• Deploying Windows 10 Using WDS Server 2012 R2
• Customizing Windows Image Using DISM for Windows Deployment

So let’s begin to capture Windows 10 reference image.

1. Press Windows+R to open run and type Sysprep and run Sysprep. On the Sysprep tool select Enter System Out-of-Box Experience (OOBE) and select Generalize the click OK. 

2. Once the Sysprep has complete, system will restart and boot it from Network. You must configure you system to boot from network. Just press F12 to go to Pexe.

3. Now select Capture Image to capture Windows 10 reference image or PC.

4. On the Welcome to Windows Deployment Services Image Capture Wizard page click Next.

5. Now select the directory where you want to capture, type image name and image description then click Next.

6. Select Name and Location or tick the check box of Upload image to a Windows Deployment Services server. When done click Connect and type user credential. Select Image Group name also then click Next. 

7. This will take a long time to complete the process of capturing Windows reference PC.

8. When it has complete click Finish and restart your Windows 10 reference PC. Configure and select the reference PC language, time, user and password, because it has been completely out of box by executing Sysprep. 

9. Go to Windows Deployment server and check the result of Windows 10 capturing. The Windows 10 captured image should be transferred successfully to WDS server.

OK, that’s all about to capture Windows 10 reference image with WDS and Windows Server 2016 or Server 2012 R2.

Capture Windows 10 Reference Image video tutorial

If you have any question let us know and how can we help you to solve your OS and App deployment problems in your production environment.

The post How to Capture Windows 10 Reference Image using WDS? 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.

Windows Deployment is the core task of network infrastructure when a system administrator want to install clients operating system too fast at a short period of time. To customize Windows image with Deployment Image Service and Management (DISM) tool will help you to create a thin image which contain all necessary software, Apps and drivers.

Understanding Windows Image Files

There are two images (Install.wim and Boot.wim) on the installation Windows DVD. You can find them within the Sources folder.

• Install Image: Is used to install the full Windows operating system. Install images can include operating system, applications, configuration changes and several install images.
• Boot Image: The primary purpose of boot.wim image is to load a minimal operating system and boot the system to Windows pre-execution environment (WinPE) so that the full operating system to be loaded, or to perform troubleshooting.

To see the complete information of an Image using DISM command see the following command.

dism /get-wiminfo /wimfile:d:\sources\install.wim

The result shows that image is a Windows 8.1 Enterprise Evaluation with Index number of 1 and size is in bytes. Let’s see the information of a different image.

dism /get-wiminfo /wimfile:i:\sources\install.wim

Yes it is a Windows Server 2012 R2 with 4 different edition. Now you must completely understand the Index number of Images.

To see the information of Boot image, execute the same command and type boot.wim instead of install.wim image.

dism /get-wiminfo /wimfile:i:\sources\boot.wim

Do the similar task on Pre-execution environment (PE) with the following Imagex command line.

imagex /info d:\sources\install.wim

So you became familare with Windows images and know the differences between install and boot image and knowing how to get information of an image with DISM command line tool.

Customize Windows Image With DISM

A custom image mostly called thick image contains all software, applications and drivers unlike the thin Image that only includes operating system image. To customize Windows Image you must mount the install image offline services.

Mounting Images

To customize windows image, firstly copy the install.wim image from Windows installation DVD to a folder then mount it with the following DISM command.

dism /mount-wim /wimfile:e:\image\install.wim /index:1 /mountdir:e:
\MountedImage

It takes a few minutes to completely mount the image.

• The /wimfile: point the location of install.wim image.
• The /index: shows the index number within .wim image which previously explained.
• The /mountdir: point the path of mounted image, where the extracted image files are located.

Here is the mounted files of install.wim image. Now to see the mounted image information, just type “dism /get-mountedwiminfo” command.

OK, now time to modify the image using DISM.

Modifying Images

You can customize the below options and features of windows image.

• Add Windows drivers
• Add or remove packages and features
• Miscellaneous image modifications

Lets starting to add and remove some Windows features to this image. To add a package you must know the existing features and packages within your image.

To see the packages information type the following command. “dism /image:c:\mountedimages /get-packages”. It list all existing packages.

The best practice is to export all packages to a txt file.

dism /image:c:\mountedimages /get-packages /format:table >ImagePackages.txt

The list’s of exported packages in a text file. In order to see the exact package information type the following command.

dism /image:c:\mountedimages /get-packageinfo /packagename:Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.514

You can check to see if any patches have been applied to applications within the system with the /get-apppatchinfo switch.

dism /image:c:\mountedimages /get-apppatchinfo

How to add a Package?

In order to add a package to your custom image, firstly download the package then add it.

dism /image:c:\mountedImages /add-package /packagepath:c:\downloadPackages\(package name)

To remove a package from your custom image do it with remove-package command.

dism /image:c:\mountedimages /remove-package /packagename:(Package name)

To enable and disable a features, do it with disable-feature or enable-feature, see more How to Install Windows Features Offline?.

To enable a features: “dism /image:c: \mountedImages /enable-feature /featurename: (Feature name)”.

To remove a feature: “dism /image:c: \mountedImages /disable-feature /featurename: (Feature name)”.

How to set a license key?

In order to set the product key, type “dism /image:c:\mountedImages
/set-productkey: (Enter the key)”.

How to Save the Custom Image?

Finally, after editing images try to save it with dism /commit-wim command.

dism /commit-wim /mountdir:c:\mountedimages

This command apply offline changes to image and save it. Then you should unmount the image using dism /unmount-wim command.

dism /unmount-wim /mountdir:c:\mountedimages /commit

When you un-mount the image, the mounted files will no longer available to mounted folder and removed.

Now the custom image is ready to deploy with Windows Deployment Services or System Centre.

OK. These are the essential dism commands to customize windows image for windows deployment. I hope you to find this Customize Windows Image article helpful and if you need more information? just type dism /? to get the dism helps or ask your question through comment.

The post How to Customize Windows Image Using DISM for Windows Deployment? appeared first on TECHNIG.

Deploying Windows 10 using Windows Deployment Services with Windows Server 2012 R2 is the third parts of Windows Deployment articles. You can read the previews articles about how to Install and configure the WDS from below links.

• Part 1. How to Install and Configure WDS In Windows Server 2012 R2
• Part 2. Configure Windows Deployment Services on Server 2012 R2?

So in this post we trying to install Windows 10 as client OS for network workstation computers. In part 2 we added Windows 10 install.wim image and created a boot image also.

The WDS Server is ready to response for client requests. Make sure that the active directory and DHCP Server are running and work perfectly. It depends to your network environment, I have installed Active directory and DHCP Server in one server and WDS on the separate server which is the member of domain. You can install them on one server, both of them work the same but installing on the same server is not a good practice in real environment.

Deploying Windows 10 Using WDS

If you are ready, go to client computer and boot it with network card (Pxe). I assume that you have set the boot option of the client to boot from the network and just turn on the system.

1. The system will boot from network, so ask you to press F12 for network service boot. Press F12 to boot the system with Pre-boot Execution Environment (PXE).

2. The system will boot and trying to install. Just follow the steps.

Note: It is not necessary to press 12 always to boot the system. You can change the boot option from Properties of WDS. Just go to Windows Deployment Services properties and select the Boot tab. Now select the “Always continue the PXE boot” for known and unknown clients. But it is not a good practice in the real production environment, because of the security reasons.

3. On the Windows Setup page, select the language and keyboard then click Next. The system will ask you the credential, type user name and password and click OK.

You must enter the correct user name and password, otherwise you will face credential errors and unable to continue.

4. Now select each Windows image you want to install. Here I have just one enterprise edition. Select the and click Next.

5. The other process are the same as the the clear installation of a windows operating system. So don’t worry and just create the appropriate partitions and continue the installation till the end.

If you don’t know the process of Windows Installation, follow the step by step article of How to install Windows?

Deploy Windows 10 with WDS Using Server 2016

This video demonstrate the process of deploying Windows 10 using WDS with Windows server 2016.

Hope you find this short Windows 10 deployment article and video demonstration helpful. Feel free to ask you question about deploying Windows 10 with WDS and MDT. Read the article of deploying Windows 10 with MDT on enterprise network.

The post Deploying Windows 10 Using WDS and Server 2012 R2 appeared first on TECHNIG.

The first part of Windows Deployment Services was about the Installation of  WDS on Windows Server 2012 R2. Read it from ‘How to Install and Configure WDS In Windows Server 2012 R2‘. But in the second part of WDS, we will show you how to add Windows Images for deploying, creating Boot Image and Capture Image for capturing the reference PC which is a custom image’s of a Windows operating system. So I don’t talk anymore and let’s deploy clients with Windows Deployment Services using Windows Server 2012 R2.

Add Image To Windows Deployment Services

We need to add two types of images in WDS, install.wim and boot.wim. Then install.wim images are the operating system images that you deploy to the client computer. You can also use the Install.wim file from the installation media (in the \Sources folder of Windows DVD), or you can create your own custom images.

To boot your system through the network card, you must add the boot.wim image of the latest Windows Operating System. The Boot.wim images are Windows PE images that you boot a client computer to perform an operating system installation. In most scenarios. Boot.wim image is also located in the Sources folder of Windows DVD.

While you are login in as a domain admin or member of the Administrators group to WDS Server, go to Server Manager and open Windows deployment services from the Tools tab of Server Manager Dashboard.

Expand the Servers then right-click the Install Images and click Add Install Image.

On the Add Image, Wizard page type the name of a group and click Next.

On the Image, Files page click Browse and select the install.wim image from Windows sources folder and click Open and then click Next. 

On the Available Images pages select Windows edition, whatever you want and click Next. Here we only have Windows 10 technical preview for the enterprise.

It will take a few minutes to check the integrity of image’s and adding images. When the image added successfully, just click Finish and see the Clients group that has the image ready for deploying to clients machines.

That is it. You can add as much as Image you want. But now try to add the Boot.wim image the same as an Install image. But instead of install.wim image select boot.wim image.

Now you can deploy and install Windows 10 for your network clients. In the next part, we will install the client operating system through the network using WDS.

Configure WDS on Windows Server 2016 – Video Tutorial

The post Configure Windows Deployment Services on Server 2012 R2? appeared first on TECHNIG.

How to Install and Configure WDS in Windows Server 2012 R2 is a step by step guide to Windows Deployment Services. Windows Deployment Services is a Microsoft server technology for network-based installation of Windows operating systems and It is the successor to Remote Installation Services of Server 2003. In Windows Server 2012 R2, the following requirements needed for installing Windows Deployment Services role, depending on whether you choose the default installation (both Deployment Server and Transport Server), or only the Transport Server role service.

WDS Prerequisites

• The Windows Deployment Services server must be a member of an Active Directory Domain Services (AD DS) domain or a domain controller. You may need to ‘Install Active Directory in Windows Server 2012 R2‘.
• The Domain Name System (DNS) server on the network before you can run Windows Deployment Services. DNS will install with Active directory domain services, but if you have not, read the DNS Installation article ‘Install and Configure DNS in Windows Server 2012 R2‘.
• For deploying IP address you must have a Dynamic Host Configuration Protocol (DHCP) server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing the clients that want to install OS remotely. Read the topic ‘Install and Configure DHCP Server on Windows Server 2012 R2‘ for DHCP Server.
• You must have the appropriate credential to install role. It means you must be the member of local admin or domain admin. The hard disk volume must be NTFS.

How to Install and Configure WDS?

In Windows Server, sign in to the server as a domain admin and open the Server Manager if it’s not will start automatically. If the step by step is time consuming for your, watch the video tutorial at the end of this article.

On the Server Manager click Manage and then click Add roles and features. On the Before you begin page click Next.

On the Select installation type page, click Role-based or feature-based installation, and then click Next.

On the Select destination server page, select the appropriate server, and then click Next. By default the MS2.technig.local server has selected.

On the Select server roles page, scroll down and then select Windows Deployment Services check box. in the Add feature that are required for Windows Deployment Services? click Add Features and click Next. This task will install the Windows Deployment Services Tools which included in Windows Remote server administration tools.

On the Select features page, click Next.

On the WDS page once read the information and click Next.

On the Select role services page, select the role services to install for Windows Deployment Services. Leave these role services selected by default if you want to install both the Deployment Server and Transport Server. Click Next.

Finally on the Confirm installation selections page, click Install.

When the installation process complete successfully, click Close and go to Server Manager dashboard.  Now we have the WDS role and lets try to configure it.

How to Configure Windows Deployment Services?

While you are log in as domain admin account or local administrators members, go to Server Manager and click Tools then click Windows Deployment Services in order to open it.

On the Windows Deployment Services console page expand the Servers and right click the MS2.technig.local then click Configure Server.

On the Windows Deployment Services Configuration Wizard page, read it once and click Next.

On the Install Options page select integrated with Active Directory and then click Next.

On the Remote Installation Folder Location, select the location where you want to keep all Windows Images and configuration files and then click Next.

On the PXE Server Initial Settings page select Respond to all client computers (Know and unknown) and click Next. Remember, we are in the test area so in the real network environment select whatever you want.

The sever will start and complete the configuration. On the Operation Complete page unchecked the Add image to server now and then click Finish 

Here is the Windows Deployment Services in Windows Server 2012 R2.

OK, that’s all Install and Configure WDS. The installation has completed successfully. To continue the WDS configuration, adding Windows images and creating capture image read the following articles: Configure Windows Deployment Services on Server 2012 R2?

Video Tutorial, Install WDS on Windows Server 2016

The post How to Install and Configure WDS In Windows Server 2012 R2 appeared first on TECHNIG.