Supporting ConfigMgr. workgroup clients

In order to successfully discover and install the ConfigMgr. clients on workgroup computers you need to configure a few settings.

  • Configure a Server Locator Point
  • Configure the proper client installation settings
  • Configure the network discovery method
  • Configure the Network access account
  • Configure the client push installation account.

Site Systems

When you are working with clients that are not able to query the Active Directory services for ConfigMgr information you need to create a Server Locator Point – SLP. In my example I have one SLP a the central site. The SLP is used by the client during the site assignment process.

Client agent installation settings

My client push account has these settings: smssitecode=s01 smsmp=sea-cfg1 smsslp=sea-cfg1 fsp=sea-cfg1 where sea-cfg1 is the name of my site server and s01 is the site code


In order to use client push I need to define a local account on the workgroup computer. In ConfigMgr. I can create a reference to that account by specifying $computername$\accountname (or %computername%\accountname).


I you have multiple passwords or accounts then specify each of them. ConfigMgr. will try each of the accounts until it succeeds.

Network access account

The network access account is used by the workgroup clients to connect to the configmgr. infrastructure like the distribution points. When specifying the account make sure that it doesn’t have administrative permissions in the domain, a “normal” domain account will do just fine. You specify the account in site settings, client agents, computer client agent.

Network discovery

In order to discover workgroup clients you need to configure Network discovery. Before you configure this make sure that the site server is member of the DHCP users group in the domain (otherwise the DHCP discovery will fail). Also make sure you have restarted the site server after adding the server to the group.

In network discovery I use the DHCP tab and fill in the name or IP address of the DHCP server. Next configure the discovery schedule, make sure that you configure the start 4-5 minutes ahead of the current time (otherwise the discovery process might never start).

Once you have configured these settings you will be able to use client push to install the configmgr. client on workgroup computers. The clients will appear in the administrator console just like a domain computer. Only issue is the approval of the client. By default only domain computers are automatically approved. The approval setting is controlled on the site properties.

Troubleshooting tips

To troubleshoot the client push account, monitor the ccm.log file on the site server.

To troubleshoot the network discovery, monitor the netdisc.log file on the site server.

To troubleshoot the client assignment process, monitor the clientlocation.log file on the client.

By | 2009-11-02T09:41:20+00:00 November 2nd, 2009|Configuration Manager (SCCM)|4 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.


  1. Eswar koneti November 16, 2010 at 13:28 - Reply

    in addition to the above,here is Step by Step guide managing Work Group computers in SCCM environment

  2. When someone writes an article he/she retains the idea of
    a user in his/her brain that how a user can be aware of it.
    Thus that’s why this article is outstdanding.


  3. Cyndy June 3, 2014 at 15:21 - Reply

    Is this still relevant for SCCM 2012 r2?

  4. naked eliquid April 3, 2017 at 15:57 - Reply

    “Great artical, had no problems printing this page either.”

Leave A Comment