Pages

Saturday, June 2, 2012

Automatically log off when I login in my Windows Server 2003

Wow I had this happen to me and it sucked big time. What I did to fix it was boot to the recovery console (safe mode works better if you can get to it) by finding your install cd and running a recovery console and then using system restore (kind of) from with in there. If you already tried running checkdisk and fix boot skip down to the second 12 steps below the dashed line.

1. Insert the Windows 2003 cd into the top cd drive
2. Turn the computer off
3. Setup the computer to boot from cd: either by pressing F2, F9 or Delete to go in BIOS or by pressing F12 on Dell computers to launch the Boot Device Menu
4. As soon as you get the message Press any key to boot from the cd hit enter.
5. Wait ~3 minutes for the Windows Setup to initialize
6. At the Welcome to Setup screen press R to repair windows using recovery console.
7. Wait a couple of minutes while setup examines the hard drive.
8. You will be prompted to choose a Windows installation. Press 1 on the top of the keyboard and then
9. You will be prompted to enter the Administrator password. Press Enter if no password was set.
10. Perform a disk check:

chkdsk /p
fixboot

11. Type exit to restart the computer.
12. As soon as the computer starts hit F8 every second to bring up the Advanced Options Menu.
13. Choose the Last Known Good Configuration.
14. If these steps didn't resolve the issue go back in Recovery Console and this time run the system restore.
_______________________________________________--

1. launch the recovery console just like before.

2. When you’re at the Recovery Console command prompt, change into the root directory of the system drive with the cd command (i.e., cd \).

3. Change into the System Volume Information directory by typing cd system~1 on most machines, or cd “System Volume Information.”

(The filenames with ~1 are generated by default to provide backwards compatibility with programs that only recognize 8.3-format filenames. It’s possible to disable 8.3 filename generation on NTFS volumes to gain some speed, but the speed gained by doing this is generally pretty small and it can have the unintended consequence of making it impossible to use 8.3 filenames in contexts like this. If you can’t use 8.3 filenames to navigate, 8.3 name generation might be disabled. See Microsoft’s support document called How to Disable the 8.3 Name Creation on NTFS Partitions.

4. The System Volume Information directory contains a folder name _restore followed by a GUID in curly braces. Change into it by typing cd _resto~1; if that doesn’t work you’ll have to type cd “_restore{GUID_STRING}”, with the full GUID string in place of GUID_STRING.

5. In the _restore directory are a group of subdirectories starting with the letters RP and followed by a number. These are the different restore points available for that volume.

6. Check the date on each directory and look for one that corresponds to a date before you began experiencing problems.

7. Change into the appropriate directory. If the directory is named RP74, for instance, change into it by typing RP74.

8. Inside that directory will be a subdirectory named snapshot; change into that directory as well (cd snapshot)

9. The snapshot directory holds backup copies of the SOFTWARE and SYSTEM Registry hives, named _REGISTRY_MACHINE_SOFTWARE and _REGISTRY_MACHINE_SYSTEM, respectively.

10. The target directory for these files is \Windows\System32\Config, and the hives there are named SOFTWARE and SYSTEM. Rather than overwrite those files entirely, you can rename them to something else. Typing ren \windows\system32\config\software \windows\system32\config\software.bak and ren \windows\system32\config\system \windows\system32\config\system.bak will rename them to software.bak and system.bak, respectively.

11. Copy in the backup hives: copy _REGISTRY_MACHINE_SOFTWARE \windows\system32\config\software and copy _REGISTRY_MACHINE_SYSTEM \windows\system32\config\system.

12. Type exit to leave the Recovery Console and restart the computer.

No comments:

Post a Comment