Windows, Office, Xbox More. For printers, cameras, network cards, and more. Managing Workgroup Clients in System Center 2. Configuration Manager Chris Sugdinis. Here are some key points to consider when managing workgroup based Config. Mgr 2. 01. 2 clients. The flufffree SCCM course that shows you how to install and administrate SCCM within your network, screenbyscreen. Distribution Points. Lets start by addressing the types of boundaries that a Configuration Manager 2. A workgroup client cannot use Active Directory Site boundaries. This is because a workgroup operating system isnt joined to a domain so the operating system itself does not have the permissions required to query Active Directory Domain Services to determine what AD site it is in. Default outofthebox booting on WinPE with SCCM 20122016 is quite slow Ive seen boot times up to 20 minutes. This is because System Center Configuration. The same condition is true of a domain joined computer that is a member of a different forest. A workgroup client strictly uses boundaries based on IP subnet boundaries, IP address ranges and IPv. The only exception to this rule is an isolated case that has to do with the workgroup computer build process during Operating System Deployment OSD. As a result, workgroup systems cannot supply the AD Site in their boundary request and the MP does not resolve the AD Site for usage in the location stored procedure calls. Below is an example from MPLocation. XmN189nbMc/maxresdefault.jpg' alt='Download Software Updates Sccm 2012 Practice' title='Download Software Updates Sccm 2012 Practice' />AD Site. MPGet. Content. DPInfo. Unprotected PR1. PR1,SMSPackage,0. CWS Contoso. com,CWS Contoso. Client. Location. Info Location. TypeSMSPackage Distribute. On. Demand0 Use. Download the latest from Windows, Windows Apps, Office, Xbox, Skype, Windows 10, Lumia phone, Edge Internet Explorer, Dev Tools more. Azure0 Allow. WUMU0 Use. Protected0 Allow. Caching0 Branch. DPFlags0 Use. Internet. DP0 Allow. HTTP1 Allow. SMB1 Allow. Multicast1 lt ADSite NameDEFAULT FIRST SITE NAME lt Forest NameCWS Contoso. Domain NameCWS Contoso. IPAddresses lt IPAddress Subnet. Address1. 92. 1. Address1. IPAddresses lt Client. Location. Info Next is similar MPLocation. The AD Site Name is no longer returned and all content location requests are determined based on IP Subnet or IP Range data alone. MPGet. Content. DPInfo. Unprotected PR1. PR1,SMSPackage,0. Client. Location. Info Location. TypeSMSPackage Distribute. On. Demand0 Use. DPFlags0 Use. Internet. DP0 Allow. HTTP1 Allow. SMB1 Allow. Multicast1 lt ADSite Name lt Forest Name lt Domain Name lt IPAddresses lt IPAddress Subnet. Address1. 92. 1. Address1. IPAddresses lt Client. Location. Info When looking at the properties of a workstation client, the Active Directory Site Name property is always null even when the client is installed and the machine is in a managed AD Site boundary. The Configuration Manager agent retrieves the Active Directory Site Name from the OS if it is available and later returns that information to the site MP when making content location requests. Adobe Acrobat Install Error 1606 Could Not Access. The Config. Mgr agent also includes AD Site Name in heartbeat discovery DDR data if it exists. In both cases, for a workgroup client this property will always be null. The reason the Active Directory Site Name is null in the screenshot above is because the operating system cannot read Active Directory Domain Services to determine which AD Site that the system resides in. If you use AD Site Boundaries as your standard boundary type but are presented with the requirement to start managing workgroup clients, you have two options. Leave your AD Site boundaries as is and chose not to add the equivalent IP subnet or IP range boundaries. If you chose this option, your workgroup clients always use your fallback DPs provided you use the Allow fallback source location for content option see screen shot below during deployments. This is often an acceptable situation as the percentage of workgroup clients in the environment is usually very small. The other alternative is to keep your AD Site boundaries in place and change your process to allow adding the equivalent IP subnet or IP range boundary alongside your AD Site boundaries. If you currently use IP boundaries as a standard but you are migrating to the use of AD Site based Boundaries, then its fine to add those equivalent AD sites to the same boundary groups. Your domain joined clients will always use the AD Site boundaries and they will ignore the IP subnet boundaries. The workgroup clients will continue to use the IP boundaries and will be unaware of the AD Site Boundaries. If you have a relatively small number of workgroup clients to manage and you dont have your IP Subnets or IP Ranges mapped out in your boundaries, then your clients will always pull content from a fallback DP. If this is the route that makes the most sense for you then just insure that your deployments are configured to allow fallback because the workgroup clients require it. There is flexibility in managing workgroup clients and the choice is yours. You can optimize your environment for workgroup clients by insuring that you have IP Subnet or IP Range boundaries defined where applicable to your network topology. This is the ideal choice as it will allow your workgroup clients to consistently retrieve package content from the closest DPs. This may be a time consuming process but the payoff may be significant if your workgroup client population is large and your network is running at full capacity. If the number of workgroup clients in your environment is small, your network is robust, and you use AD Site boundaries as a standard, you may want to consider the alternative of leaving your boundaries as is and just standardize your workgroup client deployment process to always allow fallback. You can decide on a blend between of the two choices above to address key areas on your network where fallback behavior would not be a good idea on an ongoing basis. Workgroup Client Installation. To install the client when you have no IP subnets or IP range boundaries defined for site assignment, use the following example. It is a time saver. Example Command line. SERVERSMSPRIClientccmsetup. SMSSITECODEXYZ SMSMPserver. DNSSUFFIXcorp. contoso. FSPserver. 02 noservice By specifying the SMSSITECODE and not using AUTO, you are telling ccmsetup to install the agent to a specific site regardless of how your boundaries are defined. There is no dependency or need for IP subnet or IP range based boundaries for the purposes of client installation if you are specifying the actual site code that the client will use. Specify the management point using the SMSMP parameter. This is an important parameter when not using auto assignment. Specify the DNS suffix using the DNSSUFFIX parameter. Specify the Fallback Status Point using the FSP parameter. Specify the noservice parameter so that the installation runs under the context of the currently logged on user for the entire duration of the installation. By default, ccmsetup. This means that ccmsetup. The local system account of a workgroup computer does not have rights to a domain joined primary site server so if you try to run ccmsetup. The local system account of a workgroup computer will not have rights to the network share on a primary site server to pull down additional required files and the install will fail. When viewing ccmsetup. Source folder cws r. SMSPR1Client is invalid. Skip it. Below is a more detailed snippet from ccmsetup. Command line C WINDOWSccmsetupccmsetup. SMSPR1Client SMSSITECODEPR1 SMSMPCWS R2. PR1. CWS Contoso. CWS Contoso. com FSPCWS R2. PR1. CWS Contoso. PM 3. 32. 4 0x. 0CFCSource folder cws r. SMSPR1Client is invalid. Skip it. ccmsetup 62. PM 3. 32. 4 0x. 0CFC Local System account cannot access this network shareSsl.