Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING No Computers Showing 2020-08 Updates Required

  • Thread starter Thread starter ITGurl22
  • Start date Start date
  • Replies Replies 13
  • Views Views 2K

ITGurl22

Active Member
Messages
25
Solutions
1
Reaction score
1
Points
3
Out of 181 of my asset count, 0 of them are showing up as being required for the new August updates. Under the Statistics it says 181 assets are unknown and they last update was on 8/14/2020. I've run a Synchronize Software Updates, to see if that would trigger something and nothing has changed. All of my machines are on Windows 10 v1909 and I'm using SCCM v2002 with Console version 5.2002.1083.2000. I'm still new to this application, so any help would be appreciated. It looks like most if not all my machines are on Client Version 5.00.8790.1007. Could that be the issue? Do I need to update the SMS client on all my machines? I take that back, two of my testing machines have SMS client v. 5.00.8968.1021.
 
I figured it out. The Default Web Site in IIS for my SCCM server had stopped. When I tried to start it I received an error message:MicrosoftTeams-image.png
After further investigation, the binding settings for port 80 had changed to https. I deleted that binding and created a new one for port 80 with the http setting. I restarted the default web site and waited and hour. When I came back all of my client status said active instead of inactive.

This happened once before back in June. I'm wondering if it occurs after Windows server updates. Does anyone know why this keeps happening?
 
Do you have another website in IIS?

If you do which you should not, check this link here to check if there is another website that uses port 80 link

Windows updates will not do that.
 
The only other site within IIS is WSUS Administration, but it uses two totally different site bindings and port numbers. Could that be the issue?
 
in your default website, do you have an ip address assigned to the port 80 or you left it unassigned? do you have another webserver engine running on the server?
 
There is no IP address assigned to port 80. How would I check to see if there was another webserver engine running?
 
Try running the Powershell script that i linked above. Do you have Tomcat or nginx installed and running on the server?
 
I ran the script and it just shows the Default Web Site whih is SCCM and the WSUS Administration. No Tomcat and nonginx installed. I looked in event viewer and couldn't really tell what killed SCCM, but below is the most common error and sourcee (SMS Server) that I see:
On 8/16/2020 2:17:29 AM, component SMS_MP_CONTROL_MANAGER on computer SVR-SCCM.MCHENRY50.LOCAL reported: MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 404, Not Found.

Possible cause: Management point encountered an error when connecting to SQL Server.
Solution: Verify that the SQL Server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of Management Point Role (smsdbrole_MP) in the SQL Server database.

Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL Server SPNs are correctly registered. Review Q829868.

Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which the site is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which the site is configured to use.

Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.

Possible cause: The MP ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the MP ISAPI is configured to run under has not been denied batch logon rights through group policy.

For more information, refer to Microsoft Knowledge Base article 838891.
 
Here's something interesting....every time I restart the server since upgrading to 2002, the binding for port 80 (HTTP) changes to HTTPS.
 
I thought the latest hotfix rollup solved the problem for SCCM version 2002. I installed the hotfix rollup and immediatley afterwards port 80 http was changed to https. I deleted port 80, added it back as http and rebooted the server. When the server came back up it stayed at http. When I checked this morning, the port 80 was flipped back to https.
 
looks like its a bug with version 2002. is there an option for you to upgrade your CM current branch or 2002 is the latest?
 
I've already done that and read that article and the problem is still happening. I was going to try and upgrade to version 2006 to see if that fixes it.
 
  • Like
Reactions: Edy

Forum statistics

Threads
7,186
Messages
28,053
Members
18,330
Latest member
curtsmith
Back
Top