Everything I find on the internet is nice but does not represent KStars in the version I found on the astroberry nor the updated version. I have to be missing something but I can't find out what it is. I know it should be easy but I am not able to do so. On the other hand, the laptop has the power needed but I can't connect KStars for remote access. I read that the raspberry 3 B+ should have processing power to do the job but I seems to be otherwise. When the exposure is completed the image is downloaded and as soon as downloading finishes KStars disappears but the INDI connection remains active.

I can start imaging with my main camera but not while guiding and I can start guiding but than I am not able to start imaging. I don't really mind at that point but it is weird.Ĭonnecting everything works fine but as soon as I try to start imaging I run into troubles. The first thing is really: if I start KStars everything gets slow. That is why I think I am missing something. I know it should be accessible but somehow I am not able to connect. When I disabled 'Windows Installer RDS Compatibility', the chained MSI was able to run.Thank you for your reply. 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.

Raspberry pi teamviewer freeze