Casper remote window

[#1]

We have created two packages Office 2008 package and the 12.2.0 office
2008 update package. The issue is when we deploy office 2008 it works
fine but when we deploy the update package on top of it, it breaks the
office install. None of the office icons launch any apps... Anybody had
any idea what are we doing wrong here?

Toufiq Yakoob
CTS (Client Technical Services)
Sears Holdings Corporation Information Technology,
3333 Beverly Rd., Hoffman Estates, IL 60179 Office: B2-172A,

Phone: 847-286-2932 Email: tyakoob at searshc.com
<mailto:tyakoob at searshc.com>

SHC Blackberry: '2244650508 at messaging.sprintpcs.com'

[jstrauss]

What I've done in the past is use Composer to install the update by taking a "New and Modified Files" snapshot, packaging it as a DMG and deploying it to managed clients. That has worked every time. Is that what you're doing?

-----
J.S.
Sysadmin, LHS L.A.
213-381-5121 x.265

Sent from my phone.

[#3]

No we just used the MS mpkg file, so we will try your idea.. thanks

Toufiq Yakoob
CTS (Client Technical Services)
Sears Holdings Corporation Information Technology,
3333 Beverly Rd., Hoffman Estates, IL 60179 Office: B2-172A,

Phone: 847-286-2932 Email: tyakoob at searshc.com

SHC Blackberry: '2244650508 at messaging.sprintpcs.com'

[jstrauss]

Yeah, metapackage files have never worked for me for Office updates. It could be because there are user-configurable options inluded in the mpkg or because the mpkg calls other pkgs to install, but I'm not sure. Interestingly, extracting the individual pkgs from the Office mpkg and throwing them into Casper Admin hasn't worked for me, either. The "New and Modified Files" snapshot in Composer has proved reliable in this regard. :)

-----
J.S.
Sysadmin, LHS L.A.
213-381-5121 x.265

Sent from my phone.

[#5]

Thanks a lot..

Toufiq Yakoob
CTS (Client Technical Services)
Sears Holdings Corporation Information Technology,
3333 Beverly Rd., Hoffman Estates, IL 60179 Office: B2-172A,

Phone: 847-286-2932 Email: tyakoob at searshc.com

SHC Blackberry: '2244650508 at messaging.sprintpcs.com'

[talkingmoose]

The original Office 2008 DVDs contained version 12.0.0, which had a few
permissions issues. If you can get a hold of a DVD that was later released
with Office 2008 12.1.0 then this problem will likely go away.

We have the 12.0.0 installer and so I made a 12.1.4 package at the time we
were ready to deploy. I start with that and then deploy the latest update
from Microsoft. Installing my 12.1.4 package along with the 12.2.0 update
worked just fine for me.

--

bill

William M. Smith, Technical Analyst
MCS IT
Merrill Communications, LLC
(651) 632-1492

[ernstcs]

Yup, I've been able to use the Meta package for updating in most cases. I did seem to recall having issues trying to update my 12.1.7 packages at one point for some reason though...

I usually maintain two packages a completely updated traditional composer package for imaging time and then I keep the meta updater as well for that same version for patching.

Craig E

[#8]

I don't even do a new & modified (patch) package. I do a whole new (New Files) install package where I:

Install 12.0.0
Upgrade to 12.2.0
Remove items in the /Users folder from the diff.
Compose

It takes the same amount of work as install Office and then doing a New & Modified diff on an existing package. This way, I can use this package to install a clean install of 12.2 for my imaging configurations or overwrite an existing install. In neither scenario does Office break, as long as you do it startup or logout when you can be sure users don't have their Office apps open.

Just my $0.02

[Bukira]

I always use the ms mpkg packages and never have a problem, I Install 12.0.0 via a ms original dmg then install 12.1.19 via mpkg and then 12.2.0 and it just works everytime

[jstrauss]

Maybe I inadvertently tried an update from 12.0.0 to 12.2.0 and I didn't realize, because the 12.2.0 update didn't work. My bad, then.

-----
J.S.
Sysadmin, LHS L.A.
213-381-5121 x.265

Sent from my phone.