The clients will download the package from the remote site at their next heartbeat, unless an Upgrade Schedule has been set in which case they will receive their schedule and download the package at that time. Enter the URL and path to the SETUP.EXE for the installation package. In the Add Client install package window, select the option Download the client package from the following url( http or https)ħ. Click Add Client install package, under Tasks.Ħ. Select the group in which the clients in remote location are located.ĥ. Log into the Symantec Endpoint Protection Manager.ģ. Then, copy the SETUP.EXE to the folder or Virtual Directory on the web server where it will be hosted.ġ. exe:Ĭreating new Client Installation packages in the Symantec Endpoint Protection Manager Console Refer to the following KB Article to create a client installation packager as a single. Continue the installation process and restart the Symantec Endpoint Protection Manager in Step 5. If you do it in Step 1, it may cause an issue with starting the SEP services. Next verify you can connect to the web sever/virtual directory from any client by browsing to the URL of the folder or virtual directory from a client's web browser.Ģ. After installing the software, you are prompted to restart the Symantec Endpoint Protection Manager. However, if using IIS, you should also create a Virtual Directory for the client package and set only Read and Browse permission. IIS is the most common, but SEP will work with any web server so long as it is configured appropriately. Using this option in SEPM requires the use of a 3rd party web server. Use the following procedure to allow clients to run installation packages from a different source than the SEPM: Copy the Symantec End Point protection to your computer it usually packed in zip file DATA SHEET SMANTEC ENDPOINT PROTECTION 14 04 Symantecs single agent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |