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

Deploying Big Packages

Created: 25 Mar 2007 • Updated: 07 May 2007 • 6 comments
trb48's picture
0 0 Votes
Login to vote

Do you ever have to push out large software packages to thousands of computers under your care? If you push out a big software package does it always install? Here's a secret that'll help with the heavy lifting.

When I have pushed out large software packages I always ran into the same problem: there was not enough time at night to push the software out and install it. This became a big problem under a tight schedule.

After trying several different work-arounds, I came up with a really simple, yet effective solution:

  • Create a job in Deployment Console that copies the software package to destination computers. This should be done during the day.
  • Create a second job, that is scheduled to run at night. This job will actually install the software.

This way, you can install the software on all of the computers at the same time. This method has saved my neck a number of times.

Comments 6 CommentsJump to latest comment

erikw's picture

Copying the large packages over the day is a good suggestion. There is a small bug!

The user will be affected with a slow PC. He or she will notice this, and they will call the helpdesk.

It is a good idea to submit this first to the user.

regards
Erik
www.svs4u.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

0
Login to vote
trb48's picture

I have done this tons of times. The packages were usually about 300MB or bigger. No one ever complained (that does not mean it will slow down their computer). I think that if you stagger the computers out, and are careful with the package deploy you will be fine.

But, Erik is right. You should ask the customer before you slow down their computer...

-trb48

-2
Login to vote
erikw's picture

A copy action of 300 mb is not really slowing down.
deploying a package like office 2007 that is over 1 gb is a different story.
regards
erik

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

-4
Login to vote
kmieciooo's picture

If you will use bandwidth throttling set up to: 30% customer should not notice any difference (usually)with PC performance.

kmiecio || Altiris Admin || ACP - NSF :::...

kmiecio || Altiris Admin || ACP - NSF :::...

0
Login to vote
SK's picture

Only the NSAgent can do that. The only time I would use the DS method is if I really needed the software deployed the same day that I wanted to install it.

Usually my customers create and test the package, and then assign it to their package servers (which use bandwidth throttling) a couple of days or a week before they want to start enabling tasks to target the end User.

This way, the package is already local to the end users environment, which normally does not need to have bandwidth throttling enabled.

For DS to have limited bandwidth for file copies, you would need to use either QOS or a HW network metering function.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

-2
Login to vote
kmieciooo's picture

Yep you're right... i was thinking too quickly (and i'm not using DS every day... just occasionally... so QOS is there any solution?

kmiecio || Altiris Admin || ACP - NSF :::...

kmiecio || Altiris Admin || ACP - NSF :::...

0
Login to vote