Windows 2003 instantly logs off admin while in DSRM
Hi all,
We're trying to migrate the OS of an old server machine to a new one (VMware environment, that works so far).
If we boot the new machine (Windows 2003), single domain controller, we get the error we need to reboot into DSRM.
problem is: if presented with the logon in DSRM mode, the server logs on and then instantly logs off. First thought was maybe we used to wrong password, so we resetted the DSRM password on the old server (kb article http://support.microsoft.com/kb/322672) and took a new offline backup. Same problem after restore of the new backup.
Any other ideas?
We're trying to migrate the OS of an old server machine to a new one (VMware environment, that works so far).
If we boot the new machine (Windows 2003), single domain controller, we get the error we need to reboot into DSRM.
problem is: if presented with the logon in DSRM mode, the server logs on and then instantly logs off. First thought was maybe we used to wrong password, so we resetted the DSRM password on the old server (kb article http://support.microsoft.com/kb/322672) and took a new offline backup. Same problem after restore of the new backup.
Any other ideas?
Last Comment
What method did you use to migrate the data from the old system? First guess is the drive permissions are incorrect.
ASKER
Used shadow protect recovery cd.
Booted the old server with the recovery cd -> started full backup to USB disk.
The software takes a full image of the partitions on the harddisk.
Restored backup boots and everything. Only the AD gives the error. I've seen before that "changing" the network hardware adapter can also affect active directory but i don't know if it has anything to do with this.
We wanted to avoid a new server installation so we don't have to rejoin all pc's in the domain.
Booted the old server with the recovery cd -> started full backup to USB disk.
The software takes a full image of the partitions on the harddisk.
Restored backup boots and everything. Only the AD gives the error. I've seen before that "changing" the network hardware adapter can also affect active directory but i don't know if it has anything to do with this.
We wanted to avoid a new server installation so we don't have to rejoin all pc's in the domain.
ASKER
hmm not sure. But when booting with a bartpe cd in restored environment, it sees partition C (original server) as D and partition D as C.
could it be the restored OS also recognizes the partitions in the wrong order?
could it be the restored OS also recognizes the partitions in the wrong order?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Active Directory
Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.
86K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
