Same problem, same fix! Took me real long time, pulled a lot of hair, glad to saw this post! For me it was the WMI sec settings, they disappeared after a Windows patch round. My App sources are even physical boxes, so no movement or whatsoever involved.
All kudos!
Another thing we did to our problem server was to use a scheduled task to do a salvage repository on WMI
C:\Windows\System32\wbem\WinMgmt.exe /salvagerepository
It does this every morning after the server reboots. So far so good, although we did wind up applying 2 fixes at once, so I don't have proof of which one is truly helping.
YMMV.
Hey Simon,
Definately been through that process before including step 3. I will try it again and see if it works. If not I will open a case as well. I am sorry but I couldn't find the other link. I will post as soon as I do.
If you still get the 1010 errors then some of your servers have already dropped their wmi permissions. Double check all your servers to make sure they all have the permissions set.
We logged a support incident with MS support (113012410163979 in case somebody's interested), and Ithink the problem is solved now.
I have restarted both RDSH's and RDweb servers at least 10 times today, and haven't seen the issue reappear, but I still had some event ID 1000 and 1010 in the RemoteApp and Desktop Connection Management/Admin. Please give this a try if you have the same issue, and let us know what your results are. Mileage may vary, and use at your own risk and blah blah. :)
Here is the response I got from MS support. The part I think helped out was section 3 (last one) - Rebuilding the WMI repository on each RDSH and RDweb server.
Please confirm if you have perform the following steps:
==============
•Add the RD Connection Broker computer account to the TS Web Access Computers group on the RD Session Host server.
•Modify the DCOM permissions on the RD Session Host server.
•Modify the Windows Management Instrumentation (WMI) security settings on the RD Session Host server.
I noticed that you have added the WMI permission, please also confirm if the DCOM permission is corrected.
After that please try to reboot the RDS servers to test if this issue still occurs, if this issue still occurs on some servers, please collect the following steps:
=================
1. Please let me know the details for the RDweb failure, can you logon the RDweb of if the RemoteApp icons are unable to be listed. Please capture a screenshot to us.
2. Please perform the following steps on the affected server to test if the WMI basic query works.
-------------------
Run wbemtest, connect the namespace root\cimv2
Click Query… and enter query as:
Select * from Win32_ComputerSystem.
Note: If the WMI query works, above command will list the computer name.
3. Please try to rebuild the WMI Repository on the affected RDS server and the RDweb server.
=========================
a. Disable and stop the WMI service.
sc config winmgmt start= disabled
net stop winmgmt
b. At a command prompt (cmd), change to the WBEM folder.
cd %windir%\system32\wbem
c. Rename the repository folder
rename repository repository.old
d. Re-enable the WMI service.
sc config winmgmt start= auto
e. Run the following command to manually recompile all of the default WMI .mof files and .mfl files
cd %windir%\system32\wbem
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %sCheers
Simon
I to have had this issue. Whats differnt for me is the WMI permissions are constantly getting reset. Either on restart or overnight. Has anyone seen this? I've come accross this:
This one talks to writing a script to get them to repopulate but I am hesistant to do this as it looks like it was in beta when they were discussing this fix
http://technet.microsoft.com/en-us/library/ee891251(v=ws.10).aspx
I also went through all of this as well
http://technet.microsoft.com/en-us/library/ee891251(v=ws.10).aspx
I'm in the same boat as Howard, Martin and others. Our RDSH servers reset WMI settings on reboot, happens on 4 out of 5 servers. Pretty serious problem, since it breaks our RDWeb platform. >_<
Howard, you mention 2 links, but you pasted the same link twice. Could you find the link to the script you mention? I would like to have a look at it.
Oh, and our servers were NOT cloned. Clean installs from Windows Deployment Server.
Cheers
Simon
I to have had this issue. Whats differnt for me is the WMI permissions are constantly getting reset. Either on restart or overnight. Has anyone seen this? I've come accross this:
This one talks to writing a script to get them to repopulate but I am hesistant to do this as it looks like it was in beta when they were discussing this fix
http://technet.microsoft.com/en-us/library/ee891251(v=ws.10).aspx
I also went through all of this as well
http://technet.microsoft.com/en-us/library/ee891251(v=ws.10).aspx
Thank you very much for the fix to this issue.
We had a VMWare server crash and I manually moved the VM's to another host. During the move VMWare asked if the VM was copied or moved, I selected move.
When the server came up it did a WMI auto recovery (event ID 65) and reregistered some components (event ID 63).
The permissions for the "TS Web Access Computers" group was missing in Root->CIMV2->TerminalServices.
Just wanted to acknowledge. This solution worked for me. I was just initially installing RDWA, RDSH, and RDCB and encountered this issue :
| |||||||||||||||||||||
I had the same exact problem, and this solution fixed my issue as well. I also cloned a VM, then did a sysprep to change the SID which led me to this issue. Thanks to all involved, this was aHUGE help. I also wanted to add that in addition to modifying the WMI security settings to add the TS Web Access Computer group, I also had to re-import the security certificate(s) and re-add them to RemoteApp Manager under Digital Signature Settings - I hope this helps someone as this thread has helped me.
Thank you!!!
Also had this problem. But afer checking the group, dcom security, wmi security still no success.
After a lot of debugging figured out the the RDWeb server still was not able to do the WMI call to the RD hosts.
but after making the change below it works1. Start IIS
2. go to Application Pools
3. Select RDWebAccess
4. Go to Advanced settings
5. under Process Model change the identity to the domain administrator and password
6. do a iisresetAfter those changes it works for us.
Checked with a comparable situation here the identity was internal network tried to change it this and do a iisreset but did not work.
know the domain administrator has to much rights. Have to look into this later.Think the problem is related to the fact the RD WebAccess is also domain controller.
please let me know if this solution helps you, and let me know if the RD Webaccess is also domain controller in your situation
I attempted this solution as well as using a Domain Admin OR the Network Service account but changing this option breaks RD Web access entirely (yes I did do an iisreset).
The RD Web access will only funciton under ApplicationPoolIdentity.
Thank you that one, fixed my issue.
RD Web Access was not able to access the RD Session Host server ts02.--.com.au. Verify that the computer account of the RD Web Access server is added to the TS Web Access Computers security group on the RD Session Host server.
event 8 RADWebaccess
ThaAlso had this problem. But afer checking the group, dcom security, wmi security still no success.
After a lot of debugging figured out the the RDWeb server still was not able to do the WMI call to the RD hosts.
but after making the change below it works1. Start IIS
2. go to Application Pools
3. Select RDWebAccess
4. Go to Advanced settings
5. under Process Model change the identity to the domain administrator and password
6. do a iisresetAfter those changes it works for us.
Checked with a comparable situation here the identity was internal network tried to change it this and do a iisreset but did not work.
know the domain administrator has to much rights. Have to look into this later.Think the problem is related to the fact the RD WebAccess is also domain controller.
please let me know if this solution helps you, and let me know if the RD Webaccess is also domain controller in your situation
Thanks for this, I had run into this issue before after an MS Update that took days to get working again, after uninstalling the patch that caused the issue. I cannot remember the full patch ID, but the last part was 9917. Now after another update the issue shows up again.....
Changing this setting worked like a charm. Though I used "Network Service" over a Domain Admin account.
Brian
Also had this problem. But afer checking the group, dcom security, wmi security still no success.
After a lot of debugging figured out the the RDWeb server still was not able to do the WMI call to the RD hosts.
but after making the change below it works
1. Start IIS
2. go to Application Pools
3. Select RDWebAccess
4. Go to Advanced settings
5. under Process Model change the identity to the domain administrator and password
6. do a iisreset
After those changes it works for us.
Checked with a comparable situation here the identity was internal network tried to change it this and do a iisreset but did not work.
know the domain administrator has to much rights. Have to look into this later.
Think the problem is related to the fact the RD WebAccess is also domain controller.
please let me know if this solution helps you, and let me know if the RD Webaccess is also domain controller in your situation
1. Check if the "TS Web Access Computers" security group on the RDSH server has incorrect permissions in DCOM and/or WMI:
For checking DCOM security settings:
1. Start the Component Services MMC snapin
2. Navigate to Component Services -> Computers -> My Computer
3. Right-click on My Computer and select properties
4. Go to the COM Security tab
5. Under Access Permissions, click the Edit Limits button
6. Ensure that TS Web Access Computers is in the list, with all of the permissions set to “allow”.
7. Under Launch and Activation Permissions, click the Edit Limits button
8. Ensure that TS Web Access Computers is in the list, with all of the permissions set to “allow”.
For checking WMI security settings:
1. Start the WMI Control MMC snapin
2. Right-click the WMI Control node and select properties
3. Go to the Security tab
4. Navigate to Root->CIMV2->TerminalServices
5. With TerminalServices selected, click the Security button
6. Ensure that TS Web Access Computers is in the list with Execute Methods, Enable Account, and Remote Enable set to "allow"
2. Verify the RD Session Host server's firewall allows WMI calls.
3. Verify that the RD Connection Broker hasn't lost its trust relationship with the domain.
4. See if non-RDS related WMI calls can be successfully made to the RDSH server. This can help differentiate between a general WMI issue and an issue calling the RDS WMI provider.
Hope that helps,
Travis