Mystery Solved: Target Client Config Not Found Explained

We've checked the client config section, there's nothing restricting the os, the ad auth is first. I have my gp setup with three client setting configs. The users for the client setting are mapped to ad groups, and users authenticate with saml from I readded the device in the configuration manager but i still cannot push the client installation, and ccm folder completely disappeared and is not appearing anymore. Resolved by @bryan lai.

The users for the client setting are mapped to ad groups, and users authenticate with saml from I readded the device in the configuration manager but i still cannot push the client installation, and ccm folder completely disappeared and is not appearing anymore. Resolved by @bryan lai. Googling the error i get on the logs, according to palo alto in this link,. The error indicates that connecting user does not match any of the user config you have defined. First you need to identify if the error is returned by gp portal or gp gateway. Attaching failed report and new target configuration file (in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. Use globalprotect connection is failing with error matching client config not found to further expand on the goal of this article. If youre getting the okta prompt, the its going to be the config agent (or whatever the gateways version of it is).

Googling the error i get on the logs, according to palo alto in this link,. The error indicates that connecting user does not match any of the user config you have defined. First you need to identify if the error is returned by gp portal or gp gateway. Attaching failed report and new target configuration file (in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. Use globalprotect connection is failing with error matching client config not found to further expand on the goal of this article. If youre getting the okta prompt, the its going to be the config agent (or whatever the gateways version of it is). Basically the no client config is saying i know who you are, but i have no. Seeing inconsistent deployment of a config profile that is required for use of cisco secure client. The current system configuration does not allow the requested operation

First you need to identify if the error is returned by gp portal or gp gateway. Attaching failed report and new target configuration file (in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. Use globalprotect connection is failing with error matching client config not found to further expand on the goal of this article. If youre getting the okta prompt, the its going to be the config agent (or whatever the gateways version of it is). Basically the no client config is saying i know who you are, but i have no. Seeing inconsistent deployment of a config profile that is required for use of cisco secure client. The current system configuration does not allow the requested operation

Attaching failed report and new target configuration file (in. txt, as. cfg is not supported here). Kindly provide the target configuration file for spc5746cbmku6, if you have. Use globalprotect connection is failing with error matching client config not found to further expand on the goal of this article. If youre getting the okta prompt, the its going to be the config agent (or whatever the gateways version of it is). Basically the no client config is saying i know who you are, but i have no. Seeing inconsistent deployment of a config profile that is required for use of cisco secure client. The current system configuration does not allow the requested operation