Installation / Uninstallation

Back

1

Why does Application Manager require a CSE / client installation piece? I want to do it “all” using what Microsoft ships in the box.

2

Which components within the PolicyPak product family will work with what operating system?

3

What if I accidentally install the 32 bit version of PolicyPak Suite (On Premise Edition) on a 64 bit machine or vice versa?

4

What happens when the PolicyPak Suite (On Premise Edition) license expires / if my company chooses not to renew?

5

The CSE won’t uninstall or allow in-place upgrade. What should I do?

6

The auto-updater feature appears to not be working. What can I do?

7

I have lots of various Windows machine types: from 32 bit XP machines to 64 bit Windows 7 machines.Can PolicyPak Suite (On Premise Edition) install on all of these machines?

8

I do not have access or ability to create the Central Store. What should the best practice to store Paks be?

9

How does an existing PolicyPak customer make use of the entire PolicyPak Suite (On Premise Edition)?

10

How do I upgrade Application Manager when I upgrade my DCs / servers?

11

How do I uninstall PolicyPak Suite (On Premise Edition)?

12

Does Application Manager need to be installed on Domain Controller (DC)?

13

Can Application Manager deliver settings for applications that are provided by XenAPP?

14

Can I store the DLL extensions in a central location AND locally on the machine I create my Paks on and if so which one is utilized?

15

Are there any caveats about removing the PolicyPakCSE after it is deployed?

16

Are there any additional steps required to integrate Application Manager with XenAPP applications?

17

I installed the Admin Console MSI, but I don’t see the PolicyPak node when I go to edit a GPO. Why?