We've found that the 7.5.3.3 console installer forces one to use the Configuration Wizard as a second step following a remote console install. This occurs whether the install is an upgrade over an existing remote console or a spankin' new install. For an upgrade you don't get the dialog that asks what kinds of install you want to do. For a new remote console installation you get to choose the "Admin Console and Report Viewer" option as opposed to the "Full Installation" one. Still the Configuration Wizard pops up and you have to go through all of its screen to completion or the remote console installation/upgrade fails.
If the user doing the upgrade is signed into Windows with credentials that have full administrative privileges within the VIPRE application, it is possible for the user to complete the Configuration Wizard steps and successfully complete the install, but you don't want all of your VIPRE administrators and operators doing that because you're setting options back on the server that should only be set once.
The only way I can see to get my operators back in business is to temporarily give them full admin privileges within VIPRE so they can go through the Configuration Wizard steps with my guidance, and then set their privileges back down to what they were before.
This must be a bug in the installer. It can't be intentional that every remote console install or upgrade would kick off the Configuration Wizard. That should only happen for the local console install on the server.
We have an open ticket, 214130, with ThreatTrack support to help them figure out what's going wrong here.
Thank you for the post. I'll look into this to see if I can reproduce it and get it to our developers to fix.
In the meantime have them try the following so you don't have to give them admin rights.
Try opening the console again and the wizard should not launch.
Afraid it didn't. I updated the ticket with a screen shot of what we're running into now.
Thank you for the update. I left instructions for the technician handling your case. They will be in touch soon.
We figured out the problem with the registry work-around. For the operators that had never successfully completed the Configuration Wizard, there was no registry key called "HasRunPostInstallWizard", so they created it, as a String type. They figured out later that it needed to be a REG_DWORD (DWord 32-bit) type. Once they did that, the console started up fine.
That gets us up and running, but you guys still have an issue with the installer insisting on running the Configuration Wizard for remote console installs. That shouldn't be happening.