We are looking to push Adobe out via our network using group policy. We have been able to successfully complete this in our test environment. Our question is should we push reader out via GPO will this cause any problems with our users that have the professional version installed.
We also plan on pushing FLASH out with the same GPO....
Any insight is appreciated.
Don't take this wrong, but didn't you test that scenario in your test environment?
A lot of the behavior will depends on how your package was built. What has your testing uncovered? I would assume that your test plan included testing the installation behavior on a typical desktop - not a clean one.
This action is a common mistake - all the testing is performed in a clean room, clean machine, no additional apps, etc. - not the dirty, messy world of reality.
Suggestion -
Test this situation in your test environment. Then, carve out a pilot group of end-users (about 20-30) that are a cross section of your end user population (2-3 from each major 'area'). Communicate to them that you will be making the push, when the push will occur and what they should expect. Ask them for their feedback - give it 1-2 weeks. Anything and everything that they like or dislike in the new version.
Use that info to fine tune your installation and try again. Yes, this takes time - so did the Sistine Chapel. If your leadership balks - calculate the support costs of fixing a blown rollout. On a 1000 person deployment 5 min per person in any kind of frustration, is 5000 minutes - just over 80 hours. Yea, two person weeks. Now, if you have to involved some sort of support organization - double or triple the number of people involved and call minutes spent. Time and costs add up really quickly. Especially if your leadership outsourced your support infrastructure.
For the roughly 25,000 colleagues in our environment I'll perform 2-3 rounds of pilots (each one a bit larger than the last) and then a staggered rollout over several days. If anything goes sour I have time to react. You don't want to be known for torpedoing the business due to a botched rollout. You want to be known as the dude with the most pervasive application that no one ever hears about because of a lack of problems.
As for Flash - bad idea. At least have a few days separating the two. Much, much easier to spot and react to a potential problem with one variable than with two. In other words, don't set yourself up for failure.
Hope this helps.
-Doug
Douglas Hanna is a member of the Production Print Technology team at Aon.
www.aonhewitt.com