Loops back to Sign in page
Printix Client does not know its Printix Home
When this is the case, the Printix ID in Windows Registry is not set. This can happen if:
-
The Printix Client installation file was renamed before installation.
-
The Printix Client MSI file was deployed through, for example, Microsoft Endpoint Manager, but in command line arguments, :/id was not set correctly.
Resolution: Do NOT rename the file before installation. Type the Command line arguments correctly, for example: WRAPPED_ARGUMENTS=/id:cbfce0b5-da2a-4cb6-b7f7-a04ee31cac90. Replace the /id value with your Printix ID as shown in the name of the MSI file.
Is a web proxy and/or SSL inspection used?
In this case, the PrintixService.log file will contain the text: SrvComm Exception: Status: ProxyAuthenticationRequired.
Resolution: You MUST add the printix.net domain and subdomains as exceptions so traffic is not blocked. See also: Internet endpoints that must be unblocked.
I do not recognize the used web proxy
In this case, the PrintixService.log file contains text such as: ServerComm: running with proxy1: http://172.23.100.13:8080/ and Unable to connect to the remote server.
Resolution: See How does the Printix Client find the web proxy?
Is FIPS (Federal Information Processing Standards) enabled on the computer?
Enabling FIPS disallows the use of the MD5 hashing algorithm, which is used by the Printix Client to make some entries in the Windows Registry "tamper-resistant."
Resolution: Disable FIPS.
-
Press
Windows+R.
The Run dialog box appears.
-
Type
regedit, then select
OK.
Select Yes if prompted.
The Registry Editor appears.
- Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy.
- Change the value Enabled to 0.
- If present, also change the value MDMEnabled to 0.
- Restart the computer.
PowerShell script
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy" -Name "MDMEnabled" -Value 0