Software Deployment

H.Richburg,

If I remember you can disable the automatic updates using the Customisation Wizard.

If in a corporate environment I would have thought that you wouldn't want end users updating their software, so the update location you refer to doesn't factor into it.

I personally have disabled checking for updates etc, and if there is an update or revision of the Reader that it is deemed as required it gets packaged and deployed across the board.

When you allow users to update their own software you can not guarantee what is out there on your estate.

Thats's just my thoughts on the matter,

Thanks,

Dunnpy

Dunphy:

You make an excellent point. One that I thought of after my post but let me ask what product(s) do you use to deploy any patches?

Thanks again for the reply?

Howie,

We use SMS2003 for deployment.

To be fair, I work for an IT Outsourcing company, so it is up to the client to request applications to be packaged.
It is normal for them to submit a request asking for all automatic updates to be disabled.

If there are patches or new versions then the client's IT security team investigate the implications and make a decision.

With a product such as Adobe Reader if a patch or build revision is released, there is also a full installation also released for new installations. A new installation of Reader 8 will remove all flavours of Reader 7 as part of the installation - which makes it easier to manage the application list in SMS.

Another security 'feature' our clients have is restricted internet access, especially to download sites, so the user base can't download applications/patches at will. This makes it sometimes difficult as a packager when trying to get other tools etc of the web, but for the consistancy of the desktop estate makes perfect sense.

Hope this helps your situation,

Thanks,

Dunnpy