Even though Symantec does not support a command line install of the Symantec Endpoint Protection 12.1 client, using the default Symantec installation files, there is a way around that limitation if you want to deploy the SEP 12.1.1101.401 (ru1 mp1) client with KACE 1000. I did this with my KACE 1000 and it worked very well.
There is one limitation: you can use KACE 1000 to deploy either a 32-bit OR a 64-bit installation package at any one time, but cannot deploy both concurrently. This limitation is due to limitations with both the Symantec product and the Dell KACE product. Symantec's limitation is that a Windows 32-bit SEP install file cannot be installed on a Windows 64-bit OS. The Windows 64-bit OS must have a Windows 64-bit SEP install file. Dell KACE’s limitation is that the software inventory is unable to distinguish between a 32-bit and a 64-bit version of the exact same software title and version. Even so, there is a way around the KACE limitation that I will explain in the last step.
Here is the process for a Windows OS:
- From the Symantec Endpoint Protection Manager (SEPM), use the Client Deployment Wizard to create an installation package that you save to a network location that can be accessed by the KACE 1000. Create that package as a single ".exe" file. For instructions how to do that, consult the Symantec Administrator Manual or see my posted Deployment Tip "How to create an .exe file in the Symantec Endpoint Protection Manager for use for KACE 1000 Deployment".
- In my environment, I created an install package in which the “client install settings” was set to “Show Progress Bar”, because I wanted the Symantec installation routine to be visible at its beginning on my KACE client computers while it was installing. If you want a totally silent install for KACE deployment, you need to define that during the process of creating this install file in the SEPM. That is done in “Admin/Install Packages/Client Install Settings” in the SEPM, prior to creating your .exe installation package in the SEPM Client Deployment Wizard.
- Be aware the Symantec Client Deployment Wizard creates one 32-bit install file and
one 64-bit install file. Test the file you create here by installing it manually on a client computer to make sure your “silent” install, if you chose that, works to be silent. Be aware that the size of each .exe file will be approximately 45MB.
- c. Once this file works the way you want when manually run, it is very simple to have KACE deploy it. (Okay… it is “simple” if you know how to set up managed installations J, so I have for your benefit detailed instructions below and they should be followed in the order given for best results.)
2. If you do not already have this version of Symantec client (12.1.1101.401) in the KACE software inventory, choose the 32-bit or 64-bit install file and manually install it on a client computer, by simply clicking on the setup.exe file so that it installs on the computer. After that completes logon to the KACE 1000 admin console and run an inventory on that client computer. This puts that program into the KACE software inventory.
3. Go to "Distribution/Managed Installations". From "Choose Action" click the drop down arrow select "Add New Item". Check the box "Also show software without an Associated File", type "Symantec Endpoint Protection" in the box next to "Filter". Click the drop down arrow to the right of "Software" and choose "Symantec Endpoint Protection (12.1.1101.401). Click “Save” at the bottom of the page. We will return to this Managed installation setup later.
4. Go to “Inventory/Software”. In the search box type “Symantec Endpoint Protection” then click “Search”. Click on the Symantec Endpoint Protection item found, after confirming the version column shows “12.1.1101.401”. In the address bar of your browser is the path to this software item in KACE. The path will look something like : http://kbox1000.yourcompany.com/adminui/software.php?ID=9871. The important thing to note is the number at the end of this line. In the case above “9871” is going to be the name of the folder created on the KACE client when the managed install is pushed out to that client. Write down the number you see in your specific path. You will need that number in defining the “Run Parameters” path, later in step 7 below.
5. Open the Managed installation you created in step 3. Click the “Browse” button next to “Upload & Associate New File”. Browse to either the 32-bit or 64-bit install file you created in step 1.
6. For “Installation Command” choose “Configure Manually”.
7. For “Run Parameters” type in the path that will exist on the client computer after KACE pushes this install file out to it. For Windows 7 type this, including the quotation marks: “C:\Programdata\Dell\KACE\downloads\9871\setup.exe”. Change the 9871 to the number you wrote down at the end of step 4. So, for example if your number is 376, the whole path you will type, including quotation marks will be “C:\Programdata\Dell\KACE\downloads\376\setup.exe”. For Windows XP deployment the path will be “C:\Documents and Settings\all users\dell\kace\downloads\376\setup.exe”. Disclaimer: these paths work only if you have not changed the default path on your client computers that a Managed Installation deploys to.
8. Check the box “Don’t Prepend msiexec.exe”
9. Choose a managed action that fits your needs. I used “Execute while user logged on”, and did not test any other Managed Action.
10. Make a choice in “Limit Deployment to Labels” that fits your needs. I left the defaults for “Deploy Order” (10), “Max Attempts” (3), and “Deployment Window” “0” and “24”. I did not test any other choices.
11. If needed, choose and define Snooze, Custom Pre-Install Message and Custom Post-Install Message. I used a Post-Install User Message and did not test any other type.
12. Click “Save”. You will be prompted to allow the upload of the file to the KBOX. Be sure to allow that. Wait until the file is uploaded.
13. It will deploy according to the “Managed Action” selection.
14. If you need a 32-bit and a 64-bit installation of the SEP 12.1.1101.401 client you can deploy them one at a time. Go back to your Managed Installation and upload the 32-bit install file to the KBOX according to the direction in step 5 above. Also change the Deployment to machines section to be 32-bit OS clients. Click “Save”. That will run according to the parameters chosen in “Managed Action”. After that deploys, and now you find you need a 64-bit installation of the SEP client 12.1.1101.401, go back to your Managed installation and upload the 64-bit install file, and also change the Deployment to Machines section to be 64-bit clients, and click “Save”. That also will deploy according to the parameter chosen in “Managed Action”.