Skip navigation
All Places > Knowledge Base & Downloads > Blog > 2013 > August > 05

Using security software such as Deep Freeze, Clean Slate and Centurion Guardian with Pharos SignUp Vx can present problems, due to the way that the SignUp Client stores information locally. This document discusses issues that arise when SignUp is used in conjunction with such security software, and suggests a number of possible solutions.


See the attached Pharos TechNote.

I am able to connect to the Omega PS-150 and the web administration page, but when I click on Upgrade (to flash the firmware) or Restart, nothing happens, the browser reports "done" and nothing happens on the Omega.

Additionally, there is no 'Status' listed for the Omega(s) at the bottom of the page.
The problem is that the web interface uses the hostname to connect and run the associated code(s).

Check that the Omega can be pinged by the hostname in your environment. If that doesn't work, you can add a hosts entry to your PC or update your DNS environment so that it is reachable. If pinging by hostname works, and the other functions still do not, please contact Pharos Support.

Reboot the Omega PS100 system by unplugging the power cable from the Smart Hub. Wait a few seconds and plug it back in.


If this doesn't fix your problem, you should check to make sure you have the latest firmware (see link to "Downloads - Terminal Device Firmware")


Pharos Home Page - Support - Downloads


Additionally, there is some troubleshooting documentation as part of the firmware distributions. Read through the documentation before making any changes. If it is determined that you have faulty hardware, please contact Pharos Support to begin the RMA process.

When you save the Pharos Server Settings, If the settings is correct and the Pharos Server (Edi) can be connected correctly, the Pharos Server is automatically allowed to access the printer (since the printer server is most likely on the same Edi server).

When you view the Status -> Network status page, the Pharos server should listed in the "Computers allowed to access the printer"text box.

The current release requires a reboot to take effect! Without a reboot, the Pharos server is not listed the text box and is not allowed to print to the printer.

During the installation of Blueprint Enterprise 3.5 the follow error occurs:

"No local database server instances have the correct version and edition"


"A Local SQL Server of the correct version and edition can't be found. Check that the local SQL Server is running."

An error dialog picture is attached to confirm the error message. There is a similiar error message when installing Blueprint Enterprise 4.x as well. Please see the attached screen shots.

This is a known issue and indicates that the local SQL version is most likely not on the latest service pack. For SQL 2005 Service Pack 2 is required prior to installation.

The First Item is that the User Login Name (Account.jpg) and the Alias (ExchangeGeneral.jpg) have to be the same.

The Second Item to configure is that of the IMAP4 protocal needs to be enable and using protocal defaults. (ExchageFeatures.jpg)

Atached are the images to compare.

Interface: pharos


We have "unable to print zero length job" errors happening on our Pharos server and we're not sure why this is happening.  The print jobs in question from the clients have content in them but fail to print and this is the error we receive. In order for the Pharos Print Server to accept and print zero-length print jobs, a registry setting must be made.


1. Launch Regedit and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Pharos\Print Server.
2. Within this key, is a value, Zero Length Jobs. By default, it's value is 0, which means to "not allow." Change this to a 1
3. Quit the Registry.
4. Restart the Pharos Print Server service.


The zero-length job is normally some combination of driver and application, notably Adobe Acrobat (any edition, including Reader), but Microsoft Word will do this too. Note that allowing zero-length print jobs to print will reduce user complaint, but these jobs may often print for free. Be aware that the existence of the zero-length spool file is not something caused by Pharos, but is outside of our application and within the Spooler subsystem of Windows.

The Pharos Omega PS150 is designed to recover from errors during a firmware upgrade. Clients should attempt to update the PS150 firmware again in case of a network problem.

If a Pharos Omega PS150 does not return to a normal state or becomes upgradable, clients should contact Pharos Technical Support.

Note: An upgrade of a Blueprint server (Collector/Analyst) on a cluster cannot be rolled back. As a precaution, certain resources should be backed up before upgrading. This enables a manual upgrade if the upgrade fails for any reason.

The following steps should be carried out when upgrading a clustered 3.5 R2 or 4.1 Analyst/Collector to 4.2.

  1. Using the Cluster Administrator, take the “Blueprint TaskMaster” and “Blueprint ComTaskMaster” resources offline. Temporarily change the properties of the “Print Spooler” and “TCP/IP Print Server” resources – on the Policies tab, uncheck the option to fail over if restart is unsuccessful. Ensure all nodes are showing “Up” status before proceeding.
  2. Run the upgrade on the first, active node. When the Server Configuration Tool (SCT) appears, click the Apply button, and then click the Close button.
  3. Open the Services Manager on the active node. For both the “Pharos Systems TaskMaster” and “Pharos Systems ComTaskMaster”, set the startup type to “Manual” and configure the services to use the correct domain user account.
  4. Fail over the node. Keep the “Blueprint TaskMaster” and “Blueprint ComTaskMaster” resources offline.
  5. Run the upgrade on the second, now active, node. When the SCT appears, click the Apply button, and then click the Close button.
  6. Using the Cluster Administrator, restore the properties of the “Print Spooler” and “TCP/IP Print Server” resources – on the Policies tab, check the option to fail over if restart is unsuccessful.
  7. Open the Services Manager on the active node. For both the “Pharos Systems TaskMaster” and “Pharos Systems ComTaskMaster”, set the startup type to “Manual” and configure the services to use the correct domain user account.
  8. Add the two new services - Pharos Systems Job Service and Pharos Systems Event Log Service to the resource group as Generic Service resources.
    1. Blueprint Job Service
      1. Dependencies: Blueprint Event Log Service, Physical Disk, Network Name, Spooler
      2. Service Name: Pharos Systems Job Service
      3. Use Network Name: True
      4. Affect the Group: False
    2. Blueprint Event Log Service
      1. Dependencies: Physical Disk, Network Name
      2. Service Name: Pharos Systems Event Log Service
      3. Use Network Name: True
      4. Affect the Group: False
  9. Set the startup type to “Manual” for the two new services, and configure the Pharos Systems Job Service to use the correct domain user account.
  10. Using the Cluster Administrator, bring both of the Blueprint resources online.
  11. Click the Test button on the Server Configuration Tool.

The data stored by the Pharos Offline Proxy is configured to expire after two days. However, expired data will not be purged if the service is currently running in offline mode.

When a Pharos services comes back online from offline mode, the service must be online at least 15 minutes before any expired data is purged.

When printers have the same weight (as determined by the value for "Speed" within the Device configuration), load balancing is based on values that are updated for the print queues when the transaction is inserted into the database. The printer that is selected for the job will be the one that has the lowest "pages_since_startup" value (as a point of clarification, this is pages since the PServer service startup, not the printer's startup).  If one printer goes offline for a while, thanks to an error or some other event that causes it to be unavailable for print, more jobs will be sent to that printer when it comes back online.  The "pages_since_startup" values are cleared for all printers whenever the PServer service is restarted.


If the weights (speeds) are different, there's a proportional calculation instead. Also, if jobs are being held for reprint for a device, that can affect load balancing.


Unfortunately, no note is taken of whether one printer is idle and another printing.  This would require either the use of SNMP (a TCP device management protocol) to determine the printers' current status, or the use of the print server's Print Spooler. SNMP, while reliable, carries some inherent security risks and is often disabled on the network, and the Windows Print Spooler is not always accurate in its report of device availability. Therefore, neither are suitable paths for device status retrieval.

Below are a list of keyboard characters to avoid when creating passwords in Pharos. Or, when using Pharos Logon Plugins for authentication.



Uniprint 7.2 - 8.2

!exclamation point
@at sign, at symbol, amphora
#hash mark, pound sign
$dollar sign
%percent sign
/slash, forward slash
*asterisk, star
(open parenthesis, left parenthesis
)close parenthesis, right parenthesis
+plus sign
-minus sign
=equal sign
'apostrophe, single quote mark
"double quotes


Uniprint 8.3



Uniprint 8.4 and its Logon Plugins support all of the keyboard characters listed above


MobilePrint 1.2 - 1.3



Print Center 1.4 (Included with Uniprint 9.0)


Trackers may be unable to communicate with Blueprint servers whose server names include foreign characters. To work around this problem, use the Blueprint Server Configuration tool on the server to change the Server Host Name/Address property to the server’s IP address instead of its host name.

Use PS60 version 1.1.4 for a new Blueprint 4.2 install.



When connecting a PS60 to Blueprint Enterprise 4.1 or 4.2, the terminal's type shown in Blueprint never changes from "Generic" to the correct PS60 terminal type.



You are using an older PS60 software (e.g. 1.1.3 or older) that does not support automatic terminal type updates. Upgrade your PS60 to the latest version of PS60 software (1.1.4 as of September 10, 2010).

The PS60 software is available at:

This error message is returned when another application is installed with the Blueprint Services e.g. sharepoint, WSUS service. Some services cannot co-exsist with each other. However one quick method to determine if this is the case is to remove the following file from the root of the www service


By temporarily removing or renaming this object and restarting IIS you can rerun the Blueprint tests to determine if the other application is the cause of the problem.

Typically another application sharing the IIS default website may introduce security and application settings at the root level. This stops the default website from correctly displaying the Pharos web services. In this case xml pages that are used by the Pharos Tracker Service are displayed as HTML rather than XML.

Looking through the Taskmaster service log, you may find something like the following:

The 'OnReleasePrintJobCompleted' method on the job service has thrown the following exception: The LPR command did not receive an acknowledgement from the LPD server ''

This means that we sent the job to the printer via LPR (Line Printer Request, a common way to move printer files to the printer for output), but the printer hasn't told Blueprint that it has finished receiving it yet. Large print jobs, especially if sent over a slower, or multi-hop, network connection, may not have finished copying over to the printer before the Blueprint LPR timeout was met. The Blueprint Secure Release Here function is preconfigured with several timeout values for different steps in the Secure Release Here workflow to protect against slow system performance (or perceived slow system performance).

Of importance during the "select the job at the terminal interface and select print" workflow are the following, taken from the Blueprint server's GlobalConfig.xml file:

    <LprConfig ConfigVersion="3.3">

In this section, the values are defined in milliseconds. Let's step through the settings here:

  • ConnectTimeout. How long the Blueprint server waits when first trying to contact the LPD (Line Printer Daemon) service on the printer.
  • SendTimeout. How long the Blueprint server waits for a send operation (like copying the file to the printer over LPR) to complete.
  • ReceiveTimeout. How long the Blueprint server waits  for a response (usually, an acknowledgement) from the printer.
  • UseStrictLprSourcePorts. Not a timeout, but a way to make Blueprint behave when there are devices (uncommon) that adhere to the strict interpretation of RFC 1179 which specifies a particular range of LPR ports (721-731) that can be used. You would need to contact your printer manufacturer to find out if this is the case.

Normally, it is the SendTimeout that needs the adjustment within Blueprint, because it does a lot of sending, but little receiving. The GlobalConfig.xml file maintains this setting, and is located (by default) in C:\ProgramData\PharosSystems\Blueprint in Windows 2008 or C:\Documents and Settings\All Users\Application Data\PharosSystems\Blueprint. Open it (you may need to edit it in an application launched as an Administrator) and look for the LprConfig section. Doubling the SendTimeout value will usually take care of the problem. Once the change has been made and saved, restart the Pharos Systems Taskmaster service. Note that the Blueprint server is not the only component in the chain. Every piece in the middle (especially a router) and the printer will have timeouts set for TCP send and receive operations as well, so simply modifying Blueprint may not be enough.

On the Mac SignUp Client:

1. Open up /Library/Preferences/com.pharos.signup.plist in a text editor

2. Add the line "Client Logging Enabled", changing the value from 0 to 1

3. Reboot the machine.

Alternatively you can also do the following:

1. Open up a Terminal in /Applications/Utilities and run:

defaults write /Library/Preferences/com.pharos.signup.plist "Client Logging Enabled" 1

Logs will appear in /Library/Logs/com.pharos.signup.daemon.log and should be sent to Pharos Technical Support with the problem detail.

When running setup.exe from the Uniprint CD, the installation begins and then stops immediately with the error "Pharos cannot be installed". Alternatively, running a standalone installer such as the Pharos Station client installer, might display the message "Failed to initialize PSInst32.dll". No additional information is provided. What should I do?

Verify that the Windows Print Spooler service is started. If it is not running, the installers/upgraders will abort the process.

If this does not resolve the issue, please contact Pharos Support at

This happens because the License Upgrader expects a site code of six letters followed by two digits. This error is shown when the upgrader finds a registry file that doesn't match this pattern. You might see this error in two cases:

1.  You have other registry files in either the same folder as PharosLicenseUpgrader.exe, or in your Pharos\Bin directory. In this case, it is recommended you move the upgrader executable and the correct license file to a new folder.

2.  You have a five letter site code. In this case, you can work around the issue by adding an extra letter to the registry filename.

For example: SCODE99.REG could be renamed to STCODE99.REG or SCODEX99.REG.

The filename must be exactly six letters, and two numbers.

Adding an additional letter to the registry file name will not affect your actual site code, and will not cause any trouble with license renewals in the future.

  • Copy and fax apportionment settings have been removed from the Volume Apportionment tab on the Periods > Settings screen. Copy volume determined from a device’s meter reads is apportioned based on the copy transactions on that device. If copy transactions are not available for that device, the copy volume is assigned to the “Unknown user” in the device’s default department. This also applies to surplus volume (e.g. the meter-based volume is greater than the transaction-based volume); the excess volume is assigned to the “Unknown user” in the device’s default department. Inbound fax volume is always assigned to the “Unknown user” in the device’s default department.
  • The centralized page count failure logging mechanism has been removed. This mechanism was used in the past by the Pharos support team. As it required FTP services to function, it has been removed. In addition, the Tracker > Suspect Drivers screen in the Administrator has been removed.
  • A remote Administrator can no longer connect to a Collector. Remote connections required SQL Server. To simplify deployments, the Collector no longer uses SQL Server and hence, remote connections are no longer supported.
  • Administrator Logons on the Collector have been removed. They were required to secure remote Administrator connections – see above.
  • The Secure Release Here > Securable Queues and Secure Release Here > Print Troubleshooting screens have been removed from the Administrator. They are replaced by the Blueprint Secure Queue Configuration tool and Blueprint Secure Release Here Troubleshooter tool respectively.
  • Blueprint Enterprise does not ship with specific terminal types (e.g. Canon iMFP, Omega PS150). Terminal types are added automatically when you connect a new terminal to the Blueprint server.
  • A secured device can no longer be stand-alone (i.e. jobs sent to a secured queue related to that device are only available at that device). A secured device must be a member of a print group. If you have a scenario where a stand-alone device is required, you can create a print group and make that device the only member of that print group.

Typically you will not need a new license key to upgrade to Blueprint 4.2. However, a new license key may be required for licensed features that did not exist when your current license key was issued. If you think this might be the case, and you are a direct customer of Pharos, please contact Pharos Sales for more information by calling 888-864-7768 ext. 2 (toll free US and Canada) or 585-360-1010 ext. 2. Otherwise, please contact your Pharos reseller.

You may also e-mail for assistance.


Microsoft has made an architectural change to protect a security venerability. It allowed a user to run elevated code without permission. This change was implemented in Security Update KB2507938. The change made affects a third party library we use in our software and may cause it to be unstable or cease function.

Relief measure

Any customers reporting instability in Blueprint, Uniprint or Site Monitor services should be advised to uninstall the security update below. Security update KB2507938:

File is attached.

These steps must be carried out in the order described below:


1.  Stop the Pharos Systems ComTaskMaster service.
2.  Check task manager for an executable called popnet.exe (if it is running stop it)
3.  Run the profiler manual uninstall as follows:
     a.  Go to Program Files\PharosSystems\Core. If the folder doesn’t exist, create it.
     b.  Check for a file called CTskMstr.exe. If the file is not there, copy in the one attached (to above location)
     c.  Open a command prompt in that location and type: CTskMstr.exe -unregserver
4.  Delete folders:
     a.  Ensure the command prompt window (used for 3c) is closed.
     b.  Go to Program Files\Pharos. If it exists, delete the folder (and contents).
     c.  Go to Program Files\PharosSystems. Delete the folder (and contents).
     d.  Check for the following registry keys. (if they exist delete them)

     e.  Delete the Pharos popup printer queue in Printer and faxes (if exists)
5.  Restart the Print Spooler service in Services.


The PC should now be back to the state it was before the Popup Client was installed. and should now be able to install a new package.

The common name used in the SSL Certificate does not match the Hostname used/set in 'Blueprint Server Configuartion tool' under the 'Server Host Name / Address' field.

See attached screen shot to see a certificate and the server configuration tool of a working configuration.

When plugging in a Pharos Omega PS150 I have two network cables

a) Ethernet LAN Port on the hub
b) USB Ethernet Port attached to the USB connector on the Hub

The correct configuration is to plug the Ethernet LAN port on the Pharos Omega hub directly into the WALL jack.
The USB Ethernet ports should be connected to the PRINTERS Ethernet port.

Please see the attached note TechNote Automatic Popup and Print Queue Configuration for Mac 10.6 - 10.8.pdf , and also the Popup Client Supplement.html which explains how to install a Manufacturer's printer driver at the same time.

This 8.3 package can be used in all versions of Uniprint, including version numbers lower than 8.3.

Attached, also, is a sample package that installs a Pharos-controlled print queue configured against a non-existent server. Do not install the provided package "as is." Rather, use it as a guide in developing your own package(s).

NOTE: The instructions for modifying the 8.1 client installer can be found here: Automatic Popup and Printer Queue Configuration for Mac OS X; 10.2 - 10.5

There is a way, but it's driver dependent.  You can change it by opening the .ppd file from the .dmg.  This builds on the answer

Automatic Popup and Printer Queue Configuration for Mac OS X

Once that package has been built, you would change the .ppd file, as long as the option is there inside the driver, to accomodate duplex printing by default.



Here's an excerpt from


Printing On Both Sides of the Paper


The -o sides=two-sided-short-edge and -o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The -o sides=two-sided-short-edge option is suitable for landscape pages, while the -o sides=two-sided-long-edge option is suitable for portrait pages:


lp -o sides=two-sided-short-edge filename ENTER
lp -o sides=two-sided-long-edge filename ENTER
lpr -o sides=two-sided-long-edge filename ENTER
The default is to print single-sided:


lp -o sides=one-sided filename ENTER
lpr -o sides=one-sided filename ENTER

Note: The upgrade of a Blueprint server (Collector/Analyst) cannot be rolled back. As a precaution, certain resources should be backed up before upgrading. This enables a manual upgrade if the upgrade fails for any reason.

Starting the Upgrade

Blueprint server components are upgraded using the main installer. To begin an upgrade, select Install Pharos Blueprint from the main splash screen (you can open the main splash screen by running autorun.exe on the CD). When the installer detects the presence of out-of-date Blueprint components, it will automatically switch to the upgrader.

The upgrader uses a subset of the main installer screens to gather new configuration settings and confirm existing ones before upgrading.

Please refer to the “Blueprint Installation Guide” available on the Blueprint CD image for more information about the installer screens.

Note: If the upgrade fails for any reason, do not attempt to uninstall the failed component. In the case of a failed upgrade, Pharos Support should always be contacted before any further steps are taken.

After the Upgrade

In Blueprint 4.2, the Collector no longer requires Microsoft SQL Server. After a Collector upgrade, SQL Server and the Blueprint database are left behind. You can uninstall Microsoft SQL Server from all Collector servers after completing a successful upgrade to Blueprint 4.2. (Note that SQL Server is still required for the Analyst.) It is also safe to delete the Blueprint database after a successful upgrade.

The Analyst and Collector no longer require an FTP service for file transfers. You can uninstall the FTP service from all Blueprint servers after completing the full upgrade to Blueprint 4.2.

When you swipe your magnetic card at the Pharos Release Station you receive the following error message:


"Pharos Station  is not supported by the gateway."


How do you resolve this error?
The error is caused by not having this Pharos Station set up in the Pharos Gateway application.


You have added the Pharos Station to the Pharos Database using the Pharos Administrator but you haven't added the Pharos Station to the Pharos Gateway application.


The next step is to locate the Gateway configuration program (Pharos Blackboard TIA Configuration, CBORD, Diebold) in the programs menu and add the station name to the Pharos Station name list.


Screen shots of the various gateways have been added to this knowledge base article for reference and the location to add this station. After adding the Pharos Station you should stop and start the Pharos Gateway service.

Epson Stylus Pro Printers

Posted by toleary Aug 5, 2013

According to Epson those printers will not work with Pharos.


Epson Support
Epson America, Inc.
3840 Kilroy Airport Way
Long Beach, CA 90806-2469
Phone Number: (562)276-1305


I asked about the driver and server support for the following two printers.


Epson Stylus Professional 4880
Epson Stylus Professional 7800


Epson stated that these printers will not work in a print server environment.

This appears to be the case with all of the Epson Stylus Professional printers.

This has been seen when the configuration of the Card Swipe device is set to read all tracks and not just one track.You should also be seeing the error about "Unsupported Card Type" in the Alerts of the Pharos Administrator.

If this is the case then check that the configuration of the Card Swipe device is set to read only the Track that has the data on it and not all the other tracks.

See attached screenshot for details on where it is in IIS6 & uncheck that option as need be. A similar option exists in the 'Handler Mappings' section of IIS7, called 'Invoke handler only if request is mapped to. Start -> Run -> inetmgr -> Web Sites -> Default Web site -> PharosSystems (right click properties) -> Virtual Directory -> Configuration -> SOAP -> Edit -> uncheck Verify that file exists. Once that is done Start -> Run -> IISRESET.

This error is displayed when Pharos Omega Administrator cannot communicate with the Omega device.


Check that you can ping the IP address or name displayed in Pharos Omega Administrator from the command line. (You should be able to do this.)
Check that the device is turned on and is not behind a firewall.

Popup Client:

The Pharos Popup Client application is available in English, French, German, Italian and Spanish.

Foreign language support is offered in two ways:

1. The Popup Question and user notification dialogs support Regional Settings in Windows operating systems.
2. Standard Popup Questions are available in all supported languages.
Note: for additional information, Search Pharos Help using the term "Internationalization"

Pharos Station:

The Pharos Station component must be installed on a machine running a US English version of Windows.


The Pharos Database must be installed on a machine running a US English version of Windows.

Principal and Print Servers:

Pharos Server components must be installed on a machine running a US English version of Windows.

Related Articles:

Title: SQL Product Support and Compatibility Chart

Title: Pharos Suite Operating System Support and Compatibility Chart

I receive the following error when I try to build a package

Initializing build process.
Packages will be built to: .
Resources are loaded from: .
Package Download & Update Location is:
Loading definitions...
'psdbserver' is not a valid integer value


Initializing build process.
Packages will be built to: .
Resources are loaded from: .
Package Download & Update Location is:
Loading definitions...
Connection refused





Causes (two possible):

a)  The psdbserver 2355/tcp value is missing from the service file in C:\WINDOWS\system32\drivers\etc
b)  The psdbserver is not set to 2355.


a) Add 2355/tcp to the Windows Services file
b) Check in Pharos Administrator > File menu > Network Properties

The Omega 150 come with the VESA 75 standard mounting hole pattern, which means a hole pattern on the back of the monitor: 75mm x 75mm. The diameter of the screws are 4mm.

Screen Actual Size W230mm:H160mm:D20mm (W8.5 Inches:H6.2 Inches: D.7 Inches)

VESA® stands for Video Electronics Standards Association, an international non-profit corporation which represents more than 100 corporate members worldwide, and sets industry-wide interface standards for computing environments.

A Blueprint Enterprise upgrade should be completed in the following order:

  1. Upgrade the Analyst
  2. Upgrade all Collectors
  3. Upgrade all Trackers

Uniprint 8.3 Secure Release Service Application data folder

Print jobs waiting to be released by the user are no longer held in a Windows printer object.  They are transferred from the Windows spooler to the Uniprint Secure Release Service.  Therefore, print jobs are no longer stored in the Windows spooler directory (\Windows\system32\spool\printers).  During the installation of Uniprint 8.3 Print Services, the installer prompts for the location of the application data folder for the Secure Release Service.  After the installation, the given location will be used to store the application data for Secure Release Service, including all print jobs.

Certain configurations may result in a large amount of space being used to store pending print jobs.  It may be desirable to separate this area from operating system workspace, which can be done either during installation or subsequently.

Folder Limitations

The following restrictions apply for the Application Data folder:

  • The folder cannot reside on a network share.  This includes both direct UNC paths and mapped network drives.
  • The full path must contain only ASCII characters.

The Installer might not detect the above situations and if this is the case, the installer may fail to install the product.

How to change the print job storage location (Application Data folder) after installation

The location of the application data folder (including storage of print jobs) can be altered by performing the following manual steps:

  1. Locate the PharosSystems folder structure in the current install location.
  2. Copy and paste the PharosSystems app data folder structure to the new location.
  3. Edit the Secure Release Service config file to point to the new folder location.
  4. Delete and recreate the Symbolic Link for the JobPlugins folder.
  5. Restart the Secure Release Service.

Each step is described in more detail below.

  1. Locate the PharosSystems appdata folder.

    Find the application data folder information from the configuration file under install directory of the application (e.g. "C:\Program Files\Pharos\SecureRelease").

    Locate the file:


    Open the file, find the <appSettings> xml tag at the start of the file and note the location of the Application Data Path.

  2. Copy and paste the PharosSystems application data folder and subfolders to the new location.

    Locate the PharosSystems directory and copy the full folder structure to the new location.  (i.e. \PharosSystems\SecureRelease and all subfolders).

  3. Edit the Secure Release Service config file to point to the new appdatafolder location.

    Under the install folder of the application (e.g.  "C:\Program Files\Pharos\SecureRelease") locate the file:


    Open the file, find the following xml tag at the start of the file and change the value to the new location of the Application Data.

    <add key="ApplicationDataPath" value="NewLocation\PharosSystems\SecureRelease\"/>
  4. Delete and recreate the Symbolic Link for the JobOperations folder.

    Download Junction.exe, a Microsoft Sysinternals tool:

    Copy the file locally to the Print Server machine and open a Command Prompt window in the path of the Junction executable.  Type:

    Junction -d "<programinstallpath>\Pharos\SecureRelease\Plugins\JobOperations"

    (where <programinstallpath> is the full path of the Pharos program files installation, e.g. C:\Program Files\)

    This will delete the existing symbolic link so that a new one can be created.  Then type:

    Junction "<programinstallpath>\Pharos\SecureRelease\Plugins\JobOperations" "<appdatapath>\PharosSystems\SecureRelease\JobOperationPlugins"

    (where <programinstallpath> is as described above, and <appdatapath> is the new path for the application data folders as described in step b).

    This will create a new symbolic link, pointing to the new application data location.

    Note: Windows Server 2008 provides a built-in utility 'mklink' for managing symbolic links. This can be used instead of Junction to alter the symbolic link.

  5. Restart the Pharos Systems Secure Release Service.

    In the Windows Services window, restart the Pharos Systems Secure Release Service in order to use the new setting.

At this point it is possible to delete the SecureRelease folder in the original application data location.

Note: If the MobilePrint solution is also installed, it is important not to delete the \PharosSystems\MobilePrint directory in the default application data location.

Application Data Folder Structure

There are four folders under the Application Data location.

  • Database

    The Secure Release Server uses an SQLite database to store print job information.  The database can be viewed using SQLite compatible tools, but it is not recommended for end users to access this database.

  • JobOperationPlugins

    This folder is used to store plug-in files. For example, if MobilePrint is installed then its relevant files will be installed in this folder.

  • Job Store

    This folder is used to store print jobs.  Print jobs will be owned by the user who is logged on to the workstation.  Print jobs will always be stored under the Windows username rather than the username entered in the popup question.

  • PageCounting

    The spool files in this directory are print jobs that have failed to be page counted by the PageCounter component.  The registry value \PharosSystems\PageCounting\StoreFiles can be set to following values to control the saving of spool files to this directory:

    • 0 = don't save
    • 1 = always save
    • 2 = on failure only

Please contact Pharos Systems Technical Support to obtain an RMA form


Pharos Technical Support
US Toll Free number: 1877-848-0397
Outside the US: +64 9 523 0737

Pharos Omega PS150 devices running in firewall mode limit the use of the following printer ports:

  • TCP/IP 515
  • TCP/IP 9100

These ports can be restricted to provide access to only certain IP addresses, such as a print server.

I get the following error when I run the Blueprint Server Configuration Test:

Blueprint 3.5 SP1 Server Configuration Error:

"The request failed with HTTP status 503: Service Unavailable." for the following services : Tracker Web Service and EDI Web Service


1. Make sure that the Pharos Systems TaskMaster service is running.

2. If the TaskMaster service is already running make sure that the PharosSystemsPool is running under Application Pools

IIS Manager - > Application Pools - > PharosSystemsAppPool

Blueprint Enterprise OS and SQL Support and Compatibility Chart
This document provides charts that list support and compatibility between the operating systems, SQL Server versions and Blueprint Enterprise components.

Please see attached PDF

The Pharos Logon and Billing Portal consists of two 32-bit Windows NT DLLs. One allows for authentication of users, while the other is used to obtain the balance of user accounts and to credit them.


Note: The Pharos Logon and Billing Portal predates the Pharos External Device Interface (EDI). New customers wanting this functionality should use the EDI instead. See the attached Pharos TechNote.

See the attached Pharos TechNote.

Users might get this error message when:

  • The EDI was installed on the server without a Pharos Print Server present AND
  • A charging model was set so that the user can select a cost center from the Omega device


  • If the user installed a Print server on the same machine as a EDI server,

set the following registry key to "Uniprint" using regedit.exe


  • If the user installed a Print server on a different machine,

1. Install the EDI server again and select the corresponding Print server during installation.

2. Change the Omega device setting to use new EDI server.

(Go to the Omega device setup -> edit pedi.ini -> edit url to new EDI server)

You will have to create a new Bank or configure the Bank being used as follows:

Source of Payment: none
Source of Identification: ID Card - Keyboard Wedge
Plugin: Billing set to none, Logon set to use the IpLgnExtender executable

At System > Prompts > Logon Prompts, delete the Password prompt.

Using the ID Card/Keyboard Wedge Logon DLL allows the station to not prompt for the PIN, as is generally used by the Innovative system.

When I apply hotfix 4 to Pharos 7.2 I receive the error


006~ASP 0178~Server.CreateObject Access Error~The call to Server.CreateObject failed while checking permissions. Access is denied to this object.


In the directions on how to apply this hotfix it states to stop the www service and copy the PSDomain.dll into the Pharos Bin folder overwriting the existing then restart the www service. Was the PSDomain.dll file moved?  If moved it usually retains the permissions it had wherever it was stored before, which are not adequate for a webapp.


If no or in doubt, you should be able to view the permissions on the Pharos bin folder and use the advanced "Replace permission on all child objects" option to fix broken permissions. 


Another possibility is that you need to re-register the PSDomain.dll file, but this is rare.  If the permissions do not help, try the commandline "regsvr32 psdomain.dll" from the Pharos bin folder.

The process is different depending on the client operating system.

  • Windows XP clients:

    Change the following registry value to "MSGina.dll" instead of "NTGina.dll" and reboot.

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL

    Change the value back to "NTGina.dll" to restore the client.

  • Vista and Windows 7 clients:

    Run this command as Administrator:

    regsvr32 "%PROGRAMFILES%\Pharos\Bin\SUCredentialProvider.dll" /u

    To re-enable the client, run:

    regsvr32 "%PROGRAMFILES%\Pharos\Bin\SUCredentialProvider.dll"

When I browse to the IP address of my Omega PS150 I receive the following error message:

"The connection has timed out"
"the server at [IP address] is taking too long to respond."

What should I do to resolve this issue?

This is a common misconfiguration error and is typically one of the following issues:

  • The Omega PS150 is not turned on
  • The Omega PS150 is not connected to the network
  • The Omega PS150 network details have not been correctly configured to work on the host network
  • The incorrect IP address has been typed into the browser window

Please re-check that the Omega is powered on and correctly connected to the network and retry the browser connection to the Omega PS150.

Click here to see the current list of supported bizhub Konica Minolta MFPs.

If you would like to request iMFP software or documentation, please contact Pharos Technical Support at

Pharos Popups and Notify are now installed through Package Definitions, but when you try to create a new package on a SignUp-only installation, you receive this warning:

You do not have any Spool Queues. You need to create the Spool Queues before you create Package Definitions.
Pharos Popups and Notify are now installed through Package Definitions, but when you try to create a new package on a SignUp-only installation, you receive this warning:

You do not have any Spool Queues. You need to create the Spool Queues before you create Package Definitions.

The IP address of the Print Server in the error message does not match the IP address stored in Pharos Administrator (located under System > Servers)


Make sure these values are correct and match.


When the Copy button is pressed on the Omega Terminal Device this error occurs:

"object reference not set to an instance of an object"

The Omega is attached to an MFD and used for copy and print. The print feature works properly.


Check the Copy Lines configured in Pharos Administrator. This error can occur if any of the lines show N/A as entries. Remove or properly configure these copy lines.

In Pharos 7.2 look on the Pharos Administrator "Pharos Managed Copier" context. To fix this put "Copy Line 0" at the top of the list in the Copy Control Configuration Page.

Check which version of the Print Server the customer is running. If they are not running the latest 6.1 Print Server Hot Fix then that’s probably the cause of the problem.


Order of events is as follows.

  1. LPD Server starts receiving a print job. It creates an “entry” in the spool queue, with name of “Local DownLevel Document” and user of “SYSTEM”, because at this point they’re not known.
  2. LPD Server gets the rest of the job, updates the job name and user.
  3. Print Server detects new job, opens it, and gets the details.
  4. Print Server page counts the job, and puts the job details back with the page count info attached to end of the job name.

However, prior to Hot Fix 4 (6.1) for the Print Server we had the following order of events occur sometimes:

  1. LPD Server starts receiving a print job. It creates an “entry” in the spool queue, with name of “Local DownLevel Document” and user of “SYSTEM”, because at this point they’re not known.
  2. Print Server detects new job. Opens it, and gets the details (With name of “Local DownLevel Document” and user of “SYSTEM”).
  3. LPD Server gets the rest of the job, updates the job name and user.
  4. Print server finishes page counting the job, and puts the OLD job details back, with the page count info attached to end of the job name.

To correct an oversized Pharos transaction log follow these steps:


Close all connections to the Pharos Database:


a) Stop the Pharos License Server Service which will stop all Pharos Services
b) Close any copies of Pharos Reports that may be running.


OPTION 1: Using SQL Server Enterprise Manager or Management Studio


a) Detach the Pharos database
b) Locate the SQL Server data files. There should be two files related to the Pharos Database (pharos_data.mdf and pharos_log.ldf)
c) Delete the oversized log file (pharos_log.ldf)
d) Re-attach the Pharos database and restart the Pharos Services, starting with License and Database Services


OPTION 2: Using a command prompt


a)  In the Command Prompt run the following query to detach the Pharos database:


osql -U sa -d master -S servername -Q "sp_detach_db 'pharos'" -P password -o outputfile.txt


servername - Name of the Server
password - Valid Password for 'sa' account


b) Now, in the Command Prompt run the following query to re-attach the Pharos database:


osql -U sa -d master -S servername -Q "sp_attach_single_file_db @dbname = 'pharos', @physname = 'correct_path\pharos_data.mdf'" -P password -o outputfile.txt


c)  Restart the Pharos services starting with License and Database Services




Verify that SQL Server Agent Service is set to Automatic and running to ensure that daily Pharos Database backups are performed.
Check in SQL Server that the log is set to be 30 MB and allowed to grow at 10%.

SQL Server 2008

The backup process for SQL Server 2008 doesn't work with Pharos. It fails with a error stating that "truncate only" is not a valid option.

Note: A small video has been provided using SQL Management Studio.

Please see the attached error log and screen shot to verify the error.

Open SQL Server Configuration Manager and make sure SQL Server (MSSQLSERVER) service is running under the Built-in account. i.e. Local System Account.

Clean the Blueprint folders and delete the databases if required for a clean slate. Try and follow through the same process again.

The Pharos Station is trying to start either before the Pharos Database Proxy service is running, or before the Windows network layer has started. A bug has been identified in the Pharos Station that causes failures at startup time to be fatal instead of recovering as in earlier versions.

In some cases, it may be enough to edit a group policy setting that instructs Windows to wait for the networking before allowing users to log on:

  1. Run gpedit.msc and navigate to Computer Configuration > Administrative Templates > System > Logon.
  2. Set the policy "Always wait for the network at computer startup and logon" to Enabled.

If the Station still starts before the Pharos Database Proxy service, the 'Connection refused' error will be displayed. This can be avoided by using a batch file to ensure the service is started first.

  1. Open the Services tool (services.msc).
  2. Set the Startup property of the Pharos Database Proxy to Manual.
  3. Replace your startup shortcut with a batch file containing the following two lines:
    @net start psdatabaseproxysvr
    @start "" "%programfiles%\pharos\bin\pstation.exe"
    Replace the path to the Station if necessary.

A solution is currently being worked and and the fix will be posted on the Pharos Support web site.

Gatekeeper is a new feature for Mac OS 10.8 Mountain Lion where only applications that are from the Mac App Store or recognized developers can be installed with the default security settings.  (see attached "Package Error.png")

This can be bypassed by opening the Pharos package with a right-click or a control click and selecting "Open".  This will call a Mac dialogue box confirming your choice to open the package, even though it is not from an Apple Identified Developer.  You should then be able to continue the installation normally.

Please also note, Pharos is currently working on a signed package that will work with Gatekeeper.

Pharos Support is aware of an issue affecting some Mac systems, and is working on an appropriate solution. Any further updates will be added to this Knowledge Base article.

At this time, the problem is believed to be related to DNS resolution failing early in the boot process.  To work around this, you can try adding your SignUp Server hostname to your /etc/hosts file, or altering the SignUp Client property list with the following command:

defaults write /Library/Preferences/com.pharos.signup "Server Address" $(dig -q $(defaults read /Library/Preferences/com.pharos.signup "Server Address") +short)

This command (all one line) needs to be run either before you reboot into the SignUp client the first time, or via an ssh session.

If you wish to disable the SignUp client and restore the Mac to its original login configuration, you can perform the following steps in single user mode, or via ssh if you have remote login enabled on the Mac.  For ssh, you must log in as an Administrative user.

  1. Change Directory to the '/etc' directory:
    cd /etc
  2. Replace the authorization file with a backup:
    sudo cp authorization.backup authorization
    Enter your password when prompted.
  3. You should recieve no error messages and see a new line with the shell prompt. This means the comand has completed correctly.
  4. Reboot the machine:
    sudo reboot

When installing a package using a Windows GPO it will allow only you to install "Installer Files" of type ".msi" (Microsoft Installer).

There is a Knowledge Base article on Microsoft's web site explaining how to wrap the Pharos Package executable into an MSI file using a ZAP file.

Normally, Discount Rate Schedules are available for printing only; however, when using PS20 or Omega Network Terminals, it is possible to apply Discount Rate Schedules to copying costs as well. Some modifications to the Pharos Database are required to implement this.

See the attached Pharos TechNote.

When I release a job on the Omega I receive the following error message:

Failed to release the print job. Failed to release the print job with Guid '282f8f3b-0ec9-4db9-aca2-40136c10f3fb' to the Device with ID 1 using Identifier '015054'.  Could not connect to the LPR server. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond



Reason: Failed to release the print job. Failed to release the print job with Guid '282f8f3b-0ec9-4db9-aca2-40136c10f3fb' to the Device with ID 1 using Identifier '015054'.  Could not connect to the LPR server. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

a) Check to see if the printer is turned on

b) From the Analyst or Collector, telnet to the printer on port 515, if the port is not open this will cause the error message.

The following article contains setup instructions and user manuals for the Boscop Autoloader (networked).


The Boscop Autoloader currently connects to Pharos Uniprint via the NTSmaster.dll system embedded in the Pharos Print Server. This NTSmaster.dll was embedded in the Pharos Print server from version 6.1 on and can be used to talk to network terminals and autoloaders provided by Boscop.


All Boscop units have two modes of operation

  • Bootp - automatically assigned an IP by the Pharos Print Server
  • Static IP - assigned manually

The units are normally configured with a static IP however they can be configured to use bootp as well. To configure bootp or static IP on a Autoloader or Terminal you should swipe the Parameters card which will allow you to select either of these options.

Note: If you are using bootp the Uniprint Server is resposible for sending the unit the IP address via Bootp. Until you setup the unit correctly in Uniprint the unit will not be avaliable on the network. Bootp may not be routed between subnets. In this case you can install the bootp relay agent included on the CD.

Uniprint Setup

Uniprint by default ships with a terminal type called "VCC Terminal". You should insert a new network terminal into the Pharos Administrator\Pharos Stations\Network Terminals context. You can give the terminal any name however you will be asked for the MAC address of the Autoloader which is displayed on the autoloader at boot time.

Once you have entered the MAC address you are asked for an IP Address, this should be the IP Address that bootp will assign. To confirm the changes after installing the terminal complete the process by performing a change control.

If the Autoloader is configured corrrectly it will recieve the IP Address and the display will now ready the default "Please log in" message.

Supporting Documents

VCA Users Manual

Supporting Applications


Upgrading to Windows Server 2008

Blueprint Enterprise 4.2 does not support directly upgrading from Windows Server 2003 to Windows Server 2008 in an existing Blueprint installation. If you want to upgrade your operating system with Blueprint Server components (Analyst, Collector, and Server Tracker) already installed, you must follow the appropriate process below to complete the upgrade.

To upgrade Windows 2003 with an Analyst/Collector installed to Windows 2008:

  1. Back up the Blueprint Database of the Analyst.
  2. Uninstall the Analyst/Collector. Do not leave the database on uninstall. Refer to the “Blueprint Installation Guide” for the uninstall procedures.
  3. Upgrade Windows 2003 to Windows 2008.
  4. Install the Analyst/Collector (including a fresh database on the Analyst). Refer to the “Blueprint Installation Guide”.
  5. Restore backup Blueprint Database.

To upgrade Windows 2003 with a Server Tracker installed to Windows 2008:

  1. Uninstall the Server Tracker. Refer to the “Uninstalling Trackers” section of the “Blueprint Installation Guide”.
  2. Upgrade Windows 2003 to Windows 2008.
  3. Install the Server Tracker. Refer to the “Installing the Tracker Component” section of the “Blueprint Installation Guide”.

While the Pharos Uniprint software runs only on Windows platforms, print jobs sent from other platforms such as UNIX, Novell or Macintosh can be sent to the Uniprint system to be controlled and costed. This is achieved by using TCP/IP printing, which requires the use of an LPD Server.



See the attached Pharos TechNote.

All Pharos Omega devices support the reading of card data on track 2 only from standard non-encrypted magnetic cards. Customers that need to have additional tracks returned should contact Pharos Sales to source an external serial card reader that will return all card tracks.

The new generation PS150 devices support reading from all tracks.

PS150 devices need to be configured to enable the reading of additional track data. To do this:

  1. Open Pharos Administrator.
  2. Select the Pharos Stations > Network Terminals context.
  3. Select the appropriate option for the "Collect Data From" property on the Card Reader tab.
  4. Save and restart the terminal.

NOTE: The Omega Station application will always strip the default start and end sentinels from the SmartPAD build-in card reader and serial card readers' data streams.


When this problem occurs the green light on the card swipe will not blink when the card is pulled through the reader. It is most prevalent when the reader is mounted to the top or the right of the display. It only seems to happen with the Magtek Sure Swipe readers (p/n 21040145).


The problem is associated with RF noise in the environment, some of which comes from the PS150 display. Grounding the PS150 Card Swipe Mounting Bracket resolves the problem by providing an RF sink to isolate the card reader.

See attached document for details.

Check the following:

1. That the server can connect to the remote SQL server using SQL Enterprise from the Analyst.
2. That the default TCP/IP communication port for SQL (1433) is being used.

If the default SQL port is not being used it may be necessary to set up an alias on the Blueprint Analyst machine to map the default SQL port to the custom port on the SQL server. Clients should use the cliconfg tool to insert an alias and map it to the custom port for the remote server. After completing this step clients should re-run the Pharos Blueprint installation program.

This is a know issue in Vista.


See:  Microsoft Help and Support - Article ID: 947236


1. Click Start , type gpedit.msc in the Start Search box, and then click cmd in the gpedit.msc list.
If you are prompted for an administrator password or confirmation, type your password or click Continue.
2. Under User Configuration, expand Administrative Templates, expand Control Panel, and then click Printers.
3. Right-click Point and Print Restrictions in the right hand pane, and then click Properties.
4. Click Enabled.
5.If you do not want to restrict users to specific print servers, click to clear the Users can only point and print to these server check box.
6.If you do not want to restrict users to print servers in their own forest, click to clear the Users can only point and print to machines in their forest check box. You do not have to add any servers when you click to clear this check box.
7. In the Security Prompts area, select Do not show warning or elevation prompt in the When installing drivers for a new connection box and in the When updating drivers for an existing connection box. These settings enable the print drivers to be installed without credential or elevation prompts.

The Uniprint 8.1 install supports a fresh installation on a Windows 2003 or 2008 cluster, but not upgrading from a previous version.  The attached document provides step-by-step instructions to upgrade your Principal and/or Print services on an existing Windows 2003 cluster.

This problem may indicate that the attached hardware (MFD/switch) is powered down or malfunctioning. If there are no problems with the hardware, one or both of the Ethernet Link Mode properties may need to be changed. To change these properties:

  1. Enter the configuration menu at the Omega SmartPAD (contact Pharos Support if you do not know how to do this).
  2. If it is the Ethernet port labeled "LAN" that is not working, select the Network screen. If it is the Ethernet port labeled "Print" that is not working, select the Firewall screen.
  3. Enter a new value for the Eth0 Link Mode/Eth1 Link Mode property. Possible values are:

    • 0 = autonegotiate up to 100 Mbit full duplex for hardware that supports it, otherwise up to 10 Mbit full duplex (this is the default)
    • 1 = 100 Mbit full duplex
    • 2 = 100 Mbit half duplex
    • 3 = 10 Mbit full duplex
    • 4 = 10 Mbit half duplex
    • 5 = autonegotiate up to 10 Mbit full duplex

Start at 100Mbit full duplex and proceed downwards until you see the yellow status LED light up.

Attached is a copy of the Customer Services Kiosk Users Manual.

Please refer to this manual for installation and configuration information.

When the Pharos terminal is indicating a failure or is not performing as expected, we will need logs from the terminal to better understand the source of the problem and provide you with a resolution. All of the terminal options from Pharos (with the exception of the Konica-Minolta iMFP) can utilize a Syslog application to collect this log. Once the log has been collected, attach it to your existing Pharos Systems incident, or attach it to your new request for support. This KBase article used the Kiwi Syslog Server application.

  1. Download and install the 14-day trial Kiwi Syslog Server from the following site:
    1. Run the Syslog Server "eval" Setup to install Kiwi Syslog. Install as an application. NOTE: You do not need to install the Web Access component.
    2. Start the Kiwi Syslog from any of the shortcut locations specified during setup
    3. Set Kiwi Syslog to begin logging and save or log to a file
  2. Turn on logging for the Pharos Omega PS60, PS150, PS200, or Xerox PSX:
    1. Browse to the Omega web pages (sample: http://ipaddress:8080) and log in with the root password ('pharos' by default)
    2. Select System > Log Settings
    3. In the Syslog Server Address box enter the syslog server address where you installed kiwi syslog
    4. Change the Buffer Size to 1000 and check SOAP Packet Content as well as Station Error, Warning, Notice and Debug
    5. Click the Save Selected button.
    6. Perform the operation that results in the fault.
  3. Turn on logging for the Pharos iMFP Terminal (for all but Konica-Minolta iMFP; see the "Konica-Minolta iMFP Loging" section below):
    1. Browse to the iMFP configuration web page (consult your iMFP's Installation and Configuration guide if you are unsure how to get there)
    2. Enable logging in the "Logging" section of the page.
    3. Tick the "Syslog" box.
    4. In the Syslog Host/Server Address box enter the syslog server address where you installed kiwi syslog
    5. Choose "ALL" for Threshold.
    6. Click the Apply button.
    7. Perform the operation that results in the fault.

Konica-Minolta iMFP Logging

By default, logging output is set to minimum to reduce the overhead caused by large amounts of logging. Should the need arise to increase the logging then you will need to edit the application configuration file for the desired application. The configuration file for the Pharos for Konica Minolta service is located at: <program install dir>\PharosSystems\ Pharos iMFP for Konica Minolta\KonicaMinoltaService.exe.config. The configuration file for the Management Console is located at: <program install dir>\PharosSystems\ Pharos iMFP for Konica Minolta\PharosiMFPManagementConsole.exe.config. Open these files in a text editor and locate the following section:

<logger name="*" minlevel="Fatal" writeTo="CSVFile, consoleNew"/>

Change "Fatal" to "Trace" and then restart the Konica-Minolta iMFP service.

The HOSTS file has been set to read only or locked by another process.

Some types of Spyware software or AV software may set the file attributes of the windows HOSTS file to read-only and the Signup client needs to access this.

Most common is SpyBoy Search & Destroy. Please check the web site for your specific spyware application and search for HOSTS file to discover further on how to insure that the file is not reset to read-only upon next reboot.

Alternatively you can locate the windows HOSTS file at:


Right-click on the file and deselect the checkbox for read-only.

Re-install the Signup client