08-25-2022 10:14 AM - edited 08-25-2022 10:24 AM
We are setting up a Windows365 environment that, obviously, lives in Azure cloud. These machines are access by RDPing into them. Due to some access management controls and the systems not actually living on our network, the Windows365 machines were having issues connecting properly.
One of the engineers on the project got an idea to install GlobalProtect on these machines and connect to our network via VPN, which worked for him after installing the proper certs, etc...
However, he noticed that when he reboots the machine, he is on longer able to RDP into the machine. The only way he is able to get back into the machine is to restore it to a previous state prior to the GlobalProtect installation. He did some testing and noted that after installing GlobalProtect, if he sets the service to start manually, he is able to reboot the machine and then RDP into it, start the GlobalProtect service, and then connect to the VPN.
- Has anyone had any experience with Windows365 and GlobalProtect similar to this issue?
- Does anyone have any ideas on what may be causing the issue, and perhaps, how to correct it?
Definitely a difficult issue as no logs can be pulled due to the machine restoration being needed to even get into the machine.
Thanks!
