Join David M. Franklyn for an in-depth discussion in this video Discovering System Center clients and adding agents to devices, part of Microsoft System Center Configuration Manager Essential Training.
- [Narrator] In this demonstration as we add the clients and the client agents devices we have three main parts we're going to cover. First we're going to do discovery and create boundaries for the two domains, and set up the discovery methods to find a client computer in the users from the active directory. Then we'll use client push to install the client agent on the client computer called client one.Dave MCT.com, and then in the third part we'll examine the local configuration manager item in the control panel on the client, and in the configuration manager console we'll examine the client and the users in the collection.
So we start out here on the north AM CFG2 site since that is the primary site for the Dave MCT.com domain where the client actually resides, and it's important to know that we cannot manage clients directly from the central administration site. It doesn't have clients. We could actually do a lot of these steps there, but there's no clients that are directly attached to that. That would be attached to this particular site. That is the NA one rather than the CAS.
So in the administration work space we're going to go to the hierarchy configuration and expand that, and then go to boundaries, and note we have no boundaries at this time. So, we're going to create a boundary. So right up here in the ribbon we have the create boundary item. We can click on it and the description is we're going to call this the Atlanta boundary, and in the network field we're going to put in 172.16.0.0, and that just identifies the subnet we're using in Atlanta, and in the subnet mask 255, 255, zero, zero, and then say okay, and we'll repeat that step to make the Charlotte boundary for the 172 16 network.
So create boundary. I'm going to call this the Charlotte boundary and we're going to use an IP subnet. The address is going to be 172.17 zero zero, with a subnet mask of 255, 255, zero, zero, and say okay to that. So now we have boundaries for both Atlanta and Charlotte based on their IP addresses, and at this time we're going to create a boundary group for those.
So, we select boundary groups in the console tree and then click create boundary groups and in this case we're going to name the boundary group the North American boundary group, and in the North American boundary group that we've created we're going to click the add button below and select those two boundaries, and then say okay to that, and then that's it. We say okay to that. In the next step we're going to now bring up the active discovery method.
So we need to go to our discovery methods in the console tree and the first one we're going to set up is the active directory system discovery. So we can go to active directory system discovery, double click it, and enable it, very importantly, enable it, and none of them are enabled except for heartbeat, and we're going to apply it to a particular container in the active directory so we click the new button, which looks like a yellow sun.
So we click that, and we will browse to the active directory container which in this case is just going to be the entire domain, and say okay to that. So as you see, it's a LDAP DC equals Dave MCT, DC equals COM and note that it's set to recursively search all the child containers within this. So that will go down and look for even our child domains, like east, and any system that's there, and now we click okay, and okay again, and in the pop up window we say yes to the do you want to run full discovery, and now we're going to do the same thing for the east-cfg site server.
When we do this for the ECFG we want to set up the site boundaries there. When we go back to the CAS, once everything has been pushed up the database there, we'll be able to see all of them from there. But let's go ahead and now connect to east CFG three. We'll log in as the domain administrator. Then we'll go ahead and bring up configuration manager console, and from here we're going to go to the administration work space, and then to the hierarchy configuration, and we'll go into boundaries, which we now see the two boundaries we created for Atlanta and Charlotte.
That's actually now starting to propagate throughout the whole hierarchy, but we're going to create a boundary for the other two locations, and the first one is called the Seoul boundary and the subnet for it is 172 18 zero zero, with a 255, 255 mask, and then say okay to that, and we'll make one more for Singapore, and call it the Singapore boundary, and the IP address will be 172 19 zero zero, with a 255, 255 mask, and say okay.
We will go now down to the boundary groups, and we're going to create a new boundary group, and that's going to be called the east boundary group, and we'll add to it the Seoul and the Singapore boundaries, and then say okay. Now we're going to actually set up a discovery method. We see that we don't have the active directory system discovery shown enabled here for this site. So let's go ahead and do that now by double clicking it and enable it and now we're going to click new for the active directory container, and in this case when we browse for the container we can actually just say the east domain.
It's a child domain of the Dave MCT.com domain. Say okay to that, okay again, and yes to do full discovery as soon as possible. Now a couple other things we're going to do. We can go back to our boundary group and in the case of our boundary group select the North American boundary group, and go to the properties thereof, or double click it to get the properties. Go to references and at references what we're going to do is use the boundary group for site assignment.
That's what we want to do. So use this boundary group for site assignment, but the assigned site will be NA one, and the site system server we can set up as north AM, and say okay to that, and do the same for the east but in the east CFG server, and the east area. We want to go to properties here, and go to references, and again, use this boundary group for site assignment. It's going to be ES one and we're going to add the east CFG server, and say okay to that.
So now we're going to go over to our central CAS server and here we are now on the central CFG one. So we'll go into the configuration manager console and in the configuration manager console we're going to go to the administration work space, and then expand site configuration and select servers and site system roles. So in this case, we're going to select the north AM CFG two computer and if you go to the home tab, it will actually bring you up things that you could either right click to get to or just use the ribbon, if we click the home tab in the ribbon.
But in any case we're going to add a site system role to north AM, so we have the ribbon item add site system roles, so we can click that, and this brings up the add site system role wizard. Now if you're ever using your infrastructure over the Internet you want to make sure you're using fully qualified domain names to do so. As we see in the name that we have already listed here and populated but not changeable it already is the fully qualified domain name. So we wouldn't need to click on that, but in any case, it's always a good habit to put that in if it doesn't show up as fully qualified in the name field.
Let's click next. We're not using any type of proxy server, so we can click next, and in this case we're going to add the role which is the fall back status role. So what this tells clients is if you cannot find your site that you're supposed to be identified from your IP address because we created a boundary for that, then come back to this site and start getting information from this site in your configuration manager client, such as what site you belong to.
So it's as simple as that. It's a fall back, and from there things can happen. So we're going to click next here, and we're allowing client connections. Click next, and here's the confirm the settings page. Click next and it will go ahead and add that role. We can close at this time, and now you see with north AM CFG two selected we have a new role here in the fall back status, along with the component server, the distribution and management point, and the site database server.
Okay, now we're going to do the second part we talked about which starts off with us ensuring a couple of things. First we need to check the firewall in the clients and we need to make sure that the file and printer sharing inbound connection is enabled, and the Windows management instrumentation WMI is also enabled on the inbound domain profile. So I will now go to the client system. So here we are on client one, and that belongs to the Dave MCT domain.
So let's make sure we log into it as the Dave MCT administrator, that is, the domain administrator. So here we are on the desktop of a Windows 10 computer and what we're going to do here is bring up the firewall. Since we're logged in as administrator, we can type in WF.MSC, and in our inbound rules is where we're lookaying for this. We need to ensure as we said before file and print sharing and also WMI.
So we scroll down a little bit we'll find file and print sharing echo requests, and we just want to enable these rules and we want to enable just the domain rules. So if you see the profile that's applied and file and print sharing just to the domain and enable those. And then, after the last one of the domain profiles we'll scroll down and find Windows management instrumentation and again we want to just enable the domain profiles for WMI.
And that's it. Now we'll return tot he north AM computer system, and from here in the administration work space we want to go to site configuration, expand that, and go to sites, and we're going to go in the ribbon to the client installation settings, and then we're going to go to our client push installation, and we're going to enable automatic site wide client push installation, and in the accounts tab, we want to make sure we have a user account that can do this.
So we've created a SSCM run as account to make this happen. So let's click on the new button and say new account and we're going to browse for this in the domain as SCCM run as. Check the name on that, and there it is. Say okay, and the password. Now we want to verify this before we go any further to make sure it's going to work. So we're going to click the verify button, and then just provide a network share on any computer.
It can even be the same computer we're on, so long as it can use a UNC name to go out to that CFG two, and look, we have all of the various shares available to us. So let's just take the one where you had the prerequisite downloads and then click the test connection button, and it was successfully verified, so that's good. We can say okay and now we want to go to the installation properties and you see in this case it's going to assign the site code of NA one to the system.
But we want one other thing to be done here, and that's use the site assignments we set up earlier. So we're just going to append to this a space and in caps the word site reassign, one word. Site reassign, and that's going to be equal to true and then say okay. Now after a period of time we can go into assets and compliance and go into devices and we'll actually see our device and eventually we'll see the client status go from no to active.
At this time, of course, we don't see that, because we just kicked this off. If we now go over to the central administrations site and see what's in there it might not be completely populated obviously, until it's done so here on the north AM CFG two, since it is the NA one site. Let's go ahead and take a look. So here we are now on central CFG one, and we see the client one and laptop one computer. We can then click on the client one computer and then say install client in the ribbon above, and in the install configuration manager client wizard click next.
So we have the first option which is allow the client software to be installed on the domain controller. We're not going to select that, and then the second is always install the client software, and what this will do is even if it's already installed it will reinstall it, and this can actually help repair it or if we're doing some of the Windows 10, Windows as a server updates that has a whole new thing, such as the creators edition that we've just recently seen. Well, this will reinstall it if it is somehow corrupted in this process and also what we want to do is install the client software from a specified site.
So in this case we're going to say it's a North American site, and now click next and click next, and then close. Now we're not seeing an update yet in these areas, and you won't for a while, because it does take time for the clients to actually install and then be available to start taking policies from the management point. But let's go ahead and take a look at one of the clients. We can go back to client one.
So we're on client one and let's go ahead and go to the control panel. We can right click the start menu and go to control panel and then in the control panel expand the system and security node, and scroll down and check to see if the last item is the configuration manager icon. It's not. Now we want to check to see if it's actually installing. So what we want to do is then go to task manager. We can right click the task bar, and then select task manager, and what we're looking for is this right here, CCM setup.exe.
That is the configuration manager set up. This is the push, the software installation, that's taking place. After a while, we will then be able to see the configuration manager console within the control panel. It's just not available for us yet, because it's in the early stages of its installation, and we see the CCM setup program is no longer there. It's more or less finished. It might still be configuring things, but the initial installation program is no longer running.
Let's go back to the control panel, and let's refresh it, and we still don't see the configuration manager component yet, but it does take time to populate on this system. So we'll come back and check in a little while. Now return to the central CFG one configuration manager console. Now we can see that client one is showing as a client, and it's showing that it is in the NA one site. So now let's go back to client one and see if we have our configuration manager applet yet.
So here we are back on client one. Let's refresh the control panel, and it's still not there. But we know it is a client. It's showing up now in the devices as a client. Let me close this and start it up again. Sometimes we are required to do that just to ensure that we've refreshed things. There it is. So, didn't see it before. Now it's there. By closing the control panel rather than refreshing we can double click it or just click on it, and it brings up the configuration manager properties.
So we can see some of the information, such as the site code is NA one, that it does belong to the management point north AM CFG two, Dave MCT. We can see the components that have now either been installed or enabled or are disabled, and when we go to the actions we can see the various actions that we have available. Now actions is a very important part of the configuration manager properties because things are done in configuration manager within its own time.
In other words, things don't happen instantly, and sometimes things take a much longer period of time to occur, such as things like software metering usage data or a software inventory or a hardware inventory. So what we need to do in this case, if we want to kick them off instantly, especially if we're testing and debugging, we would then create whatever policy, such as an inventory or some application deployment, and then we'd first go to the machine policy retrieval and evaluation and select it and then say run now, and what that forces the client to do is that will cause that policy that we've just written to, rather than waiting seven days or whatever time period we assign for it to update things, to occur instantly.
So in this case, if we just started a hardware inventory, and we'll see this in a few minutes, but if we just start a hardware inventory and then we click the machine policy and retrieval and did the run now, then eventually that hardware inventory node or action would appear in this list, and then we could click on it and also run now on it to force the hardware inventory to take place. So let's go ahead and close this. So at this point we have the client configured.
Let's go ahead and close the control panel, and head on back over to central CFG one, and now that we have the client, that ends the demonstration on discovering system center clients and adding agents to devices.
- Planning and deploying a standalone primary site
- Ensuring domain and site server prerequisites
- Planning and expanding a standalone primary site
- Planning and deploying a multiple-site hierarchy
- Planning resource discovery and client deployment
- Managing content and replicating data in Configuration Manager
- Configuring Internet and cloud-based client management
- Advanced monitoring
- Upgrading to Configuration Manager current branch