Skip to main content

How To Reset a Windows 7/windows 2008 r2 server Password

  1. Problem:-image[2]
    .Insert either your Windows 7 installation DVD, or a Windows 7 System Repair disc, into your optical drive and then restart your computer. If you have either on a flash drive, that'll work too.
    Tip: See How to Boot From a CD, DVD, or BD Disc or How to Boot From a USB Device if you've never booted from portable media before or if you're having trouble doing so.

  2. After your computer boots from the disc or flash drive, click Next on the screen with your language and keyboard choices.
    Tip: Don't see this screen or do you see your typical Windows 7 logon screen? Chances are good that your computer booted from your hard drive (like it normally does) instead of from the disc or flash drive you inserted, which is what you want. See the appropriate link in the tip from Step 1 above for help.
  3. Click on the Repair your computer link.
    Note: If you booted with a system repair disc instead of a Windows 7 installation disc or flash drive, you won't see this link. Just move on to Step 4 below.

  4. Wait while your Windows 7 installation is located on your computer.
  5. Once your installation is found, take note of the drive letter found in the Location column. Most Windows 7 installations will show D: but yours may be different.
    Note: While in Windows, the drive that Windows 7 is installed on is probably labeled as the C: drive. However, when booting from Windows 7 install or repair media, a hidden drive is available that usually isn't. This drive is given the first available drive letter, probably C:, leaving the next available drive letter, probably D:, for the next drive - the one with Windows 7 installed on it.
  6. Select Windows 7 from the Operating System list and then click the Next button.
  7. From System Recovery Options, choose Command Prompt.

  8. With Command Prompt now open, execute the following two commands, in this order:
    copy d:\windows\system32\utilman.exe d:\
    
    copy d:\windows\system32\cmd.exe d:\windows\system32\utilman.exe
    
    To the Overwrite question after executing the second command, answer with Yes.
    Important: If the drive that Windows 7 is installed on in your computer is not D: (Step 5), be sure to change all instances of d: in the commands above with the correct drive letter.

  9. Remove the disc or flash drive and then restart your computer.
    You can close the Command Prompt window and click Restart but it's also okay in this situation to restart using your computer's restart button.

  10. Once the Windows 7 logon screen appears, locate the little icon on the bottom-left of the screen that looks like a pie with a square around it and then click it!
    Tip: If your normal Windows 7 logon screen did not show up, check to see that you removed the disc or flash drive you inserted in Step 1. Your computer may continue to boot from this device instead of your hard drive if you don't remove it.

  11. Now that Command Prompt is open, execute the net user command as shown, replacing myusername with whatever your user name is and mypassword with whatever new password you'd like to use:
    net user myusername mypassword
    
    So, for example, I would do something like this:
    net user sbt crazyitpro
    

  12. Close the Command Prompt window.
  13. Login with your new password!

  14. While not required, it would probably be wise to undo the hack that makes this work. If you don't, you won't have access to accessibiily features from the Windows 7 login screen.
    To reverse the changes you've made, repeat Steps 1 through 7 above. When you have access to Command Prompt again, execute the following:
    copy d:\utilman.exe d:\windows\system32\utilman.exe
    
    Confirm the overwrite and then restart your computer.

Comments

Popular posts from this blog

Duplicate IP Address has been Detected Rule

A duplicate IP address has been detected on the network Rule Knowledgebase Summary This rule generates an alert when Windows® detects that he local machine’s IP address is in conflict with one or more identical IP addresses on the network. Until the IP address conflict is resolved, remote clients and applications may have difficulty accessing resources on any of the effected computers. Additionally, the local computer may not be able to access network resources. Related Events This rule generates an alert whenever the following events occur and are recorded in the System Event Log: The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCPIP; Event ID: 4198; The system detected an address conflict for IP address %2 with the system having network hardware address %3. The local interface has been disabled. Source: TCP...

Schedule Automatic backup config in Cisco Nexus

Schedule Automatic backup config in Cisco Nexus Nexus-Sw1(config)#feature scheduler   //Enable scheduler service in Nexus Nexus-Sw1(config)#scheduler job name backup-daily      // Job Name Nexus-Sw1(config)#scheduler aaa-authentication username abcd password abcd@123     // AAA - Authentication for Job created above (If AAA configured) Nexus-Sw1(config)#scheduler job name backup-daily copy running-config tftp://192.168.1.23/$(SWITCHNAME)-cfg.$(TIMESTAMP)         //IP of TFTP SERVER , file will saved with switch name and timestamp exit Nexus-Sw1(config)#scheduler schedule name backup-daily   // Setup Schedule to run for the JOB Nexus-Sw1(config-schedule)# time ?   daily    Specify a daily schedule   monthly  Specify a monthly schedule   start    Specify a future time schedule   weekly   Specify a weekly schedule...

VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA

Source Knowledge From :-  http://geekswing.com/geek/vmware-cpu-and-ram-reservations-fixing-insufficient-resources-to-satisfy-configured-failover-level-for-ha/ VMware CPU and Memory Reservations: Fixing Insufficient resources to satisfy configured failover level for HA This post comes from a few days of poring over manuals as well as some technical support. This is a good one. The error came from trying to power on a VM in our VMware cluster and we would get these errors: “Insufficient resources to satisfy configured failover level for HA” And this alert on our cluster “Insufficient resources to satisfy HA failover level on cluster vmCluster in vmTST” Our way of thinking was we had to power one off to power another one on. But that didn’t work. Here we is the actual solution. (p.s. Great VMware HA education for me on this one!) PROBLEM SOURCE: VMware HA is turned on and you are violating constraints VMware HA is turned on, and you have i...