![]() The solution turned out to be to open a command line “as Administrator”, run “pnputil -e > pnplist.txt”, find everything in there that has the name “Juniper” in it, then run “pnputil -d oemXX.inf” for each entry, where “XX” is the actual number of the entry. They resolved it by re-imagining the machine. I had seen something similar at a customer of mine. So it was likely that something was lingering that was causing this issue. Now, this machine has had various versions of Juniper-something installed on it over the years. Network Connect, Host Checker, Setup Client, Installer Service, Pulse Collaboration, I got rid of them all. Usually, when something odd like this happens, the remedy is to uninstall everything Juniper. The installer would start with “copying new files”, then “rolling back action” and would finally tell me that “the wizard was interrupted before JunOS Pulse could be completely installed.” On my own Windows 7 machine, I had an odd error when attempting to install JunOS Pulse 5. The notes here do apply to Pulse Secure, and checking the output of pnputil, Pulse Secure did not bother to change the “Driver package provider” string, which means it still reads “Juniper”. Edit : This remains one of the most visited entries on my blog.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |