Instructions here () and followed Step 1 to list and then delete the 3rd party categories and update data. In my case, SCUP had previously been used and thus there was a lot of 3rd party (Dell, Adobe, etc) update metadata in my WSUS database. I was able to resolve the issue by looking closer at WSUS itself, and cleaning it up. ![]() ![]() I was experiencing the same issue with clients not communicating with WSUS (via SCCM CB). I'll share my experience in the event that it might help someone else. Otherwise it looks as if there are a plethora of diagnostics available to help solve problems with WSUS.ĭiagnostics WSUS site: WIKI WU_E_REDIRECTOR_UNKNOWN_SERVICE - 0x80245004 - (20484) The service ID is not supported in the service environment.īut it looks as if that one cascaded from the first.įWIW I think the WSUS forum is likely to be able to give more informed comment about your traces at whatever level you manage to make them have. Instead of concluding that 0x8024000D was the problem I think the seminal error wasĠx80240042 WU_E_UNKNOWN_SERVICE The update service is no longer registered with AU. ![]() Maybe you need to make yours verbose too. What is that showing? I see one trace involving IPv6 and another involving IPv4?īTW someone else a while ago had to use WindowsUpdate.log at a high verbose level to solve a WSUS problem somehow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |