Topic last updated—August 2007
This section provides troubleshooting information to help you resolve issues that are specific to Configuration Manager 2007 clients when they are operating in a mixed-mode site. For issues that affect both mixed-mode and native-mode clients, see Configuration Manager Client General Issues.
Most client troubleshooting issues that are specific to mixed-mode operations relate to the approval process. For more information about client approval, see About Client Approval in Configuration Manager.
Clients Fail to Automatically Approve (Mixed Mode)
If Configuration Manager 2007 clients do not automatically approve, even though you are using the default site setting of Automatically approve computers in trusted domains (recommended), the following situations might be the cause:
- Client computers do not belong to the same
domain as the site server's domain, and the site's default
management point is not configured with a fully qualified domain
name (FQDN).
- Clients belong to a separate Active Directory
forest or are workgroup computers.
- You are using a network load balancing (NLB)
management point.
- You have changed the site approval setting
after clients have successfully been assigned to the site.
For more information about client approval, see About Client Approval in Configuration Manager.
Solution
Refer to the following table to troubleshoot each situation listed above.
Situation | Solution |
---|---|
Client computers do not belong to the same domain as the site server's domain, and the site's default management point is not configured with a fully qualified domain name (FQDN). |
Configure the site system that holds the default management point role with an FQDN: |
Clients belong to a separate Active Directory forest or are workgroup computers. |
This is by design, and you must manually approve these clients because they cannot be automatically verified using Windows integrated authentication. See the procedure "To approve clients manually" in the following topic: |
You are using an NLB management point. |
This scenario requires the following additional configuration:
|
You have changed the site approval setting after clients have successfully been assigned to the site. |
This is by design, because the client approval state is set when the client is assigned to a site. To approve clients that have successfully been assigned to the site but are unapproved, perform either of the following actions:
|
Client Repair Fails for a Mixed Mode Client That Has an Internet-Based Management Point Defined
If a client computer in mixed mode has an Internet-based management point specified, the client repair function fails. This configuration is possible only in the following two scenarios:
- The Configuration Manager 2007 site was in
native mode, and clients were configured to use an Internet-based
management point. If the site is reverted to mixed mode, clients
automatically retain their Internet-based management point
configuration.
- Native-mode clients configured to use an
Internet-based management point are reassigned to a mixed-mode
site, and they automatically retain their Internet-based management
point configuration.
Solution
Reinstall the Configuration Manager 2007 client. If reinstalling the client is not an acceptable solution, you can clear the Internet-based management point (FQDN) entry by removing the data in the registry key Internet MP Hostname, which is located under HKLM\Software\Microsoft\SMS\Client\Internet Facing.
The Approve Option Is Still Available After a Client Is Approved
The Approve option remains available for an approved client, and selecting it does not result in updated log files.
For more information about client approval, see About Client Approval in Configuration Manager.
Solution
Do not select the Approve option for a client that displays as Approved. Selecting this option has no effect when the client is already approved. To confirm that a client is approved, reference the client state in the Configuration Manager console. For more information, see About Client States in Configuration Manager.