Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DuplicateOutput problem with Windows Server 2019 #6

Closed
NitriKx opened this issue Sep 21, 2019 · 13 comments
Closed

DuplicateOutput problem with Windows Server 2019 #6

NitriKx opened this issue Sep 21, 2019 · 13 comments

Comments

@NitriKx
Copy link

NitriKx commented Sep 21, 2019

I've seen a comment about Windows 2019 Server that says "I do not actually recommend Server 2019, seems to break stuff...investigating.".
What is it exactly? I may help with it.

@NitriKx
Copy link
Author

NitriKx commented Sep 21, 2019

Ok I've done the installation on a fresh Windows 2019 AMI and the problems seems to be located when Parsec tries to "Duplicate":

Screenshot 2019-09-21 13 38 53

Not all the processes are running on the LOCAL_SYSTEM, may be the hosting part is handled by one of those two processes?

Screenshot 2019-09-21 13 52 43

@NitriKx NitriKx changed the title What happen with Win Server 2019? Problem with Windows Server 2019 Sep 21, 2019
@NitriKx NitriKx changed the title Problem with Windows Server 2019 DuplicateOutput problem with Windows Server 2019 Sep 21, 2019
@jamesstringerparsec
Copy link
Member

From memory -

  • Autologon fails to work properly so the desktop doesn't unlock on startup.
  • ViGEm controller drivers don't work on Server 2019.

Can you confirm these two issues?

@NitriKx
Copy link
Author

NitriKx commented Sep 27, 2019

I’ve not tried the auto login neither ViGEm.
The streaming is not working probably because one of the process is not running with LOCAL_SYSTEM permission scope

@Carl-Gustaf
Copy link

I'm keen on getting parsec to work on 2019 server too, is there anything I can test?

@jamesstringerparsec
Copy link
Member

Is there any practical need to have this compatible with Server 2019 other than "it would be cool" ? Right now there are some bugs with inputs with Parsec and Server 2019, so even if these scripts will be made to work correctly, there will still be input issues. From my understanding there are not many functional differences between Server 2019 and 2016 as far as cloud desktops go.

@Carl-Gustaf
Copy link

Thank you for your blazing fast answer! No there are no reasons why besides the fact that my machine is a server 2019, I'll just have to get a 2016 instance.

@wagnerbarretto
Copy link

Is there any practical need to have this compatible with Server 2019 other than "it would be cool" ? Right now there are some bugs with inputs with Parsec and Server 2019, so even if these scripts will be made to work correctly, there will still be input issues. From my understanding there are not many functional differences between Server 2019 and 2016 as far as cloud desktops go.

Right now one of the main benefits of server 2019 would be to install the Xbox game pass PC app. I'm not 100% sure that it runs on server 2019 because I never tested, but in theory it would since the app requires Windows version 1903. I know for sure that the app does not install on server 2016.

@jamesstringerparsec
Copy link
Member

jamesstringerparsec commented Nov 14, 2019

@wagnerbarretto You should boot up a server 2019 instance and see if xbox game pass does legitimately install.

@htappen
Copy link

htappen commented Nov 19, 2019

Wagner, did you ever figure out how to get Xbox Game Pass installed? I've tried copying packages from a valid Windows 10 instance over to no success

@wagnerbarretto
Copy link

@htappen not yet. I'm testing on AWS and the only Windows 1903 images they provide are core versions, which are versions without UI. So in order to make it work it would be necessary to either install the windows UI components on a core image (I think it is called Desktop Experience or something like that), or take an AWS full image and upgrade it all the way to version 1903. From what I saw, both things are not very straight forward to do and I didn't find the free time to try them yet.

There is another option that is trying to run Windows 10 on EC2 like described here. This would even bring the costs down since we would be paying linux prices.

Of course all this problems are AWS related. I didn't research other cloud providers and I also don't have access to bare metal hardware to test.

@htappen
Copy link

htappen commented Nov 21, 2019

Google Cloud also doesn't offer Win10 images, and Server Core as far as I can tell has no supported way to add in the stuff necessary for Windows Store. So, I think Server 2016 is the best bet until 2022 :)

I wonder if Win10 on Azure might be easy, too? http://www.ayushrathi.com/creating-a-win-10-virtual-machine-azure-portal/

@Nun-z
Copy link

Nun-z commented Dec 16, 2019

Hi, I was able to use Xbox Games Pass with Windows Server 2016. If you use the other repo that I forked (and made a single change to), it will work with Windows Server 2019.

Admittedly, the Xbox (Beta) app isn't installed, but the individual games can be side-loaded and run through the Microsoft Store.

Partial guide: https://www.reddit.com/r/cloudygamer/comments/e4rihi/guide_to_installing_microsoft_store_on_paperspace/?utm_medium=android_app&utm_source=share 

@jamesstringerparsec
Copy link
Member

Cloud prep tool now supports 2019, closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants