Is this the size of single exe or non single exe ?

Why do you want to export and deploy packages it will be huge.
When you assign a package to a group and upgrade it uses delta files which is very small when compared to a full package

I hv tried both - The Single EXE or Full Package - The Size is 98MB.

Also checked with SEP features ( AV, PTP, NTp Etc.).... If I export a package with only AV feture the size is remain same.

I need to export the package beacuse my clients are distributed globally ( US, UK, China, AUS,  ETC). So I need to use local repository to update the clients ( NOT from the SEPM ).

We had a critical problem i.e Client moves randomly here and there ( to/from any group) post upgrade of SEP MR3.
Now its quite stable in MR4 MP2.

Is this issu fixed parmanently?

Also let me know if any new issue is the in SEP RU 5.

I've noticed, and others have as well, that the package size with RU5 actually increased.  Exporting packages with only certain features does not reduce the package size, it only tells the installer not to install those portions.

Are your systems running SEP?  Have you considered using the CLIENT PATCHES (there are about 15MB) to upgrade your clients?  We are utilizing the Client Patches together with Altiris Notification Solution to migrate all (15,000+) and it has been working pretty well.

Yes!!! 70% of total client are on MR4 MP2 and rest MR4 MP1a, MR3 and below..... our total client volume is 28,000 +.and it will be 50K + by this year end.

I am aware of CLIENT PATCHES and Altiris both but Altiris NS is not used in our setup. So in our environment it is quite difficult to use CLIENT PATCH for upgrade.

My query is -

1. Why the client size is increased in MR 5 ( Almost 20 MB ) ?
2. Is the client random movement from one to another group issue fixed in MR5?

Also would like to know is any new bug/issues faced by the MR5 users.

Yes!!! 70% of total client are on MR4 MP2 and rest MR4 MP1a, MR3 and below..... our total client volume is 28,000 +.and it will be 50K + by this year end.

I am aware of CLIENT PATCHES and Altiris both but Altiris NS is not used in our setup. So in our environment it is quite difficult to use CLIENT PATCH for upgrade.

My query is -

1. Why the client size is increased in MR 5 ( Almost 20 MB ) ?
2. Is the client random movement from one to another group issue fixed in MR5?

Also would like to know is any new bug/issues faced by the MR5 users.

1. Why the client size is increased in MR 5 ( Almost 20 MB ) ?
i assume it is becuase of addition definition size ( as this setup will be have the latest package compared to MR4 or other version).

2. Is the client random movement from one to another group issue fixed in MR5?
not aware of..nor it has been mentioned in release notes. If this the bug?

 When you do an upgrade to the groups, the package is NOT 90MB, it's more like 30MB.  An Export is a full package, an upgrade is not.

Why you are using SEP to deploy to 28,000 clients is beyond me.  It's absurd to think it can handle that, and do it reliably.

You should be using the FREE Altiris deployment tools, or some other desktop systems management package.  Most of the major products out there, can send out a package ONE time to a local subnet, and broadcast it out locally, saving a ton of bandwidth.

SEPM's deployment features should really only be used when you have no other software deployment strategies, like you're most likely to find in small shops.

When deploying a local package that is somewhat big we are using a pre-copy with a bandwith throttle of 10% a week before deployment. After a week we trigger the install from the local cache. Maybe this is something you want to consider to resolve your implementation issue to 28000 clients. We use this for a 45000 clients environment and it works fine.

Is there any new BUG in SEP RU 5?

Could please elaborate on the " BUG " that  you are referring too.

This is not addressing the size of an exported installation package but this is refering to the package a SEPM distributes to a SEP client for an upgrade

Package is around 95MB.

You could look to create your own MST for the sep.msi that ius on the CD?  May be a bit smaller.

I am guessing from the size of your environment, that you must have a deployment infrastrute in place?  Does the software you have use local proxies or repaters? 

Hi,

Correction to the release notes has been made. The new release notes are available at the link:

ftp://ftp.entsupport.symantec.com/pub/support/docu...

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

MicrosoftInternetExplorer4

The wording changed from:

The size of the exported client installation package has been reduced.You can upgrade more clients with the client installation package in less time than before. As soon as the client connects to a management server, the client receives the most recent content.

To:

The size of the client upgrade package used for auto-upgrading has been significantly reduced.

This reduces the amount of traffic that is sent to the clients when you auto-upgrade them. The auto-upgrade process is faster and conserves network bandwidth.

Best,
Aniket

Thanks aniket  for sahring that information as this was creatng a lot of confusion.It was notfied and finally it is updated.