Office 2010 Deployment (Scripted package install VS. Scripted install as dependency)
I am fairly new to K1 so bare with me. I am deploying Office 2010 and I'm juggling the method to use to perform the install. The install must be scripted because other things will happen with the install other then just installing Office. To complicate matters, some users have MSAccess installed and some don't. Here are my options.
1. Scripted install - Uses an item in the software catalogue in combination with the other task's/steps in my script to complete the install.
Note: If I use this method I would have to create a Manual software entry for the Access version of the installation. I already have a install package attached to the Discovered Microsoft Office software item.
2. Scripted install - Attaches Office install files as a dependency to the script in combination with the other task's/steps to complete the install.
Note: For each installation that occurs dependencies are uploaded to the workstation while the script is executing.
3. Use a Distribution Point (such as a file server) to host Office installation files in combination with the other task's/steps in my script to complete the install.
Note: If I use this method I loose the ability to leverage my replication shares built into the K1 (we have multiple sites targeted for deployment). Creating multiple scripts customized for each subnet while using the local replication share for that site can become messy and hard to manage.
I'm hoping someone with some Office deployment experience can chime in on what my best tactic is. Or possibly suggest something I might not have known or thought of.