As a member of the company domain, my laptop has to be connected to the domain network in order for Virtual Server service to be started properly.
11/5/20087:16:31 PM
Virtual Server
An error has occured during the creation of Service Connection points for Virtual Server in Active Directory. Either a domain controller is not available to complete the operation or there is a security problem accessing the domain. This operation will be retried the next time the service starts. Error 0x8007054b - The specified domain either does not exist or could not be contacted.
Remote Control
The service principal name for the VMRC server could not be registered. Automatic authentication will always use NTLM authentication. Error 0x8007054b - The specified domain either does not exist or could not be contacted.
Virtual Server successfully started.
The service principal names for Virtual Server could not be registered. Constrained delegation cannot be used until the SPNs have been registered manually. Error 0x8007054b - The specified domain either does not exist or could not be contacted.
I have to VPN back in every time just to start up Virtual Server. Does anybody know what I need to do to remove this behaviour? I cannot seem to find any article that discusses how to workaround this for a computer that is not in touch with the domain.
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral
Set your accounts to loca accounts... That should solve this.
I don't remember having to vpn back just to start virtual server when I'm still using virtual server... Cos I was not able to VPN back then...
HyperV a bit different, there are times I need to vpn back. But there are also time I don't... Haven't figure out the solution for that though...
Best Regards, Kit Kai, MVP (SharePoint Portal Server)
Virtual Server service is set to run as NETWORK SERVICE. Do you suggest to run as LOCAL SYSTEM?
help u see this sat