Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Eric P Ebner
1 discussion post
Hey Everyone,

Pardon me if this question has an obvious answer or I missed something in the Knowledgebase section.

I work for an IT Consulting firm and we are in the preliminary phases of conducting a small feasibility analysis of DisplayFusion, as well as some other alternative programs.

I understand with the Pro Site License you can deploy an installer to each machine, but can I deploy an installer package that already has specific features enabled? More specifically the Titlebar Buttons.

We have various machines that are on deepfreeze and we would like it where if any user, with access, can sign into their account and DisplayFusion already be installed and configured the way we want it. It would have to accommodate and start-up for all user profiles that have access to said deepfreezed machines.

If it is not possible to deploy an install package that is custom, then would the alternative be installing a clean copy and then pushing a registry file to each machine that would automatically configure the clean installation to what settings we want enabled?

Once again, I apologize if this is an obvious answer. I am only wanting to ensure there's some certainty.
Mar 5, 2015  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Responded to your email regarding this yesterday, but I'll post my answer here in case others come across this post as well.

Some of the settings can be controlled using Group Policy (http://www.displayfusion.com/KB/AdminSettings/), but others are only stored in the current user's registry. If you want to customize things like the TitleBar Buttons, Window Location rules, etc, I usually recommend the following:
  • Setup a test machine with all of the settings adjusted the way you want them
  • Export the Settings (Settings > Options > Export), this will export them to a .reg file
  • As part of your deployment, import the .reg file first (would have to be imported into HKCU, so the installer needs to run as the user, not SYSTEM, or a different administrative user), then run the installer

As an alternative to step 3 above, you could import the .reg as a user logon script. That way, it doesn't matter who the installer ran as, because the settings will always be imported when the user logs in.
Mar 6, 2015  • #2
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)