free780

I did a powershell script due to the certificate installation. It doesn't seem to install in a Task sequence but works from the software centre. Cubase do provide a admin setup utility so it will create Msis. I inherited USB dongles which we hide in PCs. Why on earth they can't provide a licence server I don't know. On macs you have to run Cubase as an administrator to click OK to give permission for the microphone on mojave.

1909 has been fairly seamless so far. I have in on about 10 PCs.

I'd use MDT. WDS is a tool not a solution. You can then specify reboot/shutdown at the end of the task sequence.

It took 2 weeks for me to get a new licence.

Thanks @smarties11 I've been chasing this issue for the last week.

Have you tried reseting the base with dism?

This is why I went with on prem. LDAP over the Internet gave me shivers.

It was written in the 2003/XP era. All those windows 10 Updates must prove too much.

It may get impacted by group policy that blocks downloads for on demand features from windows updates. I've upgraded to 1909 and had 0 issues. I have SCCM pulling out the apps I don't want. Seamless.

@sparkeh About 50 out of 2000 clients patched Office 365 Proplus 12130.20344 so I disabled the ADR. 12130.20390 still seems to fail. It looks like it's Bits or it's trying to use peer caching even though it's disabled. It fails to fallback to the CDN. Or the CDN is having issues. This reddit thread is helpful.

When it's not broken. For the Monthly Channel it doesn't seem to work at the moment. You can update 365 by downloading to a share and then running a command line to update office if you don't have SCCM.

Last Windows 7 is gone and policies and drivers. [emoji1]

The teaching staff could extend the display instead of clone so you don't display the notifications on the non primary monitor. The pinning might be possible by using the start menu layout but you'd probably have to target in the user context. Teams installs in the user context.

I have a RDS farm that was on Server 2016 and I moved it to 2019 in the summer partly for this reason. I would be tempted to move away from LTSC as if you keep Adobe software up to date its probably not tested with LTSC.

I was going to try and script click to run ro update straight from MS as I have the bandwidth and a maintaince window. To try and hit cyber essentials criteria you need to patch within 2 weeks. It looks like a BITS issue but how click to run is instructing BITS to start the job

Are you deploying to 1809 or above as the 2019 versions are not supported on any win 10 version that is older.

At least it worked. SCCM seems to be struggling with the 1910 updates this month. It may be bits related. Have you set your deployment to go out to MS if the content isn't avaliable?

Brave. Very brave.

I've got 1909 in my SUP. I've upgraded 4 PCs no issues yet.

Just a nudge if anyone else has had this issue. It seems to be a issue with Bits and SCCM. The cm client can't download the update. I've tried deleting the content and redownloading, manually updating works. I guess it's waiitng on MS. I even shifted my WSUS db in case that was the issue.

Having dealt with mac MDM management. Apple do not care about shared devices. They've broken Connect to Server in finder in Mojave. They've turned on privacy controls which you can't enable via the MDM 100%. We don't have chromebooks as we are quite invested in Office 365. Managing Shared Windows devices is so much easier than Macs.

About half of our servers are on 2019. No issues. It's just getting the support from vendors as some haven't tested on 2019 yet.

I have this deployed. No idea if it's being used.

So after saying WSUS has been OK the last few months. Office 365 Proplus updates are playing up. Oh what joy!

You can just use Windows Update for Business with Intune or without. If you want reporting you need intune I believe. WSUS isn't dead but it does need looking after like any server. Adding all products is bound to break it. There are numerous blog posts from those in the Configmgr community about tweaks you need to make to WSUS. Don't manage it via the mmc. Use powershell or Configmgr and use it as a SUP. Mine has been pretty stable on 2019 since I moved it from my Primary Site Server and gave it sql express for its DB. I try and clear out older updates and legacy products. Sometimes I think just go for WUfB but I don't think it's quite there. There were some announcements at Ignite that bring some more features which will be in public preview soon