Not sure how that would matter actually? Got a link to that? Oh wait, experts exchange makes you pay, doesn't it? From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Bobby Benninger Sent: Friday, July 11, 2008 9:02 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack someone on experts-exchange came up with a work-around. if you put the msi on sysvol rather than a standard share it installs perfectly. said he had the same problem. strange huh? On Fri, Jul 11, 2008 at 11:06 AM, Darren Mar-Elia <darren@xxxxxxxxxx> wrote: Right. Office 2007 totally broke GP-based software deployment. I've blogged about this a few times. MSPs are not really useful for GP-based deployment. Your only real customization option comes in the form of a config.xml file that allows for *some* customization. You're probably better off deploy O2K7 via startup script with MSPs. Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Northwood, Ian Sent: Friday, July 11, 2008 7:52 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack Am I right in recalling also that one can no longer use transforms for Office 2007? I think you have to build patch files (MSPs, which are kind of transforms) and deposit them in an 'Updates' folder? Check out http://www.appdeploy.com <http://www.appdeploy.com/> and use the 'Package KB' link at the top of the page or the 'Search' link off to the right. _____ From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: 11 July 2008 15:50 To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack Not using GP Software Installation. There is no "command line" From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of sunshine.baines@xxxxxxxxx Sent: Friday, July 11, 2008 7:45 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack You can pass the ALLUSER=1 throuh the install. Ex. Msiexec.exe (path to msi install) ALLUSER=1 Sent from my BlackBerry wireless device from U.S. Cellular _____ From: "Bobby Benninger" <bobby.benninger@xxxxxxxxx> Date: Thu, 10 Jul 2008 16:29:01 -0400 To: <gptalk@xxxxxxxxxxxxx> Subject: [gptalk] Re: trying to deploy Office Compatibility Pack Ok - wouldn't Microsoft have thought of this when they wrote the MSI or no? On Thu, Jul 10, 2008 at 4:09 PM, Nelson, Jamie <Jamie.Nelson@xxxxxxx> wrote: Yeah, my bad. You can specify a transform, but not property arguments. I haven't had to use GPSI in a long time since I'm lucky enough to have SMS/SCCM for software distribution. Hold up and I can write the transform for you pretty quickly. Jamie Nelson | Infrastructure Consultant | BI&T Operations | Devon Energy | Work: 405.552.8054 | http://www.dvn.com <http://www.dvn.com/> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia Sent: Thursday, July 10, 2008 2:59 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack You would need to either write a transform to make that property modification or modify the MSI package directly with a tool like ORCA. There is no way to pass property options through GPSI. Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Nelson, Jamie Sent: Thursday, July 10, 2008 12:55 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack No I would not do that. Just remove the software install and re-create it under computer configuration. You should be able to pass the ALLUSERS=1 property when you recreate the package. If memory serves me, you can't modify the arguments after the package has already been created. Jamie Nelson | Infrastructure Consultant | BI&T Operations | Devon Energy | Work: 405.552.8054 | http://www.dvn.com <http://www.dvn.com/> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Bobby Benninger Sent: Thursday, July 10, 2008 2:40 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack should i re-create it as per-user instead of per-computer? On Thu, Jul 10, 2008 at 2:50 PM, Darren Mar-Elia <darren@xxxxxxxxxx> wrote: To add onto this Bobby, it doesn't actually sound like the package installed successfully, or at least it is not being activated successfully. Did you install it per-user? IF so, did you select to install at first logon in the Software Installation UI? Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Nelson, Jamie Sent: Thursday, July 10, 2008 11:46 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: trying to deploy Office Compatibility Pack Sometimes when you deploy software through Software Installation policy it installs in "per-user" mode for the SYSTEM account. I always make sure and use the ALLUSERS=1 argument to ensure that scenario doesn't happen. Jamie Nelson | Infrastructure Consultant | BI&T Operations | Devon Energy | Work: 405.552.8054 | http://www.dvn.com <http://www.dvn.com/> From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Bobby Benninger Sent: Thursday, July 10, 2008 1:40 PM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] trying to deploy Office Compatibility Pack I am starting to really hate this MSI. Anyway I was having trouble before getting the GPO to apply because of a USERENV error in the Application Log, I removed Symantec A/V to resolve this error and now the GPO applies correctly. Now my problem is that even though the GPO applied and "Office Compatibility Pack" shows in add/remove programs, whenever I open a DOCX file I get prompted to do download the Compatibility Pack from Microsoft b/c its not installed. I have read that when you do an assigned software install it doesn't actually install the app, just preps it to install the first time you use it. Could this be where things are getting caught up, b/c I am not "using it" first correctly? Let me know what info you need to help troubleshoot. Thanks so much for any advice. - Bob _____ Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of all or any portion of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ Liverpool Victoria Friendly Society Ltd. Registered in England and Wales. Registered Office: County Gates Bournemouth England, BH1 2NF, No.61 Coll. Financial Services Authority Register number 110035. This email (and any attachments): - is for its intended recipients only and may contain confidential and /or legally privileged information. If received in error, any use of this email is prohibited. Please delete it (and any copies) and notify us on +44(0)1202 292333, ext. 4044. - is believed to be free of any virus or other defect but internet communications cannot be guaranteed to be secure or error free and we do not accept any liability for any loss or damage from their receipt or use. Opinions expressed in this email are not necessarily those of the Society. LV= and Liverpool Victoria are trade marks of Liverpool Victoria Friendly Society Limited and LV= and LV= Liverpool Victoria are trading styles of the Liverpool Victoria group of companies. LV= reserves the right to monitor and inspect emails sent to and by its employees. To find out more about us please visit: www.lv.com <http://www.lv.com/> ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________