Re: start over
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Wed, 13 Jun 2007 23:39:03 -0400
In news:7CC6F1E9-5FBD-43D3-BC60-D0B728A6FDA5@xxxxxxxxxxxxx,
Voytek <Voytek@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
We have taken over a network that's in pretty bad shape.
Its sbs 2003 and 2003 standard server that have not been replicated
in a while.
The AD structure looks corrupted. We wanted to demote the 2003
standard and have not been successfull. dcpromo returns all kinds of
errors
I would like to disconnect the SBS all together as it isn't used for
anything other then authenticating users. I want to remove the old
corrupted AD install from the 2003 standard server and later install
a new instance od AD (fresh copy)
What's the best way to remove ad on the 2003 server without
rinstalling the os Remember the dcpromo doesn't work
Thank you
You can run the dcpromo /forcedemote switch to yank AD, but keep in mind, I
have not tried it with SBS, only with non-SBS machines. SBS auto installs AD
and forcing a removal may corrupt the whole installation. Thats SBS for ya.
For more info, you can post to the SBS newsgroup. But honestly, I bet we can
get dcpromo to work, and the whole domain to work, for that matter because
more than likely, the two issues are probably related and possibly caused by
a misconfigured DNS issue. Post an UNEDITED ipconfig /all of the SBSand the
other server for starters to better help with this.
There's also the manual 14 step method too, but it is NOT supported by
Microsoft so don;t bother calling them if you mess this up:
14 Easy Steps:
1) On another DC in the domain run NTDSUTIL to move the FSMO's, er seize
them! DOH. (If this is the only DC, then don't worry about it)
2) Make sure DNS is 100% solid on the working DC. (If only one DC, don't
worry about it for now, but configure it correctly before promoting it to a
new DC).
3) Make sure working DC is also a GC. (If just one DC, don't worry about
it).
4) Boot corrupted DC into DSRM, edit the registry change
HKLM\SYSTEM\CCS\Control\ProductOptions change the ProductType value from
LanmanNT to ServerNT. This key dictates if the machine is a DC or just a
server. ServerNT means it's not a DC.
5)Command prompt > net stop ntfrs to stop FRS.
6) Delete the Winnt\Sysvol and NTDS directories.
7) Reboot the now former DC
8) Log into the now member server. Change it to a stand alone, by joining a
workgroup (My Computer Properties, Network ID tab, remove it from the old
domain).
9) Reboot the now stand alone server.
10) If there is only one DC in the domain, skip this step, otherwise, on the
good DC delete the disabled computer account for the old, now defunct DC.
11) Now on this new stand alone machine, set the Primary DNS Suffix to the
new domain name that you want (In My Computer. Properties, Network ID Tab,
Properties, More,). Reboot.
12. Make sure that DNS is configured with the new domain name and updates
set to YES.
13. Run DCPROMO to create a new domain or join the domain/tree/forest again.
14. Reboot.
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations
Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
"Quitting smoking is easy. I've done it a thousand times." - Mark Twain
.
- Follow-Ups:
- Re: start over
- From: Voytek
- Re: start over
- Prev by Date: Re: 3rd pary apps LDAP query
- Next by Date: Re: Fixing Replication Failures
- Previous by thread: Re: 3rd pary apps LDAP query
- Next by thread: Re: start over
- Index(es):
Relevant Pages
|
