Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.
Server 2003 demote issue
I went through DCPROMO of our last server 2003 DC to make it a member server but now it's just stuck at "making network connections".
What I did:
-this existing network is Server 2008R2 network with a 2008R2 DC and server 2012R2 DC (2003 functional domain)
-these servers are now primary DNS servers in DHCP settings
-all FSMO roles transferred successfully to 2008 DC
-remove 2003 server as GC
-exported from 2003 DC to 2008 DC
-run DCPROMO
-it failed somewhere at NETLOGON finding 2008 DC
-DCPROMO wizard ended unsuccessfully
-checked NIC setting on this 2003DC and saw that it was pointing to itself as primary DNS server; changed it to 2008 DC
-Ran DCPROMO again and this time it conmpleted successfully.
-rebooted and now stuck at "making network connections"
-checked AD sites and services and NTDS folder now gone from 2003 server as it should be
-AD users and computers shows it in Computers not Domain Controllers as it should
-Have rebooted in without LAN cable plugged in but just sits there for hrs
-booted in safe mode with networking but sits there with same msg
I'm at a loss. I need this server up as a member server.
What I did:
-this existing network is Server 2008R2 network with a 2008R2 DC and server 2012R2 DC (2003 functional domain)
-these servers are now primary DNS servers in DHCP settings
-all FSMO roles transferred successfully to 2008 DC
-remove 2003 server as GC
-exported from 2003 DC to 2008 DC
-run DCPROMO
-it failed somewhere at NETLOGON finding 2008 DC
-DCPROMO wizard ended unsuccessfully
-checked NIC setting on this 2003DC and saw that it was pointing to itself as primary DNS server; changed it to 2008 DC
-Ran DCPROMO again and this time it conmpleted successfully.
-rebooted and now stuck at "making network connections"
-checked AD sites and services and NTDS folder now gone from 2003 server as it should be
-AD users and computers shows it in Computers not Domain Controllers as it should
-Have rebooted in without LAN cable plugged in but just sits there for hrs
-booted in safe mode with networking but sits there with same msg
I'm at a loss. I need this server up as a member server.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
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.
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
try to boot 2003 server in "Safe Mode", check the windows event, then try to start server in "Safe mode with networking".
As I mentioned I already tried Safe Mode and get stuck at "making network connections".
I will try NTDSUtil to cleanup AD metadata.
I really need to be able to login back into this server. I'm onsite tomorrow AM. We want to to continue to use this server if possible as a member server as it hosts AUTOCAD and some user files. At the very least be able to access the drives and remove the user files. Its and HP Proliant server with 3 drives in RAID 5.
I will try NTDSUtil to cleanup AD metadata.
I really need to be able to login back into this server. I'm onsite tomorrow AM. We want to to continue to use this server if possible as a member server as it hosts AUTOCAD and some user files. At the very least be able to access the drives and remove the user files. Its and HP Proliant server with 3 drives in RAID 5.
Followed the last part, If the domain controller cannot start in normal mode
in the following link;
http://support.microsoft.com/kb/332199
in the following link;
http://support.microsoft.com/kb/332199
I've requested that this question be closed as follows:
Accepted answer: 0 points for Celica1's comment #a40642819
for the following reason:
Other suggestions did not resolve my problem
Accepted answer: 0 points for Celica1's comment #a40642819
for the following reason:
Other suggestions did not resolve my problem
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
Windows Networking
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MOS Microsoft Office Specialist - Excel 2016 Part … 129 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
netdom query dc
netdom query fsmo
nslookup domain.com
If you do not see the 2003 server in the list you are probably safe. I would then check the domain controllers OU, and also the _msdcs.domain.com folder in DNS to make sure that it is not listed under any.
I would also use NTDSUtil to ensure/cleanup any other remnants from this domain controller if any.
http://support.microsoft.com/kb/216498?
Will.