Hardware Thread, OH Flipping heck server has died in Technical; Originally Posted by Duke
Only good news is that this is your chance to turn to management and say " ...
23rd March 2010, 01:10 PM #16
Very true. Last summer's disk failure on my one and only server was when I finally got the go ahead to plan for a second server (but can't get it until this summer )
Originally Posted by Duke
23rd March 2010, 01:11 PM #17
I know you've already had a but of stick for this but I've been studying for my MS Certs of late and this has come up in the study material -
Originally Posted by srochford
[grabs book to refresh memory]
The RID Master, Schema Master and Domain Naming FSMO's CAN NOT be transfered back if you force transfer them to another DC. Very important (as in can screw up AD big time) DO NOT reactivate a server if you have force transfered any of these roles away from it.
If you have force transfered these roles then you will have to rebuild the DC from scratch.
Also, I'm not 100% if you can make (or should) make another server a GC if the original GC is off line and/or there are no other active GC's on the network. Does it not have to copy the data from them? Can this cause replication problems if a new GC is created and creates a new version of this data?
EDIT: just to be clear this is an issue with force transfering or siezing FSMO roles. If you cleanly transfer the roles without seizing them then you don't have this problem and AFAIK you can transfer the roles back. Of course the existing server with these roles needs to be up for you to cleanly transfer the roles.
Last edited by tmcd35; 23rd March 2010 at 01:13 PM.
23rd March 2010, 01:15 PM #18
He's right! Only transfer those rolls if that DC is totally completeley and utterly dead and will be thrown in the bin. If on theother hand that DC is gonna be repaired and will come back up at some stage in the near future then you will end up in trouble!
23rd March 2010, 01:15 PM #19
Our business manager has a sign that she often fixes to her office door.
It says only to knock if the school is on fire.
Last edited by K.C.Leblanc; 23rd March 2010 at 01:28 PM.
23rd March 2010, 01:18 PM #20
Do you not run some scripts from you netlogon/sysvol share? That way they replicate between DCs and you can refer to them in group policy as \\domain\netlogon\script.vbs. Which will be flexible for any DC.
23rd March 2010, 01:44 PM #21
Its not get any of the FSO roles they are on the primary domain controller. I have got log on times to about 10 mins on older machines. That's not good but usable. Am waiting for the engineer praying he can come today. I am hoping its just the powerpack.
Pray Pray Pray
Any more ideas would be gratefully received.
23rd March 2010, 01:46 PM #22
surely if the server is not functioning correctly then stone should come out right away? Have you looked at your agreement contract?
23rd March 2010, 02:15 PM #23
Stone have just turned up now lets pray.
23rd March 2010, 02:27 PM #24
yipppppeeee we now have power and its chkdisking.
By wesleyw in forum Thin Client and Virtual Machines
Last Post: 2nd March 2010, 03:42 AM
By Gatt in forum Windows Server 2008
Last Post: 27th August 2009, 01:42 PM
By tech_guy in forum Other Stuff
Last Post: 26th September 2008, 05:47 PM
By reggiep in forum EduGeek Joomla 1.5 Package
Last Post: 17th June 2008, 11:23 PM
By ryan_powell in forum Wireless Networks
Last Post: 5th September 2007, 02:04 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)