Michael

Enter duff proxy settings.

That's correct, untagged ports shouldn't be able to communicate, only tagged ports can. Untagged should only work on its own native VLAN. I guess it also depends how your router has been setup too.

Just wondering - is it possible to re-install Discover, even though it's at the correct stated version?

The first line is a clue - I presume you have tried updating the Discover DB? Could it be that x version of the SIMS DB doesn't play nice with x version of the Discover DB? Would be good to confirm versions on the working setup.

That's fantastic news Al, as it saves schools a fortune buying third party solutions! On an unrelated note, is it now possible with v4.5 to separate Report Concern contacts to a specific OU within the structure, rather than the whole structure?

Some GPOs will not work with Pro. All GPOs will work with Ent/Edu where applicable.

Windows 10 - Cover Up Edition

Are the application files and DB on the same physical server, or separate servers and are these virtualised? If separate servers or separate VLANs (unlikely), then firewall is a possible issue. Be interesting if Capita actually did a 'like for like' test of your configuration, as their test setup may not reflect yours whatsoever.

You're on the right lines, but really Capita should be able to sort these issues for you.

If you nominate a switch port which is tagged with both VLANs, then of course you can access the controller via your native range. This would be the easiest/logical solution to your issue.

So it sounds like an authentication problem.

Named pipes for example, which by default are disabled. - - - Updated - - - Thing is, I'd expect your Capita support to identify something that obvious. It's fairly typical that you have to relax SQL settings from the default with any SQL install.

Are you sure (stab in the dark), it's not the default locked down SQL Server settings, rather than a SIMS issue?

If you use Disk Cleanup (within Windows itself), you have the option of removing installer files.

Yes, if you later remove the PolicyDefinitions folder, Windows Server will revert back to its default database of files until a new PolicyDefinitions folder is created. As I say, in mine I include policies for Windows, Office 2016, Classic Shell and Chrome.

I know this discussion was started in March 2017, but the May 2017 update is solid. I've yet to test the June 2017 update, but I'll be honest, I don't apply every update every month. It really depends what's fixed and if end users are experiencing issues.

Then you're good to go, there should be no problems.

It depends - do you have a PolicyDefinitions folder already? If yes, then it depends what's in that. If you don't then it just means you're managing Windows. Windows GPOs are cumulative, so will contain settings from Win 2000 to Windows 10. Office GPOs or other are not. You just download the correct ORK Tools for your version(s) of Office, so you could for example manage Office 2010, 2013 and 2016 using their GPO sets. Optionally you can manage Chrome and Classic Shell this way too... Good luck!

Yes, you need to create a PolicyDefinitions folder within: C:\Windows\SYSVOL\sysvol\%domainname%\Policies\PolicyDefinitions Within that, you should have en-US (for language files) and admx files in the root. You can also add Office Resource Kit (ORK Tools) within here too to manage Office.

The lock screen isn't a major issue in my view. It doesn't affect the core functionality of the machine, it's just desirable to have X, Y, Z wallpaper. I'm sure Microsoft will fix it in the near future - so long as you definitely have it working on one machine (saying running 1607), then at least you're covered the setting is correct, but it local or a UNC path.

No major issues my end no.

I can't help but notice Microsoft seem to release a good OS, then a bad OS again - 1507 = Good 1511 = Bad 1607 = Good 1703 = Bad...

I'd also make sure you have the latest or newer patch installed too. For example all my 2016 servers (physical and virtual) have the May 2017 update installed.

Similar to Java, you need to whitelist domains/IPs. Alternatively just point shortcuts at IE - this still supports Flash fully as standard.

Check Write Back Cache is enabled.