Symantec Endpoint Protection 11.0 Maintenance Release 2

Paul Murgatroyd's picture
Summary
Symantec Endpoint Protection 11.0 combines Symantec AntiVirus with advanced threat prevention to deliver unmatched defense against malware for laptops, desktops, and servers. It seamlessly integrates essential security technologies in a single agent and management console, increases protection, and helps lower total cost of ownership. The upcoming maintenance release (MR2) of Symantec Endpoint Protection builds upon the previous maintenance release (MR1) by further solidifying Symantec's technical and market share dominance in the endpoint security space.
 
Customers who are currently running previous versions of Symantec Endpoint Protection should take immediate advantage of the improvements that SEP 11.0 MR2 offers. Medium to Large customers who are still running Symantec AntiVirus or Symantec Sygate Enterprise Protection should strongly consider migrating to Symantec Endpoint Protection, as the SEP 11.0 MR2 release is a more stable and efficient product (than SEP RTM release) that provides added protection and management benefits (than SAV and SSEP).
 
Availability
 
We currently expect to deliver English MR2 RTM in early April 2008
 
 
Please note, the above date refers to the Symantec internal release, external electronic availability is generally a couple of business days after this date.
 
Symantec Endpoint Protection 11.0 MR2 includes the following key improvements
 
Performance
 
Dramatic reductions in the level of network traffic between Symantec Endpoint Protection Manager (SEPM) and the SEP client and the amount of disk space consumed on SEPM and SEP client by addressing several issues, including the following:
 
• Fixed port leaks on SEPM server
• Optimized disk space usage of embedded database
• Fixed excessive disk space us by antivirus logs on SEPM
• Reduced CPU utilization of SEPM when building definitions
• Fixed excessive disk space use by LiveUpdate on SEP client
• Reduced length of accelerated heartbeat on SEP client to optimize communication between SEPM and SEP client
 
Functionality/Usability
 
Improved the user experience by ensuring that all features function as expected/documented and reduced the amount of time for users to perform tasks by addressing several issues, including the following:
 
• Resolved inconsistent scanning of files on SEP client
• Improvements to SEPM console home page include all charts displayed properly, all agents and agent status appear correctly
• Fixed site and agent replication issues
• Fixed ClientRemote Utility
• Optimized creation of group folders so that they can be created in a timely manner
• Optimized performance of Active Directory synchronization to avoid database deadlocks
• Minimized boot time on SEP client by optimizing Symantec processes during startup
 
 
Stability
 
Reduced the amount of crashes and errors that appear on the screen, which includes the following:
 
• Addressed issues that triggered error messages on SEPM and SEP client
• Addressed issues that caused blue screens and other crashes on SEPM and SEP client
 
 
Communication/Connectivity
 
Improved communication between SEPM and SEP client, which includes the following:
 
• Addressed issues with SEP client communicating with SEPM behind a firewall with NAT or after changing the remote console port
• Addressed issue when SNAC Enforcer fails after adding too many MAC addresses
• Addressed issue with Agent SNAC service blocking Checkpoint VPN client connections



Message Edited by Paul Murgatroyd on 03-05-2008 06:38 PM

Message Edited by Paul Murgatroyd on 03-22-2008 12:40 AM

susanthas-123's picture

Hi Paul,
 
Nice to hear about the memory utliazation has been reduced for SEPM in MR2. Look forward to test that out quickly. So is this means we can safley advise customers to run their SEPM in VMWARE? I prefer to do server consolidation and help them to reduce the hardware cost as well. Is Symantec ofically support for virtualized SEPM?
 
Regards,
susantha
newpylong's picture

Upgrading from the Original release to MR-1 was a disaster. As I am sure everyone is going to want or need MR-2, is it going to be possibly to safetly do this without completely uninstalling the SEP manager and client's and installing MR-1 like we had to before?
Matt Pierce's picture

If an RTM or MR1 client is upgraded to MR2, will the new live update enhancments clean up the excessive disk space useage?   Also, does MR2 fix the inline client upgrade process?  My RTM clients never updated to MR2 despite the proper group client configuration.  Support said this is a know issue and would be fixed soon.

smbtech's picture

Does MR2 address the issue with SEP breaking Outlook attachments?
Paul Murgatroyd's picture

yes, thats fixed.  Its also fixed in the outlook client only patch, if you haven't already downloaded it?
 
 
 

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

smbtech's picture

I have used the Outlook patch, but have also run into situations where that hasn't resolved the issue and I had to completely uninstall the Outlook scanning feature. I have a few clients that I have upgraded to SEP because of the issues I've had at other clients, as well as clients on the initial release that I have not upgraded to MR1 because the organization is so large that it would take an unacceptable amount of time to touch all the client pcs in the network in order to resolve the Outlook attachment issue.
mansley's picture

Are the high CPU usage issues addressed in this release?  We have uninstalled everything but the AV portion from all of our PCs due to this.
 
What about issues with clients not logging into the server.  Out of our 300+ clients maybe 50 have green dots on the server view.
Thorsteenster's picture

We haven't gone to MR1 yet, when MR2 is available can we go right to it or do we have to go MR1 then MR2?
Hurricane Andrew's picture

Will the SEP Manager now support Server 2008?  The beta releases I tested still squaked when trying to install the management piece on a Server 2008 box, though the client was fine.

----
"Hurricane" Andrew
Milford, Delaware

Screen_Name's picture

Is there any fix on the bad virus def problem creating gb's of .tmps in the VirusDefs folder until manually cought by the user to correct the issue?

BigNose's picture

I have tried to apply MR1 to client by applying package to the group in the SEPM. Client who has same network segment with SEPM get message and succesfully upgrade. Tho other clients on different segment get message and SEP not upgrade ( I was posted this issue). Although, I could deploy MR1 using push deployment (vpremote).
 
Is the MR2 resolve this issue? Thanks.
drcoelho's picture

We have been running SEPM on a VMWARE (esx 3.5) guest os very successfully.
froby's picture

How/where do you apply these patches?
 
I tried all 4 of the files at the link and none of them would run on the server or on client machines.
 
The response was that there was nothing found to update.
 
Brian
Los Angeles
dfhbac0's picture

Does this fix the problem of Semsvc.exe 'looping' and taking up 90% + cpu about once per week and requiring the Server to be re-booted?
GrahamA's picture

MR2 will provide Windows 2008 support for the SEP client only. A future maintenance release will most likely provide Windows 2008 support for the SEPM also.

GrahamA
Product Management, Symantec Security Solutions

Hurricane Andrew's picture

GrahamA,

Thanks for the reply!  I'm anxious to be able to upgrade our test network!


----
"Hurricane" Andrew
Milford, Delaware

Ben Noach's picture

Paul,
    I am suffering here waiting to get this fixed. My drives are filling up systems crashing. Some will not update at all. I dumped Trend Micro for this product. I am thinking of going back. I may be forced too.

The 21st is a long way off down a ling dark tunnel!!

-John Hill

The_Stranger's picture

In the files section there was a release on the 4th - the MP1 release.  What is this? 
pbogu's picture

@The_Stranger

It's a patch for MR1 SEPM

Symantec Endpoint Protection Manager fixes

Agents do not appear in Symantec Endpoint Protection Manager
Fix ID: 1178101
Symptom: Agents do not show up correctly in Symantec Endpoint Protection Manager. If Symantec Endpoint Protection Manager is restarted, agents will show up correctly. However, after Active Directory synchronizes with Symantec Endpoint Protection Manager, the agents will display offline again. This occurs every 24 hours.
Solution: Modified the order of how objects are processed so that agents appear correctly as "online" in Symantec Endpoint Protection Manager.

Port leak on Symantec Endpoint Protection Manager
Fix ID: 1183253
Symptom: Symantec Endpoint Protection Manager becomes deaf as clients download updates, CLOSE_WAIT sockets are not closed, and the server is out of ports and becomes deaf to the console. As this continues, at some point you can no longer remote desktop to the server. When the server is full, 3500 sockets are in CLOSE_WAIT, almost all the rest are in TIME_WAIT, and there are 15 or so talking to the database and clients. As time passes, the CLOSE_WAIT sockets slowly rise.
Solution: Symantec Endpoint Protection Manager process no longer has CLOSE_WAIT states after clients download updates, preventing the leaked ports from monopolizing all the server's ports.

Symantec Endpoint Protection Manager Management Console Home Page: Virus Definitions Bar chart and IPS Signatures chart do not display
Fix ID: 1190971
Symptom: Charts on the Home Page appear blank.
Solution: Modified code to ensure that chart information is displayed as expected on the Home Page.

Group Folders are not created or take too long to create
Fix ID: 1191851, 1201662
Symptom: When you have a large number of existing groups, creating new groups fails as SemSvc.exe runs a check on all existing folders (one folder for each group). After over an hour, the new group is not created. When viewing created groups, some contain 2 files, while others contain over 20 files. In some instances, creating a group would take over an hour.
Solution: Added a condition that optimizes creation of groups, so that groups and group folders are created and created in a timely manner.

Import of policy from one Symantec Endpoint Protection Manager domain to another fails
Fix ID: 1183186
Symptom: After clicking "Import" to import a policy from one Symantec Endpoint Protection Manager domain to another, the action fails with no error message. This particularly happens when attempting to import firewall policies that use rules which apply to host groups that are not present in the new domain, or when importing policies from a migrated Symantec AntiVirus server group into a new domain.
Solution: Import action failed because new domain did not contain the same host group names. This issue is resolved by implementing the following: create host group if it doesn't exist in new domain; adding error handling messages if an error does occur, and merging host groups if user selects to overwrite existing policy for already existing groups.

The_Stranger's picture

I did read and search - but thanks for the response.
Paul Murgatroyd's picture

There is a fix in MR2 for tmp definition files.  There are numerous fixes in for client and SEPM performance, hopefully something here will help, if not please log a support call
 
On the drive filling up side, are you using the scm.lucontentcleanup.threshold variable in your conf.properties file?
 

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

reza akhlaghy's picture

Paul,
 
Did MR2 fix device control bug which was set to "Most Restrictive" instead of "Least Restrictive"?
You know currently you cannot block USB because it will block all mouse/printer/... while you
added them "to do not block" list
Bored Silly's picture

To deal with the Temp folder creation problem, we've been running a  script created by my coworker on a Fedora 8 Linux box (since deleting folders from a Windows box was slow).  If you have a spare box to install Fedora on, you can use the following script.  I created a folder inside the root profile folder (since the script will have your Windows domain account and password in it) then used the script (shown below the line) along with a file called serverlist containing the list of PCs and servers names.  I created mine by running a "net view >serverlist" at a DOS prompt on my Windows box.  If the PC is offline, it will take a minute or so to timeout and continue on but at least you don't have to babysit it.  When it's done, repeat until MR2 is released.

Note: this is for Windows XP.  Windows Vista has a different path for the virus defs which is located at: C:\ProgramData\Symantec\Definitions\VirusDefs.  We don't use Vista but if you do, you'll need to replace the lines containing

/mnt/folder-name-containing-the-script/Program\ Files/Common\ Files/Symantec\ Shared/VirusDefs/tmp*.tmp

with the following path

/mnt/folder-name-containing-the-script/ProgramData/Symantec/Definitions/VirusDefs/tmp*.tmp


Good luck


________________________________________

#!/bin/bash

inputfile=serverlist
totalnum=$(cat $inputfile | wc -l)

let "current = 0"
cat $inputfile | while read servername
do
let "current = current + 1"
echo Processing $servername \($current of $totalnum\)
mount -t cifs -o user=domain-name/username,pass=password,uid=503,gid=503 //${servername}/C$ /mnt

du -m /mnt/folder-name-containing-the-script/Program\ Files/Common\ Files/Symantec\ Shared/VirusDefs/tmp*.tmp
rm -r /mnt/folder-name-containing-the-script/Program\ Files/Common\ Files/Symantec\ Shared/VirusDefs/tmp*.tmp
umount /mnt
done


Bumiputera's picture

I got same problem like BigNose, the different is i'm applying package to the group ini SEPM with same network segment with SEPM and the upgrade failed. Does anybody have the answer ?
Philonius's picture

I have run the Outlook patch and while it fixed the ability to disable Outlook Attachment scanning (and still open your attachments), it did not fix the Outlook Attachment Scanning itself based on my own testing. If you use the arrow keys to move from one email to the next, then try to open attachment, it still causes Outlook to crash. Since I don't want a bunch of customers with RED-X Shields in their systems trays, please explain to me if MR2 actually fixes the Outlook Attachment Scanning, or just fixes the ability to disable it. I have 7 businesses waiting to be upgraded, and I will not be doing it if you folks don't have this fixed. Without the patch, we could disable the Outlook support, but customer could not open any attachments. With the patch we can disable it, but still cannot arrow through emails and open attachments with it enabled. Anxiously awaiting verification...
eoc's picture

Can you tell me if a fix for the "application failed to intiliaze" problem is include in MR2?
tekwerker's picture

Does this MR fix the issue with Symantec Mail Security for Microsoft Exchange 6.0?
Heath Higgins's picture

@tekwerker - could you tell what issue you are referring to?
Marco Sues's picture

"MR2 will provide Windows 2008 support for the SEP client only. A future maintenance release will most likely provide Windows 2008 support for the SEPM also."

This means SEP will not support a Windows Server 2008 (only) Domain without a Server running on 2003 for deployment ?

I think that this future maintenance realse will not be in year 2008...

Thanks..

Paul Murgatroyd's picture

Marco,
 
I think you might be surprised :-)
 
I'd be interested to know how many customers want to migrate everything to Windows Server 2008 now, especially those using web based applications.

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

Hurricane Andrew's picture

The only thing stopping the bank I work for from a significant migration is licensing.  We have a boatload of Server 2K3 licenses and CAL's, but did not acquire them through software assurance so in effect we'd have to "duplicate"  hundreds of CAL's to make the move.  If we had purchased our previous CAL's through software assurance, we'd already be deploying Server 2008.
 
For my own small business, I'm already running Server 2008, and have been for nearly 9 months.  This weekend will be the upgrade from the RC to final code.  Wish me luck :smileysurprised:



Message Edited by Hurricane Andrew on 03-19-2008 06:47 AM

----
"Hurricane" Andrew
Milford, Delaware

Magnus_Sweden's picture

we are about to migrate to SEP from 10.x and will at the same virtualize our management server, and I see no reason to be still running on 2003 (other then that it's not currently supported) so I want to be able to run SEPM under 2008...
 
 
AV Specialist's picture

Hello
 
I have heard from a symantec employee that the MR2 (english) will be available at the beginning of april and not at 21/03/2008
 
Is that right?
 
Greetz
AV Specialist
PhilC's picture

Hi,
I have just heard the same, can we get confirmation??
thanks,
Phil.
SKlassen's picture

We'll be migrating all of our servers to Windows 2008 over the next few months.  Just waiting for SEP MR2 to be released to start the ball rolling.
Fabian-H's picture

I got the information that the MR2 will be realeased at Wednesday, 02. April
SKlassen's picture

I also received a message from a Symantec support engineer I've been working with, for a support case, that MR2 has been pushed back to the beginning of April.
PinnGeek's picture

Greetings,
This seems to be the correct location to ask this, but have sympathy for a first time poster.
I’m experiencing network communication loss exactly as described in Symantec Document ID: 2007102613484948.

Their solution is to install MR1. When I finally jump through the hoops to get to the download file location, the files I see are for version 11.0.1   My version is listed under Help-About is 11.0.780.1109

Does this mean I already have MR1 installed? Is there any way to find out?If not, should I wait for the mentioned April 2 delivery of MR2?

And last, could it be I am in fact going to the wrong location for the Patch? If someone would be so kind as to paste the path for the English version, at least I could compare where I am looking. Here is the current file I am finding that seems to be what I need except for the version:  Symantec_Endpoint_Protection_11.0.1006_MP1_AllWin_EN_SEPM_PATCH.zip

So 3 questions in there, Thanks

Sandeep Cheema's picture

   11.0.780.1109 is the original RTM version , It means that you do not have the MR1 installed.
 
   11.0.10000 is the MR1.
 
  11.0.1006 is the MR1 MP1
 
Symantec_Endpoint_Protection_11.0.1006_MP1_AllWin_EN_SEPM_PATCH.zip, A maintanance patch meant to be appled only on versions that have the MR1 installed.
 
 
help1234's picture

MR2 is supposed to be released today correct? For the english version...I cannot find it on fileconnet...
Technologist's picture

Logged into file connect today and it is still MR1....


Symantec Endpoint Protection 11.0 - International English  11.0.1375 MP1   International English


So is MR2 available today or not?

--t




Message Edited by Technologist on 03-21-2008 09:17 AM

Clifton Hastings's picture

I'm running the MR2 beta on a Windows Server 2008 x64 box that is my primary file server and it is having serious performance issues when File System Auto-Protect is enabled.  The moment I disable it everything runs great.  So I would be cautious about running out and installing it on all of your Server 2008 boxes for now, especially ones you are using for file sharing.
Bsalyer's picture

I need to get the XP clients running smoothly before I install the client on a server. I'm looking forward to the MR2, any word on if it'll be out today?
Bored Silly's picture

I asked our BCAM this and he verified that all MR releases are cumulative thus you don't need to install previous MR versions (in this case MR1) prior to installing MR2.

SKlassen's picture

The word from several support engineers is that the release of MR2 has been pushed back until early April. 
 
Another thing to keep in mind is that when Symantec gives a release date, a given item may take a couple of days to show up on FileConnect.  Example:  If Symantec had been able to release MR2 today, as was the originally announced date, chances are it wouldn't have been available on FileConnect until Monday.  Just something to work into the planning of maintenance time windows around Symantec releases. 
Technologist's picture

Scott Klassen wrote:

"Another thing to keep in mind is that when Symantec gives a release date, a given item may take a couple of days to show up on FileConnect.  Example:  If Symantec had been able to release MR2 today, as was the originally announced date, chances are it wouldn't have been available on FileConnect until Monday.  Just something to work into the planning of maintenance time windows around Symantec releases. "

Do you realize how lame that potentially sounds? My translation:

"When Symantec gives a release date do not expect it to be available that day because they never have the file ready for their customers to download. Instead, keep checking the forums and File Connect for when it might eventually show up. Sometimes this may take days (or even over a week - yes this has happened to me). So don't plan on upgrading to the latest version on release day because the upgrade file will not be there."

lol.

--t

jonsmi's picture

The first message in this thread states: 3/21/2008 Available for Download. And this is today. If they couldn't make it, they should have known it yesterday and posted information on the delay.
SKlassen's picture

I agree with both of you. 
 
In both cases I chalk it up to red tape and bureaucracy.  Symantec is a massive company with many different departments, each of which has it's own hierarchy and approval schemes.  I've seen several different posts by Symantec employees that give a little insight into how this works.  If for example, there was new information to be posted in the KB.  The engineer who noticed this would have to write up a draft of the new info, get it approved by his/her supervisor(s), forward it to Q & A for testing and validation, then it goes to the KB people who review and possibly edit, finally going to the web site people for posting.  It can be a long drawn out process, especially if changes need to be made.  Same thing with something posted to FileConnect, it has to be approved and checked by multiple people in a long chain.  The point of this sort of process is to catch mistakes before they can affect the customers (us). 
 
I can't say I'm happy with the way it works either, but it's the way things are.  Most large enterprises operate in exactly the same way. 
 
I planned on beginning my rollout of Server 2008 this weekend, which I now have to delay until MR2 is out.  I sort of wish that they hadn't posted the release date to begin with, keeping it a bit more vague, such as late Q1.  It was silly to give a specific date while the MR was still in beta and not finished with Q & A.  I'd have to assume that the delay is due to some bug or problem that was found late in the beta cycle.  I'd rather wait a bit longer than get a patch that will make things worse and not better.  That being said, there should have been an official sticky post about the delay.
 
Then again, there's always the chance that the support engineer who told me, and the ones who told others here, about the delay were misinformed and it might still be set for RTW today.  It's just a little past 8:30AM at Symantec HQ, so they still have about 15 hours and 23 minutes to get it out on the 21st.



Message Edited by Scott Klassen on 03-21-2008 08:36 AM

Jason1222's picture

Although I agree with the last couple of threads, and Symantec should have indicated "tentative" on the release, because yes; as most of us know, RED-TAPE is everywhere.
 
However, I don't understand why everyone is panicking that the release isn't out, if anything you should consider it a blessing in disguise.  I am personally not a big fan, especially on a holiday-long weekend, of deploying anything into a live environment on a Friday.  Not in the morning and not in the afternoon.  Personally, Sunday, for Easter Brunch I would like to be with the family, and not trying to figure out what exploded in my MR2 release...  No offense Symantec. 
 
But, by all means if they do release it today, I look forward to the "MR2 broke my [fill in the blanks]" threads on **Tuesday**, I didn't have to spend the whole weekend figuring out.  I for one, am going to enjoy my 3 days off.




Message Edited by Jason1222 on 03-21-2008 12:05 PM

Hurricane Andrew's picture

LOL! :smileyvery-happy:
 
Well put, Jason!

----
"Hurricane" Andrew
Milford, Delaware

Paul Murgatroyd's picture

As most of you will probably have guessed by now, we have had to extend the MR2 timescales a little so that we can work out a couple of aspects of migration.  We now expect to deliver MR2 RTM in early April.  The good news however is that feedback from our MR2 beta program has been very positive so far, if anyone has the beta and hasn't provided feedback, now is the time to do so!
 
To clear up a few comments, the dates posted originally were our internal release dates (and also US PST dates, not GMT) - this is how we work and have always done so.  Builds will then appear shortly afterwards on Platinum and normally take a couple of business days to make their way onto FileConnect.  As FileConnect works based on licensing and SKU's it is a great deal more complicated to map entitlement across, than just posting it (as is the case with Platinum).
 
At the moment, all I can do is apologise and wish everyone a peaceful holiday weekend with your family and loved ones, and please... if you have the beta and haven't given feedback yet, then please do so!
 
thanks

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

SKlassen's picture

Thanks for the info Paul.
guidoelia's picture

You should also tell us how long we have to wait from the english release and a localized version (Italian in my case)
I cannot find yet the Outlook patch  for MR1 Italian !
 
Regards
 
 
 
Bud's picture

Does anyone know if MR2 will fix wireless connection using WPA?  Ever since I loaded Endpoint 11.0 I have been unable to maintain a wirelss signal (MR1 dis not fix this problem, like it said it would)
Ben Blackmore's picture

Personally I'm hoping MR2 will allow administrators to define granular access to certain functions for standard users via a policy setting, i.e. allow a standard user to disable the firewall/add their own firewall rules, without having to make everyone a local admin on their workstations (very bad practice!), this is something I miss most from Symantec Client Security.
Paul Murgatroyd's picture

guidoelia, we are working on dates at the moment, but French, Italian, German and Spanish are our top priorities for localisation and should be available reasonably quickly after the initial release.
 
as far as I can tell, the outlook patch is available for Italian, but you would need to contact support to get it (which you can do via https://mysupport.symantec.com) - we realise this isn't ideal and are trying to get patches like this posted to our support ftp site.
 
Bud, I will respond separately to your message
 
Ben, does "Mixed Control" not meet your requirements? (Clients\Select Group\Policies Tab\Location Specific Settings\Client User Interface Control Settings\Server Control --> Customise OR Mixed Control --> Customise)

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

ValhallaWS's picture

Yeah.  Have had the same **bleep** problem with the same **bleep** file.  Takes about a week for memory and CPU usage to blow out.  I found the easiest way to fix the problem is to kill the process (it restarts itself shortly afterwards) about once a week.  No need to re-start server.
 
I've been told MR2 will fix the problem.  Fingers crossed. 
Vmax8's picture

Paul, any news about an exact download date at Fileconnect? Without MR2 our deployment of Vista SP1 is stuck.
Bsalyer's picture

What issues are you having with Vista's SP1?  I've been running it along side SEP and havent had any issues at all. we havea very small Vista test group still but its actually running better on Vista than it does on XP
Vmax8's picture

Vista SP1 doesn't show in Windows Update because of SEP, specifically the Network Threat Protection. It's documented by Microsoft here: http://support.microsoft.com/KB/948343
I didn't try the standalone installation of SP1, so I don't kow if the installationt works or not, but I read, that it will result in BSOD because of SEP.
figo's picture

the compatibility problem with vista SP1 only happened on machine with wireless card.

those desktop PCs should be good.

for wireless users, MR2 is coming, :)

thanks

tekwerker's picture

Wait for MR2 for Vista SP1. It has already been stated by Symantec staff that MR1 on Vista SP1 is not a supported configuration. And it's not like it's the first time somebody has gone on and said "oh, the only issue was so and so" and surprise, another problem crops up. If you install MR1 on Vista SP1 and you have issues, the "it worked fine for me" crowd will say it's your own fault for not running it in a test environment first.
 
Personally, I've had enough of being an unpaid beta tester.
Bored Silly's picture

FYI - Accourding to my BCAM, 4/14/08 is the new tentative release date for MR2.  It was going to be today but it's being delayed for QA purposes.

The_Stranger's picture

I am running SEP 11 MR1 on Vista, with and without SP1.  The issues, for me at least are no different than the are for XP or 2003 server or 2008 server. 
Spike's picture

I'm running SEP RTM client on several laptops with Vista SP1 and wireless connections without any issues. Still looking forward to MR2. Avoided MR1 because of all the issues I read about here. Sounded like it would just make things worse rather than better.

SKlassen's picture

I'll tell you Spike, MR1 fixed dozens of issues with the original release.  As long as things are working well to your satisfaction, with MR2, right around the corner, it's probably no big deal that you haven't already updated to MR1.  If MR2 is delayed again though, I would suggest updating to MR1 and then MP1 for your SEPM server.
 
Spike's picture

Hopefully MR2 is right around the corner, but if something strange comes up in QA and it sees a significant delay I will certainly keep MR1 in mind.

Ben Blackmore's picture

@ Paul Murgatroyd,

Any update on the ETA for MR2 to be released to fileconnect?

Cheers

Ben



Message Edited by Ben Blackmore on 04-04-2008 04:31 AM

Robert Foster's picture

Casting my vote for Windows 2008 SEPM support... I have at least one client who has just installed Win2008, and purchased Endpoint Protection - wanting to install SEPM on it - I'm currently looking at installing VMWare and WinXP - they don't particularly want to purchase another license for Win2003 at this point in time...

SKlassen's picture

Robert:  The latest information on this board says that MR2 will support Server 2008 for a client install, but not as the platform for SEPM.  This support will be added in the near future.
Robert Foster's picture

Scott: I know - I was just casting my vote anyway...

PeterTWJ's picture

To me, Symantec Endpoint Protection 11.0 Maintenance Release 2 is critically needed.

Judy 2's picture

Hi Paul:
 
Your message about the release date for MR2 is early April - Has it been release yet? If so, what would be the release # for example (11.0.1000.xxxx or 11.0.2)?
 
Thanks for your help, Judy
Knottyropes's picture

Judy did you read page 7 of this post?
 
:robotindifferent:
Judy 2's picture

I scanned through Page 7, but still did not see an actual release date for MR2...
 
I've logged into fileconnect this morning and the only current one in there is the Maintenance Patch.
 
Which message is it?
 
Judy
Judy 2's picture

Never mind I found it - April 14th :)
ISP236's picture

Are there any release notes (acutally deploying the update) MR2 coming out yet..?  Or were there any for MR 1?
 
Just want to see how this is going to work and get a handle on how we are going to deploy before the update is released.
 
Thanks.
Knottyropes's picture

 
Guess you did not see it on page 7 of this post.
 
I have also upgraded to MR1 MP1 and it has resolved a few issues.
 
note on how to intall below in my post.
 
SKlassen's picture

The current release notes for SEP 11.0 can be found at http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121216360648?Open&docid=2008021516381048&nsf=ent-security.nsf&view=854fa02b4f5013678825731a007d06af.  MR2 changes will be added to the document at this same link once it is released.
Ben Blackmore's picture


ISP236 wrote:
Are there any release notes (acutally deploying the update) MR2 coming out yet..?  Or were there any for MR 1?
 
Just want to see how this is going to work and get a handle on how we are going to deploy before the update is released.
 
Thanks.


From my experience upgrading from the initial release (RTM), to MR1, there were 3 ways of upgrading.
 
1. Push out the install with the SEPM console. The user will get a popup telling them a new version is available, and ask if they want to upgrade. You can configure this to allow the user to postpone, but force that it has to be install by a certain time/date etc.
2. Add the new release to group policy software installs, and roll it out when machines boot up. MR1 could install over the top of the RTM without having to uninstall it first. I would expect MR2 to be the same.
3. There was an MSP patch file available for MR1, which could be applied to the RTM, and updated it, without having to perform a full re-installatation. MR2 will hopefully have a similar MSP patch, as they are much smaller in size, (12mb I think the MR1 MSP was, rather than the 118mb for the full blown MR1 install).
 
HTH

Ben



Message Edited by Ben Blackmore on 04-08-2008 01:30 AM

Paul Murgatroyd's picture

For those of you with SymBeta accounts, we released MR2 Release Candidate last night.  Its available to download from SymBeta now.
 
Ben, not sure why you saw 118MB package for MR1?  It should be no more than about 70MB in total (assuming you have the single exe setup?)

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

Ben Blackmore's picture

Paul,
 
We use the MSI option to deploy through Group Policy Software Installation. The Admin install is about 117mb for this.
 
Ben
 
dwhight's picture

I have a symbeta account and have logged on but cannot see the MR2 beta package. Is there something I need to do. I am registered to the Symantec Endpoint Protection 11.0 project.



Message Edited by Paul Murgatroyd on 04-09-2008 03:16 PM

Paul Murgatroyd's picture

when you login you should see something like this?
 
 
Just click the SEP 11.0 MR2 (WIN Server 2008 support) link and that should take you through the download the files?

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

dwhight's picture

I only see Symantec Endpoint Protection 11.0 in my projects list. How do I subscribe to\add the MR2 project?

Paul Murgatroyd's picture

if you have the MR2 link then you need to add it into your SymBeta account by visiting the link and logging in with your normal user name and password... it should add it in...
 
 

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

dwhight's picture

Maybe I'm missing something but I don't have an MR2 link.
Paul Murgatroyd's picture

you have PM

Paul Murgatroyd
Principal Regional Product Manager, Enterprise Security Group, Symantec
Endpoint twitter feed: http://twitter.com/symc_endpoint

ChadG's picture

hi guys,
 
Is MR2 also an update for clients?
 
 
 
 
thanks