Start-LogHighLevelOperation creates a log entry to record the start of a high level operation.
Start-LogHighLevelOperation can be called to log high level configuration changes which originate from customized configuration scripts. Start-LogHighLevelOperation should be called before the script invokes service SDK cmdlets which execute the configuration changes.
Start-LogHighLevelOperation returns a HighLevelOperation object which contains information about the started high level operation. The "Id" property of the returned HighLevelOperation uniquely identifies the started high level operation. This can be supplied into the "-LoggingId" parameter which is implemented in all service SDK cmdlets which execute loggable configuration changes.
High level operation logs are automatically created by the XenDesktop consoles when:
o Initiating an operation which performs configuration changes.
o Initiating an operation which performs an administration activity.
Configuration Change and Administrator Activity
A configuration change is an operation which alters the configuration of the XenDesktop site. Examples of a configuration changes include:
o Creating or editing a host.
o Creating or editing a catalog.
o Adding a user to a delivery group.
o Deleting a machine.
An administrator activity operation doesn't directly alter site configuration, but it could be an operation carried out by an administrator as part of site management or helpdesk support. Examples of administrator activities include:
o Shutdown/start/restart of a user desktop.
o Studio or Director sending a message to a user.
o Rebooting a user's desktop.
Once the change being logged has completed (whether successfully or not) the Stop-LogHighLevelOperation cmdlet should be called to log the completion of a started high level operation.