The answer to this problem is a little different if you’re just starting out with PolicyPak, or if you’ve been a customer for years.
- If you’ve been a customer for years, you should start to ask yourself: “When did this happen, and why now?”
- If you’re just starting out with PolicyPak, then these steps will help you out to get close to the goal to determine where the problem is.
Additionally ask yourself:
- Am I having a problem on ONE, TWO, MANY or ALL machines? If the problem is simply on ONE or TWO machines, this is not likely something we can dive in, tear apart and make a bug-fix for. This is NOT likely a PolicyPak problem (even if removing PolicyPak magically “fixes it.”)
- Am I having a problem with ONE, TWO, MANY or ALL *USERS* or User profiles? For instance, sometimes we see that “When I log on as Jane to Jane’s machine, there is a problem. When I log on to Jane on Frank’s machine, the problem is absent.” This is NOT likely a PolicyPak problem (even if removing PolicyPak magically “fixes it.”) In these cases, you should blow-away the affected User’s profile and see if that corrects the issue.
Bug fixes / hotfixes for PolicyPak are made for predictable, reproducible behavior which is different than the intended result. So if you have one or two machines which are crashing or having other problems, we recommend the items in this section anyway; because maybe they could help.
But if the other 99% of your machines are configured in largely the same way, then it’s likely some problem with this “just one” machine and it’s somewhat unlikely we will be able to determine what.
We recognize that blowing away or resetting someone’s computer can be painful; but unless you can reproduce the unexpected behavior on MULTIPLE COMPUTERS, it is unlikely we will be able to reproduce it, and hence, we cannot build you a fix for a single misbehaving computer.
Moving on to slowdowns and weirdness: Almost all problems of slowdowns and weirdness are not usually PolicyPak bugs or problems; but instead are System-y software like:
- Similar system software that would “beat up” PolicyPak, which then makes it do bad things.
- Other kinds of software that would be a problem would be other desktop management software in the same “ballpark” of PolicyPak, and/or user experience management software and/or other least privilege management software.
Here’s an email we got back from a customer after they had their own “A-ha moment…”
“You can close the case now. The issue was with our Appstack. CSE was previously installed in the appstack and that made a mess in the registry. We reinstalled the whole appstack and woop – start menu and browser router works again.”
This is a typical response AFTER unloading or adjusting some kind of SYSTEM software the beats up on PolicyPak.
In order, here are things we ask you to try before we continue:
- Did you install the latest Client Side Extension? Even if you’re having a problem with an older Client Side Extension, we won’t ever fix that one. We only ever fix the LATEST one. So be sure BEFORE YOU CONTINUE that you’ve tested the problem out with the LATEST Client Side Extension.
- Did you try the information in this article? PolicyPak has a DRIVER, and sometimes the DRIVER can get in the way of things. Knowing the DRIVER is a problem can be helpful.
Only test this out if installing the LATEST Client Side Extension doesn’t clear up the problem.
- After #1 and #2, did you perform the steps to get us the LOG files and GPRESULT reports?
Maybe something will jump out and just tell us what it is. Do NOT attach this to an EMAIL. You must get an SRX first by emailing support, then, in the BOUNCEBACK, you’ll get directions for how to UPLOAD your log files.
After that.. if nothing jumps out at us.. here are the steps you’ll need to perform:
- Perform an exclusion to your AntiVirus using this article
- If #1 didn’t work, then uninstall your AntiVirus. Does that clear it up?
- Typically, something has changed to cause the problem. A change could be:
- Something in Windows. (Windows 7 to 10 upgrade, Windows 10 to 10 upgrade, new fix in Windows, etc.)
- Something you’ve installed that ISNT PolicyPak.
- Something that’s in a GPO and causing a PolicyPak problem.
- A later Client Side Extension build of PolicyPak, which is showing a new problem, where a previous Client Side Extension build did not exhibit the problem.
These are generally the four causes of change.
Therefore, to get us close to the goal, your team will have to narrow it down. The ideal way to do this is:
Troubleshooting Scenario 1 (best): Bring up a new machine and triangulate where the problem is
- Bring up a new (latest Current Branch) Windows 10 machine.. fully patched and NO APPLICATIONS AT ALL..
Warning / NOTE: Do not “image” a machine. Bring it up, totally fresh on new hardware / new VM.
- Add PolicyPak…
→ Stop: Do you see the problem now?
If YES, then the problem is likely something in Group Policy; some security setting which is preventing PolicyPak from performing it’s function. Provide us with PPLOGS and GPRESULT reports from THIS ARTICLE. Do not miss any steps
If NO.. then you need to BUILD UP the machine until you find the cause. Remember: If this was a problem / bug affecting all customers, we would know it immediately. So the problem has to be something in your configuration. Now, hand-install or automatically deploy each application and system software, one by one.. and keep testing until PolicyPak has the problem. Then.. When you think you’ve found the problem.. UN-LOAD the offending software. When PolicyPak functions perfectly, we then know the program that is having a problem with PolicyPak, and we can then reproduce it here in house and make a workaround or a fix.
Troubleshooting Scenario 2 (less good): Bring up a “deployed” machine and work backward to find where the problem is
In this scenario you’ve got your deployed machine, and you’ll strip away things until the problem is resolved.
- Have a machine with the problem.. with EVERYTHING ON IT.
- Add LATEST PolicyPak Client Side Extension (do not install any older extensions).
- KEEP STRIPPING IT DOWN until the problem goes away.
→ Stop: When did the problem release itself?
Troubleshooting Scenario 3 (also less good): Bring up a “deployed” machine and install old PolicyPak CSEs to reveal the problem
If Scenarios #1 and #2 fail to work, it’s possible the problem is in the latest PolicyPak Client Side Extension, but not in some EARLIER PolicyPak Client Side Extension.
You should be able to reproduce the problem 100% of the time with the NEWEST, and 0% of the time with the OLDER Client Side Extension.
- Have a machine with the problem.. with EVERYTHING ON IT.
- Add PolicyPak Client Side Extension …latest Client Side Extension first!→ Stop: See the problem happen. Then….
- Uninstall PolicyPak and keep installing EARLIER PolicyPak Client Side Extension versions until the problem doesn’t happen anymore.. and when it doesn’t happen anymore we can look to see what changed on OUR side and then build a new Client Side Extension version for you to test.