Endpoint Protection

SEP RU6

Before sending this to a service request I thought I’d check with this group to see if anyone else is seeing the following behavior.  I’ve tried this on two different computers using both IE8 and Firefox 3.6.x.  This seems to be only impacting packages exported using the web bases SEPM console.  The java console gives me different packages. 

I recently updated my RU5 servers to RU6.  The installations went through without a hiccup and everything seems to be working except this one thing.

Using the SEPM Web based console I go to the Admin\Install Packages and export a selected package.  In every case I get a file that is 119.175KB in size.  I first noticed this when trying to export an unmanaged client so I tried exporting a managed client.  The results were the same.  Comparing CRC-32, MD5 and SHA1 hashes of the various files they all come up the same which tells me I am getting the same set of files whether I try exporting a RU5 or RU6 client and whether it is a 32 or a 64 bit package.

Something has to be off somewhere if this is happening.

I just tested this in my environment. With the exception of the Mac client, all packages are exactly the same size when exporting from the Web Console..

I  recommend opening a case with support ASAP.

https://mysupport.symantec.com/

http://www.symantec.com/business/support/contact_techsupp_static.jsp

From Symantec Support:

"Further internal testing and investigations have confirmed that using the webpage SEPM console connection (not the locally installed Java Web console) will generate only a 32-Bit default installation package, and that this is a recently discovered defect and is currently under investigation. The correction for this issue will be released as soon as possible with the following next version of SEP. Symantec recommends utilizing a locally installed interface to create custom installation packages (i.e., the SEPM console may be used while working physically at the machine hosting the SEPM, or a locally installed Java Web console may be used on any other machine)."

Apparently this isn't a quick fix since we're going to have to wait for the next version.  Seems like they could streamline this update process and just give us a patch.

https://www-secure.symantec.com/connect/forums/sepm-killing-us

I'd not get too excited to create packages and schedule automatic deployment yet............

Could you please PM  your case number. I would like to stay on top of this.

Thanks,
Thomas

Symantec Case 412-211-023