HELP - I think I just screwed up!

[tazz]

Hi, I just thought I'd tidy up the AD and deleted some objects that I thought no longer existed - I inherited this network two years ago.

2 of these things were NTSRV1 and NTSERVER - we don't have any servers of that name so I deleted them. I was given a choice of demoting them as they were apparently DCs (but my 2 existing DCs still remain) but I chose an option along the lines of "this DC no longers exists and will never be used" or something.

Since then it is taking eons for users to log on to workstations. It takes ages to get past "loading your personal settings...." Logging off is still dead quick though.

Any tips will be most welcome!

[Dos_Box]

Oh.
Dear.
Right what you need to do first is to ensure that none of the FSMO roles were assigned to the old servers and that AD is pointing to the current role holders.

http://support.microsoft.com/kb/324801

Clear DNS of any referances of them if you can and ensure that they are not still listed as forwarders etc. Then check that their computer accounts are removed. I have to be honest here, I've had AD die before and nothing ever brings it back. Even schema restores are never sucessful. Unfortuneately AD is not perfect and does break easily.

[tazz]

I love you Dos_Box!

That worked - boy do I need to go on a course!!

[djm968]

Lucky Guy!

I had to rebuild two DC's from a Syatem State Backup becuase someone did exactly what you did 3 days work!

May I suggest that in future you consult edugoogle before you click OK in future.

That click could have cost you your Job and the School money to fix it.

[tazz]

Thanks djm, 'nuff said.

[djm968]

Thanks djm, 'nuff said.

Sorry just read that back and it sounded very condescending… ops:

[Heebeejeebee]

AD borked on us a few months ago and it took us 3 days to fix the servers and to go round all the machines and take them off the domain and put them back on again. (?) This was the only way we could get the machines to connect again after a System State restore.

Still not found the reason why it dropped a server out of AD but apparently it does happen.

HBJB

[Dos_Box]

I love you Dos_Box!

That worked - boy do I need to go on a course!!

I am glad, a borked AD is a heart stuttering affair at the best of times. Which bit fixed it BTW?

[zag]

I've had an "Active directory is re-indexing" >> "re-indexing failed please reboot your server" on our main DC a while back. That was fun repairing

Luckily you should always have 2 DC's in the school and I have learned to have them on simple workstations that can be easily fixed.

There are lots of knowledge based articles on removing a DC from the schema and DNS, its not really a complicated process but can solve alot of problems.

[Heebeejeebee]

Hmmm, here's something that I can't find by Googling: If one of your DCs has an issue with AD does that problem replicate to the others or do any others somehow know that it's borked and put a good copy back?

HBJB

[zag]

When mine went tits up the other DC was absolutely fine.

[tazz]

Changing the schema master role fixed it Dos_Box - thanks again.

I'm a lucky gal BTW djm968!

[djm968]

Changing the schema master role fixed it Dos_Box - thanks again.

I'm a lucky gal BTW djm968!

Sorry tazz........ I always put my foot in it! ops:

[Grommit]

One question......

If the DC with the FMSO roles on crashes can the users still log on ?

[djm968]

If the the DC is also the Global Catalog then not normally no. However you should not have all your eggs in one basket so to speak ie. split the rolls accross other DC's