Skip to main content

What does the Create a system repair disk do?

For those of us who have been around the IT world for a while, we know the pains of using the Windows recovery tools. For the 2000 and 2003 servers, we had the recovery disk that rarely worked. This all changed with Windows Vista and Windows 7. The recovery environment for both of these operating systems run in a graphical interface that is built on Windows PE.

To access the recovery environment for Windows 7, you have two methods. You can boot from the installation media or create a recovery disk from the installation media. To get to the recovery environment, boot from the Windows 7 media. Click Next to confirm your language and time. At this point you will be presented with the option to Install Windows 7. If you look to the lower left of that window, you have the option to enter the recovery environment.

This environment will allow you to run Startup Repair, System Restore, System Image Recovery, Windows Memory Diagnostics, and Command Prompt.
To create a system repair disk that will be bootable, and contain all these tools, log into Windows 7. Click Start --> All Programs --> Maintenance --> Create a System Repair Disk.

Reference: http://www.winhelponline.com/blog/create-system-repair-disc-windows-7-and-vista/

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...