This is observable via the tray/menu bar icon messaging. Locally on an endpoint, you may see that the Umbrella roaming client's state is constantly changing or 'flapping'. Switching States or Statuses Frequently (Flapping)
In this case, another user with admin credentials would need to download a new config file. If the user is later deleted from org, the config file will no longer function because the user validation will fail. The cause for an unregistered Umbrella roaming client is almost always one of three reasons:Ĭonfig File User ID-When an admin user downloads the config file (OrgInfo.json or ist) for registering the Roaming Client, the user's ID is embedded into the file. This is considered to be an "unregistered" Umbrella roaming client.
Alternately, the Umbrella roaming client may not show as registered in the dashboard.
If you are running antivirus software or other security-based software products, check the security logs to make sure the installation was not blocked by the security software in question.Īfter installation, the Umbrella roaming client tray icon may be gray or red.Typically, parameters such as the "OrgInfo" information were not passed correctly, or the installation method was missing source files. If a single installation is successful, but installing through the command line or deployment system is not, verify your Command Line Parameters or the relevant Mass Deployment article.
If the Umbrella roaming client (127.0.0.1 and/or ::1) is returning a public IP and querying the local DNS servers is returning a private IP, contact support.Ī failed installation refers to the Umbrella roaming client installer exiting suddenly with or without an error code or crashing during installation. If one of the local DNS servers is returning a public IP address, you'll need to rectify that, as the Umbrella roaming client might be passing the Internal Domain DNS lookup to that server and using the response as the result. Be sure to substitute the internal domain name and local DNS server as applicable: These commands should be run from a machine experiencing the issue with the Umbrella roaming client install. If the domain in question has been added to the Internal Domains list, check to make sure all of your DHCP-delegated DNS servers are returning the private IP by running the following commands (in Terminal or Command Prompt) and compare the results. If you cannot resolve internal resources (domains), ensure you've added all domains which host local resources to the Internal Domains list. If you meet the minimum requirements and the Umbrella roaming client does not install correctly, open a ticket with Support. Make sure you meet the minimum requirements for your distribution. Scenario 2: You installed the Umbrella roaming client using the manual installation method, performing a single installation. If the Umbrella roaming client did not install, proceed to Scenario 2. If the Umbrella roaming client installs correctly, double-check our mass deployment articles ( Using Standardized Images and Using Apple Remote Desktop in OS X) and make sure each step was followed precisely. In this case, try installing the Umbrella roaming client on a machine locally through the manual installation method. Scenario 1: You installed the Umbrella roaming client using a distributed or mass deployment method, such as GPO, Apple Remote Desktop, using a standardized image, etc. There are several reasons why the Umbrella roaming client won't install correctly. Did the Umbrella Roaming Client not install?