Re: Networked Office
From: AndyC (andyc69_at_tiscali.co.uk)
Date: 07/22/04
- Next message: kennymurdo: "Wireless Domain Access"
- Previous message: paul: "Remote Desktop Connection"
- In reply to: Sarah Tanembaum: "Re: Networked Office"
- Next in thread: Sarah Tanembaum: "Re: Networked Office"
- Reply: Sarah Tanembaum: "Re: Networked Office"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Jul 2004 11:56:46 +0100
"Sarah Tanembaum" <sarahtanembaum@yahoo.com> wrote in message
news:2m8lp5Fk4fk8U1@uni-berlin.de...
> Forgive me if I was mistaken.
>
> Let me rephrase my understanding of your(MS) solution:
>
> 1- I put all the executable file as well as dll on the server to share
with
> other workstation without
> copying any exec and/or dll file on the workstation.
Almost correct. You create an Administrative Install on the server with:
msiexec /a office.msi
This creates the correct folder structure for the server. No files are
copied to the workstation.
You then use the Office Custom Installation Wizard to configure the way you
want the Office installation done. In your case this would involve selecting
"Run from the Network" for all options. However it's perfectly valid to mix
and match if, for example, you wanted Powerpoint installed locally or
Outlook to install locally on first use etc.
You then save the .mst file in your server's shared office folder (referred
to from here on in as \\server\office)
> 2- I just create a shortcut and registry setting and voila I can ran the
> office apps?
> PS: I'd like to see the scripts that create those shortcut(don't need
> the shortcut, I'd like to just
> execute it directly from the network-attached directory) and
> registry setting(what setting do
> I need?)
Depending on your environment you can do this one of two ways:
1) If you have Active Directory, just create a GPO containing the Office
package with the .mst transform you created earlier and assign it to the
relevant Organisational Unit.
2) Alternatively, run the msiexec utility from a startup script or similar
method, again applying the relevant transform. Something like this should do
the trick:
msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb
This will create the appropriate registry information and Windows Installer
shortcuts for the setup you decided upon in your Custom Installation. If you
don't want the shortcuts you can always opt to omit them in your .mst file,
although I don't really see and advantage in that.
> 3- Just to be sure! NO INSTALLATION PROCESS ON THE WORKSTATION AND NO
> EXEC and DLL files COPIED TO WORKSTATION?
>
> Are those correct! If they are, please forgive me, but I can bet that was
> not the case!
Yes that is correct. EXE or DLL files are only copied to the local
workstation if you request it in your installation. One possible caveat to
this is that Office 2003 has a few .NET optional extras (programmer support
IIRC) which have to be installed locally if you want them (because of the
way .NET Code Access Security works), although 99% of people probably don't.
AndyC
- Next message: kennymurdo: "Wireless Domain Access"
- Previous message: paul: "Remote Desktop Connection"
- In reply to: Sarah Tanembaum: "Re: Networked Office"
- Next in thread: Sarah Tanembaum: "Re: Networked Office"
- Reply: Sarah Tanembaum: "Re: Networked Office"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
