Deploying OpsMgr 2012 R2 Agents Using ConfigMgr – Part 1

By reading the title of this article, you may think, this practice is so common, is it worth blogging? Before I started this task, I thought it should be a quick one that I can knock off in 30 minutes. I had to say, I was wrong, I ended up spent few days on it. Before I get into the details, I’d like to share some background and what I want to achieve. I’ll then go through the steps I took in ConfigMgr 2007 as well ConfigMgr 2012 R2. This is probably going to be too long for one blog

Management Pack for ConfigMgr 2012 Clients – Testers Wanted!!

I’ve written a OpsMgr management pack to monitor ConfigMgr 2007 clients in the past. The MP was published in this blog. Over the last month or so, as part of a project that I’m working on, I have written a Management Pack to monitor ConfigMgr 2012 Clients via OpsMgr 2012. This MP provides individualised monitoring for ConfigMgr 2012 clients, where the Microsoft ConfigMgr 2012 management pack does not. To be honest, I wasn’t really happy with the ConfigMgr 2007 Client MP that I wrote almost 2 years ago. I think there are a lot of areas that needs improvement. So

ConfigMgr Report: Total Number of Packages Per Distribution Point

Today I had to create a report in ConfigMgr to list total number of packages that have been assigned to each Distribution Point. The SQL query is rather simple, a one-liner. Here’s the query: This query works on both ConfigMgr 2007 and 2012. ConfigMgr 2007 Report: ConfigMgr 2012 Report:

Installing SCCM 2012 SP1 Secondary Site with a Pre-Configured SQL 2012 Instance

Over the last week, I’ve been re-installing my SCCM lab environment to SCCM 2012 SP1. I’m using Windows Server 2012 as the base OS for all site system roles and all database engines and SQL reporting server run on SQL 2012. I got stuck few days ago when I was building my first secondary site. I was trying to use a pre-installed SQL 2012 Express With SP1 instance for the secondary site database. I followed the instruction that I have previously blogged for SQL Express 2008 R2: http://blog.tyang.org/2012/04/09/installing-sccm-2012-rtm-secondary-site-using-a-pre-installed-sql-express-2008-r2-instance/ After I installed and configured the SQL express instance for the secondary

Passed MCTS for SCCM 2012 Exam today

Around 8-9 months ago, a friend of mine gave me a copy of beta version of trainer’s handbooks for Microsoft course 10747A (Administering SCCM 2012) and 10748A (Deploying SCCM 2012). I normally don’t read any Microsoft course materials as I always found better books out in the market. When I was given these books, there weren’t any SCCM 2012 books available because SCCM 2012 wasn’t even RTM’d at that time. So I started reading these trainer’s handbooks and surprisingly, I found they are actually really good. With everything else going on at work, all the SCOM stuff I’ve been doing

SCCM 2007 Client Management Pack Updated

I received an email this morning regarding to the SCCM 2007 Client Management Pack that I wrote few months ago. Someone pointed out it had some issues in the language packs section of the MP. I had a look and realised the TYANG.System.Center.Configuration.Manager.2007.Monitoring.mp does have some orphaned string resources. A bit background of this MP. I originally wrote this MP for my employer. Before I posted it on my blog, I removed everything that were specfic to my employer (few monitors, application components, relationships, discoveries, etc.). However, I ddin’t delete associated display string resources in here: I have just updated

My Observation on SCCM Clients BITS Settings

Yesterday, while we were reviewing the SCCM (2007 R3) client BITS settings at work, we (my team) have some interesting findings with SCCM client’s BITS settings. We found when the BITS bandwidth throttling settings are configured for a SCCM primary site. SCCM clients get the policy and write the settings into Windows local policy: SCCM Computer Client Agent BITS Settings: BITS Settings from SCCM Client’s Windows local policy (Local Policy –>Computer Configuration –>Administrative Templates –>Network –>Background Intelligent Transfer Service (BITS) –>Limit the maximum network bandwidth for BITS background transfers): As you can see, the SCCM site setting is identical to

SCCM 2012 Log Parser: cmtrace.exe

In my opinion, THE most used utility (other than SCCM console) for any SCCM administrators / engineers would have to be trace32.exe. Back in SMS and SCCM 2007 days, trace32.exe comes with the SCCM Toolkit, which contains a bunch of other tools. Speaking of my own experience, out of all the tools provided by the toolkit, trace32.exe is the one I used the most. Now with SCCM 2012, trace32.exe has been replaced by a new tool called cmtrace.exe. Unlike trace32.exe, cmtrace.exe is actually built-in in SCCM, there is no need to download separate toolkits for it. cmtrace.32 can be found

Installing SCCM 2012 RTM Secondary Site using A Pre-Installed SQL Express 2008 R2 Instance

Since System Center 2012 was RTM’d few days ago, I have started updating / migrating my home environment. After I migrated my 2 Hyper-V servers from VMM 2008 R2 to VMM 2012, I have started building a brand new SCCM 2012 environment so I can migrate SCCM 2007 to it. My plan is to install a Central Admin site, a child primary site and a Secondary site so I have a simple 3-tier hierarchy like my existing 2007 and 2012 Beta 2 environments. The Central Admin site and the child primary site installation all went pretty smoothly. But I had

System Center Configuration Manager (SCCM) 2007 Client Management Pack for SCOM

12/08/2012: This MP has been updated. Please refer to this post for more details of the update. The download link in this post has also been updated. Background Over the time, I have seen some issues and challenges for SCCM administrators to effectively and proactively managing SCCM clients.  I have personally seen and experienced some challenging issues. For example: Silent clients due to the SMS agent host service not running. SCCM Clients are reporting to the incorrect site due to the combination of overlapping boundaries and auto site assignment. SCCM Clients missing new functionalities due to Missing SCCM hotfixes (i.e. Power

%d bloggers like this: