Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Upgrade Client With Package

Created: 31 Jul 2014 • Updated: 01 Aug 2014 | 7 comments
This issue has been solved. See solution.

Hi,

I planing to upgrade my SEP client from SEP 11 to SEP 12. However I have a few doubts need so clarification.

1) "Distribute upgrade over XX days" If I plan to have this upgrade run over the network over 7 days, do it mean I need to enter 7 inorder for the upgrade to be active within 7 days after I implement the policy?

2) I had a mix environment of Win 7 32bit and 64bits. Do it mean I need to create 2 different upgrade policy for. 1 for 32 bits and 1 for 64 bits?

3) will SEP able to identify the different OS function such as 32 bits and 64 bits?

Hope to hear from you soon.

Operating Systems:

Comments 7 CommentsJump to latest comment

.Brian's picture

1) It means it will happen over 7 days time. This starts when the client first checks in. If you enable now, 7 days later they will be done.

2) Yes, you need to add both 32/64 bit, the client will pull down the correct one.

3) Yes, no problem

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

blcharles's picture

1) So I want it to happen once the client check in to the SEPM, I uncheck that option? Am I right?

.Brian's picture

Yes, then you wouldn't set this number. I believe default is 1. Just be aware that if you set it to 0, it depends on how many clients you have but you could saturate your bandwidth quickly. Just something to think about.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

SOLUTION
blcharles's picture

Thks for the advise. As such, setting it to 1 day will be a better choice.

.Brian's picture

Correct. You should be fine then.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Rafeeq's picture

You should be careful while using this setting

 Example: If you have 2 clients and set it to distribute over 30 days, the first one will go immediately and the second will go after 15 days.

Using Distribute Clients over X days will assign a time to each client and only allows the client to get the update at that time. If the client misses it, it doesn't get the update until the cycle starts over. Example: That client that had to wait 15 days is offline on Day 15. On Day 16, the SEPM denies the update. On Day 17, the SEPM denies again... this will continue until Day 31 when the SEPM will assign new times to the clients. Even though this is an extreme example, you can see how this could make clients take a long time to get their updates. Even on a more reasonable 2-3 day distribution, a client could miss a number of consecutive update cycles.

https://www-secure.symantec.com/connect/forums/com...

Manipillai's picture

Major issue which I observe was client fails to communicate after upgrade as root cause as 11.0 use port 80 for communication but after upgrade Symantec will use port 8014, as Symantec will do its configuration need to keep you manager running until upgrade complete.

Second root kit issue make sure you have update the patch before upgrade

Pl check this discussion for better understanding of upgrade
https://www-secure.symantec.com/connect/blogs/late...

>MK

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<