Problem: The user reported that regular Domain Users could not use the AutoCAD product that is installed as a component of Autodesk. A message said that the application couldn't write to the registry. No kidding, some software really can be an SOB! I didn't do the installation, but I got the call when it wouldn't work.
Solution: Sorry, but I have to vent a little bit here. So that you know I'm not just picking on Autodesk, I've seen this problem with lots of products. COME ON PEOPLE! Don't you know that many organizations use your products in lab environments where most of the users don't OWN the machine the product is running on and don't have ADMINSTRATIVE PRIVILEGES???? Why in the name of God would you develop an application that writes to the registry every time the procuct is launched?? I did find some documentation that says you can run with Power User rights, and that's true. BUT, we don't want the lab users to be Power Users either. This is no help! (WHEW..... I feel better now).
Anyhow, most of the time we can work around these silly problems with various software packages by giving write access, or sometimes full access to the product's root directory, or to some file. For the Autodesk problem we have the added challenge of trying to find out which registry key the users need to write to. We haven't quite figured it out yet, but when we do I'll edit this post with the final solution.
Stay tuned.........
On second thought, I won't publish the registry key here, just because I don't want to encourage registry hacking. If you have this problem, please bug the vendor.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment