Client Deployment
The Client Deployment object provides access to the Assign Script object and the GPO Deployment object, both of which arm the domain user and computer with configurations for Desktop Authority to execute during client logon process.
Assign Script
The Assign Script object is used to assign the SLOGIC logon script to domain user accounts for User Management profiles and objects.
GPO Deployment
The GPO Deployment object provides the ability to deploy Desktop Authority's SLagent technology to client workstations by using a GPO extension.
Client Provisioning
Client Provisioning encompasses both GPO Deployment and Logon-based Deployment and dynamically chooses from the best of several deployment approaches at runtime in order to deploy necessary files to the client computer.
Off-Network Client Provisioning (manual deployment)
Off-Network Support (ONS) allows computers to receive configuration updates over the internet without having an active connection to the parent domain. Off-Network Client Provisioning (ONCP) allows for the initial provisioning of new computers to occur off-network (i.e. while being disconnected from the parent domain). Once a new off-network computer has been provisioned using ONCP, it is immediately ready to begin retrieving Off-Network Desktop Authority settings (assuming an active internet connection and ONS being configured).
However, unlike the automated on-network provisioning process, ONCP deployment can only be done outside of the Desktop Authority framework. This means Admins attempting to utilize ONCP MUST first determine an efficient method to deploy and install the necessary files to their off-network computers that require Desktop Authority provisioning.
|
|
IMPORTANT: Microsoft .NET Framework 4.6 (or 4.5) must be installed and enabled on client computers prior to provisioning using ONCP. Desktop Authority will not function correctly on computers provisioned using ONCP without a supported version of .NET already installed and enabled. In the case of computers provisioned on-network, a supported version of .NET is automatically installed if needed. |
Provisioning an Off-Network computer using ONCP
- Once all latest changes have been saved and replicated within the DA Manager Console, copy both the DAClientInstall.msi and DAClientInstall.ini from the current User Management Replication share (%logonserver%\Netlogon by default).
- Using the most efficient available method, copy both files down to each Off-network computer.
NOTE: Both files MUST be located in the same folder prior to installation.
- Install the DAClientInstall.msi file on each off-network computer. This can be done manually or automated using a custom script.
- Once the installation has been completed, the newly provisioned computer(s) should immediately begin processing Desktop Authority settings. For off-network computers, this assumes there is an active connection to the internet and ONS was properly configured prior to copying the necessary files from the User Management Replication Share during Step 1.