The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
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.
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.)
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:
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.
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:
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
I have Server 2012 Standard, and i am planing to upgrade to R2, i really like the idea of adding Essentials as a role, but will i be able to use work folders after i add Essentials role ? i have been reading on some blogs that we cant use work folders if we add Essentials Role.
can not download facebook .com server
@Raghu, the product team is actively working on this issue. You will hear from us in the near future on the solution.
Thanks for the intro! However, I cannot join our domain since Start-WssConfigurationService in my clean Server 2012R2 core installation does not have all options:
If I type: help Start-WssConfigurationService, I receive:
Start-WssConfigurationService -NetbiosName <string> -NewAdminCredential
<pscredential> [-Force] [-WhatIf] [-Confirm] [-ComputerName <string>]
[-CompanyName <string>] [-DNSName <string>] [-Hosted] [<CommonParameters>]
So, trying to join the domain with Start-WssConfigurationService –Credential <Your Credential> fails with "Invalid argument" error.
@Roland, do you mean your server is in a workgroup and you want to join a domain?
If yes, you have to join a existing domain firstly. Then run "Start-WssConfigurationService -Credential".
Thanks for sharing.