System Center in Action - All Comments

re: Understanding Updates Management

Ankit Goel — Thu, 28 Mar 2013 20:46:21 GMT

Hello Jiten,

This article is useful however would like to know about part 2 also.

Ankit

re: Configuration Manager 2012 Exchange Connector Implementation in Microsoft IT

Sam — Fri, 22 Feb 2013 01:35:41 GMT

Quick question, If I have configured read only as you have, but an administrator tries to send a device block, this request appears to get stuck in retry as it doesnt have permissions to execute. How do I now clear this from retry?

re: Client Migration from Configuration Manager 2007 to Configuration Manager 2012

Nsikak Attah — Sat, 06 Oct 2012 06:21:14 GMT

Hi, I'm wondering if using software distribution using existing config manager 2007 with appropriate command line options would not have achieved same objective especially for sites that don't have the luxury of fast links to remote locations

re: Understanding Updates Management

JitenRK — Mon, 01 Oct 2012 12:18:39 GMT

You can find LastScanState Message ID under the view v_StateNames.

re: Understanding Updates Management

CMJ — Fri, 14 Sep 2012 19:22:19 GMT

How would I convert the LastScanState Message ID to an actual useful description? I cant seem to find the associated table.

re: Extending Incident Properties and Forms

Forms — Tue, 04 Sep 2012 13:18:55 GMT

Forms need to possess best properties, because it helps in analyzing the data easily, which results in success and growth.

re: Client Migration from Configuration Manager 2007 to Configuration Manager 2012

Catherine Campbell — Tue, 21 Aug 2012 16:19:43 GMT

Hi, Ram - Naveen's working on your request for post deployment configuration. Look for a post soon!

re: Understanding Updates Management

Philip — Tue, 21 Aug 2012 16:08:49 GMT

nice info

re: Client Migration from Configuration Manager 2007 to Configuration Manager 2012

Ram Neti — Thu, 09 Aug 2012 20:48:44 GMT

Excellent information. Pl. share some insights experience and problem areas if any post configuration-- especially within the first 180 days of deployment.

re: Auditing Software Inventory Rules in System Center 2012 Configuration Manager

Benjamin Reynolds — Fri, 06 Jul 2012 23:27:02 GMT

Sorry Paul, was out on vacation...

The problem with a *.exe rule is that it is totally unnecessary and provides very little (if any) benefit.

I've never seen a *.exe rule defined with a location other than "All client hard disks". This means you're performing a complete disk scan of all disks every time software inventory runs. It also means more network usage and larger database sizes (due to the amount of data collected, sent, and stored).

The reason this data provides little benefit is because hardware inventory is already collecting this information (most likely). If the application registers itself in Add/Remove Programs (ARP) hardware inventory is picking this information up already. If the application you want to report on doesn't play nice and doesn't register itself in ARP then you can turn on Asset Intelligence (AI) which will look in several sources (MSI, registry, and WMI) to compile the list of installed applications which is picked up by hardware inventory. If for some reason the application you want to report on isn't listed in any of these locations then you can create a software inventory rule for that specific exe name and provide it a relative path (rather than running a complete disk scan). Does that help answer your question?