computer_expert

I'd rebuild the server at this point from a fresh VM with fresh media from VLSC and try again. There's some stuff in the updated section that you could verify here: https://docs.microsoft.com/en-gb/archive/blogs/reshard_sharps_blog/wsus-post-deployment-configuration-fails-on-windows-server-2012

Do you have a leftover WID DB located at C:\windows\WID\Data\susdb.mdf? That's the only thing I can think of that may be causing an issue.

That's odd - I've just set up a Server 2019 VM with SQL Express 2019 and it has worked first time. Does the use account use to install WSUS have permissions to the new WSUS DB? Uninstall WSUS, delete the DB and check IIS to ensure the 'WsusPool' Application Pool has been removed, as well as the 'WSUS Administration' site in IIS. Also delete and recreate the location where the WSUS downloads are stored. Once you've done this, try reinstalling WSUS again.

Have you tried running the post setup by opening the WSUS console rather than using server manager? I had a similar problem recently and I think this was what I did to fix it...

Try plugging both in. I think I had an issue on a 12th gen dell where it did this until I plugged both PSUs in.

Do you know if it is the PSU fan or not? Does it have redundant PSUs with only one power cable connected? If it isn't, look at the power settings/profiles on both the BIOS and iDRAC and see if adjusting both to see if it helps. Also check to see if the iDRAC reports any errors as some servers will ramp up the fans if it finds 'unsupported' hardware installed.

Set the following reg key to 1 (DWORD) and it should get rid of that for you for the old version of edge HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\DisableEdgeDesktopShortcutCreation Not sure if it works with the new chromium edge or not though.

Applocker or software restiction policies blocking the script from executing? Is the installer less than 90 days old? https://community.sophos.com/kb/en-us/127044#How%20long%20will%20I%20be%20able%20to%20use%20the%20old%20installers?

Are you using DFS or FRS SYSVOL replication? If FRS, you'll need to upgrade to DFS as the FRS stuff has been removed starting with server 2016 rs3: https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405

You should be able to get the key from another page. I don't have access to VLSC currently, but I think it was on a page called something like 'Relationship summary' which gives you a list of all product keys for products you are licenced for.

What happens if you search VLSC for SQL rather than SCCM? Just make sure you get the same version that is currently installed on your server as the keys will probably be different between versions. Stupid question, but you are clicking the download link/button aren't you?

Are you not able to run the edition upgrade (Maintenance>edition upgrade) from the SQL media to input the key? If you don't have the SQL media, it should be listed as an option in the part of VLSC where you download SCCM current branch according to replies in my quick search. A new SCCM release was pushed to the slow ring the other day (version 2002). I'd wait for the SCCM 2002 media to be released if you go down the route of a fresh install.

Good to hear it's working again. PKI can be a complex beast and stop a lot of things working when it breaks.

Have a look at the CRL locations on the NPS server certificate. If it has the old location, you'll need to revoke and reissue the NPS server certificate. I'm not sure if you need to do the same for a user certificate or not (I don't use AO VPN or user based certificates yet).

That will be the issue. The server cannot verify what certificates have been revoked so it will reject all certs even if still valid. For the expired CRLs, you should be able to generate new CRLS by opening Certification Authority, expanding your CA, right-click Revoked Certificates , click All Tasks , and then click Publish (do the same for delta crl too) I think the incorrect location is something to to with the CA Exchange certificate. Edit - yes, incorrect location is to do with the CA exchange cert having the old location: https://itcallswin.blogspot.com/2016/01/pkiview-ocsp-location1-error.html Don't forget to update the AIA and OCSP (if you use it) locations in the CA properties before doing the stuff in the link above - https://docs.microsoft.com/en-us/windows-server/networking/core-network-guide/cncg/server-certs/configure-the-cdp-and-aia-extensions-on-ca1

Run pkiview.msc on your CA server. Do you get any red crosses? If you do, this should give a good idea of where to start looking.

The unifi switches need the controller for the initial config, but it can then be switched off until you need to change a setting/update firmware etc. The edgeswitches mentioned above are standalone as far as i'm aware (but can be managed by UNMS if needed, UNMS isn't the same as the unifi controller though). Not much of a issue as you don't need POE but I think the POE edgeswitches only support the non standard Ubiquiti 24v POE. edit - On further inspection some of the POE edgeswitches support both POE types (ES-8-150W) but others don't (ES-10X). Even the non POE edgeswitches are still ~£50 ish more than the gs108tv2 (around £52)

You can only 'officially' redirect the desktop/documents/photos folders. You may be able to use gpo folder redirection to bodge it, but in my testing (a number of years ago I have to add), it caused sync issues and stopped working if the local user profile corrupted for any reason.

Just don't snapshot DCs then restore when it fails. You'll be in for a world of pain if you don't want to reinstall DCs: https://support.microsoft.com/en-gb/help/875495/how-to-detect-and-recover-from-a-usn-rollback-in-windows-server-dc Installing updates is best done by running sconfig from a command prompt on server 2016. They will take a while (hours...) per machine to install due to the well known issues with how long server 2016 takes to patch and microsofts lack of interest in fixing it.

If the certificate is from an internal PKI (such as active directory certificate services) you should use push the root certification authority public certificate to the iPad. That way the iPad should trust any certificate issued by the Root CA (subordinate CAs, NPS, IIS webservers etc) without a prompt.

Why buy it when you can download it for free?

This may help, but does seem like a long way round: https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/connecting-ipads-to-an-enterprise-wireless-802-1x-network-using/ba-p/1128842

Having experience of the dismal unifi USG devices, don't bother. I'd keep the juniper as that has NGFW and UTM capabilities unike any of the ubiquiti routers. Also that the unifi kit can't do SSL inspection/content filtering (think safeguarding...)

Avoid the unifi USG routers. They are awful. If there are features you want but are not yet supported, you are in for a long wait for them to be implemented (if Ubiquiti can be bothered - a good example is if you need to disable nat, you need to edit json files for it to stay permanent as you can't do it via the UI despite feature requests being open for years). Have a look at something like pfsense/untangle/sophos xg home if you have an old desktop/server hanging around and don't mind running it 24/7.

There's a checkbox to add the DNS name as part of the SAN in the certificate template properties (subject tab) but it only looks like it works when the info is retrieved from info in AD. Have a look here as well, but just be aware that the web pages here need to have ADCS web enrollment enabled: https://www.vkernel.ro/blog/configure-internal-windows-ca-to-issue-san-certificates Edit - just noticed that a few of the commands have escaped HTML in them so remove the & and replace with the ampersand character