None of the Mobile devices send data back to ERA after Wmvare Server move

[NagyLaszloSchrack 0]

Hi,

I hope I'm writing in the right topic.

We have moved our Eset server from Hyper-V to Wmvare.

And I have noticed that after this move, none of the mobile phones are sending back Data to ERA.

I can send a schedule and run for example a "Find" task, it will execute, the mobilephone will have a new event(pop up or whatever you want to call it)  called "Eset found your device", but if I look at the Location details on the webconsole I see nothing, it is empty.

Same with the last logon feature.

I can press synchronize on the mobile device to force sync with the eset server, but on the webconsole it will still says that the device have not been  connected since X-days.

Computers are working as intended since my laptop has no problems and the last log connected column is refreshed.

this is what we are using currently:

ESET PROTECT (Server), Version 10.0 (10.0.1128.0)
ESET PROTECT (Web Console), Version 10.0 (10.0.132.0)
 

Microsoft Windows Server 2019 Datacenter (64-bit), Version 10.0.17763.4737

DB Version: Microsoft SQL Server 2019 (RT Express Edition (64-bit) 15.0.4298.1


Thank you for your help in advance.

Best regards,

Laszlo Nagy, It technician

[Marcos 5,243]

Did you follow the steps from https://help.eset.com/protect_install/10.1/en-US/migration_same_version.html when migrating the server?

I'm afraid at this point it will be necessary to re-enroll the phones as per https://help.eset.com/protect_cloud/en-US/?add_mobile_device_wizard.html. You could raise a support ticket to confirm my assumption.

[NagyLaszloSchrack 0]

14 hours ago, Marcos said:

Did you follow the steps from https://help.eset.com/protect_install/10.1/en-US/migration_same_version.html when migrating the server?

I'm afraid at this point it will be necessary to re-enroll the phones as per https://help.eset.com/protect_cloud/en-US/?add_mobile_device_wizard.html. You could raise a support ticket to confirm my assumption.

Hi thanks for the reply.

No because this article doesn't apply.

The only thing that changed is the virtualization tool used to manage the virtual machine that the Eset server is on.
Wmvare have a conversion tool built into Vcenter for converting HyperV Virtual Machines to Wmvare.

We swapped virtualization tool from Hypervisor to Wmvare and pretty much converted the whole server.

Everything is the same down to the hostname of the server, the only thing changed is the Network Interface (to be more precise a NIC from a different manufacturer) but the Ip remained the same. (what also changed is the physical machine that the Virtual Server is on)

And re-enrollment won't solve this problem since new mobile enrollments show up as unmanaged and their status won't chanage.

[Marcos 5,243]

Please raise a support ticket for further troubleshooting if MDM is running and the hostname of the server didn't change either.