Endpoint Protection

Upgrade process from SEP 12.1 RU1 MP1 to SEP 12.1 RU2 

11-20-2012 03:19 AM

Hi,

We have seen an article about upgrade process graphical overview

Now we will see upgrade process from existing SEP 12.1 RU1 MP1 to the latest SEP version i.e. SEP 12.1 RU2

Prior to upgrade please go through this article.

Release Notes and System Requirements for all versions of Symantec Endpoint Protection and Symantec Network Access Control

http://www.symantec.com/docs/TECH163829

There is not any major change in the upgrade process. Port 8446 will be used for Remote Management web services.

Stop the SEP 12.1 RU1 MP1 Symantec Endpoint Protection Manager Service before starting upgrade process.

The download is a zip file and the file size is approximately 1.5 GB in size

Once the download finishes successfully, extract the contents of the compressed file to a location of your choice

Navigate to the extracted files, then enter the SEPM folder and double-click on setup.exe OR Symantec Endpoint Protection Manager.msi file.

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

07-24-2013 07:25 AM

Hello,

One of the possibility can be a corruption of  Application and Device control policy (ADC).

Replace with ADC policy version2 which can be downloaded in KB, I would suggest to test this by creating test group.

http://www.symantec.com/docs/TECH132337
 

07-23-2013 09:11 AM

Hi Chetan

 

Both options are off. Here is the error message I get even if I am logged on as local admin:

 

07-23-2013 06:57 AM

Hi,

Make sure Windows 7 machine User Access Control (UAC) and Windows defender is disabled.

07-23-2013 06:13 AM

Hi Chetan

We have upgraded our SEPM to 12.1 RU2 a month ago. All works perfect except that when upgrading clients by running an installation package, I get an error" there are no permissions to upgrade registry files on the machine" We only have Win7 machines. Please advise.

David

07-16-2013 07:09 AM

Nice Work Chetan

07-10-2013 10:50 AM

Hello Everyone,

Previously we used to download the latest software from https://fileconnect.symantec.com  Now It has been changed to https://symantec.flexnetoperations.com.

Currently old URL is redirecting to the new one.

07-02-2013 10:27 AM

Dear All,
SEPM Upgradation process from SEPM 12.1 RU1 MP1 to 12.1 RU3.
Graphical Overview...:)

07-02-2013 09:54 AM

Hi,

I haven't created it.This article I had created last time.

Upgrade process from SEP 12.1 RU1 MP1 to SEP 12.1 RU2.

https://www-secure.symantec.com/connect/articles/u...

It should be the same while doing an upgrade to RU3. 

Howeve let me know if you want that article.

07-02-2013 08:13 AM

Hi Chetan,

 

can you send me 12.1 ru 2 to ru 3 upgradation process view........

 

06-06-2013 12:58 PM

Thanks for sharing Pete.

06-06-2013 12:06 PM

Yes...Pete

05-25-2013 03:50 AM

Hi Chetan,
Thanks for your suggetion...
can you share knowlegebase for upgrade SQL server from 2005 sp2 to 2008.
Regards,
Subhash

05-23-2013 09:25 AM

Thanks Man !!!

05-23-2013 09:24 AM

Hi,

I do apologies for the late reply.

SQL upgrade and SEPM upgrade these are two things.

If we looked at the SEP 12.1 RU1(Applicable for RU1 MP1 as well) System requirements we can see it supports the following SQL versions.

  • SQL Server 2005, SP4
  • SQL Server 2008
  • SQL Server 2008 R2
  • SQL Server 2012

For SQL upgrade you can consult with Microsoft for best approach however I think you can directly upgrade from SQL 2005 SP2 to SQL 2008.

In you case you need to upgrade the SQL version first then proceed with the SEPM upgrade.

04-08-2013 11:28 AM

Dear All,
I having SEPM 12.1 RU1 MP1 and SQL 2005 SP2.
it is require to upgrade databse first to upgrade sepm 12.1 RU2?
kindly suggest i should upgrade SQL 2005 sp2 to sp4 or direct SQL 2008.
Regards,
Subhash

02-26-2013 12:01 AM

Nice article Chetan,

02-25-2013 07:39 PM

thank you for sharing this article Chetan !

02-10-2013 01:18 PM

Greate Chetan.....

02-08-2013 06:13 PM

Sorry, I found the answer.

https://www-secure.symantec.com/connect/articles/pending-file-rename-operations

 

02-08-2013 03:20 PM

Hi Chetan,

We have an issue where after stoping the SEP 12.1 RU1 MP1 Symantec Endpoint Protection Manager Service. It will not allow us to install the setup.exe OR Symantec Endpoint Protection Manager.msi file.

We have tried mulitple reboots to hopefully fix the problem. We did notice however that if we do not stop the Symantec Endpoint Protection Manager Service that it will alow us to install.

What do you recommend we do?

thanks in advance

02-08-2013 12:13 PM

Hi Rupesh,

In SQL database upgrade process also t would be the almost same like embedded.

02-08-2013 11:06 AM

is there any documet for 12.1 mp1 to 12.ru2 Sql data base upgradation.

also details like port and database name password.where it find.?

02-08-2013 05:42 AM

HI,

Q. Is a reboot required to complete the client upgrade from 12.1.1 to 12.1.2

--> Yes it's required.

02-07-2013 04:28 PM

Chetan,

It will only prompt for a reboot if I set that option in the client install settings on the upgrade package. I don't want to cause a reboot of clients if it a reboot is not required.

My question is more basic: Is a reboot required to complete the client upgrade from 12.1.1 to 12.1.2. 

We did not need to do this in SEP11 for minor client upgrades within SEP11.  I would hope we have not taken a step backward in the SEP12 product.

02-07-2013 04:13 PM

Hi,

Are you saying that I must restart the client after I auto-upgrade the client from 12.1.1100 to 12.1.2

--> Yes, it should prompt for the reboot.

02-07-2013 03:38 PM

Chetan,

Just to be perfectly clear:

Are you saying that I must restart the client after I auto-upgrade the client from 12.1.1100 to 12.1.2? 

I thought that the mandatory restart only applied to clients that were being upgraded from releases earlier than 12.1.1 (11.x, etc)

01-30-2013 09:54 AM

Hi,

This is by design. We need to have SEP 12.1.2 SEPM to export RU2 Mac package.

 

01-02-2013 04:52 AM

Hi Dickson,

Q1 : If only upgrade SEPM, will the SEP Client in SEPM server (not in the client group) also automatically upgrade?

--> In Enterprise Edition SEPM won't upgrade clients automatically.But in Small Business Edition SEPM will upgrade clients automatically & If required you can stop it as well.

Q2 : Does this upgrade for SEPM or SEP client require a reboot?

--> Reboot is required for the SEP clients to upgrade to the latest version.

Q3 : For client, the new version of "Client Install Package" should be available after upgrade SEPM. If I do not want to use "AutoUpgrade" option because I do not want to upgrade all clients in a group at once, can I export a client installation package for this upgrade? (run this single exe in client server to upgrade.

--> Yes it's possible. However when you assign package to the group it will not start upgrade process for all the clients immediately. I believe it would upgrade only 10 clients at a time.

Q4. If the upgrade requires a reboot in Q2, does the restart option depend on the "client installation setting" in package or on the "Reboot Option" in the client management setting?

---> It's depend upon client install settings. You need to configure schedule reboot option as per business requirement.

Q5. (this question should in a new content) If I do not want the client to reboot by content download or any request, should I set the "Restart Type" to "Do not restart" because the Production server should not restart by itself?

--> Yes select 'Do not restart"

01-02-2013 02:29 AM

Thanks for Chetan's details explaination of upgrading.

 

Upgrading from 12.1 RU1 MP1 to 12.1 RU2 for SEPM and SEP client


Q1 : If only upgrade SEPM, will the SEP Client in SEPM server (not in the client group) also automatically upgrade?

Q2 : Does this upgrade for SEPM or SEP client require a reboot?

Q3 : For client, the new version of "Client Install Package" should be available after upgrade SEPM. If I do not want to use "AutoUpgrade" option because I do not want to upgrade all clients in a group at once, can I export a client installation package for this upgrade? (run this single exe in client server to upgrade.)

Q4. If the upgrade requires a reboot in Q2, does the restart option depend on the "client installation setting" in package or on the "Reboot Option" in the client management setting?

Q5. (this question should in a new content) If I do not want the client to reboot by content download or any request, should I set the "Restart Type" to "Do not restart" because the Production server should not restart by itself?

 

11-27-2012 06:15 AM

Thanks Chetan, for checking ..

 

 

11-27-2012 05:54 AM

Hi,

It should work without any issue.

However it's recommended to use same version for both i.e. SEPM & SEP clients.

11-27-2012 03:13 AM

SEP clients - SEP 12.1RU1MP1

SEPM - SEP 12.1RU2

 

Has anyone tested whether the clients will communicate to the server and is it working?

11-22-2012 10:30 AM

Hi,

In test environement I am able to managed SEP 12.1 RU2 client through SEPM 12.1 RU1 MP1.


 

I could also import the MAC 12.1 RU2 package into SEPM 12.1 RU1 MP1 but while exporting the Package I am also getting the same error.

Need to check whether it's supported or not.

 

11-20-2012 02:57 PM

At the same time , We are importing the MAC 12. RU2 package to SEPM 12.1 RU1 MP1, Succesfully we are able to imported to SEPM , but while exporting the Package we are getting the below error. Except this package , remaining old packages are able to export successfully.

After importing the package, SEPM server has been re configured  as per below article. But no luck. Please attached Screen shot

"https://www-secure.symantec.com/connect/forums/sep-121-error-failed-create-folder-which-publish-package"

 

Preparing...
Working on Group My Company\Default Group...
                Creating folder: C:\Documents and Settings\skanchar\My Documents\My Company_Default Group_Mac\Symantec Endpoint Protection version 12.1.2015.2015...
                Retrieving the group Management Server List...
                Retrieving the package data from the management server...
Failed to export to Group Default Group
Try to export to Group Default Group using Group ID 92C1BA6DAC1D1B1600AD106F8B57AE04
                Creating folder: C:\Documents and Settings\skanchar\My Documents\92C1BA6DAC1D1B1600AD106F8B57AE04...
                Retrieving the group Management Server List...
                Retrieving the package data from the management server...

 

 

11-20-2012 02:21 PM

Hi,

I will test it & get back to you.

11-20-2012 01:12 PM

SEPM 12.1 RU1 MP1  support Sep 12.1 RU2 clients..?

SEPM version :12.1 RU1 MP1

Client Version :Sep 12.1 RU2

11-20-2012 09:49 AM

Nice Article Chetan...!!!!

Related Entries and Links

No Related Resource entered.