Can I add new users/computers on second DC, in SBS 2008 environment, while SBS server is offline?


I am planning to have SBS 2008 domain with an addition DC server running windows server 2008 standard and both servers will take GC role.
As per SBS restriction, my second DC (windows 2008 standard) cannot take any of 5 FSMO roles.
In case of SBS server is down for few hours, shall I be able to add or remove users/computers on second DC?
Any other service disruption in AD management?

Kindly provide details, when you post the solution. Thanks!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

A few hours' downtime shouldn't impact anything noticeably as long as you have another DC.  No details to mention really.  But why would your server be down for hours at a time anyway?
roger_rexAuthor Commented:
Hi Datedman,

Thanks for your comment.
I am planning a solution to face a situation that hardware failure or critical error occurs on SBS server and recovery takes few hours.

As I will not be implementing the second DC as RODC, I should be able to write to AD database, in case of SBS server's failure. But all the FSMO roles are held by that SBS server. This limitation triggers me think about this situation.
In my experience it's not a problem.  That's why I have a second DC everywhere even if it's a virtual machine. :)
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Lee W, MVPTechnology and Business Process AdvisorCommented:
The FSMO roles allot batches of IDs for various domain functions... in SOME cases, they are only referenced when another DC runs out of (gets low on) things like SIDs for user accounts.  Technically you should be fine to create new users and computers - BUT, you SHOULDN'T DO IT because the SBS server, when created there, will setup the accounts properly for your domain.  The wizards from SBS will not extend to the second server.  The second server should, in some respects, be considered Read Only and essentially as a backup to preserve your AD should the primary server fail - that is, YOU should not make any direct changes on it, other than, if necessary, resetting a person's password.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ah thanks leew, i should have specified that i haven't used SBS for a while, didn't know that about it.
Lee W, MVPTechnology and Business Process AdvisorCommented:
For example when created with the wizard, they will belong (be prompted to confirm that they should belong) to the proper groups, create an exchange mailbox, etc.  None of this happens if you set them up on the non-SBS DC.
roger_rexAuthor Commented:
Hi Leew,

I found your comment is impressive.

Just want a clarification. Can we create an account on second DC, while SBS is offline, and create a corresponding mailbox, when SBS comes back?

IMHO, group membership should not be an issue, as those groups will exist on second DC. Moving an account among the groups also is an easy task.
Lee W, MVPTechnology and Business Process AdvisorCommented:
I didn't say group management was difficult.

And yes, you can create an Exchange Mailbox later...

BUT, WHY would you make your priorities creating a user account and not getting the server running again?  Why would you not wait to get the SBS Server running appropriately?  

I'm not saying you WILL have problems, but SBS is designed to be managed by wizards with the wizards taking care of various tasks.  When you don't use the wizards, you open yourself up to sporadic problems - a user created with the wizards may not be otherwise identical to one that is created through "standard" means.  I've never taken the time to compare the differences in differently created user accounts in SBS - seemed pointless since the SBS server will never be down for an extended period with a good backup and recovery plan in place and a good warranty.

Frankly, if you want redundancy, I'd suggest putting SBS on a virtual machine running off the server.  If the server fails (anything short of catastrophic hard disk failure), you can just copy the VHD off the server hard drives and boot it from a laptop, desktop, another server - whatever, and be back in business in minutes.
roger_rexAuthor Commented:
Hi Leew,

That's great!

Your comments really help, even though I do not love to rum my SBS from VM, for performance reason. My hardware is not that strong.

Really appreciate you guys sparing time to answer me!

Points awarded!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.