Windows Server 2008 Thread, Full system restore and AD woes in Technical; I've already given up on this issue and initiated a full server rebuild and restore from scratch, but this baffled ...
7th January 2011, 06:54 PM #1
Full system restore and AD woes
I've already given up on this issue and initiated a full server rebuild and restore from scratch, but this baffled me and I'm adamant I'll found out what it is!
Story is as follows (sorry, no TL;DR version)
Server arrives with a HDD failure, one of 4 in a RAID10 (SATA drives on ICH9r controller with Adaptec hardware interface, onboard) had gone. No worries, replace and it'll rebuild. Unfortunately the people that got hold of it before me neglected to check the backup tapes worked/contained good backups, and proceeded to *format and rebuild the entire array*
At this point I butt in and tell them I'll sort it out. Wanted to rebuild as Raid5 with a hotspare but chipset didn't support it (HP ML150 G5 - real POS). Rebuilt array to start from a clean plate, installed plain OS (Server 2008 x64) and cobbled together a workable system from 4 different backups. Finally booted into DSRM and recovered systemstate and AD successfully. Tested, all working OK - DHCP, DNS, AD, all working 100% perfect. Over the moon and left it in the storeroom until it would be delivered after Christmas.
So I return this week and decide to give it another test session before sending it back to site. Hangs on detecting the HDD - bugger, that's another one gone. Another HDD arrives, wang it in place of the faulty unit, add as a hotspare, restart, lo and behold it builds into the array and it looks happy. Restart server and get to logon prompt.
"Wrong username or password"
No, it's not. Reboot into DSRM.
"Wrong username or password"
Reboot into Safe mode. It logs in! Don't understand. Rebooted into normal mode and leave it at login screen. We also have a member server in from the same site, so hook it up to a switch with the main DC (being recovered). I can log in fine. AD is surely working. So to make sure it wasn't a cached resource, I used the Utilman.exe hack to get me to the command prompt on the DC. Created a new user, lo and behold I can log into it from the member server. But still can't on the DC.
Also reset the admin password from the same utilman hack with net user administrator password - this change takes effect on the member server (no AD or replication, mind) but not on the local machine.
Could only think that AD was generally naffed, but backupexec then stopped working and refused to let me restore systemstate & AD. At this point I ghosted the entire machine as it stood and left it as it is now, doing a full rebuild from scratch.
Any ideas why this would have happened? Degraded array shouldn't cause that surely?
2nd February 2011, 01:31 PM #2
- Rep Power
So the long and short of this is failed Hard Disk was replaced, then you wanted to use DSRM for which you think you have the password for but it doesn't work. Am I right? If so......
I'm certain that when you add a Server to any Domain it prompts you for DSRM password before it continues installing AD onto the Server, which can be different (user specified) to the Administrator account password specified at server initial build stage (long time since I've done it so not 100% sure). Maybe the password entered for DSRM at the time AD was added isn't the password you have! Which would explain you using Administrator password and getting nowhere.
Just a thought?
By DaveP in forum Downloads
Last Post: 3rd May 2011, 09:54 AM
By morganw in forum Windows
Last Post: 9th June 2010, 11:32 AM
By ste78564 in forum Windows
Last Post: 28th September 2009, 05:30 PM
By sparkeh in forum Windows Server 2000/2003
Last Post: 9th July 2009, 01:07 PM
Last Post: 11th October 2006, 10:20 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)