This article provides information about the Push Deployment Wizard included with Symantec Endpoint Protection.
You can use the Push Deployment Wizard as an alternative to the Client Deployment Wizard to deploy client software by pushing the client software to remote computers and automatically installing it.
You would need Administrator rights / privileges to the Windows domain to which the client computers belong or to the computers themselves, if they are in workgroups.
You can use the Push Deployment Wizard to install clients in a remote location where you have few systems but the bandwidth between the two locations is very low and you are unable to install all the clients at one time.
Comparing the Push Deployment Wizard and the Client Deployment Wizard
You could use the Push Deployment Wizard in the following situations:
For example, a Domain Administrator in charge of thousands of clients in the network, and wants to share the work of deploying the client packages with a back-up administrator, but does not want to share the access to the SEPM console. In that case, simply share the Push Deployment Wizard along with installation packages previously created from the SEPM. This action would help divide the job.
The Push Deployment Wizard is included in the full installation file for 12.1.6 and newer, in the Tools\PushDeploymentWizard\ folder. You can download this file, Symantec_Endpoint_Protection_12.1.6_Full_Installation_language.exe, from FileConnect, where language represents the product's language code.
For versions earlier than 12.1.6, the Push Deployment Wizard for Symantec Endpoint Protection (SEP) 12.1.x was in the Tools and Documents download file.
See Related Articles for information on how to download files from FileConnect.
For this example, you copy the installation package and the Remote Deployment Tool across the network to avoid excessive bandwidth usage.
Client-only patches can be found on the Symantec Support site in the Downloads area. You can also use the client-only installer packages available from FileConnect.
NOTE: Ensure that you are always using the latest version of the tool that is equal to or greater than the version of the client being deployed ensure compatibility.