Cloud Prep Tool not setting up auto log in

[morningjon]

Hi, i've been attempting to create a new gaming pc on AWS but every time I run the tool it doesn't prompt me to set up auto-login. I'm also having issues with it recognizing my local controller on the cloud machine. AWS doesn't even register the controller as an unknown device within the device manager.

I'm using a g4dn.xlarge and pasting the script from here directly into PowerShell with admin privileges.

[Maladril]

+1 to this. Also, the GPU update tool doesn't really update even after it says it must reboot and inputing "Y". I'm on Google Cloud

[berniewatts]

Having same issue as @morningjon. on windows server base 16 and 19.

[jamesstringerparsec]

Auto Login has been removed as it is insecure, you now must log into the instance using your password.

My Xbox One Series X controller worked correctly over Parsec in Windows Server 2019

[morningjon]

Auto Login has been removed as it is insecure, you now must log into the instance using your password.

My Xbox One Series X controller worked correctly over Parsec in Windows Server 2019

HI James,

I found a script to take over this part so it's good there.

However, I'm trying to use an Xbox 360 controller on Server 2016 and it's outright not having it. I've reinstalled drivers and tried reinstalling the controller emulator to no avail. It worked fine on a machine I spun up about a month ago, but won't work on a new machine that I'm making. The controller shows up with no issues on the local machine.

[jamesstringerparsec]

You should switch to Server 2019

Auto Login has been removed as it is insecure, you now must log into the instance using your password. My Xbox One Series X controller worked correctly over Parsec in Windows Server 2019

HI James,

I found a script to take over this part so it's good there.

However, I'm trying to use an Xbox 360 controller on Server 2016 and it's outright not having it. I've reinstalled drivers and tried reinstalling the controller emulator to no avail. It worked fine on a machine I spun up about a month ago, but won't work on a new machine that I'm making. The controller shows up with no issues on the local machine.

[morningjon]

You should switch to Server 2019

Auto Login has been removed as it is insecure, you now must log into the instance using your password. My Xbox One Series X controller worked correctly over Parsec in Windows Server 2019

HI James, I found a script to take over this part so it's good there. However, I'm trying to use an Xbox 360 controller on Server 2016 and it's outright not having it. I've reinstalled drivers and tried reinstalling the controller emulator to no avail. It worked fine on a machine I spun up about a month ago, but won't work on a new machine that I'm making. The controller shows up with no issues on the local machine.

I tried that but as the Xbox 360 controller driver is no longer officially supported on 2019 I thought that might be causing the issue. I sourced a copy of it from the internet archive but experienced the same problem, hence my move back to server 2016

[jamesstringerparsec]

It works fine, I tried it today.

On Tue, 1 Jun 2021, 22:46 morningjon, @.***> wrote:

You should switch to Server 2019

Auto Login has been removed as it is insecure, you now must log into the instance using your password. My Xbox One Series X controller worked correctly over Parsec in Windows Server 2019

HI James, I found a script to take over this part so it's good there. However, I'm trying to use an Xbox 360 controller on Server 2016 and it's outright not having it. I've reinstalled drivers and tried reinstalling the controller emulator to no avail. It worked fine on a machine I spun up about a month ago, but won't work on a new machine that I'm making. The controller shows up with no issues on the local machine.

I tried that but as the Xbox 360 controller driver is no longer officially supported on 2019 I thought that might be causing the issue. I sourced a copy of it from the internet archive but experienced the same problem, hence my move back to server 2016

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/parsec-cloud/Parsec-Cloud-Preparation-Tool/issues/75#issuecomment-852433777, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGBUNXX44CNLOK5EQPEPDLTQVBJTANCNFSM45MWKFNQ .

[morningjon]

It works fine, I tried it today. … On Tue, 1 Jun 2021, 22:46 morningjon, @.***> wrote: You should switch to Server 2019 Auto Login has been removed as it is insecure, you now must log into the instance using your password. My Xbox One Series X controller worked correctly over Parsec in Windows Server 2019 HI James, I found a script to take over this part so it's good there. However, I'm trying to use an Xbox 360 controller on Server 2016 and it's outright not having it. I've reinstalled drivers and tried reinstalling the controller emulator to no avail. It worked fine on a machine I spun up about a month ago, but won't work on a new machine that I'm making. The controller shows up with no issues on the local machine. I tried that but as the Xbox 360 controller driver is no longer officially supported on 2019 I thought that might be causing the issue. I sourced a copy of it from the internet archive but experienced the same problem, hence my move back to server 2016 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJGBUNXX44CNLOK5EQPEPDLTQVBJTANCNFSM45MWKFNQ .

i'm spinning one up now to try yet again, but unless something has been changed in the prep tool i expect the same results. your comment above said you tested an xbox one contr

[morningjon]

didn't mean to close that! i'm spinning up a fresh 2019 server now to try once again, i'll let you know what happens