WSUS Clients status not yet reported

Well about two days ago our WSUS server had crashed and I pretty much had to reload it. Now the problem I'm having is that all of the clients show as not yet reported. I've checked a couple things and first problem I found was the Virtual Directory named Selfupdate was not in IIS. I had to create that myself and set the rights and paths as follows:

Directory: %ProgramFiles%Update Services\SelfUpdate

Security: Anonymous Access Enabled

Now that is all that I found and it seems there is more to it. You also have to set

Security: Like above but also set Integrated Windows Authentication.

Execute Permissions: Scripts Only

From a client Computer I ran the folowing command:

wuauclt /resetauthorization /detectnow

Before I did the above the log file c:\windows\windowsupdate.log had the following errors/warnings

Cached cookie has expired or a new PID is available

Once I set all the above my client had connected and downloaded new updates. A good link to follow is

IIS Settings For WSUS

Installing IIS on server 2003 for SMS

Well found a good link for the correct way to install IIS for SMS on windows server 2003. Follow the link.

Installing IIS

mp.msi exited with return code: 1603

While installing the MP role on SCCM 2007 my MPsetup.log file showed me the mp.msi exited with return code: 1603 error message. The following fixed that error and my MP installed successfully the next try.

BITS is not installed with IIS. Goto

add/remove programs > add/remove windows components > application Server (click details) > Internet Information Services (Click Details) > *CHECK* Background Intelligent Transfer Service[BITS] Server Extentions

Make sure it checks both options under the details of BITS. Click oks and after the install try installing the MP role again and it should be successful.

SCCM SMP 500 error

Just stumbled across the top solution. I'm going to try it now and see if my error goes away. Seems over night the error has happen 4 times. I'll post updates if it fixes my error

@@@@@@@@@@@@@@
@@@ SOLUTION 1 @@@@
@@@@@@@@@@@@@@

Issue: MP Control fails with HTTP test request failed, status code is 500, 'Internal Server Error' on a Management Point running a 64-bit OS hosting 32-bit (x86) based IIS. The MPControl log contains the following:

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 1/23/2008 5:53:30 PM 4792 (0x12B8)
Http test request failed, status code is 500, 'Internal Server Error'. SMS_MP_CONTROL_MANAGER 4792 (0x12B8)

The IIS Logs may also show the following:

W3SVC1 192.168.0.35 CCM_POST /ccm_system/request - 80 - 192.168.0.105 ccmhttp 500 0 193
W3SVC1 192.168.0.35 CCM_POST /ccm_system/request - 80 - 192.168.1.109 ccmhttp 500 0 193
W3SVC1 192.168.0.35 GET /SMS_MP/.sms_aut MPLIST 80 - 192.168.0.35 SMS_MP_CONTROL_MANAGER 500 0 193
W3SVC1 192.168.0.35 CCM_POST /ccm_system/request - 80 - 192.168.0.61 ccmhttp 500 0 193

Browsing to http://SiteServer/SMS_MP/.sms_aut?MPlist returns a 500 as well.

Cause: This problem occurs because the ASP.NET registry keys are missing. The ASP.NET registry keys are missing when you install ASP.NET after the Enable32bitAppOnWin64 Microsoft Internet Information Services (IIS) metabase setting is set to a value of 1. Because IIS is configured to run in 32-bit mode, the ASP.NET installation does not create the ASP.NET registry keys in the 64-bit registry. The ASP.NET installation creates the ASP.NET registry keys only in the 32-bit registry.

Resolution: To resolve this problem, follow these steps for 32-bit or 64-bit mode:

To enable 64-bit mode:

1. Click Start, click Run, type cmd, and then click OK.

2. To enable the 64-bit mode, type the following command, and then press ENTER:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

3. Type the following command, and then press ENTER:

cd C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727

4. To install the 64-bit version of ASP.NET, type the following command, and then press ENTER:

aspnet_regiis -i

5. Type the following command, and then press ENTER:

iisreset

----

To enable the 32-bit mode:

1. Type the following command, and then press ENTER:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

2. Type the following command, and then press ENTER:

cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

3. To install the 32-bit version of ASP.NET, type the following command, and then press ENTER:

aspnet_regiis -i

4. Type the following command, and then press ENTER:

iisreset


@@@@@@@@@@@@@@
@@@ SOLUTION 2 @@@@
@@@@@@@@@@@@@@

In management Console I just started getting the following error:

SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error

So far the fix that works 99% of the time is as follows

1. Remove the MP role and reporting role by highlighting the roles on the server and deleting them. Check MPSetup.log to make sure it is fully uninstalled.

2. Remove IIS

3. Reboot

4. Delete the Inetpub folder (C:\inetpub) I renamed to inetpub_OLD for safety

5. Reinstall IIS - I used server management and added the application server role back. Make sure to enable WEBDAV in the IIS console under web service extentions. **ALSO** add remove windows component and make sure BITS gets installed. otherwise error 1603 will show in the MPsetup.log

6. Add back the reporting point.

7. Add back the MP role and check the box to allow clients to use the MP. Check The MPSetup.log to make sure it install is successful.

8. Watch the MPcontrol.log file. May take up to 20 minutes for the normal HTTP 200 messages to appear, but it should work and communications should resume with your clients.

So thats it. Main things to check are the logs to make sure the install and unisntalls are successful other wise other errors may occur. I usually do a search for the log files. Also make sure BITS and WEBDAV are setup correct. WEBDAV just needs to be allowed. BITS needs to be seleted

Sccm 2007

For those that don't now what sccm means it is System Center Configuration Manager. Its pretty much the upgrade from SMS 2003. Its just about the same pain in the neck to install and configure.. I found a few sites that had semi-walkthroughs on installing and configuration. I followed step by step and basically still was faced with many errors. SQL actually was piece of cake as I haven't had to touch it since I clicked finish...

So after about 2 and a half days I think I've finally got it fully installed and working. After the second day of researching errors and trying various fixes about 1/4 of my clients were accepted and installed. I've been trying to clear the error messages and worry about the warnings at another time. So far I've had to reinstall IIS about 2 - 3 times and make sure WEBDAV was allowed. I've also had to remove roles and reinstall them from the System Management Console. I think I redid the MP about 2 - 3 times as well. I was getting 500 and 501 errors about every hour and for the last 3 hours it hasn't come back yet ::crosses fingers::

Basically for anyone trying to get it installed and are seeing MP or SMP errors, those are your roles so you may just need to uninstall the role, check the log files to make sure it finishes successfully, then reinstall the role. Also I had my boundries setup for AD but it seemed to work better with IP subnet. Well I'll find out tomorrow if I'm all set to go on and try other tasks such as software updates and pushes. Remote management seems to be working. I'll try and get some reference links to the sites that did help me..

Good Luck!!