free780

Well for Server 2016 RDS the time frame has been extended. But if your running LTSC you should run the VL version of Office. If you want Office 365 Proplus you need to be running Windows 10 SAC. I'd recommend 1709 at this stage. Basically if your using LTSC Microsoft presume you are keeping everything on prem or its a use case (Boiler Control,Medical Scanners,Thin clients etc). If you all in with Office 365 you need to stay current. So 1 Windows 10 update year. Autumn would be best as you get 30 Months Support Monthly updates to Office 365 Proplus.

It's the modern apps which update per user. You néed to allow the domain *. mp.microsoft.com so the app updates can download. You an force Group Policy to use Bits, WUDO is on by default which checks other PCs for the updates but if it fails to download updates from a peer it will update via Bits anyway. So it's best to force Bits. There's no caching option for store apps on a local server. I wouldn't block the domain.

Or a gentle push away from mapped drives onto share point.

Have you tried setting your proxy settings in the Chrome GPO rather than relying on the system setting. Also are you using WPAD as chrome looks for this unless disabled by Policy.

You could try a different switch port or another switch.

Or 11/18 for countries that put the date in the correct order. :runs away from americans:

I've seen this issue over the last 10 years. Close reader and reopen and the printers appear. I haven't seen it recently so I thought it had been fixed.

Stay clear of 1803. The gift that keeps on giving. 1709 seems the most stable at the moment.

Yep I remember back on 1511 *. *. mp.microsoft.com was using a lot of bandwidth. If your a office 365 org I think *. Microsoft.com is recommended to be allowed unauthenticated.

I think you have to all a domain unauthenticated and no SSL interception. I can't seem to find it. If you use fiddler and/or smssnif you should be able to find it.

https://docs.microsoft.com/en-us/windows/deployment/update/waas-delivery-optimization#download-mode Set the download mode to Bypass.

How do you have WUDO configured. I would force it via group policy to use Bits.

You can turn on Verbose logging for GPP Drive maps. I found if you don't use FQDN it can fail intermittently.

When your creating the template you can create the links with Edge and send to Start within Edge. Then I think it will honour the default browser on an exported layout.

I usually go \\domain\share\application\version. Mainly due to updates for applications. However if an application such as Autodesk has issues with long directory structures (and users require read access) I create a new share \\domain\vendor\application_version I use DFS in case the source folders need moving.

Well. I think patch Tuesday will be the release date.

It's because it's new and shiny or ofsted!

Don't show staff. It'll be like dual screens all over again.

I've wanted to test to standby with shared laptops. So they wake when charging and update.

I have over 10000. Just a Python script does the export from AD or a CSV if you export using powershell. The https up to Adobe's cloud. It would work if there wasnt a 2 device limit and the SSO worked like Office. A 5 device limit may work.

There are two methods of storing a profile via GPO to roam bookmarks and settings. The issue is that you can experience corruption when users change the version of chrome they are using. You can control the updates and push out a new version but you most likely won't be able to get your whole environment on the same version overnight. I couldn't find a silent command line to force updates. Also Google gradually push updates and turn on features. I assume if you sync via gsync accounts you don't hit this issue. Or have 1:1 devices.

I wouldn't touch LTSC unless you have a use case. Thin clients for example. Windows 10 isn't perfect. I'm currebtly reimaging to 1709 as 1809 isn't ready yet.

I found AD integration with user groups is very broken in PM. Apple don't seem to have have fully tested it. Though it looks like it might be EOL soon.

1903 - The stability update.

I've actually had the SCCM console get strange black bars and freeze. But I put it down to 3rd party addins and display driver. I get the occasional pausing but could be several 3rd party applications.