Is there a setting that can be applied to prevent future updates? We are a larger enterprise customer and explorer issue caused major problems in our organization. We're happy to apply updates as they are provided but would rather have control over the process.
We're in the process of implementing Fences in a medium/large enterprise environment. Great product that could be much better - and likely more widely adopted - with some additional functionality that assists in the standardization and deployment of the product: Allow for the full export/import of all configuration information. Currently you can export/import an XML file but that provides only fence names and location
That's correct - we're using the process supplied in the "Volume Configuration" document for most of the work. While the export/import process captures specific icon names and their associations with a specific fence, it doesn't capture the rules (ex. If shortcut name contains "Compliance" put icon in the "Organization" Fence). We're close to getting it working by exporting the HKEY_CURRENT_USER\Software\Star
Another question - Using /oemlayout and /applylayout we can save the basic Fences configuration. Is there a way to export the rules applied to fences? For now we're exporting specific portions of the registry key in HKCU (HKEY_CURRENT_USER\Software\Stardock\Fences\Rules) and importing when we apply the layout.
Thanks, Sean. While we intend to incorporate Fences into our image, we have a large number of existing machines that we need to target initially. We're performing most of the steps above with our installer currently. Appreciate the tip concerning SdDisplay.exe - we'll add that to our script. As a suggestion that may help with enterprise-level adoption, it would helpful if the installer accepted additional parameters that allowed the license at t
Our organization recently purchased a large number of Fences 3 licenses and have started developing a package for deployment. Is there a way to both install and activate the license? As it stands we can automate the install, but the application launches afterwards and asks for a key. We can then use the command line tool to activate our license but it's confusing for our end users.