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

ConfigMgr 2007 R3 is making a step in Green IT with Power Management

This post is not meant as a guide for installing or configuring the R3 feature pack and/ or Power Management. I will just show, in a few screenshots and a bit explanation, what the possibilities are regarding the Power Management feature in ConfigMgr 2007 R3.

PwrMngmntAgentAs we all already knew, one of the coolest new features of ConfigMgr 2007 R3 would be Power Management. Another step in the direction of Green IT.  The Power Management feature provides a new Client Agent which enables you to apply power settings to client computers in the organization and monitor the power usage of these computers.

How to Enable the Power Management Client Agent

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Site Management > <YourSiteName> > Site Settings > Client Agents.
  2. Select the Power Management Client Agent and click in the Actions pane Properties (or right-click the Power Management Client Agent and click Properties) to open the Power Management Client Agent Properties.
  3. Select Enable power management on clients and click Ok.

After a policy refresh the Power Management Client Agent will be enabled on the client.

How to Enable Power Management settings PwrMngmntSettings

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Computer Management > Collections.
  2. Select <YourCollectionName>, click in the Actions pane Modify Collection Settings (or right-click <YourCollectionName> and click Modify Collection Settings) and select the Power Management tab to open the Power Management Settings.
  3. Select Enable power management settings, specify the power management settings (like different power plans and wake up time) and click Ok.

Now you have this possibility to enable Power Management settings on a per collection base. These settings work in a same way as setting Maintenance Windows on a per collection base.

How to view the Power Settings/ Capabilities/ Costs and Consumption

During the installation of R3 a new cab-file (MicrosoftReportPack) will be placed in <ConfigMgrInstallationDir>\Reports\Power Management.  PwrMngmntReportsWithout importing this cab-file you will not be able to see the Power Management reports, so don’t forget to import these handy reports! 

  1. Open the Configuration Manager console and browse to System Center Configuration Manager > Site Database > Computer Management > Reporting Services > <ServerName> > Report Folders.
  2. Select Power Management.
  3. Select the report that your want and click in the Actions pane Run (or right-click the report that want and click Run).

In these reports you can see all the information about Power Management, from capabilities till costs and from settings till consumptions.

Share

Data Source Settings of the Reporting Services in ConfigMgr 2007 are grayed out

Since the release of ConfigMgr 2007 SP2, I’m running ConfigMgr 2007 SP2 R2 (in Native Mode) on Windows Server 2008 R2. After installing the ConfigMgr Reporting Services Point I noticed that I couldn’t configure the Reporting Services, because the Data Source Settings where grayed out.

After doing some research and searching online I came on the FAQ about Reporting Services from the ConfigMgr Team. For those FAQ’s take a look at this link: http://blogs.technet.com/configmgrteam/archive/2009/05/14/faq-sql-reporting-services-integration-with-system-center-configuration-manager-2007-r2.aspx

One of these FAQ’s is the following: Do we support https enabled report server instances?

There are known issues in the R2 release with https enabled report server instances. There are some methods in the reporting services webservices  API that are inherently secure  methods and if SSL is configured on a report server instance these methods  cannot be invoked via http and require https connections. Internally, since we leverage some of these APIs, we fail to perform some actions.

Workaround: Unfortunately there is no easy workaround for this other than to not use SSL enabled report server instances. However there is a configuration setting that can be tweaked to get around this problem but it is NOT recommended to tweak this setting if the report server instance is hosting other reports (not specific to Configuration Manager).

Open the rsreportserver.config file using notepad and search for the property "SecureConnectionLevel". This value should be set to 3 (or some value > 0) for secured report server URLs. Change this value to 0 and save the rsreportserver.config file. (The default location for the default instance is under [SystemDrive]:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer).

After using this workaround it all worked like a charm!

Share