First off, here are a few details of my site.
Version: LANDesk Management Suite 126.96.36.199
30,000+ pc's running Win7
I understand each organization has its own needs, but is there a general best practice in regards to large multicast deploys?
We currently have guidelines in place that I think our outdated.
Example of deployment to 10,000 pc's with a 500MB package
- policy supported push used
- # of devices for distribution = 61
- bandwidth, WAN = 25%, LAN = 75%
- max # of MDR = 5
- max # of failed multicast to process = 240
- # of days to cache locally and on MDR = 14
- # of install tasks used = 20
A typical deployment would consist of multiple install tasks with no more than 500 pc's in each. This is what I am challenging.
The logic behind this decision was the # of potential calls to our service desk if something goes wrong with the deployment.
If I had only used 2 tasks of 5000 vs 20 tasks of 500 and something went wrong (whether it be LANDesk or the package itself), our service desk would be inundated with calls.
The only benefit I see to having more tasks is that you have more MDR's and the distribution goes faster, but also adds more strain to the network.
In almost all cases, issues arrising from a deployment are not caused by LANDesk itself, so I don't see the benefit of multiple tasks.
Many of the deployments we do are much smaller than 500MB.
Are there any gurus out there that can either validate this or recommend a better/best practice?