You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the following log file, an error message that resembles the following is logged:
100
100
@@ -162,7 +162,7 @@ If you're using a PKI server authentication certificate, follow these steps:
162
162
> [!NOTE]
163
163
> When installing clients from the Internet, make sure that the `/NoCRLCheck` parameter is included with the `CCMSetup` command.
164
164
165
-
## Error code 401 and CMGService_Invalid_Token
165
+
## Error code 401 (CMGService_Invalid_Token)
166
166
167
167
The client hasn't communicated with the site (via CMG or MP) for over 30 days, or the `CCMSetup` command is attempting to use an expired token with the `/regtoken` parameter. In the following log files, error messages that resemble the following are logged:
168
168
@@ -191,7 +191,7 @@ This issue occurs because the token is expired or not properly added, renew, and
191
191
192
192
To renew the expired token, connect the client to the internal MP directly or reinstall the client by using a new [Bulk registration token](/mem/configmgr/core/clients/deploy/deploy-clients-cmg-token#bulk-registration-token).
193
193
194
-
## Additional information
194
+
## More information
195
195
196
196
For further troubleshooting, of Client to CMG communication issues, we recommend next actions:
0 commit comments