This is the wildest thing I’ve ever seen. My client was describing to me the problem, but I had a hard time believing them until I could see it reproduced for myself. When attempting to add direct memberships to a collection, sometimes it only shows returns a subset of the limiting collection and not the full list. I have found out that this is indeed a known bug/case that is open with the ConfigMgr development team.
When using the direct rule wizard and using a mouse with clicks, it only makes a handful of resources available from the limiting collection.
Then when repeating the steps but using the only a keyboard and buttons, all 1000+ systems became available.
The limiting “parent” collection was a created in a unique way that is new to ConfigMgr 2012. Of that collection, it’s limited to All Systems, but the memberships rules is using the new “include collections”.
What made this “funny” at my client is that literally every time I did a direct membership, it worked for me….and every time the client did it, it failed. We all couldn’t help but laugh because they thought I was somehow messing with them.
Ran into a situation with a remote CM12 console being unable to connect to a site server. According to the local SMSAdminUI.log file:
Transport error; failed to connect, message: 'The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) '\r\n Microsoft.ConfigurationManagement.ManagementProvider.SmsConnectionException \r\n The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryProcessor.ExecuteQuery (String query, Int32 blockSize, Dictionary`2 contextInformation)
Initial troubleshooting indicated that this was a problem with the Windows Firewall blocking remote administration. However, the firewall was off one the site server. Yet some posts indicated that the ports needed to be allowed, regardless of the firewall being on/off. So I opened up those, but it still couldn’t connect.
I took a step back and went to the basics – could I ping the FQDN? No, I couldn’t! Yahtzee! I could ping the short name just fine, so I just needed to have Windows map the IP to the FQDN. So as a quick fix, I just added an entry into the C:\Windows\System32\drivers\etc\Hosts file – and voila, the remote CM12 console could now connect!