Skip to main content

I am deploying Office 365 and few Adobe CC packages through Self service and the download becomes very very slow once multiple computers start downloading the packages.

Here is how am doing it:

A policy is caching the packages to all computers, then another policy installs the cached packages scoped to a smart group of computers that have those packages and make them available in self service.

Its taking a very long time for the packages to show up in self service, so I was wondering if theres a better way to deploy. The packages were being downloaded through http, but I was getting most of them were timing out, so i turned off http, and now they are going through afp which seem to work lil better but still very slow downloading.

I have about 700 computers, 1 JSS and 1 Distribution point both hosted on 2 different mac mini.

Will things get faster if I were to add a second, and third Distribution point?

Please advise

Thanks

@casper.admin If you want to install on every computer you have managed, in your Policy that caches the installer use a Scope Target of All Managed Clients (that's a selection under Computer Groups when Target Computers is set to Specific Computers - as you discovered you can not have an Ongoing policy set to All Computers but you can this way). You need 2 Smart Groups you can reference under Scope->Exclusions for this policy - a group for machines that have the package cached, and a group for machines that have the software installed. This policy should have only 2 payloads besides General - a Packages payload that Caches the installer, and a Maintenance payload set to Update Inventory.

thanks all for the replies. All seem to be going but seeing few computer failing to copy from the DPs. maybe the load is too much as I am caching 8 Adobe CC packages, SmartNotebook and Office 365.

The packages do exist on all 3 of my Distribution points but I am still seeing this error message on some computers, not all computer though. Some do execute and complete with no problem.

@casper.admin Do those machines eventually manage to cache the installers, or do they perpetually fail with the no such file or directory error? If the former, I'd suggest taking a look at the error logs on your DPs to see if they were dropping connections due to load.

@sdagley Which logs should I look at? It seems like it failling when I have multiple computers trying to cache at the same time, however I have 3 DPs in place.

@casper.admin Look at the logs for the SMB or AFP processes on your DPs for the times corresponding to the failed copy to the client machines and see if you can figure out why the server didn't respond.

Terms & ConditionsCookie settingsAccessibility statement