DJ-1701

Hmm, interesting... I just installed 11.4 with the MST holding the code on a virtual machine with no network connection and it stated it was activated...

Well if you do need it in the future, in the Display settings you can give change the Scale and layout a go, which is usually at 100% to a value like 175%.

Happy Birthday Edugeek! Only two more years and you can head to College.

I assume the blurred out part was the door number. Would have been pretty hard to guess which house posted it otherwise. Very sweet.

Well I can tell you what's wrong... there is no } at the end of the ForEach statement. That's why I always format my code like the following, makes it easier to spot issues with those brackets. $usernames = Get-Content ForEach($line in $usernames) { $oldhome = "\\fileserver\home\$line\My Favourites" $newhome = "\\fileserver\staffhome\$line\My Favourites" robocopy $oldhome $newhome /E /W:1 /R:1 }

Might have to follow this from the Office 365 A1 Plus Licensing thread then and get in contact with the Academic Verification Engine Team.

This is what I have in 365 admin center for purchases. This should be how the licenses get assigned via 365 admin center. Then you just install Office 365 with SCA and they should be able to use it.

It's a good question... though it also depends if they really use Office that much at all at Primary level. Most of the time I see the Primaries using browses to access web content more than not. Could always create one login a class I guess.

Well all Office 365 plans have been renamed Microsoft 365 anyway, but if you had the Office 365 A1 Plus plan, yes shared computer activation will work fine.

If you have SSO setup, the accounts are automatically logged in when you load Office products, so you don't see any screen.

As long as your users are licensed it's fine. I just setup an installer for Microsoft 365 for Enterprise and Shared Computer Activation, since the users are all using SSO they are automatically logged in and it notes that they have a license to use the Applications.

Well, unfortunately I have just confirmed that Office 365 Device-Based Activation no longer works, and has been retired. Anyone lucky enough to be on EES rather than OVS can use the new method of Microsoft 365 Device Based Subscription for Education though for those of us that don't have that many staff to get EES I am wondering where to go from here... Only option I can think of is Shared Computer Activation... lucky we have SSO setup... but of course if anyone is using a stand alone school device with a local account, that's where things get interesting for us all... I thought I would start this thread first to notify anyone that starts getting PreflightCheck failed - wait: 463, PreflightCheck failed - wait: 459, PreflightCheck failed - wait: 390, etc errors. Second for anyone to discuss where they are going from here... or let us know there is a magical thing us OVS users can do to get DBA or DBS working. [sarcasm Self Test Complete].

Well, I have it up and working, and information about how that happened is in the thread, I would have thought @Dom_ would have it working too. Since a couple of years back I have been given more information on this though, and basically from what I have been told Quantum filtering cannot read internal IP's unless you are using the AD proxy. So what you need is either: 1) Use the AD proxy on the device and create rules based on your internal static IP for the device, and then create a profile in Surfprotect based on the internal IP... or if not possible... 2) Request the static internal IP address to be mapped to an external address, which then you can use to create a profile in Surfprotect based on the external address.

Bingo, bango, bongo, that was it. Many, many thanks! Remove (and afterwards re-added) previous thanks to all me to give you the Rep you rightly deserve.

Sorry, if I did say my master plan it might have helped... and again thank you so much, instructions do say CS, but will try CI, sounds logical if that is a requirement for WSUS that it should work!

Just installing the Database Engine Service and apart from the default, setting the SQL collation to SQL_Latin1_General_CP1_CS_AS as will be using for SCCM after WSUS can be installed and this was mentioned as required in their instruction.

This is so very wierd... installed from scratch on a workgroup, failed... installed from scratch with SQL 2017 instead... failed again. Same darn error.

The SQL does execute successfully, and I do get a different error when trying to complete post-installation (Fatal Error: Could not find stored procedure 'dbo.spSetDefaults'), but unfortunately when deleting the DB and running the command I just get Fatal Error: Database creation failed. I will continue battling with that error and as you suggest installing when the server is in a workgroup. Many thanks for your help.

Please tell me there is a DIY store around the corner called 'Hammer Time'.

Yeah, this was from fresh ISOs from VLSC and I have rebuilt the VM a few times before I started using Snapshots. As in line with my bad luck, that's one of the articles I have followed to configure from the command prompt which also failed. Thanks very much for your helpful posts, just typical that this weirdness continues to stump me as it has for a few days now.

Nope, unfortunately not. Enough to drive you crazy huh?

Ironically, this is a virtual server, been rebuilt quite a few times using the Domain Admin account with windows authentication to the SQL database and the VM currently has checkpoints on. Uninstalled WSUS, deleted DB, checked IIS no WsusPool nor WSUS Administration. WSUS download directory deleted. Reinstalled... same failure. How very, very odd...

Unfortunately that failed as well.

Ok, bit of an odd one... Windows Server 2019, SQL 2019 and WSUS... I can add the Role of Windows Server Update Services with the WSUS Services and SQL Server Connectivity options, but once that completes and I have to do the Post-deployment Configuration stage, it tries for a little while, then falls overs, I have tried with Server Manager, I have tried in Command Prompt to execute this, it always fails and appears to have the same message either on screen or in the log file... 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. My Google Fu can't find anything online that will help, have tried dropping the db and restarting, no joy at all. This works perfectly fine with WID instead of SQL, but we want to use this with SQL. Any ideas?

Thanks @Net-Ctrl, it's nice to get an honest overview from an established reputable company such as yourselves rather than some chancers I've heard contacting schools.