Our Story

Who we are and how we solve complex IT challenges.

Our Certifications

Microsoft certifications and partnerships validating our technical expertise.

Leadership

Meet the Experienced Leadership Team Driving WME’s Success

Advisory Updates

Expert guidance on Microsoft, security, and compliance developments.

Case Studies

Real-world outcomes from complex Microsoft-focused IT engagements.

Podcast

Podcasts, panels, and interviews where WME leaders share how they help high-growth companies and IT partners scale.

Ebooks

Practical guides on the Microsoft moves you can’t afford to get wrong.

Financial Industry

Secure technology solutions for regulated banks and financial institutions.

Healthcare

Secure Microsoft solutions for compliant, connected, and modern healthcare organizations.

Manufacturing

Cloud and security solutions supporting modern manufacturing operations.

Non-Profit

Cost-efficient Microsoft solutions for mission-driven organizations.

Public Sector

Microsoft-based IT services for secure public sector modernization.

High Tech

Scalable cloud, security, and staffing for fast-growing technology companies.

SMBs

Scalable cloud, security, and staffing for fast-growing technology companies.

Cloud Migration Services

Transition your workloads to the cloud securely for greater scalability and performance.

Data Migration Services

Securely transfer your business data with minimal downtime and maximum integrity.

Application Migration Services

Move your applications seamlessly to modern platforms with minimal business disruption.

Identity & Security Migration Services

Strengthen identity management and security while transitioning to modern Microsoft solutions.

Security Solutions

Protect your business with proactive cybersecurity, compliance, and risk management solutions.

Endpoint Management

Secure, manage, and monitor every device with modern endpoint management solutions.

Licensing Optimization

Get discounted pricing, a dedicated licensing team, and a plan that fits how many seats you actually use.

Power Platform

Unlock the full potential of the Microsoft Power Platform Suite to streamline operations, automate repetitive tasks, and gain real-time insights that drive business growth.

Sharepoint Solutions

Supercharge your business productivity and enhance visibility through our proven SharePoint expertise.

IT Staffing

Connect with skilled IT professionals to strengthen your team and accelerate project delivery.

Accounting & Finance

Connect with experienced accounting and finance professionals to support your business goals.

Software Version in SCCM Compliance Settings

May 13, 2014

This article is part of an ongoing series about Compliance Settings. This article will focus on using compliance settings to ensure that all of your devices have the most up-to-date version of a particular piece of software. I am going to use the VMware Horizon View Client as my example.

Application Collection

First, we must isolate all devices with a particular software installed, regardless of version. To do that, create a new collection. Create a query rule for membership. Now, you can either hit the “Show Query Language” button and paste in this code:

select
SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Na
me,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainOR
Workgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join
SMS_G_System_ADD_REMOVE_PROGRAMS on
SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID =
SMS_R_System.ResourceId inner join
SMS_G_System_ADD_REMOVE_PROGRAMS_64 on
SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceID =
SMS_R_System.ResourceId where
SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like “%VMware
Horizon View%” or SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName
like “%VMware Horizon View%””

Now, when you click “Show Query Design” and select the “Criteria” tab, it should look like this:

You can double click the two criteria and change your application name. Remember to leave the percent signs if you leave the operator as “is like”. The correct application names can be found by using the Resource Explorer for a device. You will need the second “Install Applications (64)” if the application appears under that section in Resource Explorer.

Once we have our application collection built, we can define the compliance setting.

Compliance Setting

First, we need to create our configuration item. To do that, navigate to the compliance settings area of the console and click “Create Configuration Item” from the ribbon. Give the item a name and description. When you get to the “Settings” section, click Give the setting a name, and change “Setting Type” to file system. Click browse, and find the file in question. You can connect to another computer (as long as remote management is turned on) and also find the file. Now, check the “The selected file must be compliant with the following rules” check box. Click “Add” and select the correct setting. Normally, version would be a great thing to use. I have to use “Date modified” because VMware put letters in their version number, and SCCM can’t handle those.

Remember that when the devices meet this requirement, they are considered “compliant”, so use the version that you want your devices to have when setting this up. When complete, your windows should look similar to this:

We have one slight problem here, which we will be able to fix after clicking OK. Because this application is installed in “Program Files (x86)”, we get the wrong environment variable. So after clicking OK, change %ProgramFiles(x86)% to %ProgramFiles% and check the “This file or folder is associated with a 64-bit application” check box and click OK.

You can now click through the rest of the Configuration Item wizard.

Now we need to create our baseline. Navigate to the “Configuration Baselines” section of Compliance Settings, and click “Create Configuration Baseline” in the ribbon. Give your baseline a name, click the “Add” button, and select “Configuration Items”. Find the configuration item that we just created, click “Add”, then click OK.

All that is left now is to deploy the baseline to the collection we created earlier. After deployment, you can create a collection of non-compliant computers by selecting the deployment, then clicking “Create New Collection” in the ribbon and selecting “Non-compliant”.

Disclaimer

All content provided on this blog is for information purposes only. Windows Management Experts, Inc makes no representation as to accuracy or completeness of any information on this site. Windows Management Experts, Inc will not be liable for any errors or omission in this information nor for the availability of this information. It is highly recommended that you consult one of our technical consultants, should you need any further assistant.

Share:

Facebook
Twitter
LinkedIn

Get Microsoft Updates Before They Cost You Downtime

Retirement dates, licensing changes, and security updates from a Microsoft-exclusive team, sent when they matter, not on a filler schedule.

Related Posts

WME Article - A Complete Guide to Windows 365 Boot

A Complete Guide to Windows 365 Boot

Windows 365 Boot is your gateway to a more seamless and efficient virtual desktop experience. Discover how this innovative feature