---
title: "Blueprint: Resolving a missing or duplicated Blueprint Tracker Machine GUID"
slug: "blueprint-resolving-a-missing-or-duplicated-blueprint-tracker-machine-guid"
tags: ["Blueprint", "tracker", "duplicate"]
updated: 2024-04-23T20:07:05Z
published: 2024-04-23T20:07:05Z
canonical: "kb.pharos.com/blueprint-resolving-a-missing-or-duplicated-blueprint-tracker-machine-guid"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Blueprint: Resolving a missing or duplicated Blueprint Tracker Machine GUID

### Goal

Resolve a missing or duplicated Machine GUID

### **Environment**

- Pharos Blueprint v3.5
- Pharos Blueprint v3.6
- Pharos Blueprint v4.1
- Pharos Blueprint v4.2
- Pharos Blueprint v5.0

### Change

Blueprint Tracker deployed to Microsoft Windows desktop clients.

---

### Cause

- A missing Machine GUID is normally caused by inadvertant deletion of the computer's record in the Blueprint "psbprint" database's "Machines" table.
- A duplicated Machine GUID most often happens when a "MSI snapshot" utility is used to convert the provided .EXE installer into .MSI for deployment purposes. The resulting MSI file includes the Windows Registry key and value for the Machine GUID, and this is then applied to every install target, undoing the unique nature that a GUID is supposed to provide.

### Resolution

*In Blueprint 4.2 and lower:*

1. Run the Uninstall package created by the Blueprint Administrator application. For information on how to create an Uninstall package if one is not available, see "Upgrading and Uninstalling Trackers" in the Pharos Administrator Help pages.
2. Run the Install package created by the Blueprint Administrator application.

*In Blueprint 5.0:*

1. Copy BlueprintTracker.exe from the server's \PharosSystems\Blueprint\Deploy folder to the workstation.
2. In an administrative command prompt navigate to the directory containing the .EXE and type blueprinttracker.exe /uninstall /clean.
3. Reboot the workstation, allowing Windows to remove any files that were in use during the removal operation.
4. Go back into an administrative command prompt and install Blueprint Tracker. Options and syntax can be found on page 20 of the "Tracker Deployment Guide" found in the Blueprint 5.0 installation software.
5. Exit the command prompt window.

The workstation will now have a valid, unique GUID associated with it.

## Related

- [Blueprint: Print jobs are not importing due to a PHAROSDBERROR_FOREIGN_KEY_CONSTRAINT error with the Logical Printer GUID](/blueprint-print-jobs-are-not-importing-due-to-a-pharosdberror-foreign-key-constraint-error-with-the-logical-printer-guid.md)
- [How to Disable Signup Client from a Terminal window](/how-to-disable-signup-client-from-a-terminal-window.md)
- [How many copy lines does Pharos support?](/how-many-copy-lines-does-pharos-support.md)