How to Install Configuration Manager Clients on Workgroup Computers
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
Configuration Manager 2007 supports client installation for computers in workgroups. You can install workgroup computers using the method specified in How to Install Configuration Manager Clients Manually.
The following prerequisites must be met in order to install the Configuration Manager 2007 client on workgroup computers:
The client must be installed manually on each workgroup computer. During installation, the logged-on user must possess local administrator rights on the workgroup computer.
The workgroup computer must be able to locate a server locator point to complete site assignment because they cannot query Active Directory Domain Services. The server locator point can be manually published in WINS, or it can be specified in the CCMSetup.exe command line properties.
In order to access resources in the Configuration Manager 2007 site server domain, the Network Access account must be configured for the site. For more information, see How to Configure the Network Access Account.
There are a number of limitations to supporting workgroup computers in WINS:
- Workgroup clients cannot locate their default management point from Active Directory Domain Services, and instead must use DNS, WINS, or a server locator point. For more information, see Configuration Manager and Service Location (Site Information and Management Points).
Workgroup clients assigned to native mode sites cannot locate management point information in WINS. The preferred alternative method for workgroup clients to find their default management point is to use DNS publishing. For more information, see Determine If You Need to Publish to DNS.
Global roaming is not supported, because clients cannot query Active Directory Domain Services for site information.
Native mode clients cannot be automatically configured for options related to native mode, such as native mode communication, certificate selection, and the option to allow HTTP communication for roaming and site assignment. These options must be specified using CCMSetup.exe command line properties.
Active Directory discovery methods will not discover computers in workgroups.
Advertisements targeted to users are not possible.
The client push installation method cannot be used to install the client on workgroup computers.
A workgroup client cannot be used as a branch distribution point. Configuration Manager 2007 requires that the branch distribution point computers be members of a domain.
Examples for Installing Configuration Manager Clients on Workgroup Computers
In the following examples, the Network Access Account is configured, a server locator point is installed on a computer named SLPSERVER, and the default management point is installed on a computer named MPSERVER. The site is named ABC and the domain is contoso.com. All site system servers are configured with an intranet FQDN.
You map a drive to \\MPSERVER\SMS_ABC\Client and then run one of the following commands.
Example 1: CCMSetup.exe SMSSLP=slpserver.contoso.com SMSSITECODE=ABC DNSSUFFIX=constoso.com
This example installs the client in mixed mode for intranet client management, specifies the server locator point because it is not published to WINS, and specifies the site code and DNS suffix to locate the default management point.
Example 2: CCMSetup.exe FSP=fspserver.constoso.com
This example requires WINS to publish the management point and server locator point. In addition, the client must be on a network location that is configured as boundary so that automatic site assignment can succeed from the server locator point. The command installs the client in mixed mode for intranet client management, it does not specifies the server locator point because it is published to WINS, and specifies a fallback status point on server FSPSERVER, to help track client deployment and to identify any client communication issues.
Example 3: CCMSetup.exe /native CCMALWAYSINF=1 CCMHOSTNAME=mp2server.contoso.com CCMFIRSTCERT=1 SMSSITECODE=ABC
This example installs a workgroup computer for native mode without CRL checking and for Internet-only client management. The client is assigned to the Internet-based management point named mp2server.contoso.com in the ABC site, and if there are multiple PKI client certificates, the client will select the certificate with the longest validity period. For this command to succeed, the client must have a valid client PKI certificate installed and trust the server PKI certificate on the Internet-based site system servers in the ABC site.
This example is suitable for installing the client from the intranet. If the computer is on the Internet and is not connected over a VPN, you cannot run CCMSetup.exe from a mapped drive. Instead, provide the installation files locally (for example, on removable media) and use the /source: command to specify the location of the installation files. For example: CCMSetup.exe /source:E:\Client /native CCMALWAYSINF=1 CCMHOSTNAME=mp2server.contoso.com CCMFIRSTCERT=1 SMSSITECODE=ABC
Overview of Configuration Manager Client Deployment
How to Install Configuration Manager Clients Manually
About Configuration Manager Client Installation Properties
Decide If You Need to Configure HTTP Communication for Roaming and Site Assignment (Native Mode)
Determine If You Need a Server Locator Point for Configuration Manager Clients
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.