Re: Networked Office

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sarah Tanembaum (sarahtanembaum_at_yahoo.com)
Date: 07/22/04 

Date: Wed, 21 Jul 2004 22:06:08 -0400

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.

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?)

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!

Thanks

<andyc69@tiscali.co.uk> wrote in message
news:ujnl7szbEHA.3096@tk2msftngp13.phx.gbl...
>
> "Sarah Tanembaum" <sarahtanembaum@yahoo.com> wrote in message
> news:2m79i9Fjk2lvU1@uni-berlin.de...
> > <andyc69@tiscali.co.uk> wrote:
> > >You can run office from a network share if you so choose. Create an
> > >Administrative Install on the server, use the custom installation
wizard
> to
> > >create a .MST where all the options are set to "Run from the Network",
> > >deploy via Active Directory or a login script. Not exactly rocket
> science.
> >
> > Is this what you call running from the network by copying/deploying
> file(s)
> > to
> > workstation(s)?
>
> Where did I say anything about copying files to the workstation?
>
> If you deploy Office with the setting "Run from the Network" it does
> precisely what it says. The only files copied are shortcuts/registry
> entries, the executables and dll's etc remain on the fileserver only.
>
> Perhaps you ought to check your facts before making wild assumptions about
> the capabilities of Windows over your so-called "more advanced OS/Apps"
>
> AndyC
>
>

Relevant Pages

  • Re: Networked Office
    ... 1- I put all the executable file as well as dll on the server to share with ... 2- I just create a shortcut and registry setting and voila I can ran the ... NO INSTALLATION PROCESS ON THE WORKSTATION AND NO ... EXEC and DLL files COPIED TO WORKSTATION? ...
    (microsoft.public.office.setup)
  • Re: Networked Office
    ... 1- I put all the executable file as well as dll on the server to share with ... 2- I just create a shortcut and registry setting and voila I can ran the ... NO INSTALLATION PROCESS ON THE WORKSTATION AND NO ... EXEC and DLL files COPIED TO WORKSTATION? ...
    (microsoft.public.windows.server.general)
  • Re: VB Script not executing
    ... No it is the creator (not the recipient) of the email where the script does ... The DLL is definitely registered on the creator workstation... ...
    (microsoft.public.office.developer.outlook.forms)
  • Re: Winlogon notification DLL and user token
    ... structure has the user's workstation, desktop handle, and user token ... I thought the user token the notification DLL gets was supposed to be ... Have you tried impersonating the user in your DLL and then send ... something across the pipe to your COM server which then again ...
    (microsoft.public.win32.programmer.kernel)
  • [Full-Disclosure] IE is just as safe as FireFox
    ... >> a shortcut to firefox.exe on user desktops. ... > Can the executable reside on the workstation with the settings stored ... In my case, executable doesn't recide on workstation, it's placed on ... network file server. ...
    (Full-Disclosure)