October 25, 2011 7 Comments
It seems like a lot of businesses are bringing a second server online lately, perhaps discovering the benefits a Terminal Server (or Remote Desktop Services Server or even Multipoint) can bring, or maybe it is a Server that will run SQL for an LOB application. Personally i prefer to keep the SBS free of Apps if possible, especially accounts programs.
The SBS PAO (Premium Add on) Is a great way to get that second server and SQL license, but it may not be the most cost effective route to get what you want, so make sure you do your research before purchasing.
That’s my little marketing pledge done, now on to the technical stuff.
If you are familiar with installing SBS and general networking, likely you know already how to add a second server to an SBS Standard network, but what about essentials?
- Do you try to install the connector?
- Do you use the traditional ‘Computer Name’ tab in System Properties?
- Does it show up in the Dashboard?
- Does it get backed up?
Connector or Not Connector that is the question!
Firstly you need to ask what OS is your server. Is it Server 2008, 2008 R2 or maybe an older 2003?
The connector software will install on Server 2008 R2 Standard, IF you are running SP1, and also if your Server is NOT a Domain Controller.
If you are not running SP1 you will see this message if you attempt to install the Connector software.
If you want to know which OS’s and Versions are supported, check out the ‘supportedOS’ XML file on your essentials box.
You will find that file in this directory
C:\Program Files\Windows Server\Bin\WebApps\Client\Package\
If you want to know what version of Windows you are running, you can type this command into an Elevated command prompt:
systeminfo | findstr /B /C:”OS Name” /C:”OS Version”
Assuming you meet the requirements you will be presented with a warning about Supported Client OS’s and you can click on ‘Continue Anyway’ to continue the installation.
You may want to note that it is not possible to install the connect when logged on using Remote Desktop. Also the same problems affecting install on Client OS’s can strike on a Server install. Plenty of resources out there for those, but my post is where i will point you.
Now for my disclaimer.
Adding the connector is not supported. You get a big warning to the same effect. If you do decide to install the connector it is at your own risk, i am not going to be held responsible for anything, whether it works or doesn’t work, whether it works some of the time and whether it makes you look silly. By reading this disclaimer in your head or out loud you have waived any legal responsibility on my part in perpetuity throughout the universe.
Is it in the Dashboard?
Yes. If you install the connector then it will indeed show up in the dashboard.
Does it get backed up?
The short answer? Yes it does.
It does appear that the SBS Essentials ‘Client Backup’ will backup the server OS.
However, i have to stress this is not supported, and because of that there is no guarantee from anyone, Not me, Not Microsoft that you could successfully restore your server from that backup.
The SBSE client backup does not contain ‘agents’ for the Server OS or any applications you may be running on it, like SQL, so a backup with the SBSE client backup cannot be trusted, or guaranteed.
If you are going to have the Server show up in the dashboard, i recommend you disable the SBSE backup, and instead rely on your own backup strategy for the Server, but i am not discussing that in this post.
You can disable the backup from the dashboard, by clicking ‘Customise Client Backup for the computer’ and clicking disable backup.
You may also want to disable the launch pad.
The launch pad runs, or at least seems to run, perfectly well on the server. I set my test server up as a RDS (TS / Terminal Server) and logged into with two separate accounts, and the Launchpad ran fine for both. The only thing i didn’t like was that a helpful or considerate user may want to poke around the backup settings, and that could be bad, so to remove temptation, my advice would be disable it.
- Likely as not you wont need the Launchpad on that server anyway.
- You can disable the Launchpad through the registry, or via MSCONFIG.
All of the above is subject to one exception. Windows Multipoint Server 2011. (WMS)
This Server OS, is supported for use with Essentials, can handle the Connector install, and perhaps most importantly, is also supported to be used with the SBSE Client backup.
If you haven’t heard of, seen, or used WMS, then get yourself along to the SMB MVP Community Road Show and see it in action.