PreConfigured Paks

Back

1

Why would I want to bypass Internal (pre-defined) Item Level Targeting?

2

Why do some Paks have pre-defined Item Level Targeting for an EXACT version number, and others say “Version 7 to 99″ (or similar)?

3

Why can’t I seem to find (or perform) UI lockdown for Firefox, Java or Thunderbird ?

4

What is the official support policy for the pre-configured Paks?

5

What is “Internal (pre-Defined)” Item Level Targeting?

6

What do I do if I find a problem with a preconfigured Pak?

7

Using the Pre-configured Pak for Java, how do I prevent “Java has discovered application components that could indicate a security concern.” Pop up?

8

One of my Pak entry’s settings is not getting delivered on target machines. What should be the first thing to look into?

9

Java: I have already un-checked “Check Updated automatically”. But I still get prompted for updates.

10

Is “Internal Item-Level Targeting” on by default?

11

I added a Pak and some items are Greyed out / not available. In other Paks, everything seems available. What’s happening?

12

How-to: Configure Chrome HomePage using PolicyPak

13

How will I know that an existing Pak will work with the version of the application I have today (and tomorrow)?

14

How often do the policy Paks for specific apps get updated?

15

Can I enable / disable add-ons for Firefox and/or Internet Explorer?

16

Can I deliver, manage and/or revoke certificates directly to Firefox or Internet Explorer?