Deploying Office 2003 Basic To A *Computer* Via GPO

Otacon

Otacon

Otacon

Soldato
Joined
10 Jan 2004
Posts
21,921
Location
All over
Ok folks, someone is lying to me somewhere, because this just isnt working. I'm messing about with pushing Office to computer accounts in a domain. Obviously going down this route I'm limited to the "auto-install this application by file extension activation" option - no auto-install at logon. The trouble is, for some reason I cant fathom, it just isnt working.

Office Basic is only Word, Excel and Outlook 2003. If I look at the software installation properties of my GPO, the package is registered against the correct file extensions. If I choose one of those file extensions on my client machine - I just get the standard 'no program associated' message, and no install is invoked (as it should be). This happens regardless of what permissions the user has (Admin/Power User/User).

I've used this option before with third party apps, and it works fine. Why wont Office comply?
 
Again, this is a computer account install. File system permissions (if that's what you're getting at, it's not very clear) are irrelevant.

It may be something odd to do with the MST file. I can push this out to a user from a GPO using the same MSI/MST and it works fine... however when I push to the computer account, an error is logged saying that the installation package doesn't support the use of transforms (which is evidently a lie).

M0KUJ1N said:
so I cheated a bit and used Office Pro with a transform creating with CIW to only install Word, Excel and Powerpoint
Click to expand...
I hope that last part's a typo, because if not, then you aren't cheating - you're breaking the law. Office Basic 2003 is Word, Excel and Outlook only. Not Powerpoint.
 
Computer assigned packages dont properly install until a user tries to open a file which requires that application.
 
Nice random font change :p

File extention activation works as intended when assigning to a user. It also works as expected when assigned to a computer with some other packages. It isn't working with office, regardless of how many reboots or policy refreshed I give it, and logs the error I quoted above (which is lying).
 
You must log in or register to reply here.
Back
Top Bottom