Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 507
  • Last Modified:

New Windows 2008 R2 server AD install problem

New Windows 2008 R2 server rebooted after AD and DNS server install, during which setup only asked for Directory Services repair password, which I have. After reboot will not accept Local Administrator password, which I also have. I didn't see any request to enter Domain Adminstrator password (did I just miss it?) during the AD install.  I can boot to Directory Services Repair in safe mode using Directory Services Administrator password.  System tells me AD and DNS are not installed.
I would like to either:
1. Revert to pre AD install (I have no backup of machine)
2. Reset Administrator password

Since this is a pre-production machine I could re-install, but that is my last choice.
0
jsvarga88
Asked:
jsvarga88
  • 3
1 Solution
 
PhilonatorownerCommented:
2cents- I have found that 2008 r2 installs so fast that it is often faster to just reinstall then trouble shoot problems with clean installs.
0
 
jsvarga88Author Commented:
That may be necessary, but is my last option - I have one more server to configure, and I don't want to make the same mistake again, since I don't know what I did incorrectly.
0
 
woolnoirCommented:
I understand that, but its hard for us to guess what is setup incorrectly without some diagnosis to go on.
0
 
jsvarga88Author Commented:
Have the correct Local Admin Password, and after reboot and attempt to logon using these credentials again, it started to log on, "Welcome" then came back with message "There are no logon servers available to service the logon request"
0
 
jsvarga88Author Commented:
A reinstall was necessary, thanks.
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now