Guest Henk Hoogendoorn Posted January 4, 2012 Posted January 4, 2012 Today I created a new Office 2010 package and program for a customer in ConfigMgr 2007 R3. I've created an MSP file to do a unattended installation. An advertisement of this package and program is set on multiple collections. When there's no Office 2010 installed already everything goes fine! but when Office 2010 already exists on the device it stops/hangs on setup.exe in Task manager. Probably there's a hidden pop-up mentioning it want to repair or remove Office 2010, but because of ConfigMgr 2007 setup it's not visible. How can I prevent that setup.exe hangs on setup.exe on these devices? Is there a way to configure this in an MSP file or config.xml file? When there's an option to arrange always a repair when Office 2010 is installed, that's also fine with me. My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn Continue reading... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.