Solved

Windows Small Business Server 2008

Posted on 2011-09-19
2
271 Views
Last Modified: 2012-05-12
Am I right to understand that in Win SBS 2008, the operation master roles are all held by the sbs server and cannot be seized?  Let me give you an example of what I mean...Consider that in a network there are 3 servers.

Server 1 – Small Business Server 2008
Server2 – Windows Server 2003 (Domain controller, DNS)
Server3 – Windows Server 2003 (Domain Controller, DNS)

Server 2 and Server 3 can have no barring on the continuity of the network because none of the FSMO roles can be seized from the Small Business Server should it fail.  When restoring the network, the most crucial server is server 1 and therefore must have the most protection.  It’s fair to say that having the other servers as domain controllers may allow people to log on but for the network to function long term, server 1 has to be restored.   I am thinking this in terms of the RID master and so on

Having the Windows Server 2003 machines acting as backup domain controllers and DNS servers is actually restricting the functionality of the domain as the functional level is at win server 2003.  

Thanks for your input
0
Comment
Question by:cmatchett
2 Comments
 
LVL 39

Accepted Solution

by:
Krzysztof Pytko earned 500 total points
ID: 36559262
Yes, that's right! SBS server must be a forest root Domain Controller with all of 5 FSMO roles. If you move any of them to another DC, your SBS will be rebooting itself regurarly. So, that's true that SBS is "the most important" server in your environment. But remember, doing backups of each server (especially DCs) is very importantant!

If you do not use any special role of SBS (like Exchange, SQL aso.) you can seize FSMO roles to another Domain Controller in your network freely. But remember, you won't be able then restoring it from backup and join network. After FSMO roles seizing, previous server must be completely reinstalled. SBS is for small to medium organizations and has limitations because of that.

Do regurarly system state backups of your SBS and other DCs, backup their content and until your hardware would be OK, you will be always able to restore them.

Seizing FSMO roles is the last option and should be only used when hardware cannot be repaired and System State Backup cannot be restored.

Regards,
Krzysztof
0
 

Author Comment

by:cmatchett
ID: 36572549
super...thanks a bunch!
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question