centralize one local profil for all desktops for centralize application settings... RRS feed

  • Question

  • hello...

    I have nightmare with adobe applications. This app write setting in 10000000000 places on folders, subfolders, and registry. Because of that I simply cant centralize my settings or write script for sharing settings to comps. I have department with 30 workstations connected to 2008 r2 active directory. My mind think that maybe I can use same login name (and virtualy same document and settings folders) in all 30 workstations, instead that every user have own user name when logon. What you think about that scenario? pros and cons. All workstations have same hardware.


    Monday, February 7, 2011 2:00 PM

All replies

  • You can set a bunch of options before deploying the software to your computers. The time you invest in your deployment, is gained back tenfold in management...

    E.g. : this tool lets you customize the look and feel, and other options, of adobe reader and acrobat tools :
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=4950 (download version 9 for "9" deployments)

    Here you have similar tools  and guides for the "CS" suite :

    Configuring your setup using these guides and applications will reduce the "100000000000" places and settings. You can pre-configure settings such as language, regional settings (mm vs inches etc.), configure if the application needs to look for updates or not, and so on. Practically everything you would want to preconfigure!

    If you need further modifications that are NOT handled by the tool, and you want to centralize the management of the settings, then I would recommend taking a look at http://technet.microsoft.com/en-us/library/cc731892(WS.10).aspx . That will allow you to manage files and registry settings. If you look a bit around, you'll also find ADM/ADMX files that can be used with GPO's. I would recommend browsing through the knowledge base at "appdeploy.com" as well, other people share their experience in deploying software there : no need to re-invent the wheel ;-)

    Avoid situations where 30 or more people use a generic logon, I don't see why you would do that.

    Monday, February 7, 2011 7:34 PM