A frustration I’ve had in using SCCM 2012 was that when an object (collection, software update, package, application, etc.) is moved into a folder, you can’t search for the object without first navigating to the folder. After watching a MMS
SQL Reports Subscription Ownership
We have a number SCCM Reporting Services subscriptions for our automated reporting. Yesterday I had a former team member’s ID removed from SCCM access and today most of the automated reports did not run. When a report subscription is created
SCCM 2012 User Device Affinity and Windows XP
Referencing the Microsoft TechNet article titled How to Manage User Device Affinity in Configuration Manager @ http://technet.microsoft.com/en-us/library/gg699365.aspx How to configure the site to automatically create user device affinities Use the following procedure to enable your Configuration Manager site to automatically
Notepad++ and syntax highlighting for non-default file extensions
Thanks to this article (http://www.mattblodgett.com/2007/11/notepad-tip-syntax-highlighting-for.html) for helping me fix an annoyance with Notepad++. I often use Notepad++ as a lightweight editor for scripts. However, some script files like .wsf are not a recognized language and I have to manually select
SQL 2012, BIDS, and SSDT
With SQL Server 2012 Business Intelligence Development Studio is replaced with SQL Server Data Tools. BIDS = Business Intelligence Development Studio SSDT = SQL Server Data Tools (http://msdn.com/data/tools.aspx) If you customize SQL Reporting Services reports for SCCM 2007 or ConfigMgr
Case Sensitive comparison in SQL
The default collation that Microsoft SQL uses (and requried collation for SCCM) is case-insensitive. Here are some tips for performing a case-sensitive comparison despite the case-insensitve collation. Convert data to binary [cc lang=’sql’ line_numbers=’false’]SELECT * FROM MyTable WHERE CAST(Value1 AS
SCCM 2012 SP1 refresh / KB2801987
The original ISO for Microsoft System Center 2012 Configuration Manager SP1 contained a nasty little bug that prevented the ConfigMgr client from installing. The problem was that the authenticode signature for MicrosoftPolicyPlatformSetup.msi, a required component of the client agent, was
SCCM Report of Operating Systems and Types
Based on Sherry Kissinger’s blog http://myitforum.com/cs2/blogs/skissinger/archive/2009/06/23/32bit-vs-64bit-report.aspx here is the summary report for a list of Processors, OS Type, OS Name, and Computer count. select pr.datawidth0 [Processor bits] , pr.addresswidth0 [OS bits] , sys.Operating_system_Name_and0 [OS Name] ,count(sys.resourceid) [Computers] from v_r_system sys