I have the same issue.
My situation is even more unacceptable as I have archived expired Virtual Machines that I need to retrieve information from urgently.
Because they have been moved to a different computer (to be stored and unlocked) they give the same error.
I also noticed the problem about two days ago but I thought I would allow a day or so for the problem to be fixed.
Frankly its getting a bit ridiculous, I have to catch an international flight in two days and the information I need to take with me is trapped in this nonsensical bullshit.
Hot tips for your developer: Don't enforce server contact restrictions without at least giving me the opportunity to enter my restrictions password and bypass it.
you can (or at least I can) actually remove the restriction, by
- Open the VM and enter the encryption password
- "Edit virtual machine settings" and enter the restrictions password
- "Options" -> "Access Control" -> untick "Enable Restrictions"
But that does not solve my problem at all
For some reason it wont even let me get to the point where I can go into the settings.
I get prompted for the encryption password (my machines are encrypted) and then it goes straight to the restrictions server error.
Like I said its nonsensical and frankly completely negligent.
I can't even run 3D acceleration on my machines because they need to run Office. I really am scratching my head as to how I am supposed to take vmware seriously.
I contacted support.
"...The query you have posted is technical in nature and you have reached the VMware licensing team.
I have also tracked the Order # 22817616 for Workstation 11 and can see that the order was placed on ' 2014/12/15'. As the complimentary support is for thirty days for Workstation 11, I won't be able to transfer the case to the technical team.
If you require immediate technical assistance, you can refer the link mentioned below to purchase Pay Per Incidence to avail technical assistance from our VMware engineers:.."
They want me to pay for the privilege of them telling me why their server isn't working correctly.
Needless to say I have begun the process of phasing out vmware in our organisation and removed it from consideration for our larger scale virtualisation plans.
We are facing the same issue with the policy server validation being set to http://rvm.vmware.com
We have been using the virtual machine for few weeks, and suddenly it would not boot up due to policy server validation; linked to the site http://rvm.vmware.com
1) What is the validation that is done by this url? Does it expect any output?
2) This validation stopped from Jan/22nd or Jan/23rd
3) We are working on a SAP provided VMWARE Virtual machine with policy validation set to above URL.
4) The error we are getting is that the Network Adopter not being recognized as the authorization failed from VMWARE
VMware has posted an error on its page Temporary Maintenance - VMware | United States
but does not give any timeline. Is this even an issue or not?
VM Ware Support is unaware of this message, and even to provide the very basic information (when will this get fixed, is there a defined workaround; is this a planned outage with a workaround or an unplanned outage) are unclear and we keep getting the standard error to raise a paid service ticket!
Any resolutions? Anybody else facing this issue?
We tried reinstalling the virtual machine, and we get the same issue as the first message on this thread:
"The restrictions management server must be accessible when this restricted virtual machine is used for the first time on this host.
Check your network connectivity and try again." (see screenshot).
VMWare insisting on a paid service desk ticket to even consider looking at the issue!
We are also experiencing this same issue, we once had working VM's and now they will not boot.
A few weeks ago, I started an official bug report for this, and as of now, the original Server is working for me again!
For future reference according to the support:
Basically a NTP server is what is required.
Although this did not work for all NTP Servers for me,
http://ntp3.sf-bay.org is working.
I also opened a case with VMware Workstation support and found the same resolution of using http://ntp3.sf-bay.org as the destination restrictions management server. The technician indicated it is a known problem with VMware Workstation version 10.