Windows deployment server without domain

In Windows PowerShell, unlike in the Add Roles and Features Wizard, management tools and snap-ins for a role are not included by default. To include management tools as part of a role installation, add the -IncludeManagementTools parameter to the cmdlet. Otherwise, management tools and snap-ins cannot be installed on servers that are running the Server Core Installation option of Windows Server.

Right-click the shortcut for Windows PowerShell when it is displayed on the Start page in the Apps results, click Advanced , and then click Run as Administrator. To view a list of available and installed roles and features on the local server, type Get-WindowsFeature and then press Enter. The results of the cmdlet contain the command names of roles and features that have been added to this computer.

In Windows PowerShell 4. A module is automatically imported the first time you run a cmdlet that is part of the module. Also, Windows PowerShell cmdlets are not case-sensitive. When the installation is finished, verify installation by running Get-WindowsFeature. This will install both the Deployment Server and the Transport Server roles. The previous command line tool, Servermanagercmd. It is recommended that you use the Windows PowerShell cmdlets. Server Manager will start automatically.

If it does not automatically start, click Start , type servermanager. 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. The local server is selected by default. On the Select server roles page, scroll down and then select the Windows Deployment Services check box. Click Next. Remote Server Administration Tools are required to manage this feature.

Select Include management tools if applicable. Click Add Features. On the Select role services page, select the role services to install for Windows Deployment Services. If you wish to install both the Deployment Server and Transport Server, leave these role services selected. Windows Deployment Services will now be added to the server.

Installation progress will now be illustrated in the Add Roles and Features Wizard. Transport Server does not require any additional roles or services.

Both of these services require an NTFS partition for the file store. You will also need to add at least one boot image and one install image to the image store. After you install the Windows Deployment Service role, you must configure the server. Once you have used the instructions in this section to configure the server, add a boot image, and an install image, you will be ready to deploy images.

Then, you can use the instructions in the rest of this guide to perform more advanced tasks like creating your own install images, creating discover images, or configuring an unattended installation.

If Windows Deployment Services is installed in Standalone mode, it can be configured without having a dependency on Active Directory. There are two configuration options for Windows Deployment Services. It can be configured to integrate with Active Directory or be configured as a standalone server. To configure the server role in Standalone mode, use the following procedure.

Then see the following section to add images to the server. On the Remote Installation Folder Locations page, choose the default path or enter your own path to the remote installation folder. On the PXE Server Initial Settings page, choose desired option to define which client computers this server will respond to. This will complete the configuration of Windows Deployment Services.

When the configuration is completed clear the Add images to server now check box, and then click Finish. If you want to modify any of the settings of the server, right-click the server in the MMC-snap in, and click Properties. Now that you have configured the server, you will need to add images.

These images include a boot image which is the bootable environment that you initially boot the computer into, and the install images which are the actual images that you deploy. For instructions, see Steps for adding images. You may skip this if you have chosen to install Standalone mode, and proceed to Steps for adding images. To install Windows Deployment Services integrated with Active Directory, the following prerequisites are required. To configure the Windows Deployment Services server role integrated with Active Directory, use the following procedure.

On the Install options page, choose Integrated with Active Directory. Now that you have configured the server integrated with Active Directory, you will need to add your images. For instructions, see the next section, Steps for adding images. You must add at least one boot image and one install image before you will be able to boot to the Windows Deployment Services server and install an image.

Boot images. Boot images are Windows PE images that you boot a client computer into to perform an operating system installation. In most scenarios, you should use the Boot. The Boot.

Install images. Install images are the operating system images that you deploy to the client computer. You can also use the Install. The following instructions use Windows 7 installation media as an example for creating an install image that can be deployed with Windows Deployment Services. You can also use the same instructions for server installation media. Browse to choose the default boot image Boot. On the Image Metadata page, enter the desired image name and description.

After you have at least one boot and one install image on the server, you can deploy an install image. Select the appropriate boot image from the boot menu. Then she would spend almost as much time installing the applications on each computer. Monica is the only IT professional at Fabrikam, which means that she also must help teach users about the new operating system. Therefore, it is important that she minimizes the amount of time she spends on deployment.

To accomplish this, Monica chooses to use Windows Deployment Services because she can:. Adds the Boot. Adds the Install. Uses the MMC snap-in to create a capture image from the boot image she added in step 3. This image contains Windows PE and a wizard that will capture her custom image into a.

All users at Fabrikam have the same desktop hardware, which was purchased from a single vendor. To deploy a standard image to the computers, Monica does the following:. Boots a reference computer from the network and installs the Install. Uses the Image Capture Wizard to recapture the operating system and upload it directly to the Windows Deployment Services server.

Now, Monica is ready to install the new operating systems. She does not need to migrate any user data, because all of the employees store their user data on a server rather than on their hard disks. She reboots a client computer and then presses F12 to perform a network boot. This boots her into the Boot. She selects the disk partition and image she wants, and then the installation begins. While waiting for the image to be applied to the first computer, Monica boots another computer and starts the same process on that one.

Northwind Traders is a shipping firm with three offices: a central office in Tooth City, and branch offices in the towns of Brushville and Flosston. His responsibility is maintaining the client computers used by the company's employees. These are mostly desktop computers, but the sales force uses laptops for customer presentations.

There are computers in the central office in Tooth City, and 25 each in the Brushville and Flosston offices. Each site has an internal network running at MB per second MBps , and the branch sites are connected to the Tooth City office by a T1 line. Ron has three Windows Deployment Services servers at the Tooth City office and one in each of the branch offices, which are administered remotely.

Previously, this would have involved many expensive trips to Brushville and Flosston, and it would have taken Ron several weeks to complete. He wants to use Windows Deployment Services to deploy Windows remotely; however, company policy dictates that there can be only one DHCP server on the corporate network, and this server is located at the Tooth City office.

Remotely deploying images to the 50 computers at the branch offices would cause immense congestion on the connection. Use the network boot referral system to minimize network traffic between the branch sites and the central office. Ron prestages each client computer and assigns the appropriate branch office server as the referral server for each.

This ensures that the client downloads files and images from the local server, which minimizes traffic on the line between the offices. Installing Windows Deployment Services requires a reboot. You can see the "Windows Deployment Services" container on the left side on the screen with the "Servers" container underneath, but nothing further.

When you try the "Add server" command to add the local computer you will find the following error:. The error indicating "This machine is not currently joined to a domain" indicates you need an Active Directory domain and you can only add servers to the Windows Deployment Services MMC which are member of an Active Directory domain.

If a server you are trying to add is not a member of an Active Directory domain, you receive this error, even if it's the local server. How can I do that? Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related 3. Hot Network Questions. Question feed. Server Fault works best with JavaScript enabled.