Home > Enterprise Mobility Management > Device Enrollment > Systems Manager Installation using Active Directory GPO

Systems Manager Installation using Active Directory GPO

Table of contents
No headers

In large environments, it isn't time efficient to install software on individual PCs one at a time. In order to perform tasks like deploying the Systems Manager agent in bulk, administrators of Windows environments with Active Directory can make use of Active Directory Group Policy Objects to administratively push software out to a large number of devices.

 

For more information on GPOs, requirements, and any Microsoft or Active Directory questions, please consult Microsoft's documentation for software installation using Active Directory GPO.

 

This article will cover the steps required in a typical Active Directory environment to push out the System Manager client for Windows to devices across an AD domain.

 

1. Choose your Systems Manager network from the Networkdrop-down, then go to MDM > Add devices > Windows.

 

2. Download the Windows installer image by right-clicking on the Download link and saving the .msi file to the Desktop

 

3.  Move the .msi file to a shared location; in this example it's a "Software" folder on a file server.

 

20845443-0887-4dde-9283-ab8a9ccc2a14

 

4.  Start the Group Policy Management tool.

 

d1bf09d0-5ac7-4a73-b51a-480e953298a5

5. Navigate to [your_company_name]-Computers, right-click, and choose "Create a GPO in this domain and link it here..."

 

9acf8fc1-8396-44ba-8bef-4307d9be927f

 

6. Give the GPO a name, for example "systems manager" or "Meraki Systems Manager"

 

450a8e06-6977-4e06-b5d9-54fee44f8a48

 

7. Under "Group Policy Objects", find the GPO you created, right-click on it, and choose "Edit..."

 

d5af37a2-9c16-424e-804a-3bd7e79fd190

 

8. In the window that pops up, navigate to "Computer Configuration" to "Policies" to "Software Installation"; right-click it and choose "New" and "Package..."

 

8cc69d09-02bc-4b6b-aaed-eb9fd073ef0e

 

9. Browse to- or type the full path of the .msi package on the share.

 

30f68244-b64b-4b15-9c33-ebddb27e777c

 

10. In the "Deploy Software" window that pops up, leave setting to "Assigned".

 

ae62734c-2ef6-43a4-96be-5e212f6df076

 

11. Right click the entry you created and enable "Enforced"

 

c836e5b4-b04b-4d7a-84b7-e2838b70322d

 

12. Start a shell by clicking on the Start button (then "Run..." on some versions of Windows") and typing "cmd".

 

5f50dc9e-8dea-40e9-83f5-b3c4a8747108

 

13. In the cmd shell that pops up, type "gpupdate /force"

 

160b8ed8-8340-4ff4-a508-d1a708d7682c

 

14.  Wait until gpudate completes.  You are done.

 

d215d43f-d2cd-4696-9783-973540018392

You must to post a comment.
Last modified
16:39, 26 May 2017

Tags

Classifications

This page has no classifications.

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community