Okay, I'm real new to networking AST and AutoCAD so be nice I have ADT2005 working "perfectly" (at least getting the license) for about 45 users. Most of our shared files are on a "read only" drive, which I control the changes on. I install new systems using the NIW. In order to have the installs work correctly, we must first grant full read/write privileges to this drive, install ADT2005, then remove write privileges. Now, I assume I will somehow apply the service patch to the "network image" of ADT2005 (I've seen that option in one of the configuration dialog boxes). I've read the README file, but still want to ask a few questions: 1. After patching the Network Image of ADT2005, how does this get "transmitted" to the networked copies at the users workstations? 2. In order to apply the patch, I believe I have to regrant ALL users read/write privileges to the "CAD common" drive, yes? Are there any other issues I need to think or be concerned about. TIA! -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email:
Patching the administrative image will not 'transmit' the service pack to existing users. In fact, it is best not to patch the administrative image until all current installed seats have applied the service pack. The reason is that each seat will attempt to refer to the original install image. If you patch the install image then you will need to have an Acad 2005 CD at each workstation or uninstall AutoCAD and reinstall from the new image. Some companies do the later as a matter of policy. If your users have administrative rights on their workstation then you could use communication center to implement Service Packs from the Autodesk site or through a local server using a patch list. Patch list implementation is documented in the Service pack Readme. There are lots of ways to deliver Service Packs to workstations and the best choice has a lot to do with the tools and expertise available within your organization. If you are new to this stuff you may find it worth while to get some professional assistance in analyzing your environment and implementing a solution.
So, what you're saying is that I have to install the SP1 for ADT2005 at EACH workstation, using ADT CD's? I've downloaded the patch, so I assume I could just double click on that to run the patch, instead of using the Internet. I assume I must grant read/write privileges to ALL locations of ADT files? -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email:
If you have already patched the admin image then you will have to carry around the CD, if you didn't you will not. Read only access to the image should be all you need to apply the SP at workstations if you did not patch the image. Sure, you can double click on the SP exec at each workstation to apply the SP so long as the person doing the double clicking has administrative rights to the workstation. jerry
I haven't patched the Image yet, so I'll try just doing a local station. Everyone has local admin rights. -- Regards, --------------- Reid M. Addis Registered Architect Architectural Applications Specialist Granary Associates 411 North 20th Street Philadelphia, PA 19130 Ph. 215-665-7056 email:
This issue can also be experienced when deciding "Patch or No Patch" with MS Office admin installations. The recommended procedure (from MS) is to never update the admin install with a service pack/patch. Always install SP's and patches to the client directly (automation using scripting, gpo, shortcut in email, etc. of course!!). Cons: All installs must have SP's and patches applied directly (i.e. each PC with the app installed must have the SP/patch executed on that PC). I think this provides consistency, knowing that every new install must have each SP or patch applied. Pros: Microsoft Installer (MSI) technology will work properly. Add/Remove components and MSI repair for the application will function as expected.