Endpoint Protection

A couple of months upgraded our installation to SEP V11 MR4 from Symantec Corporate Edition V9 and deployed the MR4 clients about the network. I have installed V11 MR4 & SEPM V11 MR4 in the SBS 2003 Server. All worked fine.

Then on reveiwing the download directory I discovered that MR4 MP1 had been released.

So being new to SEPM I was having a lok around, and figured out how to create an install package for the updated MP1. I was doing this on my work station and I have since discovered that the new install package is created in the Localsettings/temp directory. As I intend to try and keep all my production work on the Server (SBS 2003), I thought - no problem I'll recreated the install package on the server.... however I have now hit the problem that SEPM wont let me either replace the new install package (with one generated on the server), or let me delete it to start again. On Delete attempt  I get the messsage:
"Symantec Endpoint Protection Version 11.0.4014 for WIN32BIT is the latest package. You cannot delete it."

So how do I get round this one please?

Paul

Hi,

I did not exactly understand what you are doing but there is no reason to delete a package in the console.
Select the package you want install in your machines, export it and deploy/run it in your machines. That's all.
If you want automatically migrate your existing clients from 11.0.4000 to 11.0.4014 just apply the migration procedure:

service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009021008321148

Regards,

The package you are trying to delete can be deleted only if a package for a newer version for the same build {32 bit or 64 bit} exists in Admin->Install Packages tab.

You can follow the document below for exporting installation packages from SEPM:


Creating custom Client Installation packages in the Symantec Endpoint Protection Manager Console

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/c741ec26fa674b1e8825738a0076abf3?OpenDocument

You can deploy those packages with the migration deployment wizard:

How to Deploy Symantec Endpoint Protection to your client computers using the Migration and Deployment Wizard.

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/476542a2b4508f3d8825739300615c98?OpenDocument

Hope this helps.

Aniket

So we upgraded to MR4MP1 yesterday. Selected a group with only two computers to test the package install and it did/has not worked yet. First we tried to do it between a particular time "window" at 0 day and then at 1 day, no luck. Then tried again leaving it sit overnight, but still nothing. Then again this morning, and now even without a "update schedule" checked. So how do I get the install to go out? The MR3 version had a "within" xx hours setting that worked GREAT. Why make the change? And now that you have, how do I use it? This is a VERY frustrating product. Everytime Symantec attempts to fix something they break something else. I am getting tired of this nonsense.

One of the computers finally updated the client, still waiting for the other. So does this mean the "scheduling" piece does not work? And if not, when will it? I would like to control, at least to some extent, when the update might install the new client on my computers. It would be nice if this was controlled and happening overnight. And another thing for the SEP wish list: I wish we had MORE control on the definition and the client updates. It would be nice to have an immediate update if I select it, either globaly, on a group, or on a cleint. It seems SEP is not manager friendly and tries to circumvent what I WANT TO DO. It should allow for some intervention from my end. Just a thought.

You can update a client, group or global on demand if you want to.

From either Monitors->Reports (run a report that grabs the clients you want)-> at the top select 'update content' select either highlight or All, then run it

OR

From Clients -> right click on a client/group/My Company, select 'update content'


Either way you can then check the status from Monitors->Command Status and it will give you progress.

wow, nice server issues going on today.

In The Past...
It doesn't update immediately when we select update content. It takes its good ol' sweet time. When I want to update a client or definition NOW, I want it to do it right THEN and THERE when I tell it to. But it doesn't do that. At least not in our environment. My other computer has updated...finally. So now ... Do I schedule for my department or unschedule? I want it to update tonight between 00:30 and 04:00. And what does "0 days" mean? It would tend to mean don't do it in any days. and then "1 days" would do it in 1 day. Symantec...You are making this stuff too complicated for my little brain.

Okay, so I guess I will set it for the time desired and then in 1 days because doing it in 0 days makes me think it won't do it because 0 tends to mean don't do it in any days and I have passed that time for today...so confusing.

Here's the absolute easiest way to upgrade clients with a new version NOW:

1)  Assign the package to the group that you want to update (Look in the Clients section, under the Install Packages tab).  Do not set a schedule and make certain that you are assigning the correct version (64-bit for X64 clients and 32-bit for X86 clients).

2)  Go to the Admin section>Servers>Site, and click on Download LiveUpdate Content.  This will kick off a LiveUpdate check on the SEPM server, which will pick up on the new client install package.  Your clients will start pulling and installing on their next check-in.

Two quick caveats:

1)  I've always found the scheduling feature to be a bit flakey, so avoid using it personally.  Never quite seems to do what I was expecting.

2)  If you find that a client here and there doesn't update with the rest, to my experience, chances are that the client(s) already has an installer change scheduled for the next reboot.  This will cause the SEP installer to quit.  In these cases, I just remote reboot the client and then the new package will install just fine.  Changes waiting on a reboot are found in the registry at HKLM_SYSTEM\CurrentControlSet\Control\Session Manager.  Look for a key starting with Pending.

Doing an unscheduled install is a bit scary. I would like to set a timeframe for the upgrade so my users computers are not adversely affected. I guess I don't understand how something that seems so simple does not seem to work very well. I was able to get clients in my department updated during the selected windows last night so I think I will continue down that road. If it is an unstable process then I hope Symantec will fix it so it works as intended.