Also - a lot of info I gleaned from the web indicated a good workaround was to disable UDP for remote connections.
#CHROME REMOTE DESKTOP GET STARTED GREYED OUT PATCH#
I think there was a patch back in April to deal with that. I read about some specific issues with WindRDP - and how a black screen or frozen screen was an issue a while back. Gotta say - if I had not seen that random RDP screencap on the web, I may have hacked away at this for hours or days.Īnyone else see this disconnect with Wind(Specifically)? Is the "old way" deprecated now without my knowledge? How can RDP in one area of the OS be set to on while the other remains off? While I am for fresh revisions of core utilities as we move thru the "Windows as Service" model - what the heck is going on between my first dialog - which looks like it should turn on Remote Desktop the same way it always has for years - vs the "new" method contained within Settings? I slid it to on, closed Settings and instantly could connect to the new VM via RDP from my client workstation. Now - the screen-cap above is from my work PC - but on my test VM - the "Enable Remote Desktop" slider was set to OFF. Had never seen this before so I open that up: I messed around looking at a bunch of other things, reading a few articles on the Internet and then stumbled across one that referenced Remote Desktop Settings from within the Windows 10 Settings app. At first glance - I should be able to connect. The dialog looked normal to me - especially the Remote Desktop panel:įor years - I have ensured RDP is enabled via the registry - in my case I have a tweaks script - which bakes itself into my Task Sequence during the MDT install. My first stop was to right click in the "This PC" icon and then Properties. Simply could not connect to the VM after it was set up. The build was fine, deployed fine but for the life of me I could not get RDP to work.
Over the weekend - I built a new Windows 10 v1809 image via MDT for deployment to a couple of test VMs.
0 kommentar(er)
