Who deleted that deployment?

WhoDeletedThatDeploymentThis blog post will be a short follow-up post on my previous blog post about Who created that deployment?. This post will answer the, in most cases, less important question about who deleted that deployment. Just like the information about the creation of a deployment, the information about the deletion of a deployment is also stored in the database.

Use the same buildin report named All messages for a specific message ID to track the deleted deployment. Again, the only missing detail is that it’s not clear which Message ID belongs to which action. The following table provides an overview with exactly that information. It will show per object type which Message ID belongs to the deletion of a(n) deployment/ assignment.

Object Status Message Message ID
Application User “<>” deleted the deployment of application “<>” to collection “<>”. 30228
Package User “<>” deleted a deployment named “<>” deploying program “<>”. 30008
Task Sequence User “<>” deleted a deployment named “<>” deploying program “<>”. 30008
Software Updates User “<>” deleted updates assignment “<>”. 30198
Configuration Baseline User “<>” deleted updates assignment “<>”. 30198
User Data and Profiles Configuration User “<>” deleted configuration policy assignment “<>”. 40702
Remote Connection Profiles User “<>” deleted configuration policy assignment “<>”. 40702
Certificate Profile User “<>” deleted configuration policy assignment “<>”. 40702
Email Profile User “<>” deleted configuration policy assignment “<>”. 40702
VPN Profile User “<>” deleted configuration policy assignment “<>”. 40702
Wi-Fi Profile User “<>” deleted configuration policy assignment “<>”. 40702
Antimalware Policy User “<>” deleted client settings assignment “<>”. 40305
Windows Firewall Policy User “<>” deleted configuration policy assignment “<>”. 40702
Client Settings User “<>” deleted client settings assignment “<>”. 40305
Share

Who created that deployment?

WhoCreatedThatDeployment

This blog post will be a short post about a question I often get when there was an accidental deployment and nobody dares to admit that he (or she) was responsible. The nice thing, at least for the colleagues and the manager, is that all this information is stored in the database and that it’s actually pretty simple to check.

There is a buildin report named All messages for a specific message ID that can be used to track the created deployment. The only missing detail is that it’s not clear which Message ID belongs to which action. The following table provides an overview with exactly that information. It will show per object type which Message ID belongs to the creation of a(n) deployment/ assignment.

Object Status Message Message ID
Application User “<>” created a deployment of application “<>” to collection “<>”. 30226
Package User “<>” created a deployment named “<>” deploying program “<>”. 30006
Task Sequence User “<>” created a deployment named “<>” deploying program “<>”. 30006
Software Updates User “<>” created updates assignment “<>”. 30196
Configuration Baseline User “<>” created updates assignment “<>”. 30196
User Data and Profiles Configuration User “<>” created configuration policy assignment “<>”. 40700
Remote Connection Profiles User “<>” created configuration policy assignment “<>”. 40700
Certificate Profile User “<>” created configuration policy assignment “<>”. 40700
Email Profile User “<>” created configuration policy assignment “<>”. 40700
VPN Profile User “<>” created configuration policy assignment “<>”. 40700
Wi-Fi Profile User “<>” created configuration policy assignment “<>”. 40700
Antimalware Policy User “<>” created client settings assignment “<>”. 40303
Windows Firewall Policy User “<>” created configuration policy assignment “<>”. 40700
Client Settings User “<>” created client settings assignment “<>”. 40303
Share