Endpoint Services, MECM, Install the MECM client on endpoints
Install MECM client on managed endpoints
Microsoft Endpoint Configuration Manager (MECM, formerly SCCM)
University of Illinois IT Pros leveraging MECM, hosted by Technology Services' Endpoint Services team
Deploy the client to on-campus endpoints
Using Client Push via the admin console is the easiest and least troublesome method in 2 steps:
Place the primary site computer AD object name for your campus into the Administrators group on all endpoints via Group Policy (see the table below for the server list). You can also add a group to the endpoint's Administrators group which contains the relevant AD object as a member. MECM will recursively look into subgroups to find the computer object for your campus listed below.
AD object name Hostname Campus SCCMUICPS1 SCCMUICPS1.ad.uillinois.edu Chicago SCCMUIUCPS1 SCCMUIUCPS1.ad.uillinois.edu Urbana-Champaign
Initiate a Client Push to your endpoints via the admin console by following Microsoft's directions. Deploy the client to off-campus endpoints
Create a collection of your unit's off-campus endpoints with an old client version
When creating the collection, include your unit prefix when naming the collection (e.g. UIUC-YourUnit-***) and select your unit's all systems collection as the limiting collection
Select 'Query Rule' from the 'Add Rule' drop-down, include your unit prefix naming the query and select 'Edit Query Statement'
Select the Criteria tab and the first 'sun' icon to open the 'Criterion Properties' dialog box
Input the following values
Criterion type: SubSelected values
Where: Click 'Select', for 'Attribute class' select 'System Resource', for Attribute select 'Resource ID'
Operator: 'is in'
Subselect: select resourceid from SMS_CollectionMemberClientBaselineStatus where SMS_CollectionMemberClientBaselineStatus.CNIsOnInternet = 1
Click OK to save.
Select the sun icon again to open the 'Criterion Properties' dialog box, then input the following values
Criterion type: Simple value
Where: Click 'Select', for Attribute class select 'System Resource', for Attribute select 'Client Version'
Operator: 'is less than'
Value: Click 'Value' and select the
largest value, usually at the bottom of the list. Click OK twice to save.
Click OK to save and close the Query Statement Properties dialog box, then click OK to save and close the Query Rule Properties dialog box
Click next to save and close the collection
Once the new collection populates, right-click the collection, select 'Deploy' and 'Program'
Search for https in the filter, select '[version] Install via HTTPS' and click next
Be sure to select the latest version. The version number will increase with each MECM update to our environment.
Select your unit's distribution point group
Select 'available' for self-service deployment via Software Center, or 'required' for a mandatory deployment
Select 'Send wake-up packets' and click next
Click 'New' to specify the assignment schedule
For 'Rerun behavior', select 'Never rerun deployed program' and click next
For self-service deployments via Software Center, select 'Allow users to run the program independently of assignments' and click next
On the 'Distribution Points' page, select 'Download content from distribution point...' for both drop-downs
Select 'Allow clients to use distribution points from the default site...'
Click next to start the deployment
For new versions of the client:
Right-click your collection of off-campus endpoints and select 'Update Membership'
Navigate to \Software Library\Overview\Application Management\Packages and select the older 'HTTPS Client Package [version]' package.
Select the 'Deployments' tab in the bottom window and delete the old '[version] Install via HTTPS' program deployment
Select the newest 'HTTPS Client Package [version]' package and deploy the '[version] Install via HTTPS' as per step 8
Review these Microsoft articles for additional information on client installation methods:
Contact the EPS team