Do you really want users modifying the configuration settings for an application that integrates directly with your valuable data? Of course not, and that’s where PolicyPak comes in. We enforce and lock down the optimum settings that you, the administrator, want to enforce upon your users. This is why PolicyPak supports FileMaker Pro, and dozens of other applications as well, locking down your users and enforcing your own configuration settings to give your users a predictive experience every time they access the application. Keep your FileMaker configuration settings enforced and streamlined with PolicyPak. Check out this video to see how it’s done.
Manage file maker pro
Hi. This is Jeremy Moskowitz, Group Policy MVP and Founder of PolicyPak Software. In this video, we’re going to learn how to manage and lockdown FileMaker Pro using PolicyPak.
I’ve already got “FileMaker Pro” installed on my target computer, and I’m already just a regular user here. As you can see, I’m logged on as a guy called “EastSales User4.” If we open up the application from the start menu and go to “Edit/Preferences,” we can see a number of settings here for our users to mess up.
If I go to “General,” we can see some important settings that govern updates for new version releases as well as the default language. “Layout” has some interesting options concerning application usage for my users. “Memory” has some very technical settings that I basically don’t want my users to even approach.
Let’s see how we can ensure compliance and perform desktop management of settings quickly using PolicyPak. I’ll go ahead and switch over to my management station computer. We’ll go ahead, right click over our “East Sales Users” and “Create a GPO in this domain, and link it here.” We’re going to call it “Lockdown FileMaker Pro.” This GPO is now associated with the East Sales Users.
I’ll right click over it. I’ll click “Edit.” I’ll dive down under “User Configuration/PolicyPak/Applications/New/Application.” There it is: “PolicyPak for FileMaker Pro” along with other applications like “Java,” “Flash,” “Firefox,” “Skype” and lots of other important desktop applications that your users utilize every day and you want to make more secure.
Let’s start with “General” because I know my users love the drag and drop text selection feature, so I’m going to enable that by enforcing the checkbox value (“Allow drag and drop text selection”). I’m going to also uncheck the “Notify me when an update is available” as well as uncheck “Notify me when a new version is available.” Notice how these settings became underlined as soon as the checkbox values were changed. This means that the setting’s values are going to be delivered through PolicyPak.
Now to make sure these settings are always enforced, I’m going to lock them down in a way only PolicyPak can do. I’ll right click over the notification settings and select “Hide corresponding control in target application” so that my users can’t even see this setting.
Next, let’s go over to “Memory.” Here, I want to “Save cache contents” “every” “hour.” Then to make sure that my users don’t alter that setting (or any setting on this tab for that matter) I’m going to right click on the tab itself and select “Disable whole tab in target application.”
Finally, I’ll go to “Layout” and configure these settings so my users have a predictive experience. Now I’ll go over to these settings and select “Perform ACL Lockdown,” which will prevent the most savvy of users from modifying the setting, which I’ll demonstrate shortly.
Let’s head on back over to my target client machine. We’ll get a command prompt and run “GP Update.” Now you could envision the user logging on for the first time or using a Terminal Services or a Citrix machine or using a VDI session or changing job roles or getting a new computer. Any of these things would trigger Group Policy to kick in. I just happen to be using GP Update.
Now that that’s done, let’s go ahead and reopen the application. We can see that our desired settings for “General” have been delivered and those notification settings have been hidden. Notice that I can’t even click on the “Memory” tab and that the settings in “Layout” have also been delivered.
Now let’s say that this user is knowledgeable about the registry and tries to circumvent the settings in that way. I just happen to have the registry settings saved here and, as you can see, any attempt by the user to modify the registry value is futile.
And we’re done. That is how incredibly easy it is for you to use PolicyPak and to manage and lockdown FileMaker Pro as well as tons of other desktop applications. If you’re looking for a trial of PolicyPak, just click on the “Webinar/Download” button on the right.
Thanks so much for watching, and get in touch with us if you’re looking to get started. Talk to you soon.