Script to update SEP 12.1 installation packages
Hi,
I wrote a little Powershell script to update existing SEP 12.1 Installation Packages with the latest definitions for all modules.
Instructions:
On the SEPM 12.1 share the following folder for “everyone – read”
Export Packages without ticking the box “Create a single .EXE file for this package”
Ensure that the following .ZIP files exist in the 32Bit and 64Bit package folder:
Download the script and the modify the first lines for your environment
#Needs to be modified for each environment: $SEPM = "SEPM.mycompany.local" $content = "\content$" $x86Setup = "C:\SEP\My Company_Workstations_WIN32BIT\Symantec Endpoint Protection version 12.1.1101.401\" $x64Setup = "C:\SEP\My Company_Workstations_WIN64BIT\Symantec Endpoint Protection version 12.1.1101.401\"
The first two lines are for the SEPM Server name and the share of the content
The last two lines are the folders where your packages are stored. Save the script as .ps1
Now you can run the script and it will update the definition files in your package folders:
Packages are now up to date!
If you want to only update the Virus Definitions or only 32Bit / 64Bit Packages, you can delete the related lines in the "#Execution Sequence:" Part of the script.
Important Note: Do not run the script when liveupdate is installing new definitions on the SEP. This may damage your exported packages.
- Zebbelin
Comments 13 Comments • Jump to latest comment
good
Thanks very Good.
One question I have packages for servers also so shall i add the lines for the server package below the workstations
Good Point. Will add that in the next Version of the Script!
In the meantime you can change the "$x86Setup" and "$x64Setup" variable to the path of your server package and remove in the "Execution Sequence" part the definitions you don´t need (e.g. "NetworkThreat")
Nicely done.
Some features for v0.2 or beyond (in no particular order)
Keep up the good work.
Thanks Ian.
The IF EXIST is a very good tip
Unfortunately I don´t have a SEPM 11 anymore. If I find the time I´ll set one up and test the script there with your ContentInfo File.
Not sure what you mean with making the architecture a variable. I´ve stored the AMD64 and x86 setup packages on a share and update them on a regularly basis. Therefore I always update both architectures.
Currently, you have two execution blocks starting with the comments '#Copy x64 Defs' and '#Copy x86 Defs'
Both blocks do exactly the same thing, just the $osArch is different
I'm saying that it should be possible to create one block that performs the copy function with lines similar to
I believe that this would help remove duplicate code; i.e. move from two copy code blocks down to 1 copy block.
Hey, right now your script works & that's great. Keep is like that for now.
My suggestions are for long term maintainability & reducing COPY/PASTE editing later on.
Good Artical
Very helpfull artical.
good work! Keep it up for later releases.
hi,
Good Script...............
Thanks....
Don't forget to mark your thread as 'SOLVED' with the answer that best helped you
Looking the script for 11.x. Any help on same.
Nice Shared. :)
Nice Script.
Thanks.
Zebbelin,
Great script buddy! Just thought I'd let you know that with the release of 12.1.2 there are 2 additional definition zipfiles that are included in exported packages now. I talked to support and obtained the monikers that relate to them. They are:
ApPortalDefs.zip - {50B092DE-40D5-4724-971B-D3D90E9EE987}
EFAVTDefs.zip - {E8827B4A-4F58-4dea-8C93-07B32A63D1C5}
I had to add these to the Variables section and incorporate them into the "Copy x64 Defs" and "Copy x86 Defs" sections. These 2 files are bit independant so both will be used in both package types.
On another note, upon obtaining this moniker info from support, they made it extremely clear that they do not support this method of updating exported packages. If there are any problems seen from this method they prefer that the package be manually exported.
This is a great script and has helped introduce me to PowerShell.
Thanks again!
Would you like to reply?
Login or Register to post your comment.