Skip to main content

Install Pulse on Windows computers (Phantom Mode)

In Phantom Mode, a Workspace admin installs Parable Pulse on Windows computers, on one computer or with a management tool. No employee signs in to Parable. Pulse shows no tray icon, no window and no prompt. It finds each employee’s work email from Windows and enrolls that employee’s Windows account in the Workspace. The Workspace admin opens Pulse > Setup in Parable and downloads the package. A download link is valid for 7 days. The same package works in both install modes (see Install mode).

Pulse > Setup

While no computer is enrolled, Pulse > Setup shows 4 steps:
  1. How employees join: Phantom Mode or Sign in. Both show the employee disclosure, and Full text opens the whole text. Use Phantom Mode accepts the disclosure for your employees.
  2. Employees: upload a CSV or paste emails. Each email becomes an employee of the Workspace. Then choose the employee whose computer you test on.
  3. Test computer: download the package, run it as an administrator on that computer, and wait until it shows Connected. Not showing up? lists the fixes.
  4. Install on everyone: install the package with your device tool (see Configuration Manager, Intune, Ivanti (MobileIron) or Script). Each employee shows Connected, Waiting or Refused.
Once any computer is enrolled, in either mode, Pulse > Setup shows the status instead: the counts, Needs you (refused emails and computers that need attention), and the actions to add employees, download the package, and test a computer. The employees are the active members of the Workspace and the refused emails. An employee is Connected with at least one active Pulse computer.

What is in the package

Keep pulse-enrollment.json in your management tool only. With the key, a computer can enroll any email in your Workspace’s email domains and any employee that you added. If the key leaks, the Workspace admin revokes it in Pulse > Setup and downloads a new package. Computers that enrolled before keep working.
The install command has no key in it. The script reads the key from pulse-enrollment.json in its own folder:
The uninstall command:

Install mode

Pulse asks Parable for the install mode of your Workspace before it enrolls. The Workspace admin chooses the mode in Pulse > Setup and can change it later in Pulse > Settings. When you choose Phantom Mode, you accept the Pulse disclosure for your employees. Parable records the disclosure version, the time and your name. If your Workspace has no email domain yet, Parable adds the domain of your own email when you choose Phantom Mode. For example, ops@acme.com adds acme.com, so every employee at acme.com joins on their own. Parable does not add a public mail service such as gmail.com or outlook.com. To add more domains, contact Parable. Until Pulse has an answer from Parable, it shows nothing and records nothing. It asks again on the retry schedule in When Parable refuses an enrollment. Once any computer is enrolled, in either mode, you change the mode only in Pulse > Settings. The confirm names the number of computers that switch. A switch to Phantom Mode needs you to accept the disclosure again. Each enrolled computer follows a mode change at its next health check-in (5 minutes by default):
  • Phantom Mode to sign-in: the tray icon appears and Pulse stops recording. When the employee signs in, Pulse enrolls the computer as a sign-in device and removes the Phantom Mode device. Each computer keeps one active device in Parable.
  • Sign-in to Phantom Mode: the tray icon disappears. Pulse keeps the employee and keeps recording. If that employee’s sign-in expires, the tray icon appears again, because only the employee can sign in.

What Pulse does and does not hide

Requirements

  • Windows 10 version 2004 (build 19041) or later, or Windows 11, 64-bit.
  • The script runs as SYSTEM or as an administrator.
  • Each employee signs in with a domain account or an Entra ID account. For a local account, see How Pulse finds the email.
  • The computer can reach parable.work and incoming.parable.work over HTTPS.

What the script does

  1. It writes the enrollment key to the policy value HKLM\SOFTWARE\Policies\Parable\Pulse\EnrollmentToken.
  2. It installs Pulse for every employee on the computer (Add-AppxProvisionedPackage).
  3. It writes HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\ParablePulse, so Pulse starts at each sign-in.
  4. It starts Pulse at once for each employee who is signed in now. Those computers enroll within one minute and show in Pulse > Devices.
The script writes its log to C:\ProgramData\Parable\Pulse\install.log. The log never contains the key. The script exits with code 0 on success and 1 on failure.
Windows starts an app that is installed for all users only after an employee opens it once. The Run value in step 3 starts Pulse at every sign-in, so no employee has to open it. Do not remove this value.

Configuration Manager

  1. Copy all files of the package to one content source folder.
  2. In Software Library > Application Management > Applications, create an application with Manually specify the application information.
  3. Add a Script Installer deployment type:
    • Installation program: the install command above.
    • Uninstall program: the uninstall command above.
    • Detection method: registry, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, value ParablePulse, must exist.
    • Installation behavior: Install for system. Logon requirement: Whether or not a user is logged on.
  4. Deploy the application to a device collection as Required. Test it on one computer first.

Intune

  1. Put all files of the package in one folder, for example C:\ParablePulse.
  2. Package the folder with the Microsoft Win32 Content Prep Tool: IntuneWinAppUtil.exe -c C:\ParablePulse -s Install-PulseManaged.ps1 -o C:\Out.
  3. In the Intune admin center, add a Windows app (Win32) and upload Install-PulseManaged.intunewin.
  4. Install command and uninstall command: the commands above. Install behavior: System.
  5. Detection rule: registry, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, value ParablePulse exists.
  6. Assign the app to a device group as Required. Test it on one computer first.

Ivanti (MobileIron)

  1. Add the files of the package as one Windows app package, or as a PowerShell configuration that runs as SYSTEM.
  2. Install command and uninstall command: the commands above.
  3. To give an employee’s email, push a registry configuration in the user context: key SOFTWARE\Policies\Parable\Pulse, value UserEmail (REG_SZ).
  4. Assign the package to a device group. Test it on one computer first.

Script

  1. Copy all files of the package to one folder on the computer.
  2. Open PowerShell as an administrator in that folder.
  3. Run the install command above.

Optional: the employee’s email

Use -UserEmail only when Windows does not know the employee’s work email, for example on a computer with local accounts:
The script writes the email for the employee who is signed in at the console. For other employees, write the per-user policy value HKCU\SOFTWARE\Policies\Parable\Pulse\UserEmail (type REG_SZ) with your management tool.

Registry values

Only administrators can write SOFTWARE\Policies, so an employee cannot change these values.

How Pulse finds the email

Pulse runs in each employee’s own Windows session. It uses the first source that gives a valid email:
  1. The UserEmail policy value.
  2. The Active Directory mail value of a domain account.
  3. The Entra ID sign-in name of an Entra ID account.
  4. The Active Directory sign-in name of a domain account.
Parable accepts an email in your Workspace’s email domains (see Install mode) and the email of an employee that you added (see Add employees). Pulse creates a Workspace member for a new email in your domains. That member has no access to the Parable app and gets no email.

Add employees

Add an employee when the email is outside your Workspace’s email domains, for example a contractor. In Pulse > Devices, select Add employees. Paste the emails, separated by commas, spaces or new lines, or paste a column from a spreadsheet. You can also upload a CSV file: Parable takes every cell that is an email. One add takes up to 1,000 emails. Each added employee becomes a Workspace member with no access to the Parable app, and gets no email. Pulse enrolls that employee’s computer at its next try. Parable does not add an email that belongs to a Parable staff account, to another Workspace, or to a suspended member. Each Windows account binds to one employee. On a computer that several employees use, each employee’s Windows account enrolls separately.

When Parable refuses an enrollment

Pulse > Setup shows each refused email with the reason and the fix. For an email outside your Workspace’s domains, select Add to Workspace. Pulse tries again every 5 minutes for the first hour, then every hour. So a fix takes effect without a new install.

Turn recording on and off

A Workspace admin turns recording off for the whole Workspace in Pulse > Settings, or for one employee in Pulse > Devices (open one of the employee’s devices, then Recording for the employee). The employee setting applies to every device of that employee. Pulse stops capture and stops writing to its local store within one health check-in interval (5 minutes by default). Pulse keeps its health check-in, so it starts again when recording is on, and Pulse > Settings shows how many devices applied the change.

Automatic updates

By default, only your IT team installs new versions of Pulse on Windows, with the package and your management tool. A Workspace admin can turn on Automatic updates in Pulse > Settings. Then each Windows computer installs a newer Parable release by itself, at a health check-in, without your management tool.
  • Pulse installs a package only when it is newer than the installed one and Parable signed it with the same publisher as the installed Pulse. It never installs an older version.
  • The update applies to the person who is signed in. Pulse stops for a few seconds and starts again with the new version.
  • A new version goes first to the test computers that Parable and your IT admin choose. Parable sends it to every computer only after each test computer runs it.
  • Turn the setting off to stop all automatic updates for your Workspace at the next check-in. Pulse keeps the version it has.
The setting does not apply to Macs. See Updates.

Remove Pulse

Run the uninstall command. The script removes Pulse for every employee, the Run value and the HKLM policy values. It also removes each employee’s Pulse data: the enrollment and any activity that Pulse did not send yet. Windows keeps that data for an employee who stays signed in, so the script removes it itself. Per-employee UserEmail values stay in each profile. The uninstall does not tell Parable, so Pulse > Devices shows the computer until Pulse is installed on it again. In Phantom Mode, a new install on the same computer enrolls each employee again and revokes that employee’s old device. Each Windows account on a computer keeps one active device, and the employee’s other computers keep theirs. A computer that a Workspace admin revokes in Pulse > Devices stops sending, and it stays revoked. To enroll it again, run the uninstall command, then the install command.

Troubleshooting

Parable does not yet publish a customer-signed Windows package. Until then, Parable gives packages only for tests on Parable’s own test computers.