OPTION 1: UP Connector with Job Service and Client v3/Spooler in the Server Mode

• Installed .NET Core Runtime 3.1 - https://dotnet.microsoft.com/download/dotnet-core/3.1

• Deployed Job Service on the server - Deployment of YSoft SafeQ Job Service

  • You need to apply for Early Access Feature

• Deployed Spooler (Client v3) on the server - Deploying YSoft SafeQ Client v3 in the Server Mode

  • You need to apply for Early Access Feature

  • Also, stop and disable the server FlexiSpooler service

OPTION 2: UP Connector with Mobile Integration Gateway

All YSoft SafeQ servers which will be running the connector need to have:

• Installed .NET Core Runtime 3.1 - https://dotnet.microsoft.com/download/dotnet-core/3.1

• Deploy MIG on the server following - Mobile Integration Gateway deployment

  • Please make set the configuration option allow-public-user to true (default is false) in <MIG_install_dir>\bin\MigService.exe.config

    • <add key="allow-public-user" value="T"/>

• • The MIG certificate needs to be trusted by OS running the UP connector. Either configure MIG to use your own trusted certificate or ensure the trust of the default self-signed.

  • The default deployment script of the UP Connector expects the IPP spooler to be on port 631

Deploy with Default Settings

1. Make sure you have installed the appropriate .NET Core Runtime 3.1 version (see the prerequisites above).

2. Copy the installation package of the UP Connector onto the server.

3. Install the UP Connector by running the following command in the console window as administrator
   (this will install the UP Connector with the default settings, see the advanced installation below):

   .\install-win-service.cmd

4. Use the device code and URL displayed in the console window to register the connector in case this step is required and confirm it
   (the code and the URL can be found in the installation logs as well).

   USER ACTION REQUIRED:

   To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code <XXXXXXXXX> to authenticate.

5. Navigate to the URL for the Microsoft OAuth page: https://microsoft.com/devicelogin and paste there the code from the log above.

6. Then you need to log in as a user with " Application Administrator " or higher. You can see more permissions in prerequisites section.

7. You need to approve all listed consents. They should be as follows:

Advanced Installation with Custom Settings

Follow the steps from the standard installation above but exchange step #3 with the following instructions:

• Alternatively, the UP Connector can be installed using the following command in the PowerShell console window allowing to customize some settings
  (if the script is run without any additional parameters it will again result in the default settings being used):

  .\install-win-service.ps1

• The following parameters can be customized:

• • InstallPath (the default is "C:\SafeQ6\UPConnector")

  • UPConnectorZipFile (the default is "YSoft.UPConnector.zip")

  • JobServiceIppsHostname (the default is "localhost")

  • PrinterDeviceName (the default is "SafeQ 6")

  • RegistrationId (the default is generated by the script)

• • for example:

    .\install-win-service.ps1 -InstallPath 'C:\custom\location\UPConnector' -PrinterDeviceName 'My Example Printer Name'

Deployment of multiple UP Connectors in the High Availability mode

The first UP Connector is installed in the same way as described above. During the installation process, you will see the following message:

The message is also logged in the installation log. The location of the installation log is described in the Configuration and logs section.

For every other UP Connector, which will use the same printer queue, replace step #3 with the command generated by the installer of the first one. You can of course use any other parameter described in the Advanced Installation procedure described above.

Deployment with conditional access policy

We have a solution for customers that have a very strict security policy of user token expiration. This customization ensures that UP Connector will keep running even after the initial device authentication will expire due to the customer's policy.

1. Make sure you have installed the appropriate .NET Core Runtime 3.1 version (see the prerequisites above).

2. Copy the installation package of the UP Connector onto the server.

3. Install the UP Connector by running the following command in the console window as an administrator.
   (this will install the UP Connector with the default settings, see the advanced installation below):

   .\install-win-service.cmd

4. Respond to console instruction with "No". You can safely close the console now.

5. Open file <instal_dir>\UPConnector\configuration\local.json. Add the following configuration:

   "UseFunctionsKey": true

   The final local.json should look like this:

   {

   "ConnectorHubOptions": {

   "ConnectorHubUri": "https://api.up365.ysoft.cloud",

   "TenantId": "organizations",

   "ClientId": "e5eedc46-ba66-44f3-9144-060c86eb5c5e",

   "Scopes": [

   "e5eedc46-ba66-44f3-9144-060c86eb5c5e/.default"

   ],

   "UseFunctionsKey": true

   },

   "JobDeliveryOptions": {

   "ForcePrintJobOperation": false

   }

   }

6. Save changes and close the file.

7. Restart SafeQ Universal Print Connector service.

8. Open log file<instal_dir> \UPConnector\logs\upconnector.log.

9. Find and use the device code and URL displayed in the log file to register the connector in case this step is required and confirm it.

   USER ACTION REQUIRED:

   To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code <XXXXXXXXX> to authenticate.

10. Navigate to the URL for the Microsoft OAuth page: https://microsoft.com/devicelogin and paste there the code from the log above.

11. Then you need to log in as a user with " Application Administrator " or higher. You can see more permissions in prerequisites section.

12. You need to approve all listed consents. They should be as follows: