Windows Server 2012 Essentials Build document
<in progress - placeholder>
The assumption for Windows Server 2012 Essentials (hereinafter called WSE12) is that it will be the first domain controller in the network. Note this does not mean it has to be the only DC, just that like the products it inherited it's legacy from, that it has to hold the FSMO roles. The assumption is that the external router will perform the role of DHCP and provide WSE12 with a dynamic IP address. Whilst you can install the role later after the server is installed and assign the server a static IP, it is assumed that DHCP will be enabled and running on the router as you build the WSE12 server. Please review the router setup document here. When installing the DHCP role, ensure that the other DHCP servers are turned OFF before you install the role. A proper How-To is here: Official SBS Blog: Running DHCP Server on SBS 2011 Essentials With a Static IP.
As a suggestion, you may wish to shrink that last volume and divide the space into two volumes, one for data storage and the other for client backup files. Doing so will give you the flexibility to not backup the volume containing the client backup files.
On the Dashboard - the devices tab - under Device Tasks click Implement Group Policy, which will setup policies for Folder Redirection and Security Settings for Windows Update, Windows Defender and firewall.
Follow the OEM instructions here: Add Branding to the Dashboard, Remote Web Access, and Launchpad: http://technet.microsoft.com/en-us/library/jj200109.aspx
Tip from http://www.mswhs.com/2012/09/remove-default-shares-in-ws2012-essentials/?utm_source=twitterfeed&utm_medium=twitter&utm_campaign=Feed%3A+MSWHS+%28MS+Windows+Home+Server%29
Essentials can support an on premises Exchange server on a member server, hosted Exchange or an email deployment with Office 365. You can even look into using a third party mail solution such as Kerio. For an on premises Exchange server - follow Robert Pearman's Exchange script that will automatically install the Exchange server and allow it to be configured. Consider it a wizard without a GUI. Full details here: This works for sure with Server 2008 r2 and Exchange 2010 - On Prem Exchange Windows Server 2012 Essentials: The Script! « Title (Required): http://titlerequired.com/2012/10/23/on-prem-exchange-windows-server-2012-essentials-the-script/
To add network printers follow Robert Pearman's post on how to add printers: http://titlerequired.com/2012/10/24/windows-server-2012-essentials-add-a-network-printer/
You want to follow Robert Pearman's post on this topic: http://titlerequired.com/2012/10/15/enable-directaccess-on-windows-server-2012-essentials/
If you added users via ADUC or migrated to Essentials and now the user isn't in the console - follow this:
Type *cd “\Program Files\Windows Server\Bin”*, and press ENTER.
Type *WssPowerShell.exe*, and then press ENTER.
Type *Import-WssUser –SamAccountName <username>*, and then press ENTER.
Repeat the previous step for each user name that you want to import into the Dashboard.
So, you have a work laptop, or a nicely running non-domain based home network. But alas, you have no home server options anymore... You are left with the option of installing a Windows Server 2012 Essentials machine (which whilst expensive, really is a great home server option). The problem is, you don't want the machines in your home in a domain, you want them to remain totally independent for many a reason. Here is a nugget of information that you will love then. When you run the Connect computer wizard (http://nameofserver/connect) you can avoid the domain join bit by simply running this command in an elevated command prompt beforehand: reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1 ....then, run the wizard and you will get all the good backup and home features without the domain join.
(taken from see link
If you still want to use RWA with this non domain workstation 1. When prompted for the RD Gateway Credentials
- Use a Standard User defined on the WSE server. That user must be given permission to access the client machine-- done by double-clicking the user and selecting the Computer Access tab. Give it a few seconds to populate as it can be as slow as molasses.
- Use the format domain\username. The domain is the domain name created when the WSE server was first built. For example: [wse domain name]\[wse standard username] 2. If that works, it prompts with the Windows Security dialog from the client computer.
- Click on "Use another account" and once again use the domain\username format. But this time the domain should be the name of the client computer. The user should be a user of the client machine that has been given remote access. For example: [client machine name]\[client username]
See this wiki post.
If you see the following error in Health Reports... -------------------------- DFSR Event ID: 2147485861 The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. Additional Information: Volume: C: GUID: 4C7D4FA6-61AF-11E2-93ED-806E6F6E6963 --------------------------- Steps to prevent the error... 1. Change the registry key：StopReplicationOnAutoRecovery value to 1 Open Command Prompt | Regedit Go to key: HKLM\System\CurrentControlSet\Services\DFSR\Parameters\StopReplicationOnAutoRecovery Make sure StopReplicationOnAutoRecovery key is set to: 1 2. From an elevated command prompt, type the following command: wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="4C7D4FA6-61AF-11E2-93ED-806E6F6E6963" call ResumeReplication (all on one line) 3. After successfully running the WMIC command: Open Command Prompt | Regedit Go to key: HKLM\System\CurrentControlSet\Services\DFSR\Parameters\StopReplicationOnAutoRecovery Change StopReplicationOnAutoRecovery from 1 to 0 Quit Regedit For more information, see http://support.microsoft.com/kb/2663685.