sparkeh

I had this in mind but it doesn't seem to have been developed since 2014.

@robjduk Just to double check. Are you looking in MSVLC at the agreement details and are you looking at the *end* date or the *renewal* date. To know when your licence runs to, you need to look at the END date, not the renewal (been caught out by that myself )

But the free version of PDQ deploy should do what you want right? https://www.pdq.com/pricing/

Yeah, as long as the sccm client is on it doesn't matter how the OS is deployed.

Tested the fix and can confirm it works.

There now appears to be fix for this. Apparently a fix can be sent out via SCCM. https://support.microsoft.com/en-us/help/4532996/office-365-version-1910-updates-in-configmgr-do-not-download-or-apply

Co-op Vegan Festive Feast is absolutely amazing.

Sorry, its probably me, but I'm losing track of the question a bit If it helps. we licence Office 2019 through an OVS-ES agreement, this entitles us to add on Office 365 ProPlus licences. It also entitles us to have Office 365 A1 Plus licences. Therefore currently we deploy the Office 365 C2R client and use the A1 Plus licence to activate Office via device based activation as detailed here: https://sysadminedu.wordpress.com/2017/01/07/step-by-step-guide-to-deploying-office-365-pro-plus-with-device-based-activation-with-sccm/ However it appears that this is now deprecated (but still works for us) in favour of the new method called Device Based Subscription, which needs another licence adding in from your reseller. Details and requirements can bee found here: https://contosoedu.com/deploying-office-365-proplus-device-based-subscription-for-edu/

Web stuff is covered by A1 licence. You can get ProPlus by either subscribing through 365 or by having an Office volume licence agreement.

@MartinT Correct. 365 ProPlus are requested through your reseller. If you qualify for the A1 Plus licence then it *should* appear automatically. If not then you have to get 365 support to added them in. Your reseller cannot do this, the VL Service Center cannot do this. Only 365 Support can.

@MartinT No you can't. We are talking about the A1 Plus licence, not the ProPlus licence, they are different and not available from your reseller. @mullet_man They allow you to licence Office 365 C2R using Device Based Activation. Although according to the blog that lots of us used to get DBA with A1 Plus working, it was deprecated on 1 Dec 2019! (still works here though). https://sysadminedu.wordpress.com/2017/01/07/step-by-step-guide-to-deploying-office-365-pro-plus-with-device-based-activation-with-sccm/

This might help you: https://blogs.msdn.microsoft.com/george_bethanis/2014/07/29/why-an-osd-task-sequence-is-triggered-to-re-run-on-a-cm12-client/

Oh? I am able to download all the updated firmware without having to prove I have an entitlement. Downloading from this page: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00092491en_us

Update Compliance just reports on the state of your machines, so you still need a way of getting the updates installed on your machines. This could be with WSUS, Windows Update for Business, direct with Windows Update etc. Personally, I use sccm which leverages WSUS, I wouldn't recommend stopping using WSUS to go to directly using Windows Update. If you are happy with WSUS continue to use it and add in Update Compliance for reporting.

If you have iLO setup then that will tell you as well.

Which version are you using? Volume licencing? Click to run (ie Office 365 ProPlus)? What tools are you using to roll it out? SCCM? Group Policy? Another tool? There are many options with different workflows

No I don’t think so. Reads like this is on the SSD manufacture, not HP.

I imagine because of the way SCCM works with WSUS. It doesn't simply sit on top of WSUS and use the same work flow that you would if were using WSUS natively. SCCM just leverages WSUS to download the metadata of the updates to determine what's new (according to the rules you set) and then downloads the updates itself. So if you actually open WSUS you are wading through the update catalog, in sccm you are only dealing with the updates you need.

From experience, SCCM works with WSUS just fine, pretty speedy actually (faster then if you use WSUS natively).

Also, for some reason, the 12130.20410 update has been released with the 'Current Channel' naming convention (that was dropped 2 years ago) rather that the Monthly Channel convention. So, if like me, you use SCCM and you search for updates with 'monthly' in the title, if won't show up 365 updates are turning into a dog's dinner at the moment.

If you have updated to 365 1910 you may have noticed that clients cannot update to newer patches. MS have now confirmed this. https://support.microsoft.com/en-us/help/4532996/office-365-version-1910-updates-in-configmgr-do-not-download-or-apply

I can’t understand what’s going on with the monthly updates now. A few days ago all our machines jumped into life and patched to the latest version. Then a new patch was released and once again they are all failing.

Kind of... you need sccm to manage 365 updates via wsus.

I use SCCM to deploy Windows 10. I deploy an unaltered wim (as stripping apps out of the wim can now bork the installation) and use a script to remove the apps while the installation is still offline. The removal script is here: https://pastebin.com/iy2krNcd The xml containing the apps to remove is here: https://pastebin.com/5aBbjTLY You then create a package in sccm and run it during the OS setup phase of OSD

This. There is an issue with removing apps before sysprep or removing from wim before deployment. The safest method is to now remove after os deployment.