Windows Server varieties don’t behave this way, but because Windows 10 is primarily intended for bare-metal laptop and desktop use cases, power saving features are enabled by default. I simply modified the power settings to prevent sleep and hibernation and the issue hasn’t happened again. I’m not sure if an incoming RDP connection attempt would wake a physical machine in this state, but sleep isn’t very beneficial to a VM. This tells me that VMware tools hasn’t checked in for a period of time. I only noticed this when I saw a blacked-out screen in the console preview and the lack of a hostname or IP address listed. The issue was that the Windows 10 VM was going to sleep. These codes were only reported on the Mac RDP client and Windows was more generic:Ĭlearly the message “Make sure the PC is turned on” garnered no attention from a seasoned IT professional like me, but in the end turned out to be relevant. The two error codes I kept getting (0x204 and 0x4) were not helpful and just led me on a wild goose chase. In addition to the 0x204 error, I also saw “Error code: 0x4” numerous times as well. Make sure the PC is turned on and connected to the network, and that remote access is enabled. The exact error message from the Remote Desktop for Mac window is: The only way to rouse it from this state was to open a direct console window from the vSphere Client, or to reboot the VM. Initially RDP worked fine, but I noticed that after a while I couldn’t connect any more. I had recently deployed a new Windows 10 based VM that would serve as an RDP jump box to access lab resources. In the Terminal (logged in as the user in question) issue the following, which will reset (kill and it will then auto-relaunch) the preference caching daemon, as prefs are AGGRESSIVELY cached in current versions of OS X.TLDR: Modify your power plan to ensure your VM isn’t going to sleep!
Go back to the User's Library and open the Group Containers folder. Navigate into Containers and set aside and (one of those is for v8, just pull them both aside). Within that user's Library (NOT the top-level Library folder),
Quit RDP on the Mac, hold the option key & click on the Go menu to enable showing the Library & select that. I believe the below might have been necessary after Catalina install though.Īnyone have this problem with folks remoting into Windows PCs?įound a solution here which seemed to work but appears to then fail afterwards. Mostly Solved: This error is fairly generic but in these particular computers they used a special port to connect.
0 kommentar(er)
