Reference Section > Installation and Deployment > License GUI

The Client Version Manager (PC4ClientEstate.exe) lets an administrator bring every PrimeCut client PC up to the server's version from one place, so nobody has to visit each PC to approve the install. It lists the PCs that have used PrimeCut, with the version on each, whether PrimeCut is open there and whether the PC answers.

Opening it

•In the License GUI, choose Updates > Client PCs...

•In the Update Manager, click Client PCs... - it also opens by itself after a successful server update.

•From any PC, run PC4ClientEstate.exe from the root of the UPDATEPRIMECUT share. Everything it does to a PC is done as the login running it, so run it logged in as an administrator of the client PCs (a domain admin, or an IT account in their Administrators group).

The list of PCs is shared with the IT deployment scripts and kept in the scripts folder of the UPDATEPRIMECUT share. The licence server adds PCs as they log in. Untick a PC to stop managing it from here (the "All" buttons skip it); X removes it from the list until it logs in to PrimeCut again. Nothing runs against any PC until you press a button, and each button first shows the exact command it is about to run.

Updating client PCs

1.Open the Client Version Manager and check the Server version at the top.

2.Click Ping All (or click one PC's light) to see which ticked PCs can be reached.

3.Click Fetch All (or a PC's Fetch) to read the version installed on each PC.

4.Click Update on a PC, or Update All for every PC that is behind, a few at a time (batches of). A PC where PrimeCut is open is skipped, not interrupted.

5.Read the Update status and Detail columns. When a PC cannot be updated, Detail names the step that failed, why, and the login that was used.

6.For a PC that is switched off, use Ambush (below).

Status lights

Light	Meaning
Empty ring	Not checked yet.
Dotted	Being checked now.
Green	The PC answers on file sharing (port 445) and can be updated.
Amber	The PC is switched on but is blocking file sharing (port 445).
Red	The PC does not answer at all - usually switched off. Hover over the light to see why.
Faded	The result is more than 10 minutes old; ping again.

The Version column is green for the server's release, amber for the same version but an older release, red for a different version and blue for a version newer than the server.

Ambush - updating PCs that are switched off

On a PC that could not be reached, the Update button reads Ambush. Click it to hand the PC to the ambush agent, a scheduled task that watches for the PC and runs the ordinary update the moment it comes online. The button then reads Ambushing; click it again to cancel. Ambush All arms every unreachable PC at once. Each PC's result is shown in the table and written to the log.

The first ambush opens the Credentials window (also opened with Credentials...):

•The agent runs on the machine you set it up on, so set it up on one that stays on - the server, or any PC that is not shut down.

•Set up agent... asks, through the Windows prompt, for an administrator logon of the client PCs. Enter the password even for your own account. Windows stores it with the agent's scheduled task; Remove agent deletes it.

•Give up after (days): 1 to 14, default 3. Give up after (tries): failed updates while the PC is online, 1 to 10, default 1. Check every (minutes): 1 to 60, default 5.

•Tick Fetch and Update to use the same credential for those buttons too; otherwise they run as your own logon.

Notes

•Permissions: only administrators can change the scripts folder, the Client Version Manager and the list of PCs; everyone else can read them. Saving changes to the list from your own PC needs you to be an administrator on the PrimeCut server too.

•What it assumes: port 445 and the C$ admin share open on the PCs, the "Remote Scheduled Tasks Management" firewall rules on, and the Remote Registry service running. Help in the window lists every assumption.

•Logs: Log shows this session, including the exact command of the last run. A daily log is kept on the PC running the window in %ProgramData%\Kinetic\PrimeCut\ClientEstate. Right-click a PC and choose Get logs to copy its update and installer logs (C:\Windows\Temp\PrimeCutUpdate.log and PrimeCutClientSetup.log) into the Client logs folder there.