SCVMM 2012 SP1 (RTM) Deployment from VMM Console fails.

Question

Error During a library refresh, or deployment from template - It all fails:
Error (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server (MyServer).
Unknown error (0x80338105)
Recommended Action
1) Ensure that the Windows Remote Management (WS-Management) service is running on the server (myserver).
2) If the System Center Virtual Machine Manager service on your VMM management server is configured to run by using the machine account, ensure that there is not a group policy that does not allow adding machine accounts to a computer's Administrators group.
If there is, you can use one of the following workarounds:
  - Disable the group policy in Active Directory Domain Services (AD DS)
  - Modify the group policy to allow the VMM machine account in the Administrators group
  - Move the machine account to its own organizational unit (OU) and block the group policy from being applied
  - Reinstall the VMM management server and choose the option to run the System Center Virtual Machine Manager service by using a domain account, and re-add all of your virtual machines.
So, as soon as SCVMM 2012 Sp1 was released we decided that it was best to upgrade so we could utilise the new features of Server 2012 as a host.
The upgrade worked a treat. VM's deployed, Server 2012 worked. Anyway, a few days after deployment we start to see errors relating to WinRM and permissions (See end of the post). After a quick trace around we found some failed services, usually on a host
but sometimes it seemed to happen on the Library/Management server as well.
So, our setup is as follows:
Management/Library server = VMware  VM, Server 2012 standard, 6 GB memory, 4 vCPU's
Hosts = HP DL360p G7, HP DL360 Gen8 (we have a few of these), Server 2012. We also have a DL380 G7 on Server 2008 R2 Enterprise that fails as well, so it seems the error isn't O/S specific (I'm picking a VMM issue).
So I have tried many resolutions and now none of them work.
We have no restrictions on group policy for the local admin, this can be set manually, and works for that matter.
WinRM is working and the listening port is 5985 (I can see it working and listening via a "netstat -an")
Also, I have ensured many many times that all of the required services are up and running (SCVMMAgent, VirtualDisk managerment, WinRM) and initially these where at fault and a simple restart of each service (or even a full start from dead) fixed
it - Now it all fails. Even a library refresh fails. And all while each of the services required are up and running.

Answer 1

So, I have now tried a reinstall of the management server & made some changes
1- Changed the service account during the install.
2 - Added the service account user to the local admins group of each host in question.
3 - Tried "winrm /qc" .which lets me know its already up and running and configured. Although I must admit, I'm not 100% sure how to use WinRM. From what I can read, this is like an express setup and ensures you are up, running and listening.
4 - Verified that WinRM is working of the right port (Listening ports dump below)
5 - Verified that I can connect to each port required for the SCVMM Management server.
BUT, it seems the error is still there and deployments still fail,
although the library refreshes correctly now.
Error (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server ( Myserver).
Unknown error (0x80338105)
NETSTAT Listening ports dump.
PS C:\Users\nzadmin> netstat -an
Active Connections
  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8000           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8100           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8101           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8102           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8103           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49170          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49201          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49211          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:57388        0.0.0.0:0              LISTENING
  TCP    172.23.16.69:139       0.0.0.0:0              LISTENING