Snoop78

Hi All, I have a tricky report that the client is needing and I am struggling to get one out of SCCM. Scenario is this: 1) I have a SUG with all the approved patches in it (this is not a full list of Microsoft approved due to application restrictions) 2) I have a collection with all the servers listed in it (77 to be precise) Client wants a report stating the server name and then listing each update that is outstanding crossreferencing the collection with the SUG. Is there a way I can get to this point without having to run 77 seperate reports and then spending a lot of time mashing them into one report for the client, as I am sure in a month or 2 they are going to ask for the same report over again Thanks in advance Ben

We have a central solution for a lot of our clients and have a CAS, 2 x Primary Sites and about 14 Management points (in the clients domain). I had run the WSUS cleanup on the CAS but not on anything else. All management points other than 1 were fine, it was not until I completed the WSUS cleanup on the management point with the issue that the Catalog Version finally came up to the right version.

Is there any info re perfoming the cleanup from the CAS down or the management points up. I an getting conflicting info on my google searches some people are passionate about it being bottom up always and a few are top down always? Any real world clarification would be appreciated Ben

We are running SCCM 2012 CU4 and have a CAS - 2 x PRIMARY sites - Multiple managements points. We have succesfully had it working in multiple of the management point environmetns but i have come up against a problem child management point. I have setup a GPO to assist with the client push as the management point is in an untrusted domain from the Primary Site. Create the following Registry Key to lock down SCCM Management Point HKLM\Software\Microsoft\CCM\AllowedMPs Needs to be a MultiString Content: SERVERNAME.DOMAIN.COM.AU WSUS Settings Computer Configuration Policies Administrative Templates Configuration Manager 2012/Configuration Manager 2012 Client Configure Configuration Manager 2012 Client Deployment Settings Needs to be Enabled CCMSetup.exe /noservice /mp:SERVERNAME.DOMAIN.COM.AU DNSSUFFIX=DOMAIN.COM.AU SMSSLP=SERVERNAME.DOMAIN.COM.AU SMSSITECODE=A01 Configure Configuration Manager 2012 Site Assignment Needs to be Enabled Assigned Site: A01 Site Assignment Retry Interval (Mins): 60 Site Assignment Retry Duration (Hours): 12 Windows Components Windows Update Specify internet Microsoft update service location Needs to be Enabled Set the intranet update service for detecting updates: HTTP://SERVERNAME.DOMAIN.COM.AU:8530 Set the intranet statistics server: HTTP://SERVERNAME.DOMAIN.COM.AU:8530 When I get the client server (that already has the GPO applied) (Server 2012 R2) I get the following error in the WindowsUpdate.log - WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037 All the reading I can find keeps pushing me to installing all the updates for WSUS 3.0 SP2 to allow it to recognise Server 2012. In our case we are running WSUS on a 2012R2 serever (version 6.3.9600.16384) I am at a loss and my alternative to achive in the timeframes i have is to complete it manually Any assistance would be greatly appreciated. Ben

Still waiting for the Microsoft Support call to be created. In the mean time we have created our own package for the Client push and we deployed it today to some dev servers and added the registry entry into the servers via existing SCCM GPO. So far it appears to have resolved our issues and we are progressing to a production environment with the GPO and the Client upgrade. Thanks to all that have assisted with this issue and hope this helps others with similar issues.

Upgrade has been done, we are having issues with the "Configuration Manager Client Package" not getting to the Distribution Points and the Source Version in the Packages window climbing in number. Found an article with what appears to be the same symptoms http://www.windows-noob.com/forums/index.php?/topic/9410-configuration-manager-client-package-keeps-updating/ We are reluctant to go diving into the SQL Database to fix though. Once we have this resolved we will be able to start upgrading the clients and determine if the CU3 has fixed all our issues.

I will check these out, thank you. I will let you know how we go resolving this. I have just looked and we are only running CU1, going to look into the CU3 and the process to update it.

Thank you in advance. We have quite a complexed setup of SCCM 2012 R2 and due to the complexities it has some tricky hurdles to get over. We have a centrally managed environment that we then manage external domains from, but we are not able to get a domain trust in place and limited on the ports allowed through each clients firewalls etc, due to this we are not able to put in a secondary site (which would probably fix most things) but have to go with a management point on a server within the external domain. The issue we are having which is apparently a feature is that our clients are taking a round robin approach to find a management point but as you can imagine the only management point they can actually see / communicate with is the one in their domain. Does anyone know a way we can lock the clients to only communicate with the Management Point in their domain and not to try any of the others. Current Workaround: On clients that are not finally coming good we are having to put all the management points FQDN's into the Host file but all pointing at the IP of the local domain management point. As you can imagine this is not sustainable in the long term nor desirable. If there is a way to lock the clients to only want to communicate with their local Management Point I would love to know what it is