My name is Mike Chen, a program manager working on the Windows Server Essentials Deployment team. I’m honored today to introduce the new deployment story for Windows Server Essentials.
Now available as a server role
Previously, we heard a lot of feedback that users want rich features in Windows Server Essentials to be available more broadly beyond the Windows Server Essentials edition. In the Windows Server 2012 R2 Essentials release, we’ve made major investments into making our deployment available as a server role. Therefore, as Jason mentioned in an earlier blog , the features in Windows Server Essentials are being released in both Windows Server 2012 R2 Essentials and as the Windows Server Essentials Experience server role in Windows Server 2012 R2.
We use a consistent architecture across the following editions: Windows Server 2012 R2 Essentials, and Windows Server 2012 R2 Standard and Datacenter. From a technical perspective, features are packaged into the Windows Server Essentials Experience role in exactly the same way. The key difference regarding the deployment is that in Windows Server 2012 R2 Essentials, the role is pre-enabled and the configuration wizard is configured to pop up automatically when a user logs on to the computer. (There are also differences around locks and limits that are not in the scope of this blog.)
Multiple options for deployment depending on your environment
As a server role, Windows Server Essentials Experience can be deployed on a workgroup box, a domain controller, or a member server in the domain. The limitations here are that Windows Server Essentials Experience can only be deployed to a single domain environment and you can’t have a read-only domain controller (RODC) in your environment.
When deployed on a workgroup box , the configuration wizard will ask you for information to bring up a new Active Directory domain environment and configure other roles and features that the role depends on.
When deployed on a member server in the domain or on an existing domain controller (you need to join your existing domain by using native tools), the configuration wizard simply configures other roles and features without changing your domain environment. Therefore, for users who want to try out the experience, the best way is to deploy Windows Server Essentials on a member server in your existing IT environment, which is much less intrusive. The steps are:
- Join Windows Server 2012 R2 Standard or Datacenter to your domain.
- Enable and configure the Windows Server Essentials Experience role in Server Manager.
You may have already noticed that previous migration paths in the configuration wizard are not needed, because Windows Server Essentials can be deployed on an existing domain controller. If you want to migrate to the latest platform, just do an Active Directory replication and then configure Windows Server Essentials. For more information about migration, see
Migrate from Previous Versions to Windows Server 2012 R2 Essentials
.
Remote installation and Windows PowerShell
In addition to configuring Windows Server Essentials directly from the local box, you can now use Windows PowerShell cmdlets for more advanced scenarios; for example, remote configuration in the hosting environment using Windows PowerShell, or unattended installation using first logon scripts.
You can run these simple commands to perform the installation and configuration:
-
Install the Windows Server Essentials Experience role by using the following command:
Add-WindowsFeature ServerEssentialsRole
-
To configure it, use
Start-WssConfigurationService
. You can get more help information about this command by using
get-help start-wssconfigurationservice
.
-
Run the following script to configure a workgroup box:
Start-WssConfigurationService -CompanyName "ContosoTest" -DNSName "ContosoTest.com" -NetBiosName "ContosoTest" -ComputerName "YourServerName” –NewAdminCredential $cred
-
Run the following command to start the configuration to set up Windows Server Essentials as an existing domain member. You must be a member of the Enterprise Admin group and Domain Admin group in Active Directory to perform this task:
Start-WssConfigurationService –Credential <Your Credential>
-
To have installation status displayed on the progress bar, run:
Get-WssConfigurationStatus –ShowProgress.
-
To get the immediate progress without the progress bar, run:
Get-WssConfigurationStatus
Deploying Windows Server Essentials on virtual machines
With the wide adoption of virtualization, we’ve heard more and more feedback that customers want to deploy their servers as virtual machines (VMs). Windows Server Essentials Experience provides a great tool that allows an end user to seamlessly set up their physical server as a VM host and bring up virtualized Windows Server Essentials as a VM guest. This tools requires that OEM and system builders do some pre-configuration on the image. The tool works for Windows Server 2012 R2 Essentials and Windows Server 2012 R2 Standard. In a future blog post, we will share more detailed steps about how to configure this.
As a system provider, you have the option to let your customer choose between a virtual deployment or a physical deployment .
If an end user chooses a virtual deployment , Windows Server Essentials will have the Hyper-V role installed and will be able to run VMs, and the wizard will create a customized Windows Server Essentials VM based on the end user’s settings. In addition, any Windows Server roles that aren’t necessary for hosting VMs will be removed from the host to reduce the footprint on the host.
If the user chooses to do a physical deployment , the configuration wizard will install and configure the Windows Server Essentials role on the physical box.
For more information, see Install and Configure Windows Server 2012 R2 Essentials .
End user can select a virtual deployment or a physical deployment
End user is provided with a virtual deployment
Microsoft
