ThinPrint Licensing & License Server

Editing or deleting users

You can delete or disable users. In either case, their user licenses become free – how­ever, not till 28 days at least after they were last assigned to the users. You can then reassign licenses, if you want to import new users (see the last seven Illus. in Assigning a license to a user).

See also the FAQs: License Server.

• Remove
  The user is removed from Management Console and the ThinPrint license becomes released (left arrow). See also the section Releasing ThinPrint licenses.
• Undo Remove
  After deletion, this process can be reversed as long as the license for this account is blocked (max. 28 days).
• Edit
  Selecting Edit opens a dialogue, in which you can remove the check mark in front of ThinPrint enabled (right arrow). The relevant user remains on the list, but is disabled and the license becomes free. With disabling users it’s possible to deny them printing with ThinPrint.

Mobile Session Print

Using the Mobile Session Print option (formerly Mobile Print, see previous screenshot) users which already are enabled for Thin­Print can be enabled for Mobile Session Print additionally – in this case manually. Preconditions: a ThinPrint Engine license as well as a Mobile Session Print server which is already registered at the ThinPrint Notification Service. Then, with Force Update, the settings must be sent to the Mobile Session Print server and thus to the ThinPrint Notification Service. For more information see Mobile Session Print.

Releasing ThinPrint licenses

You can release ThinPrint licenses by:

• removing ThinPrint users from the ThinPrint Management Console (left arrow in previous screenshot)
• synchronizing ThinPrint users with Active Directory users (right arrow in next screenshot)
  • ThinPrint licenses of users removed from the AD beforehand (Users deleted in the screenshot following the next one) will be released automatically if they were activated for at least 28 days.
  • ThinPrint licenses of users removed from the AD beforehand, which were not activated for at least 28 days, will be shown as Users marked for removal. These can be recovered using the ThinPrint Diagnostic Utility.
  • ThinPrint licenses of users disabled in the AD will be shown as Users deactivated in AD (see last Illus. on this page). These can be released using a PowerShell script (see below).

Synchronization with the Active Directory

If users have already been removed from the Active Directory you can synchronize the ThinPrint Management Console with the AD.

• To do so, select Control Panel→ Global Settings→ AD Sychronization→ Synchronize now.

The following two screenshots show the result. If a user removed from the AD has not been enabled for at least 28 days, his license is blocked until the end of this period. However, if the user is also disabled in ThinPrint, no license will be used. Example: In the first screenshot, two user accounts are displayed as disabled in the AD. However, one of them occupies a license because it was not disabled for ThinPrint; therefore three licenses are occupied for four ThinPrint users, and one is free. As soon as the license of the user deactivated in the AD has been activated for at least 28 days, it automatically becomes free. Or you can release it manually (see the section Releasing ThinPrint licenses of users which were disabled in the AD below).

Translated with www.DeepL.com/Translator

The synchronization protocol can be saved with the options:

• Copy protocol to clipboard and
• Download Protocol as XML

Releasing ThinPrint licenses of users
which were disabled in the AD

In case you want to release ThinPrint licenses of users which were disabled (tempo­rarily) in the Active Directory follow these steps:

• Download the synchronization protocol by selecting Download protocol as XML (right in the screenshot). Store it, for example, in c:\thinprint\Protocol.xml.
• On the license server, open the PowerShell console as a member of the local ThinPrint Configuration Admins group.
• Run the following PowerShell script (the variable $filePath contains the path to the downloaded synchronization protocol):

$filePath = "c:\thinprint\Protocol.xml"
[xml]$xml = Get-Content $filePath
$xml.ADSyncProtocolModel.users.ADSyncUser | Where-Object { $_.status -eq "Disabled" } | foreach { Remove-TPUser $_.sID }