Clicking the applet will give you a Properties window for the agent that will give you some information: Further you can see the information on the agent on the remote server by launching Control Panel and you should see Configuration Manager in the list of applets. This means that the installation was successful. At the end of the log, you want to see this:ĬcmSetup is exiting with return code 0]LOG] The ccmsetup.log file will actually contain the complete information of the client installation from beginning to end. On the remote server, you can see the following items to know that the install is running:Īnd you will also see a new folder here: %windir%\ccmsetup and within that folder, you’ll see several files, the Endpoint Protection installer, and the agent install log files among them: The installation will begin immediately on the remote client. Then in the wizard make sure you select the options as seen below: Right click on the server and select Install Client. Navigate to Devices and find the server you want to push the agent to. We will be pushing the installation to our servers. Now here is the part where we will be installing the agent. Now when the agent is installed on our servers, they will be a member of the “All Desktop and Server Clients” collection, and we can now run Reports based on our custom Collection Group we just created. For now we are just doing all servers, but you could break this down by Country, Datacenter location, Client Groups, Server Types, etc. Notice we will have a folder under the “Device Collections” section, and within that folder we are creating a Collection that can contain multiple device collections. The screenshots below show the process for doing this. I added the “All Desktop and Server Client” Collection as by default, all SCCM managed servers will be added to this collection. Now you need to name your Collection, I named mine “Endpoint Protection Managed Servers” and add what existing collections you want added to this group. This will launch the “Create Device Collection Wizard”. Then select your new folder and right-click and select Create Device Collection. I named my Device Collection “Endpoint Protection Servers”. Then navigate to Overview and right-click Device Collections. Open the SCCM console on your server and open the Assets and Compliance workspace. – That the SCCM server sets the child server to Active – That all SCCM and SCEP Policies we defined earlier are enforced
– The Endpoint Protection software installs Here is a summary of what we’ll be making sure happens between the SCCM server and the Clients: Here in Part VII, we will be pushing the client to servers, showing what the Endpoint Protection client looks like on the servers, configuring custom Reports, and then closing out the series.
This will be the last post in my System Center Configuration Manager 2012 series.
0 kommentar(er)
