Networked Office

[Guest]

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

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

So we now have

bada - TS second server
bing - run all applications from local machine
boom - Run from network

If you want "newer O/S" that can do what you want that isn't bada, bing
or boom, they buy them.

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

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

 

[Sarah Tanembaum]

Perhaps you can answer my question and test it on your server and
workstations(make sure that there are at least 2 workstation and use it
simultaneously). Then, you can see where the problem are.