Redo-SbecActiveConfig is accessible with the help of BootEventCollector module. To configure BootEventCollector, go through this link.


Redoes a change to the current active configuration.


The Redo-SbecActiveConfig cmdlet redoes a change to the current active configuration. This operation is the opposite of undoing a change to a configuration.

If multiple backup configuration files are available, you can apply Undo and Redo operations sequentially to move through the configurations backwards and forwards.

If the previous active configuration was not itself restored but set afresh (or checkpointed after restore), it is saved in a backup file. When doing multiple undo/redo/restore commands in a sequence, the intermediate configurations are not saved in the new backup files. A configuration from undo/redo/restore commands is automatically considered checkpointed if it was left unchanged for an hour.

You can use the OldTimestamp parameter to modify the configuration atomically.

The restored configuration is re-checked for validity, and refused if it has become corrupted.

You must have the Builtin Administrator privilege to run this command.



Runs the cmdlet on the remote computers through a remote session. Enter a session object, such as the output of a New-CimSession or Get-CimSession cmdlet, or an array of these objects. The default is to run the cmdlet on the local computer. For more information, see About_CimSession.

Default value:None
Accept pipeline input:False
Accept wildcard characters:False


Specifies the names of the computers on which you want to perform the operation. You can specify a fully qualified domain name (FQDN), a NetBIOS name, or an IP address for each computer. For more information see Invoke-CimMethod on MSDN.

Default value:None
Accept pipeline input:False
Accept wildcard characters:False


Specifies that this operation will not throw an exception if a failure occurs. Instead the caller should examine the output of the cmdlet for the error information.

Default value:None
Accept pipeline input:False
Accept wildcard characters:False


Specifies the timestamp of the previous active configuration. This provides a way to perform the atomic changes of the configuration. Each configuration has a timestamp (the time when it was last set or restored) and an original timestamp (if the configuration was restored, the time when it was originally set, otherwise the same as the normal timestamp). This operation checks that the OldTimestamp value matches either the normal or original timestamp of the current active configuration thus ensuring that the active configuration wasn’t changed since the last time you have looked at it. If the values do not match, an error is returned.

Default value:None
Accept pipeline input:False
Accept wildcard characters:False


Redo-SbecActiveConfig [[-OldTimestamp] <UInt64>] [-Continue] [[-ComputerName] <String[]>] [[-CimSession] <CimSession[]>] [<CommonParameters>]

—————–Example 1—————–
Redo a configuration change
PS C:\> Redo-SbecActiveConfig -Continue | Format-List
This command redoes a configuration change. Format-List displays the information that the command returns.

—————–Example 2—————–
Redo two configuration changes
PS C:\> $res = Redo-SbecActiveConfig; $res = Redo-SbecActiveConfig -OldTimestamp $res.OriginalTimestamp
This command consecutively redoes two configuration changes, ensuring that no other changes are done in between, and throwing on errors. This requires that the configuration was previously undone at least twice from the most recent one.

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Redo-SbecActiveConfig

Get-Command Redo-SbecActiveConfig powershell script command cmdlet

You can also read about

  • Checkpoint-SbecActiveConfig
  • Get-SbecBackupConfig
  • Restore-SbecBackupConfig
  • Set-SbecActiveConfig
  • Undo-SbecActiveConfig

To know more PowerShell cmdlets(Commands) on BootEventCollector click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft

Leave a Reply

Your email address will not be published. Required fields are marked *