Hi,

It can be downloaded from platinum website, but that doesn't help everyone. Here are the release notes.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid_p/2007121216360648

- Jukka

Does anyone know when files will be posted so everyone can have access to them not just to the Platinum website? 

We need access to those files so we can deploy the patch... We don't really want to be going client computer by client compuer applying a patch that could be deployed.

Thanks,

Cisco

ftp://ftp.symantec.com/public/english_us_canada/products/symantec_endpoint_protection/11.0/updates/SEP32_2295To19_clientMSPMSI.exe

ftp://ftp.symantec.com/public/english_us_canada/products/symantec_endpoint_protection/11.0/updates/SEP64_2295To19_clientMSPMSI.exe

Company: Symantec Corporation
File version: 11.0.4010.19
Produce Name: Symantec Endpoint Protection
Product Version: 11.0.4010.19

This updates 11.0.4000 to 4010 (the file name indicates b2295 TO 19).

Thanks for the file links mickrussom but those are the client patches.  We are looking for the Endpoint Protection Manager MR4 MP1 patch so we can deploy the patches without having to install the client patch manually at each workstation.

Sorry about that oversight - I can't find the server-side patches anywhere either. 

HI,

Its only available on platinum website for platinum customers.

Rgrds,

SAM

Will the SEPManager MR4MP1 patch be available thru fileconnect ?

I am sure the client/manager mp1 will be available in the near future.  As we have seen in other releases there is usually a delay before the the software appears on fileconnect.

I know I have posted this here before in other threads. but this just KILLS me about Symantec, and probably others.

Company has huge bugs and problems with software - software we pay for.

company fixes bugs and problems.

Special people willing to pay big bucks get the patches for defective software first, while the rest of us wait because the State of Iowa has decided that taxpayers can't afford to buy premium support, even though the SOFTWARE is the same the platinum folks have.

It's like the rich folks in West Des Moines getting their streets repaired and disaster clean-up FIRST while the poor folks in East Des Moines wait - and wait - while the garbage piles up and the streets rot.

Why? The poor pay taxes too?

In our case, we paied the SAME PRICE to get the software to begin with, we just can't afford, at taxpayer's expense, to have 24/7 pager support for the product. But we DO expect DEFECTS and BUGS to be fixed for us at the same speed and rate that platinum folks get.

So why this discrepency?

Why should we WAIT to have buggy software fixed? Why not simply post it in all places at the same time.

So the car maker should send recall notices and offer to fix the car of the rich folks first, while the folks who bought on credit wait to have thier car recall fixed??

Sorry, this is crap.

We sit and LOSE documents, and have all sorts of problems costing the State big money while the patches we need are out there, it's just we must wait in line?

This isn't technical phone support I'm asking for, I'm asking for the patches and bug fixes that are due ALL of us - all of us equally.

If someone has some knowlege of when the Endpoint Manager MR4 MP1 Patch will be available thru file connect so all of us can downloaded and begin pushing the patches... post it here.

I hope they make it available thru file connect in the next couple days...

Thanks...

The release schedule usually follow the same timeline.  Release to Platinum comes first.  Fileconnect happens within a few days after.  We gold support masses (myself included  :)) should see it by Friday at the latest, would be my guess.

LOL - I'm glad you guys have a sense of humor! ;-)

I downloaded the "patch" and applied it manually to a server for checking out.

Is there a way to "push" this using any of the stock Symantec stuff?

Anyway, like with the old SAV 10 stuff, you could actually run patch files or other MSI files using the push features, you edited a file to trick it, and do the push as if you were pushing SAV.

Anyway to do that here?

Would be nice to be able to push this baby to a couple computers having SEVERE issues.....

Export a package from SEPM, put it in a folder on your server and use the migration and deployment wizard to push out the package.  It's no different from the SAV10 version...except for look and feel.   It works really well, you'll need ports 139 and 445 open on the client firewall to push it out. 

You can also bind a client version to a group and let SEPM upgrade the group automatically (make sure you configure your group restart notification options.   It takes a day or so to propogate.   There is also the Find Unmanaged Computer Wizards that let's you discover managed and unmanaged clients with the ability to push out the new client.

OK, so if I apply this patch to the SEM servers, that's how it builds a package? When I first got MR4 and applied it to SEM and SEP on the SERVERS, I then told it to create packages, whcih I assigned to groups and over a weekend, they were updated.

But that was a full install to both SEM and SEP running on the SEM servers.

You are saying, patch SEP running on the SEM servers, export a package?

Well, I'll give it a shot anyway, I do want to go ahead and upgrade them first...... can't hurt!

There is an advantage to not having access to the patch yet.   Let the platinum customers test the new patch for problems and watch the forum for issues.   I've learned not to jump on MR patches in the past. 

Francisco,

In the past there have not been patches for the Manager like the Client.  The Manager can only be upgraded with the full package when it becomes available.  It is not a simple thing like upgrading the client due largely to the database component.

normally I'd agree with tekkid, however, when you are having the severity and scope of issues WE are having, and the agency administrator gets involved, etc. you do ANYTHING to attempt to make a change, good or bad, you must show you are doing something, making attempts.

Word is crawling.

Opps locking is causing issues, all since SEP was rolled out here!

SEP is involved with all of this, there were NO issues here before SEP. Now there are multiple severe issues, and I' ve documented through exhaustive testing.

So I'm grabbing ANY patch Symantec puts out! Anything, and putting it on.

If I fix one thing and break another, I'd see that as relief.

Found out you can't build a package to assign with just a patch file. You have to have the full install CD or all install files.

Can't build a package from a MSP MSI file.

So for now, this will be a manual install as I can get to them.

You can probably automate the patch-only deployment using PSExec from MS/Sysinternals, but you'll need to figure out the correct command-line switches for the executable to do what you want and be silent.

The patch file as downloaded runs totally in the background, no prompts, totally silent.

Rename file to SETUP.EXE

Place file in otherwise empty folder.

Go to the Symantec Migration and Deployment Wizard.

Choose to Deploy the Client

Choose already existing package.

Navigate to the folder the newly renamed SETUP.EXE is in.

continue on and choose the computers to push it to, or the list of computers, etc.

Deploy.

It copies the file to the client and executes it in the background.

It stops the services, runs the updates, starts the services, done.

In minutes, the new version shows up in the console.

Granted this is NOT automatic while you sleep at night like assigning a package to a group would be, but it is a way to push it silently to computers of your choice if you need to do so.

Works slick, much like the SAV processes did.

That sure sounds too easy.

only 10 steps

I might give it a try.

TEST first, and if it's not totally silent, let folks know it's coming.

I didn't have to click anything on the workstations I pushed to, and so far, no one indicated seeing anything.......

I will test my self first and a few VM's, like always.

I would like to offically profess my undying love for psexec :)

psexec \\machinename -u mydomain\user -p password -c "c:\local\path\to\SEPMR4MP1patch.exe" SEPMR4MP1patch.exe

Haven't tested it, but you get the idea. Check sysinternals website for full syntax options.

-c copies the file to the remote machine before executing

cheers

Z

SEP in my laptop stopped working after upgrading to MR4MP1. After the installation was finished I checked from Client GUI that the version had changed to .4010. Then after reboot, when the teefer driver was probably replaced with the new one, SEPGUI could not be started and all network traffic was blocked and Windows was very slow. I had to set the SEP services as manual and reboot and after that remove SEP with cleanwipe. Now I try to do clean install of MR4MP1. Fingers crossed.

- Jukka

zero I've run some of the remote tools to remove bugs that Symantec has using that tool and that method.

That way I can do it while they work, and don't have to visit or remote in to their computer 100 miles away.

I download the threat removal tool, use psexec to push it to the computer, then run it. I have the tool log to a text file which I can go check later.

In this case, though, I found the migration tool worked fine. but I think psexec would even allow a command-line option if I recall, like a /s to run silent or whatever.