Some Trouble with setting up WSUS

[AlteredAdmin]

Standing up a new MP/DP also making it a Software update point, on a server 2022 fully patched. When a new server comes out i try to make a MP/DP/SUP, for sccm just to get something new in there and make sure that works for a while, before standing up new one for the other boundary groups/ locations

Like i have done in the past i install the feature and roles so that way when i add the server to sccm, those are already there.

 

 

• BITS
  
• differential compression
  
• Data deduplication
  
• ISAPI Extensions
  
• Windows Authentication
  
• IIS
  
• IIS 6 WMI Compatibility
  
• IIS 6 Metabase Compatibility
  
• Windows Server Update Services
  

However even before its added to SCCM I'm having some trouble with WSUS. Below is the error i get when i launch WSUS to do the post install things. And yes i rebooted before launching the WSUS, and this is happening before i touches SCCM.

 

Log file is located at C:\Users\USERNAME\AppData\Local\Temp\\WSUS_PostInstall_20211130T122430.log Post install is starting Fatal Error: The schema version of the database is from a newer version of WSUS than currently installed. You must either patch your WSUS server to at least that version or drop the database.

 

When i look in the post install log the only error i can find is

 

RAISERROR('Invalid schema version number', 16, 1) with nowait

I have tried Removing the Wsus and deleting the database but when i do that i says Unable to open the physical file "C:\Windows\WID\Data\SUSDB.mdf" when i reinstall the wsus roles

So i removed the server from SCCM the MP/DP was working fine btw, but since i felt like it screwed it up beyond repair i removed the roles and deleted the server from SCCM and deleted the VM. I'm now back to fully patched 2022 server.

Before i start adding things i wanted to get your input as to what the issue could be with WSUS?

Edited November 30, 2021 by AlteredAdmin

[Steve21]

Not sure if it's still broken, but there was an issue with the WSUS script for post install not fully working on 2022 which needed modification to get it to match versions

 

In C:\Program Files\Update Services\Database there's a version check script is it still showing it as scriptMinorVersion is something like 11? Which is below that 2022 is currently running so needs to be changed to 51 (need to take control of the file, change it and then reset ownership on it), then run the post install again

 

Don't have a server at hand to check, as only been dabbling with 2022 but guessing it might still be the case

 

Steve

[AlteredAdmin]

Not sure if it's still broken, but there was an issue with the WSUS script for post install not fully working on 2022 which needed modification to get it to match versions

 

In C:\Program Files\Update Services\Database there's a version check script is it still showing it as scriptMinorVersion is something like 11? Which is below that 2022 is currently running so needs to be changed to 51 (need to take control of the file, change it and then reset ownership on it), then run the post install again

 

Don't have a server at hand to check, as only been dabbling with 2022 but guessing it might still be the case

 

Steve

 

Thanks for this info when i get a chance i will check for that.

 

How did you find out about the scriptMinorVersion?

[Steve21]

Connect to your wsus database (either using sql management tools with \\.\pipe\MICROSOFT##WID\tsql\query for Windows Internals, or normal if you've migrated it to SQL), and run

SELECT * FROM tbSchemaVersion;

 

Will return what your database is currently, and compare it to that script, if it's higher than the script it seems to fail

 

Again, this was a while ago while testing so they might have released an update to fix it but seeing you said about it being fully patched guess it's still happening

 

Steve

[AlteredAdmin]

I know i'm late coming back, but it appears that Microsoft fixed this issue, if you stand up a 2022 server. Make sure to run all the windows updates, then you can setup WSUS, and it just works.

 

Wanted to update incase any one else found this thread.