nmocean
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
I just started working with SCCM and WSUS about a month ago as I was tasked with deploying both for our organizations infrastructure. Today I broke the cardinal rule of IT and decided to update SCCM from version 1906 to 2002. Of course I know don't ever do anything big on Fridays but I was a gluten for punishment.
The Issue:
I was able to get Version 2002 to install without any major issues but when I checked my WCM.log file I saw and error that struck me as weird.
"Remote configuration failed on WSUS Server"
The interesting part is before that line in the log it says that it had connected to the Remote WSUS server.
In the wsyncmgr.log file I get to following errors:
I am using SSL and before the update everything was working that I know of. I never saw these issues in the logs before doing the update. I have also restarted both servers to see if the Default "Did you turn it off and on again" would work but it has not had any effect. I have been digging online for anyone else that might have had this issue but I have not seen anything that would relate to this situation. I am hoping that I don't need to resort to wiping the remote WSUS server but if that is what needs to be done then I will have to. I did see in this article that it was a fix for another WSUS issue but I am unsure if it is related.
I know it is Friday and I will probably not be on this weekend but if anyone can provide me with some insight or needs more details on the setup of the environment then let me know and I will provide it. Thank you a head of time.
The Issue:
I was able to get Version 2002 to install without any major issues but when I checked my WCM.log file I saw and error that struck me as weird.
"Remote configuration failed on WSUS Server"
The interesting part is before that line in the log it says that it had connected to the Remote WSUS server.
In the wsyncmgr.log file I get to following errors:
I am using SSL and before the update everything was working that I know of. I never saw these issues in the logs before doing the update. I have also restarted both servers to see if the Default "Did you turn it off and on again" would work but it has not had any effect. I have been digging online for anyone else that might have had this issue but I have not seen anything that would relate to this situation. I am hoping that I don't need to resort to wiping the remote WSUS server but if that is what needs to be done then I will have to. I did see in this article that it was a fix for another WSUS issue but I am unsure if it is related.
I know it is Friday and I will probably not be on this weekend but if anyone can provide me with some insight or needs more details on the setup of the environment then let me know and I will provide it. Thank you a head of time.
