Skip to main content

Question: Does Windows Server 2008 have System Restore Points.

I’m sorry to say that no, it does not. Take a look at the second Note at the bottom of this article: http://support.microsoft.com/kb/926185

It would be nice for those using Server 2008 as a workstation OS, but it looks like we will have to rely on Volume Shadow Copy Service and good old backups.

Update to this article - May 8, 2009

For those of you running your environments in Hyper-V and want some sort of system restore, take a look at Hyper-V snapshots. Just remember to keep your data elsewhere and to thoroughly test using snapshots before using them in a production environment.

Comments

Anonymous said…
This comment has been removed by a blog administrator.
You can follow my Twitter account @JasonYoder_MCT. Also you can do a search for MCTExpert on Facebook.
Anonymous said…
dism /online /enable-feature /featurename:WindowsServerBackup
dism /online /enable-feature /featurename:WindowsServerBackupCommandlet

followed by a reboot will get you back the good old system restore point tab.

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...