Jump to content

Recommended Posts

Posted
You need to activate HUP in VLSC it seems, but when I try

 

VLSC - Software Assurance - Home Use Program

 

I just get an error. Might check again tomorrow.

My issue was I didn't have access to the section on VLSC I do now but haven't activated the HUP.

 

It mentions the number of staff we've set on our agreement so does this mean the offer is only open to staff and not students? Does it have a limit on activations as per the number on our agreement?

  • 2 weeks later...
Posted
So re: Office 2019 updates, I just re-ran the /download process and it downloaded a new version in the Shared folder\data folder rather than just updates (It seems Microsoft prefer doing it this way now) - That's going to get big very quickly, unless you can safely delete older versions over the years...
  • 3 months later...
Posted

Necro on this thread I know but curious from people that adopted from day 1.

 

When deploying through SCCM and using the shared folder path for install within the office config.xml how do you keep those base install files up-to-date as surely they are out of date by now from patches etc...

Microsoft claimed that new updates would just roll into the new download files. Is it a simple case of you are just installing the original files you downloaded in November and then clients just immediately update on next scheduled task as they realise they are out of date?

Posted
Necro on this thread I know but curious from people that adopted from day 1.

 

When deploying through SCCM and using the shared folder path for install within the office config.xml how do you keep those base install files up-to-date as surely they are out of date by now from patches etc...

Microsoft claimed that new updates would just roll into the new download files. Is it a simple case of you are just installing the original files you downloaded in November and then clients just immediately update on next scheduled task as they realise they are out of date?

Since you use SCCM, so you have it configured as a Software Update Point in conjunction with WSUS? If so, this is how I managed Office 365 updates: (Though we no longer deploy Office 365 because of a whole load of issues we had with it - we're using 2019 instead).

 

In SCCM, I had an ADR configured for each branch of Office 365 we were using, with the following criteria:

Date released or revised: Last 1 month

Product: Office 365 Client

Superseded: No

Title: Update - Semi-Annual Channel

 

I had three Office 365 deployments in SCCM; Monthly, Semi-Annual, Semi-Annual (Targeted). I created an ADR for each with the above configuration, just changed the Title field to match the channel. The schedule of the ADR was to run automatically every second Wednesday of the month (to coincide with Patch Tuesday).

 

Those ADRs were then deployed to a specific collection that had the matching Office 365 channel deployed to it.

 

I hope that makes sense.

Posted

I don't use SCCM (I seriously think it's like using a sledgehammer to crack an egg) and just have a shared folder I point my clients at - Then I have a .bat script that updates the deployment share - I've not got around to task scheduling this yet but that's how I intend to get around it.

 

I started from hating this click to run setup to being quite impressed with it. Clients are essentially constantly checking for updates and if they detect the deployment shares been updated they update opportunistically. I closed Word on one machine showing an older version and less than 5 mins later it had installed the newer version in the background.

Posted (edited)

Sorry should of been a little clearer.

 

I’m letting the clients update from the net directly via the CDN for differential updating instead of full ass replace if you pointed your clients to update from a file share, bandwidth is not an issue here and I’m not going through all the extra admin work!

 

The only thing I am using the file share for is the initial deployment.

I was just curious on whether people just update that folder periodically and then refresh it in SCCM or just leave it and have clients update straight away after install.

Edited by Tefters
Posted
I don't use SCCM (I seriously think it's like using a sledgehammer to crack an egg) and just have a shared folder I point my clients at - Then I have a .bat script that updates the deployment share - I've not got around to task scheduling this yet but that's how I intend to get around it.

 

I started from hating this click to run setup to being quite impressed with it. Clients are essentially constantly checking for updates and if they detect the deployment shares been updated they update opportunistically. I closed Word on one machine showing an older version and less than 5 mins later it had installed the newer version in the background.

@DrCheese, any chance you could share that .bat script?

  • 1 month later...
Posted
I don't get it, it says admx and adml files for all 3 office 2019,365,2016 types but only includes 2016?

They never changed the ADMX names, but those 2016 ones include all the settings for 2019, 365 and 2016.

  • Thanks 1
Posted
Which is one of the smartest ideas Microsoft have done as of late as all our GPO’s work from 2016 in 2019 and don’t involve me re-creating them all...
  • 1 month later...
  • 2 weeks later...
Posted

Has anyone downloaded Office 2019 from the Volume License Site recently ?

 

I selected Office 2019 Pro Plus and it downloaded Office 2019 SERVER! Any ideas?

 

Many thanks in advance.

Posted
We push it out via VPP now as it's on the app store, so much easier!

 

Edit: Just seen this is a Windows and Mac thread... i just saw Mac bit! Ignore my comment!!

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...