System will not logon user on after deploying an image
I made an image on Drive Image 2002, it was on a different hd than the one i have now. So I deployed the image to the new drive, and windows got to the logon screen but would not come up with a logon prompt or nothing just a dumb stupid LogonUI window in the middle of my screen.
I made an image on Drive Image 2002, it was on a different hd than the one i have now. So I deployed the image to the new drive, and windows got to the logon screen but would not come up with a logon prompt or nothing just a dumb stupid LogonUI window in the middle of my screen. My question is how do i stop this from happening?? I would like to be able to use my image disks but windows will not let me logon. I even tried recovery console and it would not let me logon to the installation. So do i have to make a whole new image set to get this to work or what??
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Just want to clarify something...
You made an Image of your old drive on a new drive, for the exact same machine, and now you can no longer login? Does it reject every username and password? Or does it just hang before the login process?
1. NTRIGHTS.exe from the resource kit allows you to restore "interactive logon permissions"
2. What file system were you copying, and does Drive Image 2002 support it?
3. If there is network activity ... can you ping the machine ... if so ... can you check the event logs remotely?
Sounds like LASS.exe or winlogon.exe is hanging
Need more info....
You made an Image of your old drive on a new drive, for the exact same machine, and now you can no longer login? Does it reject every username and password? Or does it just hang before the login process?
1. NTRIGHTS.exe from the resource kit allows you to restore "interactive logon permissions"
2. What file system were you copying, and does Drive Image 2002 support it?
3. If there is network activity ... can you ping the machine ... if so ... can you check the event logs remotely?
Sounds like LASS.exe or winlogon.exe is hanging
Need more info....
Simple fix! I ran ino this and found a solution.
fdisk /MBR
The problem is, the drive image did not copy the old disk signature, and there was probably a signature on there already (In the mbr) and when windows does not see the same signature as it expects, it will fail nd do this. Last known goodf won't help because it thinks yo have logged on properly... hehe
Fdisk/mbr will remove all signatures from the MBR (even on NTFS drives) and it will not destroy your data. When windows sees no signature at all, it will write a new one to the disk and all will be well.
Cheers.
BTW, you get fdisk /mbr from a win98 bootdisk. do it in dos.
fdisk /MBR
The problem is, the drive image did not copy the old disk signature, and there was probably a signature on there already (In the mbr) and when windows does not see the same signature as it expects, it will fail nd do this. Last known goodf won't help because it thinks yo have logged on properly... hehe
Fdisk/mbr will remove all signatures from the MBR (even on NTFS drives) and it will not destroy your data. When windows sees no signature at all, it will write a new one to the disk and all will be well.
Cheers.
BTW, you get fdisk /mbr from a win98 bootdisk. do it in dos.
ah cool i thought i did that, and it mustve been on the wrong disk or something. One way or another i ended up losing a whole partition trying to get the damn thing too boot by f-in around with bootmagic. Got the partition data back mostly. A few things i wanted i couldnt get back, but i will have to try and f-around with it on an old hard drive or something. Thanks for the info, i assumed since it booted that it saw the boot signature fine. It wouldve been nice to find it in powerquest's knowledge base, but its too hard to hunt around for your answer in those sometimes =-/.
