6 comments on “Connected Standby and OS Deployment

  1. I set up something like this, only I was setting the active power to Max Performance (as I’m dealing with servers). I would recommend using a VBScript to do this so that you can have some error checking in your command. Here’s my (super slimed down, no commented script).

    This way it will log to your SLShare and C:\Windows\Temp folder if you need to go back and check to see that this processed.

    Option Explicit
    Dim iRetVal
    On Error Resume Next
    iRetVal = ZTIProcess
    ProcessResults iRetVal
    On Error Goto 0
    Function ZTIProcess()
    Dim sCommand
    Dim sConfigname

    sConfigName = “Config-OSPowerCFG”
    oLogging.CreateEntry sConfigName & “: Starting ” & sConfigName, LogTypeInfo

    ‘//Set Commands to run
    sCommand = “powercfg -setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c”

    ‘//Run commands
    iRetVal = oShell.Run(sCommand)
    oLogging.CreateEntry “Running ” & sCommand, LogTypeInfo
    oLogging.CreateEntry sConfigName & “: Return code from command = ” & iRetVal, LogTypeInfo

    oLogging.CreateEntry sConfigName & “: Finished ” & sConfigName, LogTypeInfo

    End Function


  2. Pingback: The Myth of the Low-Cost Windows Alternative | Trials of a Network Admin

    • I think it would just be a matter of changing the “0” in the commands to your desired timeout, but haven’t tested it. As mentioned we use 3rd party software for power management. Good luck!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s