Results 1 to 2 of 2
2009-04-06, 18:54 #1
- Join Date
- Jan 2001
- Melbourne, Australia
- Thanked 0 Times in 0 Posts
We have company Word templates stored on the network. when triggered the templates get copied down onto the users local pc so the users have the latest copy.
Currenly on the Document Management System (DMS) launches, triggers scripts which goto the network location. grab the directory and all sub-directories and copies to the local pc.
If the DMS crashes. Users will start DMS and the scripts triggered to copy the templates to the local client. This is an unnecessary burden.
We are upgrading our standard operating system, and template deployments is one task being reviewed. I would like some guidelines on best practices and how you implement. or some doco would be grand...
Some suggestions are bundle the whole suite of template packages as an .msi package to deploy.
What happens when only one template is required to be updated? only that file gets pushed out as an .msi?
or do we update the version numbers and the whole suite of templates plus the updated template gets pushed out as a new .msi deployment?
We also have custom templates for MS-project & MS-Visio
2009-04-06, 19:09 #2
- Join Date
- Mar 2001
- St Louis, Missouri, USA
- Thanked 1,099 Times in 965 Posts