Start a Conversation

Unsolved

This post is more than 5 years old

F

254849

August 19th, 2013 14:00

Failed to create computer

Hi there,

I have a trial instance of vWorkspace setup in a domain, connecting to a Hyper-V 2012 server.  I can connect to the server through microsofts console fine and create VM's.  I created a template that I wish to use as a desktop and it is fully stopped and has no snapshots associated with it.

Unfortunately when I attempt to provision a computer through vWorkspace i get the following error,

"Create failed. ... . Return code 10060"

Any ideas what this means?

Nick.

44 Posts

August 19th, 2013 17:00

what are the steps you used to create the template and which provisioning mechanism are you using? for example, are you using Instant provisioning?

Kelly

August 20th, 2013 08:00

Hi Kelly,

I used the Hyper-V Manager to connect to the server and setup a Windows 7 x64 instance, then I stopped the instance.  It appears in vWorkspace but fails when copying the vhdx as far as I can tell.

Nick.

August 20th, 2013 09:00

I don't know if this is partly the reason, but when I attempt to initialize my hyperv 2012 server it comes up with this...

"Failed to remotely log onto the computer, Network path not found".

It's on the same domain and I can access it through the network fine.

August 20th, 2013 10:00

Hello Nick,

On the HyperV server, look in services and see if the Quest Hyper-V Catalyst service is present.

If it is, it means we've contacted it at some point and managed to install the Service so from the Broker try the following command line:

Telnet HyperV 5203

This will check that the Broker can reach the HyperV server on the correct port. You may need to install the Telnet Client role and obviously update the servername to match your actual server   If this fails, check the service is running and the port (5203) is open on the firewall.

However, if the service is missing, it means we never managed to install it, in which case check that you can ping the HyperV server from the broker and that it pings on an IPv4 address not Ipv6. If that works, try connecting to the C$ share as that User you specified in the Credentials page when adding the HyperV server to the vWorkspace Management Console.

Also, please let me know if you see any other Quest Services on the HyperV server.

Thanks, Andrew.

August 20th, 2013 11:00

I got a little further, 1 computer provisioned, but it won't let me log into it via the web portal for the user I have provisioned it for, it says this computer is currently unavailble.

So I have tried to initialize and install the tools on the server both of which fail to do so,  initialize fails due to data collector install failing. And the tools says that the server timed out.

August 20th, 2013 11:00

Hi Andrew,

I tried the telnet connection and it failed, so I disabled thefirewall completely on the server using the following command,

netsh advfirewall set allprofiles state off

now I can manage the computer remotely using the windows admin tools and also successfuly initialize the hyperv server.  I shall try and provision a computer again now.

August 20th, 2013 12:00

Hello Nick,

I'm glad the first problem is resolved.

For the next problem, we need to know what type of Provisioning you are doing.

For example, if you are doing instant provisioning, the template VDI needs to be

1. Joined to the Domain

2. Have PNTools installed

3. Have the Instant Provisioning tools installed.

(There is a more in-depth list in the Admin guide)

If you are doing traditional provisioning with Microsoft Sysprep, you need to make sure the VDI is NOT joined to the domain first

Thanks, Andrew.

August 20th, 2013 12:00

aah, steps 2 and 3 I have not done so I shall give that a try too.

August 21st, 2013 09:00

Hi Nick,

How's it going?

August 21st, 2013 10:00

Hi Andrew,

Unfortunately after installing the PNTools I still didn't have any luck, I couldn't find the Instant Provisioning tools to install onto the template VM.

I've spent the good part of 3 days on the system attempting to R&D something and I ended up looking at the site on IIS.  I have a basic understanding of how it works under the hood, but as setting up the system has taken so long thus far, including downloading stuff which is terribly slow here I'm going to have to park it for now.

So basically what I wanted to do was integrate a different authentication provider, but after looking at the login view it appears that the users credentials are passed back to the site and then that performs windows integrated / kerberos lauthentication on behalf of the user.  If that's the case then I doubt I can integrate with it as I need to use claims based authentication or at least have a way of authenticating a user without their Windows password as I've already proven their identity by that point.

Have you any idea if this is the case?  Many thanks.

Nick.

No Events found!

Top