SEPM console lists all available SEP client packages ready for deployment. But, at times you may have requirement for older or newer version of client package.
In my case i had a situation, I have SEPM 14 but some particular thin client machines are not having enough resources for SEP 14 client. Thus, I need to get SEP 12 client package for deployment on thin clients.
Whole procedure is break down in steps,
STEP 1. Keep license key ready and go to https://symantec.flexnetoperations.com/control/symc/registeranonymouslicensetoken . Incase desired version of SEPM is not available call Symantec support. Symantec support will share new license key.
STEP 2. Once you get desired SEP version listed in portal like 'Symantec Endpoint Protection 12.1' click and proceed to product version in desired language.
STEP 3. Select 3rd option and download .exe file.
STEP 4. It recommended to execute downlaoded .exe file, which will extract all files to folder. ( client package can also be imported using .exe but, this is not recommended approach)
STEP 5. Goto extracted folder, Symantec_Endpoint_Protection_x.x-x_SEPM_EN → Packages. verify it is having .info files.
STEP 6. Now, to import goto SEPM console → Admin (Tab) → Installed Packages (Tab) → Add a client Installation Package... → Provide name of package and browse the .info file in STEP 5.
STEP 7. Once successfully imported you can export client package or deploy to SEPM group.
But is Symantec really joking? This is Enterprsie procedure?
Apart from this, the new SEP 14 exe files do not ask for the target directory. Therefore, this procedure is no longer valid