[SOLVED]PCOP cv8 console not updated

[ErinC]

I rolled out the PCOP v6 client to our work machines last night about 10:30pm. Now at nearly 10am the next day, various PCs are still showing in the console as Unprotected or as pending restart. I know for a fact that the machines have fully installed clients and they have been rebooted.
The console appears to be not showing the up-to-date status. The console is also very slow. Anyone else experiencing these kind of issues ?

[Pandamonium]

ErinC, we have had some reports.

Are some machines reporting correctly?

[ErinC]

Yes some are reporting correctly, most are not. I've just re-checked the console and some of the unprotected ones are now showing as protected.
There are still issues though, some are showing as requiring reboots when they have been rebooted already.

This is disappointing because the console really needs to reflect the agent status in as close to real time as possible in order for us to control the roll out of the v6 client properly.

[revcall]

I have just installed v6 on two workstations as part of the 30 day trial and am having the same issue. Hopefully there is a quick fix or this will be a very short trial.

***EDIT***
I also noticed that both listed as successful installs on the cv8 only for one workstation to change to "unsuccessful" about 10 minutes later. The distribution tool still lists both as "successful."

[ErinC]

Yes - 2 days after our upgrade and one PC is still showing as unprotected in the console, despite looking fine on the client side.
Some other machines are still showing as pending restart when they have been restarted already. Logged issue with corp tech support via email but no response as yet.

[ErinC]

Update: just received a response from tech support about this.

The issue with machines not showing up in the console as "protected" in real time is partly due to the current migration process. We have 100,000s of machines all talking back and this is having an effect on delaying the reporting. This will be resolved once the migration process settles down. In the meantime, there are scripts that can be run on the local machine to force the client PC to talk back to the console and correctly integrate.

For 32 Bit computers

C:\Program Files\Panda Security\WaAgent\WasLpMng\WAPLPMNG.exe walupd -force
C:\Program Files\Panda Security\WaAgent\WasLpMng\WAPLPMNG.exe waltest -force

For 64 Bit Computers

C:\Program Files <x86>\Panda Security\WaAgent\WasLpMng\WAPLPMNG.exe walupd -force
C:\Program Files <x86>\Panda Security\WaAgent\WasLpMng\WAPLPMNG.exe waltest -force

The explanation makes sense but capacity planning should have been done better. At the very least the staggering of updates should have been implemented better so as not to overload the servers.

[revcall]

Thanks for the update Erin. It's difficult to get a sense of how well this works due to this issue.

[ErinC]

I agree, which is exactly why I'm not willing to roll this out to any customers yet.

I got some further info from corp tech support;

We have moved the PCOP6 platform away from our own server and onto Microsoft Azure to allow for the extra capacity needed. As you have experienced, there are still some issues with the new clients reporting back. We have, in fact, phased the roll out of version 6 and are doing this in a staggered way to minimise impact.

So it looks like Panda misjudged the load on their infrastructure and decided to move some/all to the Microsoft Azure cloud. Sounds like a bit too little too late to me but they'll get there eventually.

[DRN]

revcall / ErinC,

The issue is now resolved, but there have been reports of PC still sitting in the Unprotected tab, even though they are fully functioning on the PC itself. To resolve this you can do one of the following.

1. Manually Force an update of the information from the PC.
Navigate to C:\Program Files\Panda Security\WaAgent\Waltest.
*Note: On 64 bit machines the directory is located in C:\Program Files(x86)
Delete all the .DAT files located in the directory:
WALTEST.DAT
WALTESTDF.DAT
WALTESTLT.DAT
Open a Command Prompt (cmd.exe)
Navigate to C:\Program Files\Panda Security\WaAgent\Waslpmng
Execute the command:
waplpmng waltest -force

2. Save the following code to a .bat file and you can deploy it however you wish to selected computers or through a GPO.
@ECHO OFF

:Start

REM **************************************************
REM *** Check OS Version
REM **************************************************
Set RegQry=HKLM\Hardware\Description\System\CentralProcessor\0
REG.exe Query %RegQry% > c:\checkOS.txt
Find /i "x86" < CheckOS.txt > c:\StringCheck.txt

If %ERRORLEVEL% == 0 (
:Run Windows 7 32 bit specific commands here.
Echo "This is 32 Bit"
GOTO 32Bit
) ELSE (
:Run Windows 7 64 bit specific commands here.
Echo "This is 64 Bit"
GOTO 64Bit
)

:32Bit
REM **************************************************
REM *** 32 Bit
REM **************************************************
ECHO 32

REM **************************************************
REM *** Delete WalTest Files
REM **************************************************
CD %programfiles%\Panda Security\WaAgent\Waltest\
DEL WALTEST.DAT /F /Q
DEL WALTESTDF.DAT /F /Q
DEL WALTESTLT.DAT /F /Q

REM **************************************************
REM *** Run WalTest
REM **************************************************

CD %programfiles%\Panda Security\WaAgent\WasLpMng\
waplpmng waltest -force

GOTO END

:64Bit

REM **************************************************
REM *** 64 Bit
REM **************************************************
ECHO 64

REM **************************************************
REM *** Delete WalTest Files
REM **************************************************
CD %programfiles(x86)%\Panda Security\WaAgent\Waltest\
DEL WALTEST.DAT /F /Q
DEL WALTESTDF.DAT /F /Q
DEL WALTESTLT.DAT /F /Q

REM **************************************************
REM *** Run WalTest
REM **************************************************

CD %programfiles(x86)%\Panda Security\WaAgent\WasLpMng\
waplpmng waltest -force

GOTO END

:END
REM **************************************************
REM *** Clean Up
REM **************************************************

DEL c:\checkOS.txt /F /Q
DEL c:\StringCheck.txt /F /Q