script doesn't work on g4 instance about parsec-cloud-preparation-tool HOT 7 CLOSED

The g4dn issue is caused by AWS now hiding their drivers in a private S3 bucket, which means there is no way for me to find out the new driver without needing you to provide an AWS access and secret key. So I will need to refactor that part of the script to ask for those details.

For now... visit the AWS support site https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/install-nvidia-driver.html#nvidia-gaming-driver

As far as ParsecAuth goes, yea that's missing. It's waiting for a code review. Basically what you need to do for now is not use RDP and instead use VNC to log into Parsec.

from parsec-cloud-preparation-tool.

For the record, I got the same on a g4dn.xlarge instance
(all three things:

• the TLS errors
• the "no split method" error
• no ParsecAuth.exe
  )

What DOES seem to work pretty well is running the script on the pre-configured NVidia gaming Win 2016 AMI. That takes about 15 mins to set itself up the first time, but after that I ran these setup scripts, got the above errors, but you can sign in the Parsec over VNC and clients can connect and it runs pretty good (on a sample of one 2013-era game)

from parsec-cloud-preparation-tool.

Also experiencing these issues on a g4dn.xlarge instance.

from parsec-cloud-preparation-tool.

AWS now hiding their drivers in a private S3 bucket

But it still worked just the day before you did a new code update.

from parsec-cloud-preparation-tool.

I have followed the AWS instructions on installing the vGaming Driver & licensing it. Although Parsec detects the machine and can connect, the display resolution is not automatically set correctly,

--- and there's no input being passed to the machine [IE, seemingly no keyboard or mouse instructions.] Any advice? Had no problems in the past like this.

--- EDIT : -- Input is fixed by toggling the exclusive input mode on the host device, but strangely two virtual displays have been created.

-- EDIT2:
Hopefully this helps someone - I then fixed the double virtual display problem by uninstalling the Microsoft display driver, via device manager.

--EDIT3:
Actually, this did not solve the problem as now thew resolution is capped. The driver auto reinstalls even when using VNC rather than RDP.

from parsec-cloud-preparation-tool.

Hi guys, can you please try the executable below, this WONT fix the gpu driver issue but hopefully will let you see Parsec via RDP. Let me know if it helps.

https://github.com/jamesstringerparsec/Parsec-Service-Manager

from parsec-cloud-preparation-tool.

This issue is solved

1. Copy all text from https://raw.githubusercontent.com/jamesstringerparsec/Parsec-Cloud-Preparation-Tool/master/PostInstall/PostInstall.ps1
2. Open %appdata%\ParsecLoader\GPU Updater Tool.ps1 in Notepad, replace all text in the document with the text you copied from Step 1.
3. Save the file (do not Save As)
4. Run GPU updater tool on the desktop

from parsec-cloud-preparation-tool.