MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

MHousler — Fri, 08 Jul 2011 12:09:31 GMT

Is there any easy way to turn it back on to systems I've already pushed out? I have probably 30 machines out there before I figured it out and found this thread :(

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Adam — Thu, 31 Mar 2011 23:28:12 GMT

What is the fix for those machines that have already been deployed before catching that System Restore is disabled. To my knowledge, there is no option via GPO to "enable" system restore - only an option to disable it.

Any ideas on that guys?

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Michael Niehaus — Thu, 06 Jan 2011 16:10:49 GMT

You don't even need to rename the "GetObject" function, just delete it altogether. I'm not sure how that one slipped through...

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Jaybird283 — Thu, 30 Dec 2010 23:50:10 GMT

Craig Walls Post worked for me. Thanks! i have been trying to figure this out all day...

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Jaybird283 — Thu, 30 Dec 2010 23:19:02 GMT

Are there any side effects after changing the name of that function? i am having the same problem and i am testing your theory now.

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Craig Walls — Tue, 30 Nov 2010 07:15:06 GMT

We've just been troubleshooting the LTICleanup.WSF script and discovered that there is a FUNCTION declared called GetObject which is breaking the script.

We've renamed the function to LTIGetObject and now the script does more of the things it's supposed to... :-) The GetObject function doesn't actually seem to be called by anything, so as far as I can tell it was only put in to ruin my day...

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Sam R — Fri, 05 Nov 2010 21:30:06 GMT

Bah, my VB king-fu is weak. Still, LTICleanup is running out of juice somewhere between copying the logfiles to windows\temp and re-enabling SystemRestore. The minint folder is still there, with only a couple of files in it - that may be a clue. Adding lots and lots of logging entries and trying again...

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

Sam R. — Fri, 05 Nov 2010 19:31:38 GMT

We're still getting Win7 deploys with SystemRestore turned off. After reading this post I took a look at the EnableSystemRestore function in LTICleanup.wsf, grabbed it and ran it as a standalone VBS - still nothing. Then I commented out the On Error statements and got the following:

Microsoft VBScript runtime error: Type mismatch: 'oEnv'

I am currently testing with the following code for Function EnableSystemRestore (yeah its probably ugly, if it works I don't care):

Dim iRetVal, oSRP

strComputer = "."

On Error Resume Next

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\default")

Set oSRP = objWMIService.Get("SystemRestore")

iRetVal = oSRP.Enable("")

On Error Goto 0

EnableSystemRestore = iRetVal

re: MDT 2010 Update 1: Fix to re-enable System Restore in ConfigMgr task sequence

ConfigMgr #1 Fan — Wed, 11 Aug 2010 00:10:01 GMT

Does this exclude servers such as Windows Server 2008 / Windows Server 2008 R2 where System Restore is disabled?