I’ve never been a big fan of ProtectionPilot, but the offerings of their competition are usually even worse. Today i’ve installed a new instance of McAfee ProtectionPilot 1.5, and i’ve used a special character when entering the password. After completing the setup routine, i wasn’t able to login. If that was caused by the special character, or because i mistyped the password (twice!), i don’t know.
Anyway, i wasn’t able to login into PP, receiving the error message that the password is wrong (or the server isn’t running). I’ve verified that the PP server was up and running (naimserv.exe listening on ports 81, 82 by default). I’ve had a look at the server logfile (in the PP install path, called server.log), showing the familiar HTTP 403 error message whenever i entered the wrong password.
McAfee’s official statement is that you have to reinstall PP to reset the password. But i was to lazy for this.
In case you didn’t know, ProtectionPilot is basically a castrated version of McAfee’s ePolicy server. So when looking around the web for what i could do now, i’ve found an interesting McAfeehelp.com forum post, that showed how you can reset the password in McAfee ePolicy.
The MSDE that ships with PP didn’t have neat database access tools, and the solution is also distributed along the thread.
Basically when dealing with MSDE, you’ll have to use commandline tool osql to access the ProtectionPilot database. osql is located in %ProgramFiles%\Microsoft SQL Server\8.0\Tools.
First, look how the database is called. You can use
osql -E -l to do this. You’ll then see your database instances in the format of MACHINE\EPOSERVER. The ProtectionPilot database instance is usually called EPOSERVER.
osql -E -S MACHINE\EPOSERVER to connect to the ProtectionPilot database instance.
Next, you need to the name of the ProtectionPilot database (not the instance name). Having not had much experience with Microsoft’s SQL products, i just searched for
*.mdf files, which do correspond to the database name. Usually the database name is EPO_MACHINE (where MACHINE is the name of the machine running ProtectionPilot).
Then, enter the following commands:
UPDATE UserTable SET Password='YheZGOiKbpSa6Zza9uYlLxtW/XI=' WHERE UserName='admin'
I’m not sure if the field names are correct (they’re from memory), you can use
SELECT * FROM UserTable to see the field descriptions.
If you’ve done this, your ProtectionPilot password will be “epo”. You should now be able to login correctly.