[tlack]

Has anyone actually had any luck getting this working? Seems like such a revolutionary idea that I'm dying to try it, but no luck so far.

It took me a few tries (and a couple hours) to get one of their preconfigured AMIs provisioned, excruciatingly extract the GUID from Win2k8 (people actually work this way?), but now their weird HTTP bouncer endpoint doesn't seem to be connecting at all..

[jack57]

I'm in the same boat. This is pretty frustrating considering I'm paying for this special GPU instance by the hour.

[tlack]

Are you aware of any support boards or anything like that on which we could get resolution?

[sandyman]

http://render.otoy.com/forum/viewforum.php?f=70

[jack57]

http://render.otoy.com/forum/viewforum.php?f=70 I started a thread when I could not find the AMI (honestly confusing that you must launch it through the AWS marketplace outside of the console), but now I've updated it with my current problem. Perhaps we should start a new thread for this issue.

[bilbo0s]

So I went to try this out and...

nothing.

Just like you said. It doesn't connect using their prescribed aws.otoy.com link.

I'm waiting to see if anyone actually ever gets this to work.

[sandyman]

Use the GUID=xxx user data when you set up the AMI. It use much simpler and much more secure than getting th GUID from RDP.

[bilbo0s]

Easier way to get the GUID in Windows is to use the command OTOY recommended..

wmic PROCESS get Caption,CommandLine | FIND "GUID"

but write the results to a txt file on the desktop. So...

wmic PROCESS get Caption,CommandLine | FIND "GUID" > Desktop\t.txt

I don't know why OTOY would NOT have put that value in the instance metadata on startup???

[sandyman]

You have two choices - supply your own GUID in the metadata, and this overrides the randomly assigned one, or look in RDP/ssh for it (which is more work than needed - highly recommended you add your own GUID, this way it doesn't need to be copied or grabbed from RDP/ssg)