Let it begin synchronisation > Next > Finish. Select the ‘ type‘ of updates you require, (I typically never select Service Packs, Update Rollups, or drivers, (but that’s my preference.)) > Next > Select automatically and set it for early in the morning > Next.
Select the languages you require > Next > select the products you want to update > Next. Start connecting > Wait for a while until it will let you continue.
Next (Unless you have an upstream WSUS server) > Next (Unless you have a proxy server). Remove WID and WSUS from an administrative Powershell window If yours is using SQL you will need to remove that independently, (assuming SQL is only doing WSUS of course!) Mine’s a small typical deployment using WID (Windows Internal DataBase), to prove this navigate to C:\Windows\WID, and look for SUSDB. Note if you have computer groups but don’t reference them with your GPOs you don’t need to do this. Warning: If you have ‘Computer Groups’ setup in your GPOs telling client machines that they should be in different computer group object in your WSUS deployment, then take a screenshot of all the group names before you start so you can manually add them back in after rebuild. Here I’m removing WSUS and re-installing it on the same server, I already have multiple GPOs setup pointing my clients to the WSUS server so I don’t need to do that part. So let’s say your a conscientious tech and you’ve taken over WSUS from someone else who let it get into a state! There comes a point when its simpler to wipe it out and start again, it might be simpler to create a new server/VM and reinstall from scratch, if that’s the case, do that instead of this! (Remember any GPO’s pointing client to WSUS will need updating, unless the new server has the same FQDN as the old one though!) Then I’m going to care as much as you do! Solution If I look at your WSUS and see ‘This machine has not reported in for 12 months”. If you run WSUS, log into the the thing at least once a week, sort out reporting problems, approve updates accordingly. I don’t like WSUS, the product is OK (ish) the problem with it is, every time it’s deployed, typically the person it was deployed for never looks after it, or manages it properly, and months/years later it becomes a massive ‘bag of spanners’, which is never the client’s fault, it’s always the poor guy who built it, or the support company’s fault.
0 kommentar(er)
