osecareer.blogg.se

Raspberry Pi (I used a RPi 3 Model B for this).

I hope they are a little more careful now ! Using VNC is just a little more complicated but you can find out how to set it up here. Nonetheless, Teamviewer’s ease of setup for remote access from the internet and my general use with it day to day, makes it win here since I’m not too fussed about security at the moment. Alternatives would have been any of the VNC flavours, which are particularly attractive in the face of the hacking, and subsequent mishandling of the situation, which TeamViewer suffered last year. First thing is first, and after looking at the possible solutions, I chose to go with TeamViewer for the remote desktop. Whilst linux allows us unlimited control using just a simple SSH, its sometimes nice to have a remote desktop just to manage files and directories, and for the rare occasions we might get lost in the terminal. I thought it would be a great little thing to use as a server for domotics, local websites and what not, so why not put it in a dark little corner and run it headless? And while we are at it, why not have a remote desktop? When I disabled "Windows Installer RDS Compatibility", the chained MSI was able to run.I might be projecting, but I believe a large portion of Raspberry Pi’s out there will be currently sitting in their owner’s drawers, not doing much at all since the hype around the device has settled down. When the Remote Desktop Session Host is enabled, by default, the Group Policy for the "Windows Installer RDS Compatibility" is enabled. I discovered this Windows Installer queuing behavior is controlled by a System Group Policy called "Windows Installer RDS Compatibility".

It is my guess the process that queues the installs is the "Windows Installer Coordinator". Apparently, the Remote Desktop Session Host allows multiple installs to be in process at the same time by queuing the installs.

The situation is arising from the new Remote Desktop Session Host introduced with Windows Server 2008 R2.