ConfigMgr OMS Connector

Earlier this week, Microsoft has release a new feature  in System Center Configuration Manager 1606 called OMS Connector: As we all know, OMS supports computer groups. We can either manually create computer groups in OMS using OMS search queries, or import AD and WSUS groups. With the ConfigMgr OMS Connector, we can now import ConfigMgr device collections into OMS as computer groups. Instead of using the OMS workspace ID and keys to access OMS, the ConfigMgr OMS connector requires an Azure AD Application and Service Principal. My friend and fellow Cloud and Data Center Management MVP Steve Beaumont has blogged

Detecting Windows License Activation Status Using ConfigMgr DCM and OpsMgr

Hello and Happy New year. You are reading my first post in 2015! This is going to a quick post, something I did this week. Recently, during a ConfigMgr 2012 RAP (Risk and Health Assessment Program) engagement with Microsoft, it has been identified that a small number of ConfigMgr Windows client computers do not have their Windows License activated. The recommendation from the Microsoft ConfigMgr PFE who’s running the RAP was to create a Compliance (DCM) baseline to detect whether the Windows license is activated on client computers. To respond to the recommendation from Microsoft, I quickly created a DCM

Use of ConfigMgr 2012 Client MP: Real Life Examples

Last week, while I was assisting with few production issues in a ConfigMgr 2012 environment, I had to quickly implement some monitoring for some ConfigMgr 2012 site systems. By utilising the most recent release of ConfigMgr 2012 Client management pack (version 1.2.0.0) and few DCM baselines, I managed to achieve the goals in a short period of time. The purpose of this post is to share my experience and hopefully someone can pick few tips and tricks from it. Background We are in the process of rebuilding few hundreds sites from Windows Server 2008 R2 / System Center 2007 R2

Updated ConfigMgr 2012 (R2) Client Management Pack Version 1.2.0.0

Background It’s only been 2 weeks since I released the last update of this MP (version 1.1.0.0). Soon after the release, Mr. David Allen, a fellow System Center CDM MVP contacted me, asked me to test his SCCM Compliance MP, and possibly combine it with my ConfigMgr 2012 Client MP. In the ConfigMgr 2012 Client MP, the OVERALL DCM baselines compliance status are monitored by the DCM Agent class, whereas in David’s SCCM Compliance MP, each DCM Baseline is discovered as a separate entity and monitored separately. Because of the utilisation of Cook Down feature, comparing with the approach in

How to Create a PowerShell Console Profile Baseline for the Entire Environment

Background Often when I’m working in my lab, I get frustrated because the code in PowerShell profiles varies between different computers and user accounts. And your user profile is also different between the normal PowerShell command console and PowerShell ISE. I wanted to be able to create a baseline for the PowerShell profiles across all computers and all users, no matter which PowerShell console is being used (normal command console vs PowerShell ISE). For example, I would like to achieve the following when I start any 64 bit PowerShell consoles on any computers in my lab under any user accounts:

Packaging OpsMgr 2012 R2 Agent WITH Update Rollup in ConfigMgr 2012

Background About 6 months ago, I wrote a 2-part blog series on deploying OpsMgr 2012 R2 agents using ConfigMgr  (Part 1, Part 2). Since then, Update Rollup 1 and Update Rollup 2 has been released. Because UR1 did not include agent updates, I didn’t have to patch any agents. The most recent release of Update Rollup 2 does include agent updates, I’ll have to get the agents patched. For me, and the project that I’m working on, this is a perfect timing, UR2 was release right before we production transitioning our newly built OpsMgr 2012 R2 management groups and we

Use of Disable Operations Manager alerts option in ConfigMgr

In System Center Configuration Manager, there is an option “Disable Operations manager alerts while this program runs” in the program within a package: There are also same options in the deployment of ConfigMgr 2012 applications and Software update groups: Application Deployment: Software Update Groups Deployment: Most of seasoned System Center specialists must already know that these tick boxes do not make the computers enter maintenance mode in OpsMgr. It’s suppressing alerts by pausing the OpsMgr healthservice. As far as I know, there is no way to initiate maintenance mode from an agent. Maintenance mode can only be started from the

ConfigMgr 2012 (R2) Clients Management Pack Released

Time flies, I can’t believe it’s been over 7 months since I posted the beta version of the ConfigMgr 2012 client MP for testing. I haven’t forgotten about this MP (because it’s one of the deliverables for the System Center 2012 upgrade project that I’ve been working on for the last 12 months or so). Today, I finally managed to finish updating this MP, it is ready for final release (Version 1.0.1.0). I didn’t manage to get many feedbacks since the beta version was released. so it’s either a good thing that everyone’s happy about it, or it’s really bad

Configuring System Center Update Publisher 2011 (SCUP) for Multiple Users

One thing I really don’t like about SCUP 2011 is, the settings are user specific, which means different users will have to manually configure SCUP settings on the same computer. By default, even the SCUP database is stored within the user’s profile. There are already many articles out there on how to change the SCUP database location. (i.e. http://myitforum.com/cs2/blogs/rzander/archive/2011/05/30/scup-2011-with-shared-database.aspx) Other than the database locations, all other settings such as WSUS connection, SCCM connection, Certificate, source location, etc. are all user based when configured within SCUP Options window: I figured out an very easy way to make these settings machine-based settings.

Deploying OpsMgr 2012 R2 Agents Using ConfigMgr – Part 2

This is the 2nd part of 2-part blog series. Part 1 can be found HERE. In Part 1, I went through the issues I had with deploying OpsMgr 2012 R2 agent via ConfigMgr 2007. In this article, I will go through the steps I took to deploy OpsMgr 2012 R2 agent using ConfigMgr 2012 Application model and Compliance settings (DCM). Moving to ConfigMgr 2012, I have decided to do utilise the new application model (it’s also to align the policy we set during the design phase of the System Center upgrade project: that wherever is possible, the new application model

%d bloggers like this: