Event ID 7000 : not a valid Win32 application during WSUS installation on SCCM 2012 SP1

Issue
Today after installing another fancy Windows 2012 SCCM Server I noticed that when I tried to configure WSUS and WDS the service crashed with the following error:
The WSUS Service failed to start due the following error: WSUS Service is not a valid Win32 application.
Event ID 7000.

Reason:
About a hour ago I also had an error on File Name Warning:
There is a file or folder on your computer called “C:\program” which could cause certain applications to not function correctly. Renaming it to “C:\program2” would solve this issue.
program error
I made a note of it but did not rename it because the message wasn’t wrong, there IS a file called program (no extension) on my Systemdrive. But why?
program
After a deep dive in my server configuration I discovered the distmgr.log of ConfigMgr is missing quotations while saving the log file. This could be an solution; after some more digging It looks like if the “” (quotation marks) were missing in the command line for the logfile path. Windows would then go and interpret the logfile as “C:Program”.

Program2
So this looks like a bug in the installation of the SCCM 2012 Distribution Manager installation.
To be sure I opened the program file with notepad and noticed that it’s indeed a text file.
program3

Resolution:
Rename or delete the c:\program file and the issue is solved.

Step by Step: Installing SCCM 2012 SP1 on Windows Server 2012 and SQL 2012 SP1

Well, after some testing with SCCM 2012 SP1 I decided to reinstall everything in my lab to the latest software. So Windows 2012, SQL 2012 RTM and of course System Center Configuration Manager 2012 SP1.

In this blog I used my laptop:
-Intel(R) i5-2410M CPU @ 2.30GHz, 2 Core(s)
-8 Gb of internal memory
-Two SSD disk (C:\ for OS and D:\ for Hyper-V)

Lab setup:
Domain Controller: Windows 2012 Enterprise; DC, DNS and certificate server
SCCM 2012; Windows 2012 Enterprise, SQL 2012 Enterprise, IIS and SCCM components

1. SQL 2012 installation
ConfigMgr 2012 SP1 Beta supports SQL 2012 RTM with a minimum of CU 2. ConfigMgr has very strict SQL collation requirement, pretty much across the entire System Center range, essentially only SQL_Latin1_General_CP1_CI_AS collation is supported.
This has to be selected during installation if you are running a non-USA regional\system OS.

– Login as the SQL admin on the SQL Server
– Launch the SQL 2012 RTM installer
Select Installation on the left navigation pane
Select New SQL Server stand-alone installation or add features to an existing installation
– Ok, Next,
and choose Accept the license terms, Next
We will open the Firewall later, so skip the warning
– Choose Next
– Select SQL Server Feature Installation


Select the following
– Database Engine Services
– Reporting Services – Native
– Management Tools – Basic
– Management Tools – Complete
Because I’m in a test environment I didn’t change the path’s. In production it’s recommended to choose alternative path’s
Next, Next

– Choose the default Default instance, and change the path’s if necessary and choose Next, Next
By default each of the services will be configured using a service-specific user account, we used NT AUTHORITY\SYSTEM

Do this for the SQL Server Agent, the SQL Server Database Engine and the SQL Server Reporting Services services
– Click Account Name, Browse, Browse locally for SYSTEM and accept
– Set the services Start-up Type to automatic
Select the Collation tab
– Double check
If SQL_Latin1_General_CP1_CI_AS is shown, otherwise Customize this, Next
Add the current user and a domain user at this point. I add the SQL admin and the local administrator, Next
– Select Install and configure, Next
Set Send Windows and SQL Server Error Reports to Microsoft, choose Next, Next
Alrighty then SQL is Ready, lets rock.

– Next we will run SQL 2012 SP1 (SCCM 2012 requires minimal CU2 to have an successful install)
Download link SP1 http://www.microsoft.com/en-us/download/details.aspx?id=35575
Download link CU1 http://support.microsoft.com/kb/2765331

Note If you do not install CU2 (or SP1) you’ll receive SQL Server Version Error in the Perquisites.

The Advanced logging says that the SQL server Version is not supported. So patch you’re SQL Server.

Make the nessesary Firewall Exeptions for SCCM;
– Open the settings, Control Panel, System and Security, Windows Firewall
– Choose Advanced Settings, Inbound rules
– Create a new Rule called SQL Ports,
– On Rule Type, Choose Ports, Next
– On theTCP tab 4022, 1433 and click Next
ScreenHunter_191 Jan. 25 10.08
– Choose allow the connection, Next
– On profile choose all, Next
Fill in a name (we used SQL Ports)


2. Installing the SCCM 2012 Perquisites
Open Server Manager
– Select Add Roles and features, click Next
– Choose Role Based or Feature based installation
– Select the local server, Next
Open Web Server (IIS) and ADD select the following features
Common
HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection

Application
Development
ASP.NET
.NET Extensibility
ASP
ISAPI Extensions
ISAPI Filters

Health and Diagnostics
HTTP logging
Logging tools
Request Monitor
Tracing

Security
Basic Authentication
Windows Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions

Performance
Static Content
Compression

Management Tools IIS Management Console IIS Management Scripts and Tools Management Service IIS 6 Management Compatibilty IIS 6 Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console
– Select Windows Server Update Services, Add features
– Select Windows Deployment Services, Add Features

– Choose Background Intelligent Transfer Service (BITS), Add features
– Choose Remote Differential Compression
– Telnet Client (not necessary but it’s useful), Next
– On the WSUS section choose next.
– On the Role Services choose WSUS Services and Database, Next
– Choose Store updates and choose a location (This is a testlab, in production it is not recommended to save these files to the C:\ drive), Next

– Type the SQL Server name and choose Check connection

– Next, Next,
– Choose Deployment Server and Transport Server
– Next, Install

3. Install the WADK (Windows Assessment and Deployment Kit)
In Windows 2012 you no longer use WAIK, we’re now on WADK for Windows 8.
– Go to http://go.microsoft.com/fwlink/?LinkID=252874 and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

3. Next step is to install SCCM 2012 SP1 Beta
Ok, we are now ready to install ConfigMgr 2012 SP 1 Beta
– Launch the spash.HTA from the installation media

– First check the server is ready before we get any further into the installer Select Assess server readiness

Some minor issues but no show stoppers so lets continue
– Go back to the Splash.hta screen and click Install, Choose Next
– Because we are on one demo server we choose Install a Configuration Manager Primary Site and check the Use typical installation… Choose Next.

– Choose yes and I Agree, Next
– Accept all the licence therms and choose next

– Download the files to a folder you choose and click Next

-Choose a site code, Site name and installation folder for SCCM 2012 SP1, Next

– Hit next a couple of times and then choose Begin Install

That’s it, we are now up and running.

SP1 brings a lot of nice new stuff like the cross-platform clients, Azure Cloud DP, mobile device management through Microsoft Exchange ActiveSync amongst others.
Check out what’s new in SP1 here for a list of fun things to play around with and get to know in preparation for the actual SP1 release, as well as the release notes detailing what is knowing to be in a broken state during the Beta. You can also provide feedback to Microsoft for anything quirky that you may find during the evaluation.

Have Fun!

System Center 2012 SP1 – SCOM 2012 – Evaluation (VHD)

Microsoft launched the public VHD’s for System Center 2012 SP1.
The VHD’s enables System Center customers to jointly evaluate System Center 2012 and Windows Server 2012.
The download consists of files that you extract into a single pre-configured VHD file for this System Center component.

No MSDN or TechNet subscription is required for this download.

System Center 2012 Service Pack 1 components that ship Evaluation VHDs can be found at the following locations:

WSUS sync issues after installation of SCCM 2012 SP1; Event ID 6703 SMS_WSUS_SYNC_MANAGER

Issue:

Today I bumped into a strange issue when upgrading SCCM 2012 to SP1. The installation went well and after checking the eventlog everything seemed to run smoothly.

After I changed the WSUS Sync setting of SCCM to every hour (because of Forefront Endpoint Protection) we noticed that the WSUS server didn’t function properly anymore. The Software Update Point gave the following error:
Log Name:      Application
Source:           SMS Server
Date:              14-1-2013 12:05:02
Event ID:         6703
Task Category: SMS_WSUS_SYNC_MANAGER
Level:              Error
Keywords:       Classic
User:               N/A
Computer:       SCCM01-SUP.internal.local
Description: On 14-1-2013 12:05:02, component SMS_WSUS_SYNC_MANAGER on computer SCCM01-SUP.internal.local reported:   WSUS Synchronization failed. Message: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync. The operating system reported error 2147500037: Unspecified error

1 - Issue SCCM 2012 SP1 WSUS

Cause:
After some investigation we looked into the SUP properties via Administration, Site Configuration, Servers and Site System Roles.2 - SCCM 2012 SP1 WSUS ISSUE

In the Software Update Point settings we found that SP1 has changed the 8530 and 8531 ports back into 80 and 443 (default)
3 - SCCM 2012 SP1 WSUS ISSUE

Solution:
Well this looked like an easy one; we changed the ports back to where we configured WSUS (8530 and 8531) on and the issue was solved.
4 - SCCM 2012 SP1 WSUS ISSUE

 

Upgrading System Center Configuration Manager 2012 to Service Pack 1

After upgrading my test (Beta SP1) environment to SP1 went smoothly we rolled out SCCM 2012 SP1 to one of our customers (because of a running issue which should be solved in SP1).

It caused me some sweat but got it running eventually.
The scenario:
– Windows 2008 R2
– SQL 2008 R2
– SCCM 2012 CU2

Note: To install ConfigMgr 2012 SP1 with Windows Server 2012 and SQL 2012 SP1 see http://www.toolzz.com/?p=602

Here are the steps I took:
1. Install the WADK (Windows Assessment and Deployment Kit)
First of all there are some extra requirements to take for the upgrade. In SCCM 2012 SP1 you no longer use WAIK, we’re now on WADK.
– Go to http://go.microsoft.com/fwlink/?LinkID=252874and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

2. Installing the SCCM 2012 SP1 software.
– I Downloaded the SP1 software from the Microsoft TechNet Site. It’s a little bit confusing but
System Center 2012 Configuration Manager and Endpoint Protection with sp1 x86 x64″
and “System Center 2012 Configuration Manager and Endpoint Protection x86 x64” with the date of 12 December are both valid.
– Start the Splash.hta on the disk
– Choose the Install option
SCCM SP1 Setup
– Choose “Upgrade this Configuration Manager site” and choose Next
SCCM SP1 Update 1
-Just note that there are more languages available then prior to SP1. Choose Next to continue
SCCM SP1 Update 2
– Check the prerequisite check. Because we implemented step 1 already we can continue by clicking Begin Install.
SCCM SP1 Update 3_1
In my case the installation took about one hour. The SQL database which was running on a different server was automatically updated.

3. The console issue
After starting up the console I bumped into an issue which was not very clear:

After upgrading to SP1 my console disappeared from my management server.
SCCM 2012 SP1 Console
After some troubleshooting I tried starting up the console from the directory; but it could not connect to the server.
Console issue SCCM 2012 SP1
This was strange, but after some investigating I discovered that the Console is not automatically updated with SP1 which causes this issue.
– Restarting the SP1 Splash.HTA and running Install Configuration Manager console solved the issue for me!
Update Console SCCM 2012 SP1
Checked the installation and we are indeed running on SP1 !!
SCCM SP1 Update 4
Henk Hoogendoorn posted a blog on what features are updated in the SP1 HERE.

System Center 2012 SP1 Released

System Center 2012 Service Pack 1 has reached its “release-to-manufacturing” (RTM) milestone, Microsoft announced recently.
ScreenHunter_162 Dec. 21 08.33

RTM typically refers to feature-complete products, although the final “general availability” release of System Center 2012 SP1 is scheduled for early January.
The “release candidate” version of the product had been issued previously, but was just available to Microsoft’s Technology Adoption Program testers. The last public release announcement seems to have been a beta delivered in September.

The software is now available on the MSDN site for partners and customers with SA.
It’s available on http://msdn.microsoft.com/en-us/subscriptions/downloads/.

A list of what’s new in SP1 for System Center 2012:
1. There are new Monitoring Capabilities under APM functionality:
                         o Monitoring of Windows Services Built on the .NET Framework.
                         o Automatic Discovery of ASP.NET MVC3 and MVC4 Applications.
                         o New Transaction Types: MVC Pages and WCF Methods.
2. Enabled APM of SharePoint 2010.
3. Integration with Team Foundation Server 2010 and Team Foundation Server 2012.
4. New monitoring capability allows for opening of APM exception events from Visual Studio IDE as if the exception was captured during the IntelliTrace historical debugging session. Developers can stay within their familiar environment to examine complete exception call stack.
5. New Management Packs and Support for Windows Server 2012 and IIS 8.
6. The System Center 2012 Service Pack 1 (SP1) Beta version of Operations Manager can show you different perspectives of application health in one place—360 .NET Application Monitoring Dashboards. The 360 .NET Application Monitoring Dashboards displays information from Global Service Monitor, .NET Application Performance Monitoring, and Web Application Availability Monitoring to provide a summary of health and key metrics for 3-tier applications in a single view.
7. ACS support is now added for Dynamic Access Control – new feature in Windows Server 2012, where business data owners to easily classify and label data allowing access policies to be defined for data classes that are critical to business.
8. Support is added for CentOS, Debian, and Ubuntu Linux.

The arrival of SP1 for System Center 2012 is a big deal because it will add management support for Windows Server 2012 and Windows 8 and SQL 2012.

Without this service pack, there’s no management support for those operating systems in System Center 2012.

Nice!

Office 2013 deployment with SCCM 2012 SP1 (Beta)

Just another tutorial on how to deploy Office 2013 using Configuration Manager 2012 SP1.

Extracting the Office installation and customizing the installation
First I started to get the Office 2013 software from the MSDN site and extracted it into my demo lab share file.
1. In my case it was on \\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64.


Second step is to customize the Office 2013 installation using the “Office Customization Tool”;
2. Go to a DOS prompt, go the Office 2013 folder and run setup.exe /admin
If the setup /admin runs well go to step 3, otherwise go to step 2.1
2.1 – Optional
If you run the setup.exe /admin you can receive the following error:

Files necessary to run the Office Customization Tool were not found. Run Setup from the installation point of a qualifying product.

To solve this issue, click HERE and extract the admin files in the root of the Office 2013 directory.

3. Choose Ok to create a new Setup Customization file

4. On Default File Types, I selected Office Open XML formats

5. On the Licensing and user interface check the I Accept terms and choose Display Level – none

6. Customize the further installation of Office 2013 to you’re needs.
7. Save it where the setup.exe is located. I used the name Office2013NLD_x64_Custom.msp

Next step is do deploy Office 2013 to the SCCM 2012 SP1 environment
1. Open the Configuration Manager 2012 console, Software Library, Application Management, right-click Applications
2. Create an folder named Office and a subfolder called Office 2013
3. Right Click Create application

4. Browse to proplusww.msi (location where you extract the Office, subfolder proplusrww) and click Next
5. On view imported information, click next
6. On the General information, make adjustments/notes and click next

7. Summary, click Next and choose Close
8. Select the Microsoft Professional Plus 2013 application, and select the Deployment Type tab, click Properties
9. In the Deployment Type properties, of the Microsoft Professional Plus 2013 application, go to content tab and change the Content location from “\\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64\proplusr.ww” to “\\demo-sccm01\Sources\Software\Office\Office 2013 Pro NL x64”
10. Go to programs tab, Installation program, type setup.exe /adminfile Office2013NLD_x64_Custom.msp

11. If necessary you can go to the requirements section and add requirements like
– 1 gigahertz (Ghz) or faster
– 1 gigabyte (GB) RAM (32 bit);
– 2 gigabytes (GB) RAM (64 bit)

12. Select the Microsoft Office Professional Plus 2013 x64 – NLD, change to Home tab and click Properties

13. Select “Allow this application to be installed form the install application task sequence action without being deployed”; this is necessary if you want to use it during the Operating System Deployment.

14. Select the Microsoft Professional Plus 2013 application and click Distribute Content

15. On the General, Click Next
16. On Content, click Next
17. On Content Destination, add the Distribution Point and click Next
18. Summary, click Next and choose Close
19. Right click on the Office App and choose Deploy, select All systems as collection (because we use it as an OSD deployment.

20. Just click next until completion, if you want to make adjustments it’s possible.
21. On the client force the machine policy retrieval

22. Open the Software Center, select Microsoft Professional Plus 2013 x64 NLD and click Install and the installation will start. After a minute of ten the installation is completed.
23. To check the deployment on the server, open the ConfigMgr console, go to monitoring, Deployments.
24. Select Microsoft Professional Plus 2013 and confirm the completion statistics

 

Step by Step: ConfigMgr 2012 SP1 Beta, Windows Server 2012 and SQL 2012 SP1

NOTE THIS IS FOR BETA; See http://www.toolzz.com/?p=793 for installing ConfigMgr 2012 SP1 RTM

Well, after some testing with SCCM 2012 SP1 I decided to reinstall everything in my lab to the latest software. So Windows 2012, SQL 2012 RTM and of course System Center Configuration Manager 2012 SP1 (Beta).

In this blog I used my laptop:
-Intel(R) i5-2410M CPU @ 2.30GHz, 2 Core(s)
-8 Gb of internal memory
-Two SSD disk (C:\ for OS and D:\ for Hyper-V)

Lab setup:
Domain Controller: Windows 2012 Enterprise; DC, DNS and certificate server
SCCM 2012; Windows 2012 Enterprise, SQL 2012 Enterprise, IIS and SCCM components

1. SQL 2012 installation
ConfigMgr 2012 SP1 Beta supports SQL 2012 RTM with a minimum of CU 2. ConfigMgr has very strict SQL collation requirement, pretty much across the entire System Center range, essentially only SQL_Latin1_General_CP1_CI_AS collation is supported.
This has to be selected during installation if you are running a non-USA regional\system OS.

– Login as the SQL admin on the SQL Server
– Launch the SQL 2012 RTM installer
Select Installation on the left navigation pane
Select New SQL Server stand-alone installation or add features to an existing installation
– Ok, Next,
and choose Accept the license terms, Next
We will open the Firewall later, so skip the warning
– Choose Next
– Select SQL Server Feature Installation


Select the following
– Database Engine Services
– Reporting Services – Native
– Management Tools – Basic
– Management Tools – Complete
Because I’m in a test environment I didn’t change the path’s. In production it’s recommended to choose alternative path’s
Next, Next

– Choose the default Default instance, and change the path’s if necessary and choose Next, Next
By default each of the services will be configured using a service-specific user account, we used NT AUTHORITY\SYSTEM

Do this for the SQL Server Agent, the SQL Server Database Engine and the SQL Server Reporting Services services
– Click Account Name, Browse, Browse locally for SYSTEM and accept
– Set the services Start-up Type to automatic
– 
Select the Collation tab

– Double check
If SQL_Latin1_General_CP1_CI_AS is shown, otherwise Customize this, Next
Add the current user and a domain user at this point. I add the SQL admin and the local administrator, Next
– Select Install and configure, Next
Set Send Windows and SQL Server Error Reports to Microsoft, choose Next, Next
Alrighty then SQL is Ready, lets rock.

– Next we will run SQL 2012 SP1 (SCCM 2012 requires minimal CU2 to have an successful install)
Download link SP1 http://www.microsoft.com/en-us/download/details.aspx?id=35575
Note If you do not install CU2 (or SP1) you’ll receive SQL Server Version Error in the Perquisites.

The Advanced logging says that the SQL server Version is not supported. So patch you’re SQL Server.
FIREWALL EXEPTIONS

 2. Installing the SCCM 2012 Perquisites
Open Server Manager
– Select Add Roles and features, click Next
– Choose Role Based or Feature based installation
– Select the local server, Next
Open Web Server (IIS) and ADD select the following features
Common
HTTP Features  
Static Content  
Default Document  
Directory Browsing  
HTTP Errors  
HTTP Redirection

Application
Development  
ASP.NET  
.NET Extensibility  
ASP  
ISAPI Extensions  
ISAPI Filters

Health and Diagnostics
HTTP logging  
Logging tools  
Request Monitor  
Tracing

Security  
Basic Authentication  
Windows Authentication  
URL Authorization  
Request Filtering  
IP and Domain Restrictions

Performance
Static Content
Compression

Management Tools  IIS Management Console  IIS Management Scripts and Tools  Management Service  IIS 6 Management Compatibilty  IIS 6 Metabase Compatibility  IIS 6 WMI Compatibility  IIS 6 Scripting Tools  IIS 6 Management Console
– Select Windows Server Update Services, Add features
– Select Windows Deployment Services, Add Features

– Choose Background Intelligent Transfer Service (BITS), Add features
– Choose Remote Differential Compression
– Telnet Client (not necessary but it’s useful), Next
– On the WSUS section choose next.
– On the Role Services choose WSUS Services and Database, Next
– Choose Store updates and choose a location (This is a testlab, in production it is not recommended to save these files to the C:\ drive), Next

– Type the SQL Server name and choose Check connection

– Next, Next,
– Choose Deployment Server and Transport Server
– Next, Install

3. Install the WADK (Windows Assessment and Deployment Kit)
In Windows 2012 you no longer use WAIK, we’re now on WADK for Windows 8.
– Go to http://go.microsoft.com/fwlink/?LinkID=252874 and download the ADK Setup.
– Run the ADKSetup.exe as an administrator

– I left the path’s default and choose Next
– Choose if you want to join CEIP and choose Next
Accept the Licence Agreement and choose Accept
– Check Deployment Tools, Windows Preinstallation Environment (Windows PE) and User State Migration Tools (USMT)

– Choose Next and install the Software

3. Next step is to install SCCM 2012 SP1 Beta
Ok, we are now ready to install ConfigMgr 2012 SP 1 Beta
– Launch the spash.HTA from the installation media

– First check the server is ready before we get any further into the installer Select Assess server readiness

Some minor issues but no show stoppers so lets continue
– Go back to the Splash.hta screen and click Install, Choose Next
– Because we are on one demo server we choose Install a Configuration Manager Primary Site and check the Use typical installation… Choose Next.

– Choose yes and I Agree, Next
– Accept all the licence therms and choose next

– Download the files to a folder you choose and click Next

-Choose a site code, Site name and installation folder for SCCM 2012 SP1, Next

– Hit next a couple of times and then choose Begin Install

That’s it, we are now up and running.

SP1 brings a lot of nice new stuff like the cross-platform clients, Azure Cloud DP, mobile device management through Microsoft Exchange ActiveSync amongst others.
Check out what’s new in SP1 here for a list of fun things to play around with and get to know in preparation for the actual SP1 release, as well as the release notes detailing what is knowing to be in a broken state during the Beta. You can also provide feedback to Microsoft for anything quirky that you may find during the evaluation.

Have Fun!

Creating Device Collections in SCCM 2012

Create collections in System Center 2012 Configuration Manager to represent logical groupings of users or devices. You can use collections to help you perform many tasks including application management, deploying compliance settings, or installing software updates. You can also use collections to manage groups of client settings or use them with role-based administration to specify the resources that an administrative user can access.

This article limits to collection based device collection groups.

Step 1 – Building / Creating custom Device Collections in SCCM 2012
1. In the Configuration Manager Console, click Assets and Complicance.
2. Right Click Device Collections and choose Create Device Collection
3. Type the Device Collection Name, choose Browse to limit the Collection; we choose All Systems in this example.

4. Choose Add Rule and choose Query Rule
5. Type the Query Rule name (we used Query – <Query name>), and click Edit Query Statement
6. Choose the Criteria Tab and click on the Star

7. Choose Select
7. Make you’re query statement (see some simple examples below)

Collection based on computers in a specific group:
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: System Group Name
Operator:  is equal to
Value:    <Group Name>

Collection based on computers in a specific Active Directory OU
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: System OU Name
Operator:  is equal to
Value:    <OU Name>

Collection based on computers in a specific Active Directory Site
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: AD Site Name
Operator:  is equal to
Value:    <AD Site Name>

Collection based on computers with a specific program in Add/Remove Programs
Criterion Value:  Simple
Attribute Class: Add/Remove Programs
Attribute: Display Name
Operator:  is equal to / is like
Value:    <Program Name>

Example Collections:
 -SQL Servers:
Value: Add/Remove Programs Display name is like “%Microsoft SQL%”

Collection based on computers with a specific file Criterion

Criterion Value:  Simple
Attribute Class: Software Files
Attribute: File Name
Operator:  is equal to
Value:    <File Name>

Collection based on computers in a specific Operating System
Criterion Value:  Simple
Attribute Class: System Resource
Attribute: Operating System Name and Version:  is like
Value:    <%NAME%>

Example Collections:
– Windows Vista:
Value = %Workstation 6.0%
– Windows 7:
Value = %Workstation 6.1%
– Windows 8:
Value = %Workstation 6.2%
– Windows Server 2008:
Value = %Server 6.0%
– Windows Server 2008 R2:
Value = %Server 6.1%
– Windows Server 8:
Value = %Server 6.2%

Collection based on computers of a specific hardware model Criterion
Criterion Value:  Simple
Attribute Class: Computer System
Where: Model
Operator:  is equal to
Value:    <Model>

Direct
Rule Direct rules let you to choose the users or computers that you want to add as members to a collection. This rule gives you direct control over which resources are members of the collection. The membership does not automatically change unless a resource is removed from Configuration Manager. Configuration Manager must discover the resources or you must import the resources before you can add them to a direct rule collection. Direct rule collections have a higher administrative overhead than query rule collections because you must modify this collection type manually. For more information about direct rule collections, see How to Create Collections in Configuration Manager.

Query
Rule Query rules dynamically update the membership of a collection based on a query that Configuration Manager runs on a schedule. For example, you can create a collection of users who are a member of the Human Resources organizational unit in Active Directory Domain Services. Unlike direct rule collections, this collection membership automatically updates when you add or remove new users to the Human Resources organizational unit. For more information about query rule collections, see How to Create Collections in Configuration Manager.

Include
Collections Rule The include collections rule lets you include the members of another collection in a Configuration Manager collection. Configuration Manager updates the membership of the current collection on a schedule if the membership of the included collection changes. For more information about the include collection rule, see How to Create Collections in Configuration Manager.

Exclude
Collections Rule The exclude collections rule lets you exclude the members of another collection from a Configuration Manager collection. Configuration Manager updates the membership of the current collection on a schedule if the membership of the excluded collection changes. For more information about the exclude collection rule, see How to Create Collections in Configuration Manager.