Running Z-TraceRoute. When you launch the app, click the Z-TraceRoute tab to see a window similar to the following. Do the following to run the Zscaler Network Analyzer app: Define the settings: Host: If your computer is connected to a ZEN, this field displays the host name of the ZEN. You can specify a different host name, for example, if you want to analyze the path to another ZEN. The Zscaler Client Connector for Android includes both Zscaler Internet Access and Zscaler Private Access modules. Note: This app uses the Device Administrator permission. Mobility has raised business productivity, but it’s brought its share of issues, as well. One of the biggest challenges is the need to provide complete, consistent security across devices that you may not own. Find Zscaler Inc software downloads at CNET Download.com, the most comprehensive source for safe, trusted, and spyware-free downloads on the Web. Zscaler App Download for PC Windows 10/8/7 Laptop: Most of the apps these days are developed only for the mobile platform. Games and apps like PUBG, Subway surfers, Snapseed, Beauty Plus, etc. Are available for Android and iOS platforms only.
Use the Zscaler Analyzer app to analyze the time it takes for your browser to load a web page, so the Zscaler Support team can detect potential issues. The app performs a web page load test and the results provide the Zscaler Support team with all the information they need to debug issues quickly.
ZScaler is the Internet content filtering solution used in the Stokes County School District for all users accessing the Internet inside our District or from District owned devices, used off-site. All users are required to authenticate to the content filter system to gain access to the Internet. Guest Presenters to the Stokes County School District may obtain a day-use username and password from the Technology Department, upon request. Please see your site Media Coordinator or Principal to submit guest access request.
Domain Joined Devices (Windows Desktop & Laptop computers) owned by Stokes County School District
NO USER ACTION NEEDED FOR DOMAIN JOINED DEVICES. Your ZScaler certificate and authentication cookie will automatically push down to your workstation, when you log into the CO domain. This is an automated process that occur's at login. You will NOT need to manually install the certificate to any District owned, domain joined computer. You will be prompted to login to the ZScaler login screen the first time you access the Internet, only once, from each new computer that you login to.
You will login to ZScaler using your Stokes County Domain user credentials as follows: firstname.lastname@stokes.k12.nc.us
When prompted for your password, you will enter the domain password (password that you use to login to the network at your school).
Personally Owned Devices
Personally owned devices are also required to authenticate to the ZScaler Content Filter, to gain access to the Internet. Users will be required to download and install the ZScaler root security certificate. This certificate is installed so that your Internet traffic can be securely transmitted. No data is collected from your computer, and no software or off-site monitoring capabilities are ever installed on personally-owned devices.
Before you install the certificate, you will need to download it to your computer. If you are using a Windows or Mac computer, save the file to your Desktop so that you'll be able to locate it later. Please refer to the installation instructions below, depending on your OS platform.
Below are the Instructions for manually installing the ZScaler Certificates to various Operating System platforms and Web Browsers for personally owned devices brought into our network.
Windows OS, using Internet Explorer web browser
Download all the ZScaler Certificate and save to your location choice (desktop, flash drive, etc).
Open Internet Explorer.
From Internet Explorer, go to the Toolsmenu, select Internet Options, and then in the window that appears switch to the Content tab and click the 'Certificates' button.
To install the certificate go to the Trusted Root Certification Authorities tab and click the 'Import..' button.
In the Certificate Import Wizard window that appears click the 'Next button.
To select the file, press the 'Browse..' button.
Find the saved certificate file (desktop, flash drive, etc.) and click the 'Open' button..'Next','Finish'.
The first time you open an Internet Page, you will receive a prompt from the Z-Scaler Web filter requesting that you authenticate. You will enter your Stokes Domain Username: firstname.lastname@stokes.k12.nc.us (This will be the same 'format syntax' as your email address.)
The thoughts and opinions in this post are my own and do not necessarily reflect those of Zscaler.
In this guide, we’ll walkthrough how to configure Microsoft Intune from scratch and use it to deploy the Zscaler Client Connector agent (ZCC) - formerly known as Zscaler Client Connector (ZCC).
Due to length, I’ve split this into two posts (the orginal was over 8000 words):
I suggest you use the Table of Contents to jump to the section that you need.
According to Microsoft:
Microsoft Intune is a cloud-based service that focuses on mobile device management (MDM) and mobile application management (MAM).
With Intune, you can:
In order to access Intune, you need to have either a Microsoft 365 or Enterprise & Mobility E3/E5 subscription. If you’re using a free Azure account, you’ll need to sign up to a trial, or pay per user (which can get costly).
Scott Bullock of Zscaler (@scottyb) has posted a great 10 minute video in their community forum that runs through the user experience of enrolling a fresh Windows 10 device into Intune. ZCC is automatically pushed out and transparently authenticated for both ZIA and ZPA.
When adding an app to Intune, you’ll be prompted to allocate the groups of users (or devices) that the app will be rolled out to. Hence before beginning, ensure you have the users of Zscaler inside of an AD or Azure AD group that you can assign the Zscaler Client Connector app to.
Depending on whether you want the ZCC app to be mandatory or optional for certain groups of users, you may want to divide your users into two groups:
In my examples below, I have 3 groups:
Group | Description |
---|---|
ZIA_Entitlement | This is the group of all users that are entitled to use Zscaler Internet Access (ZIA) |
ZPA_Entitlement | This is the group of all users that are entitled to use Zscaler Private Access (ZPA). In my case, this is a subset of users from the ZIA_Entitlement group as I might not want to roll ZPA out to every user in the organization. |
Zscaler - Mandatory | This group contains every user in the organization to which the ZCC app will be automatically rolled out to. Ie: The majority of users from the above two groups. If this is your organization, you might include the whole org in this group, except select users (eg: some from IT) for which the app will be optional. |
We’ll be using the Microsoft Endpoint Manager console (MEM) to orchestrate Intune. You can log in using the same Azure Portal credentials here: https://endpoint.microsoft.com
If you’re using an existing Office 365 account and have been using the Office 365 MDM, you’ll need to change the MDM authority from Office 365 to Intune. This Microsoft help article will guide you through it.
This section will cover deploying ZCC onto Windows using Intune.
To start you’ll need the .MSI installer for ZCC from the Zscaler Client Connector Portal. Log into the portal (either through ZIA or ZPA) and navigate to Administration > Zscaler Client Connector Store.
In the Windows panel, download the MSI for the latest 2.X.X version. Do not use the older 1.X.X releases.
Back in the Apps menu of the MEM portal, navigate to Apps > All Apps > Add. In the panel that appears, scroll to the bottom and under the Other heading, select Line-of-business app.
When prompted to select an app package file, upload the MSI of the Zscaler Client Connector you downloaded above and click OK.
Fill in the required details about the app:
Field | Content |
---|---|
Name | Enter Zscaler Client Connector 2.X.X.X (where 2.X.X.X is the version number of the app - this will help you distinguish what version is being distributed by Intune) |
Description | Enter Zscaler Client Connector |
Publisher | Enter Zscaler, Inc |
Ignore app version | Set to Yes. ZCC will automatically update itself once deployed, so Intune can safely ignore the version the user has installed after deployment. |
Category | (Optional) Select an app category to allocate the Zscaler Client Connector to. |
Command-line arguments | See below. |
For the Command-line arguments section, enter the following (substituting in your own cloud and domain info):
Important!
FX-PCS/WIN-E is a Shareware software in the category Desktop developed by FX-PCSWIN-E. The latest version of FX-PCS/WIN-E is currently unknown. It was initially added to our database on. FX-PCS/WIN-E runs on the following operating systems: Windows. FX-PCS/WIN-E has not been rated by our users yet. Free fx pcs win download download software at UpdateStar - 1,683,000 recognized programs - 4,592,000 known versions. » fx pcs du win download. FX Series Programmable Controllers i FX-PCS/WIN-E Software Manual Manual number: JY992D66501 Manual revision: F Date: November 2008 Foreword. This manual. FX-PCS/WIN is a. Fx pcs win e software download.
zscalertwo
Command-line arguments can be used for each platform to customize the install. For example, STRICTENFORCEMENT
can be used to block access to the internet until your users enroll in the Zscaler Client Connector.
For a list and description of all the MSI customization options, scroll down to point #5 in this help article.
Click Next when ready to move onto the Assignments tab.
There are two different sections you can allocate users or groups to depending on how you want the app rolled out to users:
Assign your users or groups to the ZCC app accordingly.
Click Next to continue and then Create on the following screen. Your Line-of-Business application will be created and the MSI will upload - be sure to wait until it’s complete.
Done!
This section will cover deploying ZCC onto macOS using Intune.
macOS requires a little bit more effort to get going than Windows does. We will need to do the following on a local macOS machine:
.app
file).intunemac
file)If you’re using MacOS Catalina 10.15 or higher, you MUST use ZCC v2.1.X or above. Catalina introduced the requirement that apps are notarized by their developers. Only ZCC releases v2.1 and above are notarized by Zscaler.
An Apple Developer Account is recommended.
You can proceed and deploy the agent without an Apple Developer account, however you will not be able to sign and notarize the .pkg
file created below without a valid Developer ID. This will result in your users receiving an error about an the software coming from an ‘Unidentified Developer’, and depending on security settings, the device may block the install altogether.
If you enroll in the Apple Developer program (US$99), you can sign and notarize your package which will make this error go away. If you’re an organization running a macOS deployment, you will most likely have a developer account for the company already.
But shouldn’t Zscaler have already signed the app I’m deploying?
Yes, Zscaler HAS both signed and notarized the .app package that will be installed. The problem with Intune is that it can only deploy .pkg
files to macOS; NOT .app
files. We need to wrap our .app file inside a .pkg file for it to work with Intune, and it is this pkg file that needs to be signed and notarized as well.
To sign an notarize the .pkg
, you will need both the Developer ID Installer and Developer ID Application certificates. You can create these under the Certificates, Identifiers & Profiles section of your developer account, but will need a Certificate Signing Request (CSR) to do so: Apple have a brief guide on how to generate one using Keychain, here.
Download the certificates when you have them and click to open the .cer
files in Keychain. Add them as a login certificate.
You can check the certificates have been installed correctly by running the following command:
If you have the Developer ID Installer and Developer ID Application certificates, you’re good to proceed.
To start, you’ll need the .app
installer for ZCC from the Zscaler Client Connector Portal.
Log into the portal (either through ZIA or ZPA) and navigate to Administration > Zscaler Client Connector Store.
In the macOS panel, click the download link for the latest 2.X.X version. Do not use the older 1.X.X releases.
Unzip the file downloaded to obtain the .app installer.
Intune will push out and install the .pkg
file - which is just our .app
file wrapped up as a .pkg
for the purposes of Intune deployment.
The problem is however, that when Intune deploys the .pkg
, it just saves the wrapped .app
to the user’s device without doing anything else. We need a way to run and install the .app
after Intune has deployed the .pkg
, PLUS a way to include arguments to customize the install. A post-installation script will do all of this for us.
To start, on a macOS device open Terminal:
Create a folder called scripts
. Inside this folder, create a file called postinstall
Note down the full path to the scripts
directory - we’ll need this later.
Open the postinstall file for editing:
Copy and paste the following into the Terminal window (modify the arguments as required):
To exit Nano, press Control + X
and then Y
to save.
This will do a silent installation of the Zscaler Client Connector (unattended mode) and automatically redirect the user to your company SSO page to sign in.
Important! When entering the cloud name (--cloudName
), DO NOT enter the .net at the end. Eg: zscalertwo.net should be entered as zscalertwo
Command-line arguments can be used for each platform to customize the install. For example, --strictEnforcement 1
can be used to block access to the internet until your users enroll in the Zscaler Client Connector.
For a list and description of all the .app customization options, scroll down to point #4 in this help article.
As an example, the script for my installation looks like the following:
Lastly, we need to make the script executable. Run the following in Terminal:
Intune only supports pkg
files for macOS. A .pkg
file is analogous to an MSI for Windows. All we are essentially doing is wrapping the .app file inside a .pkg file so that it can be deployed by Intune.
We’ll be using the built-in pkgbuild
tool to do this. Open Terminal and run the following command (change the file paths before running):
Field | Description |
---|---|
--install-location | This should point to the tmp folder, or somewhere writeable on the user machine. The .pkg will unpack itself here, then run the .app installer; which will install ZCC to the /Applications directory as required. If you change this from /tmp , you’ll need to update the postinstall script as well. |
--scripts | This should be the path to the scripts folder you created in the step above. |
--component | This file path should point to the Zscaler Client Connector .app file you downloaded in Step #1. |
--identifier | Specify a unique identifier for this package. It is advisable to set a meaningful, consistent identifier, eg: com. zscaler. zscalerclientconnector |
--version | This has no relationship to the actual Zscaler Client Connector version. This is only used by Intune. If you ever deploy another pkg via Intune for a different version of ZCC, you’ll need to increment this (eg: Version 1.1) so that Intune can tell the pkg files apart. Note that ZCC has its own update mechanism, so you don’t need to worry about using Intune to push out updates to the Zscaler Client Connector software. |
--sign | If you don’t want your users to recieve an error that your package is from an ‘Unidentified Developer’ (which will prevent installation entirely), you will need to sign the package using a valid Apple Developer ID. To do this, you will need to enroll in the Apple Developer program (US$99). If you are an organization, you probably have already done this. Make sure you correctly substitute MY-DEV-NAME with your correct Developer name / org name. If you don’t care about the ‘Unidentified Developer’ error, you can remove the--sign argument. |
The last file path listed points to the location where you want to save the output pkg file.
If you’re signing the package and are not sure about your team / developer / org certificate name, you can check this under the Certificates, Identifiers & Profiles section of your Apple Developer account, here.
As an example, my completed pkgbuild
command is below:
If you signed your package, you can validate the signatures using pkgutil
:
For example:
You only need to do this step if you signed the .pkg
file in the previous step. Otherwise you can skip to the next step.
What is notarization? According to Apple:
Notarization gives users more confidence that the Developer ID-signed software you distribute has been checked by Apple for malicious components. If there are no issues, the notary service generates a ticket for you to staple to your software; the notary service also publishes that ticket online where Gatekeeper can find it.
Beginning in macOS 10.14.5, software signed with a new Developer ID certificate and all new or updated kernel extensions must be notarized to run. Beginning in macOS 10.15 [Catalina], all software built after June 1, 2019, and distributed with Developer ID must be notarized.
We’re going to notarize the .pkg
file via the command-line. To do this, you’ll need to generate an App Specific Password for your the Apple ID of your Developer Account:
How to generate an app-specific password
Next, open Keychain and click the “+” icon to add a new Keychain Item.
notarization-tool
To request notarization from Apple, run the following command (replacing the values with your own):
Field | Value |
---|---|
username | The Apple ID username associated with your Apple Developer Account |
password | Enter @keychain: followed by the name of the Keychain Item which you saved your app-specific password to. This will fetch the password from the keychain. |
asc-provider | This is the Team ID from your Developer Account. You can find this by logging into your Developer Account and reviewing your profile |
primary-bundle-id | This should match the identifier you specified when you created the pkg. |
file | The path to the .pkg file |
For example:
If you receive an error that the tool is not on your machine, ensure you have Xcode and Xcode Command-line Tools installed.
The command will take a while to run as it is uploading your .pkg
file to Apple. Once done, it will return a UUID which you can use to check the status of your notarization request:
Once the process is complete (mine took under 10 minutes), you’ll recieve a confirmation email as to whether your request was successful or not.
The last step is to staple the notarization ticket to the .pkg
file. This ensures that a Mac device that is offline can still validate that the .pkg
file is notarized:
Note: If your command fails, wait a few minutes and try again. If your command continuously fails, and your traffic is going through ZIA or another proxy, you may need to bypass api.apple-cloudkit.com
from SSL inspection due to certificate pinning.
Validate the staple action was successful:
Before going further, test your PKG file by running it and seeing if it successfully installs the Zscaler Client Connector silently. Make sure you don’t already have ZCC installed when doing this however!
If you have an existing installation of ZCC, you can remove it under Applications/Zscaler/Uninstall-Zscaler-App
Once you’ve verified your PKG file functions correctly, we need to wrap it for use with Intune.
Download the Intune App Wrapping Tool for Mac (this is a Microsoft-owned repository).
Next:
IntuneAppUtil
file is locatedIntuneAppUtil
file executable:Locate the PKG file you created above and use the IntuneAppUtil
tool to wrap the .pkg
file to a .intunemac
file:
For example:
If everything went well, you should see the .intunemac
file in your specified output directory.
In the Apps menu of the MEM portal, navigate to Apps > All Apps > Add. In the panel that appears, scroll to the bottom and under the Other heading, select Line-of-business app.
When prompted to select an app package file, upload the.intunemac
file you created above and click OK.
Fill in the required details about the app:
Field | Content |
---|---|
Name | Enter Zscaler Client Connector 2.X.X.X - macOS 2.X.X.X (where 2.X.X.X is the version number of the app - this will help you distinguish what version is being distributed by Intune) |
Description | Enter Zscaler Client Connector for macOS |
Publisher | Enter Zscaler, Inc |
Minimum operating system | Select OS X Yosemite 10.10 (ZCC supports macOS 10.10+) |
Ignore app version | Set to Yes. ZCC will automatically update itself once deployed, so Intune can safely ignore the version the user has installed after deployment. |
Category | (Optional) Select an app category to allocate the Zscaler Client Connector to. |
Click Next to move to the Assignments tab.
There are two different sections you can allocate users or groups to depending on how you want the app rolled out to users:
Assign your users or groups to the ZCC app for macOS accordingly.
Click Next to continue and then Create on the following screen. Your macOS Line-of-Business application will be created and the .intunemac
file will upload - be sure to wait until it’s complete.
Done!