Automated Deployment of DPX Client

For Windows non-clustered nodes, you can install DPX client software from a single point in your Enterprise rather than by running the installation program from the installation image on each remote machine. This single-point installation procedure is referred to as remote deployment.

Note. Remote deployment is for initial installations; you cannot use it if you are upgrading DPX. For upgrades and updates, see Updating DPX.

Remote deployment automatically adds installed nodes to the Enterprise, with each node in a separate node group.

For database servers, you can install remotely, but you must install database support locally. For this reason, you may want to install locally for such servers just before installing the database support.

If you have Windows 10 clients, be aware of the following. The administrative account on Windows 10 is inactive by default and needs to be enabled before DPX can be installed via Remote Deployment. Therefore, if you run Remote Deployment from the master server, some Windows 10 client nodes might fail with “Access Denied” error. In that case, log into each of the Windows 10 client nodes that fail and enable the Administrator Account. Then rerun Remote Deployment from the master server.

See also. For more information on automated deployment, please refer to the Automated Deployment section in the DPX 4.9.x Reference Guide.

See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the DPX 4.10 Compatibility Matrix.