Endpoint Protection

I'm experiencing such issue that Install Packages schedule doesn't work for all the clients. Some of them get and install the newer client version, but some doesn't. What can influence such a behavior? I dont quite understand when exactly new version installation occurs. Does a computer must be restarted, or just a log off is sufficient? Also Install Packages schedule is not very clear. I can set time and days for instalaltion. But when exactly this schedule starts working on a target computer? If i specify 2 days, what will happen if a computer connects to network on a third day after setting this schedule? This dialog could have a calendar for more strict deploy schedules

I do not know if you've ever used SAV, pushing packages there gave you a nice progressbar that showed that something was happening and how far along it was.

I fully understand that our usage, we have companies with at most 30 users, isn't really what Symantec aims to please when managebility is concerned, but i still think that the old ways with progressbars is easier to view.

Nowdays i end up removing the packages, assigning them to the group again and hold my breath.

Well. After i have tried to upload the very new MR4 MP1a packages, surprisingly almost every client got updated smoothly.

Yes. I remember the deployment tool ov SAV. You can use it with SEP too. But it is actually a real pain to upgrade clients that way. At least going SAV > SEP way it was throwing install window, users had to close applications, etc. These Install packages are more transparent. Our ~200 PCs environment (Xp and Vista) was updated in two days, almost without a problem. Some users had to restart their PCs as Outlook wouldnt open attachments.

I typically see about 10% that don't get the newly assigned package out of each group. I've got to manually push the install to them. Most, however DO get it. I can't figure why some do not, while most do. There's really no differences, and in some cases, the ones that do not are a bit closer and better connections.

Of course, we see some where SMS pushes of updates fail on those computers, too. Sometimes, it's an OS anomaly and just imagine that, issues with Windows OS?

buyt pcAnywhere and use the packager tool that's included, that is, if it's still included. I LOVED that tool! It used to be free with some Symantec products. I still to this day use it to push out things that SMS can't do - reg changes, run batch files, etc. One of the coolest tools ever for getting things done on remote computers.

In our company, I'm trying to upgrade Sep 11 client using Push Deployment Wizard.
It show the process is complete but nothing happens on the remote computers.
First copy the setup.exe package, then install. At the end, show the label "Complete".
The remote computers runs Windows XP Sp3 or Windows Server 2003 R2 Enterprise Sp2.
Any suggestions?

Paolo