Installation

Launch the provided TwoPint.DeployR.Installer.msi file. At the welcome screen, click Next:

At the "End-User License Agreement" screen, once you have reviewed the EULA, check the box I accept the terms in the License Agreement, and then click Next.

On the Destination Folder page, specify the desired installation location then click Next:

On the Ready to Install page, click the Install button to perform the installation:

On the Completed page, ensure that the Launch Configuration Editor checkbox is checked and then click Finish.

Note: DeployR will attempt to create the specified SQL databases if they do not yet exist. In order for this to succeed, the default NT AUTHORITY\SYSTEM account needs to have a logon in SQL Server and must also have the "sysadmin" role.

Alternatively, the database can be manually created. Ensure that the default NT AUTHORITY\SYSTEM account is assigned the "db_owner" role in the database.

To specify a different service account, grant the new service account "db_owner" access to the database, then manually change the DeployR Service settings and restart the service. Note: The service account currently reverts to NT AUTHORITY\SYSTEM after a DeployR version upgrade.

The Configuration Editor will then launch to configure DeployR.

And Advanced Options

Some basic settings can be configured:

  • Certificate Store Location. This specifies where DeployR can find the TLS/SSL certificate needed for secure communications. This should typically remain set to "LocalMachine."

  • Certificate Store Name. This specifies the name of the certificate store (in the specified store location) containing the certificate needed for secure communications. This should typically remain set to "My."

  • Certificate location mechanism.

    • CertificateSubjectName: This specifies the subject name of the certificate that should be used. This can be specified in cases where the certificate is updated frequently (changing the thumbprint), to avoid needing to change the DeployR configuration each time this happens.

    • CertificateThumbprint. As an alternative to the certificate subject name, you can specify the thumbprint of the certificate (a hex-encoded string). If you specify both CertificateSubjectName and CertificateThumbprint, the thumbprint will be used.

  • SQL Server configuration method

    • ServerInstanceAndDB - Provide both the Instance & Database Name

      • SQL Server Instance. This will be the instance name of SQL installed. Default = .\SQLExpress, but you could have named it anything during the installation of SQL.

        • This will contain the name of the server and the name of the instance like so: MyServer\SQLInstanceName ex: SQLHost\SQLExpress

        • If the SQL is installed on the local DeployR Server, you can just use .\SQLInstanceName, ex .\SQLExpress

      • SQL Server database. The database the DeployR uses, if you pre-create one, you can enter the name, otherwise DeployR will automatically create a database named DeployR the first time the DeployRService runs.

    • Advanced - Provide the SQL Connection String

      • SQLConnectionString [Advanced]. Specify the SQL Server connection strings to be used for the two SQL databases used by DeployR. Ex for those using SQLExpres on the same server: 

        Server=.\SQLEXPRESS;Database=DeployR;Trusted_Connection=True;MultipleActiveResultSets=true;TrustServerCertificate=True

  • DeployR Content Location Path. All of the content managed by DeployR will be stored at the specified location. This defaults to %ProgramData%\2Pint Software\DeployR but can specify any valid location that the DeployR service can manage.

  • DeployR Client URL. This specifies the full URL that client devices would used to contact the DeployR server. The server name should match that used in the specified certificate; the default port 7281 should be used. An example value would be https://contoso-server.contoso.com:7281.

  • Join Infrastructure [Show Advanced]. This must be enabled so that DeployR will register with the StifleR infrastructure.

  • StifleR Service API URL. This specifies the URL and port (typically 9000) to use to communicate with the StifleR service.

  • Heartbeat Interaval (second). When Join Infrastructure is enabled, this specifies the amount of time in seconds between heartbeat events sent from DeployR to StifleR. The default value of 30 seconds is recommended.

More details about the different settings are discussed in the corresponding pages.

Once the needed settings are configured, click the Verify button to ensure the settings are valid. This will then prompt for confirmation:

Click Yes to enable and start the DeployR service.

Afer the DeployR service has started, confirm that it is properly registered with the StifleR infrastructure via the Administration -> Infrastructure services page on the StifleR Dashboard. Initially, this will show DeployR with a status of "Not approved" (a yellow warning triangle):

On the Actions menu, choose Approve to enable communcation between the two services. After approval, the status will change to a green checkmark:

For confirmation that the correct URL is provided to the StifleR platform for communication with DeployR, expand the row by clicking the > at the beginning of the row to see the details:

Before the DeployR Node shows up in the Dashboard, you need to launch the StifleR Config Editor, enable the "show advanced" toggle, then search on the word "show". Once it provides the settings, make sure you enable "Show DeployR Features". Then Verify and Save.

Next, navigate to Deployments -> DeployR -> Task sequences to confirm that communication is working.

Last updated