Networked Office

K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
K

Kevin Weilbacher [SBS-MVP]

Nope, we're not avoiding the issues. We're simply providing you "our"
experiences and insight - and that's all any of us can do. No product is
perfect. And we certainly don't pretend to have all the answers. If you
don't like our responses, then I would suggest that you consider moving your
arguments to another NG that may have the answers you are looking for.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


Sarah Tanembaum said:
I think this is very inefficient. Why can I install my apps on a disk in my
server and mount that disk on my workstation and execute the exe file from
there.

If I need to upgrade, all I have to do is upgrade the server and those 10(or
100 workstation) will get updated instantly without clogging up the network
for transferring files between the server and those 10(or 100) client
workstation.

I think you all know what I'm talking about but most of your MVP[Microsoft
....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really good idea.
I have been using Terminal Server for the last 15 months or so and it is
generally a great thing. As Kevin mentioned, you can no longer install
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very good
reasons for this. You would need a second server that would be the Terminal
Server. On SBS2000 you can indeed do this - but again, not generally a good
idea to run Terminal Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really good point
/ question as to why do you would want to turn them into thin clients. I
would probably not want to do that! Du hast schon das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of Office 2003
on your Server and install that application on each workstation from that
Admin Installation. The advantages of doing this are 1) you have a common,
accessible installation point and 2) you do not have to worry about losing
the Office 2003 CD! However, the disadvantage of doing this ( compared to
my next suggestion ) is that when you want to update the clients ( sagen
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003 from
each client ( you could use the utility from the Office 2003 Resource
Click to expand...
Kit
to
do this! ) and then running the installation on each workstation. Sure, you
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in the
logon script and make sure that it is run on each machine and then rem out
the additional lines in the logon script ). So, with this solution you have
a really nicely located Administrative Installation Point that you can
nicely keep up to date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using Group
Policy to install Office 2003 to all of your computers ( or users ). You
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or when
a Service Pack is released - and you have the ability to very quickly and
without much administrative overhead install this to your clients and - here
comes a really neat point - easily and quickly update the clients when those
security patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation ( say
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra get
PowerPoint, Word and Outlook ). Furthermore, you can set a lot of the
options via a GPO that will ensure that all of your users have the settings
that they need. You will not have to go to each computer and make sure that
all of those specific settings are properly configured. Do it via the GPO
and there you have it! Also, you can control it so that your clients can
not go to the officeupdate.microsoft.com and make untested updates to the
Office 2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber das
Group Policy Object haben....

HTH,

Cary
Click to expand...
an
a a
way
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
F

Frank McCallister

Hi Sarah

Your choice ;-) Just be sure you don't load Outlook on the server which will
crash Exchange.

Frank
Sarah Tanembaum said:
I don't think I'm worry about my network speed. I have ample bandwidth
(Giga
ethernet), fast workstation, and fast server. All I want is to execute the
app from file server.

I don;t think this is such a hard technology to implement isn't it?



Frank McCallister said:
Hi Sarah

You can run the executables from the server if you wish but a certain number
of DLLs will have to be on the WS. You don't want to do this though because
your Office programs will run as slow as mollasses because the
executables
will have to be loaded across the 100 mb network lines instead of from a
much faster HD unless you are using Terminal services where only the
video
is transmitted across the Network and even that is slower than running
local. The only time you would want to run from server is if you had
extremely small Hard Disks which make no sense with the price of HDs
these
days.

Frank McCallister
COMPUMAC


Sarah Tanembaum said:
Thanks Kevin. Unfortunately the terminal services are out of the question.
We have pretty powerful workstation and server, why would I use my
workstation
as a terminal(Isn't this goes again MS ideology)?

Secondly, why would I pay an additional license for each workstation
to access the terminal server. It is just not economical.

Or perhaps Microsoft is still ironing-out on how to implement this this
type
of
technology(networked-multi-user-multi-task-apps)?

Thanks


Sarah, what you have described is called 'Windows Terminal Server'.
You
are
right about the fact that by installing Office on one system, and letting
everyone access it reduces administrative issues. But, SBS2003 does
not
allow you to configure Terminal Server on the SBS server itself. You can
add
a separate system to act as a terminal server alongside your SBS server.
The
temrinal server would house your Office apps, and your SBS server
would
handle Exchange/email, Internet access, and file/print services.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


I'm trying to use my server as a file server, where I will store all
the
Office executable. If MS so willing, then they can tell us what
registry
setting on the local machine has to change so each of my workstation
can
run
office apps, e.g. MS Word, Excel, and other, right from their
workstation?

Is it a technology issues that prevent this to happen? What's the
big
problem since other OSes can handle multi-user apps?

Imagine if I can do that, everytime the workstation crashed and
corrupted
the disk, all I have to do is install the os, mount the directory where
office reside, and voile ... it's back up again. Also, when the office
need
upgrade, all I have to do is to upgrade the one on the server and
again,
those 10(or for that matter 100K)workstation has their office upgraded!

Any ideas?




I think you have the option upon installing if you want to install
Office
to
a server, but I am thinking if you have 10 users it is going to slow
down
your server badly. Is there a particular reason you dont want to
install
on
the workstations? You can setup admin install of office to install
just
like
Outlook installs on SBS client upon connection.


Is it possible to run office from a server?

We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
a
server with ample of memory and disk space.

We also purchase a 15-user license of Microsoft Office 2003
Professional.

Instead of installing MS Office 2003 on all the workstation, is
there
a
way
to run Office from a server?

I know of the terminal services/citrix way but that is out of
the
question
as it will add cost per client.

Thanks
Click to expand...
Click to expand...
Click to expand...
 
C

Chad A. Gross [SBS MVP]

I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.
Click to expand...

Because it doesn't work that way. Same reason you can't put your Chevy in
the Pacific and sail to China . . .

Windows applications require to be installed on the machine where they are
being executed. If the application is going to be executed from the PC,
then it needs to be installed there. If it is going to be executed from the
server, then it needs to be installed on the server, and you're looking at a
TS / Citrix solution. I'm sorry if you don't like that answer, but that's
the way it is.

--

Chad A. Gross - SBS MVP
SBS ROCKS!

www.msmvps.com/cgross
www.gosbs.org


Sarah said:
I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.

If I need to upgrade, all I have to do is upgrade the server and
those 10(or 100 workstation) will get updated instantly without
clogging up the network for transferring files between the server and
those 10(or 100) client workstation.

I think you all know what I'm talking about but most of your
MVP[Microsoft ....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really
good idea. I have been using Terminal Server for the last 15 months
or so and it is generally a great thing. As Kevin mentioned, you
can no longer install Terminal Server in Application Mode ( err,
that is the WIN2000 terminology.... ) on the SBS2003 Server itself.
There are some very good reasons for this. You would need a second
server that would be the Terminal Server. On SBS2000 you can indeed
do this - but again, not generally a good idea to run Terminal
Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really
good point / question as to why do you would want to turn them into
thin clients. I would probably not want to do that! Du hast schon
das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of
Office 2003 on your Server and install that application on each
workstation from that Admin Installation. The advantages of doing
this are 1) you have a common, accessible installation point and 2)
you do not have to worry about losing the Office 2003 CD! However,
the disadvantage of doing this ( compared to my next suggestion ) is
that when you want to update the clients ( sagen wir, dass Microsoft
Office 2003 SP1 liefiert ) you have the problem of updating each
client - this usually involves uninstalling Office 2003 from each
client ( you could use the utility from the Office 2003 Resource Kit
to do this! ) and then running the installation on each workstation.
Sure, you could probably do this via a logon script, but you still
have the administrative overhead ( you have to write the additional
lines in the logon script and make sure that it is run on each
machine and then rem out the additional lines in the logon script ).
So, with this solution you have a really nicely located
Administrative Installation Point that you can nicely keep up to
date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using
Group Policy to install Office 2003 to all of your computers ( or
users ). You simply make that one Administrative Installation Point
( via setup.exe /a ) - which you can still update when security
patches are releases or when a Service Pack is released - and you
have the ability to very quickly and without much administrative
overhead install this to your clients and - here comes a really neat
point - easily and quickly update the clients when those security
patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation
( say that Heinz and Hans get Excel, Word and Outlook while Ulrike
and Petra get PowerPoint, Word and Outlook ). Furthermore, you can
set a lot of the options via a GPO that will ensure that all of your
users have the settings that they need. You will not have to go to
each computer and make sure that all of those specific settings are
properly configured. Do it via the GPO and there you have it!
Also, you can control it so that your clients can not go to the
officeupdate.microsoft.com and make untested updates to the Office
2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber
das Group Policy Object haben....

HTH,

Cary
Click to expand...
Click to expand...
 
C

Chad A. Gross [SBS MVP]

I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.
Click to expand...

Because it doesn't work that way. Same reason you can't put your Chevy in
the Pacific and sail to China . . .

Windows applications require to be installed on the machine where they are
being executed. If the application is going to be executed from the PC,
then it needs to be installed there. If it is going to be executed from the
server, then it needs to be installed on the server, and you're looking at a
TS / Citrix solution. I'm sorry if you don't like that answer, but that's
the way it is.

--

Chad A. Gross - SBS MVP
SBS ROCKS!

www.msmvps.com/cgross
www.gosbs.org


Sarah said:
I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.

If I need to upgrade, all I have to do is upgrade the server and
those 10(or 100 workstation) will get updated instantly without
clogging up the network for transferring files between the server and
those 10(or 100) client workstation.

I think you all know what I'm talking about but most of your
MVP[Microsoft ....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really
good idea. I have been using Terminal Server for the last 15 months
or so and it is generally a great thing. As Kevin mentioned, you
can no longer install Terminal Server in Application Mode ( err,
that is the WIN2000 terminology.... ) on the SBS2003 Server itself.
There are some very good reasons for this. You would need a second
server that would be the Terminal Server. On SBS2000 you can indeed
do this - but again, not generally a good idea to run Terminal
Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really
good point / question as to why do you would want to turn them into
thin clients. I would probably not want to do that! Du hast schon
das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of
Office 2003 on your Server and install that application on each
workstation from that Admin Installation. The advantages of doing
this are 1) you have a common, accessible installation point and 2)
you do not have to worry about losing the Office 2003 CD! However,
the disadvantage of doing this ( compared to my next suggestion ) is
that when you want to update the clients ( sagen wir, dass Microsoft
Office 2003 SP1 liefiert ) you have the problem of updating each
client - this usually involves uninstalling Office 2003 from each
client ( you could use the utility from the Office 2003 Resource Kit
to do this! ) and then running the installation on each workstation.
Sure, you could probably do this via a logon script, but you still
have the administrative overhead ( you have to write the additional
lines in the logon script and make sure that it is run on each
machine and then rem out the additional lines in the logon script ).
So, with this solution you have a really nicely located
Administrative Installation Point that you can nicely keep up to
date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using
Group Policy to install Office 2003 to all of your computers ( or
users ). You simply make that one Administrative Installation Point
( via setup.exe /a ) - which you can still update when security
patches are releases or when a Service Pack is released - and you
have the ability to very quickly and without much administrative
overhead install this to your clients and - here comes a really neat
point - easily and quickly update the clients when those security
patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation
( say that Heinz and Hans get Excel, Word and Outlook while Ulrike
and Petra get PowerPoint, Word and Outlook ). Furthermore, you can
set a lot of the options via a GPO that will ensure that all of your
users have the settings that they need. You will not have to go to
each computer and make sure that all of those specific settings are
properly configured. Do it via the GPO and there you have it!
Also, you can control it so that your clients can not go to the
officeupdate.microsoft.com and make untested updates to the Office
2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber
das Group Policy Object haben....

HTH,

Cary
Click to expand...
Click to expand...
 
C

Chad A. Gross [SBS MVP]

I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.
Click to expand...

Because it doesn't work that way. Same reason you can't put your Chevy in
the Pacific and sail to China . . .

Windows applications require to be installed on the machine where they are
being executed. If the application is going to be executed from the PC,
then it needs to be installed there. If it is going to be executed from the
server, then it needs to be installed on the server, and you're looking at a
TS / Citrix solution. I'm sorry if you don't like that answer, but that's
the way it is.

--

Chad A. Gross - SBS MVP
SBS ROCKS!

www.msmvps.com/cgross
www.gosbs.org


Sarah said:
I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.

If I need to upgrade, all I have to do is upgrade the server and
those 10(or 100 workstation) will get updated instantly without
clogging up the network for transferring files between the server and
those 10(or 100) client workstation.

I think you all know what I'm talking about but most of your
MVP[Microsoft ....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really
good idea. I have been using Terminal Server for the last 15 months
or so and it is generally a great thing. As Kevin mentioned, you
can no longer install Terminal Server in Application Mode ( err,
that is the WIN2000 terminology.... ) on the SBS2003 Server itself.
There are some very good reasons for this. You would need a second
server that would be the Terminal Server. On SBS2000 you can indeed
do this - but again, not generally a good idea to run Terminal
Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really
good point / question as to why do you would want to turn them into
thin clients. I would probably not want to do that! Du hast schon
das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of
Office 2003 on your Server and install that application on each
workstation from that Admin Installation. The advantages of doing
this are 1) you have a common, accessible installation point and 2)
you do not have to worry about losing the Office 2003 CD! However,
the disadvantage of doing this ( compared to my next suggestion ) is
that when you want to update the clients ( sagen wir, dass Microsoft
Office 2003 SP1 liefiert ) you have the problem of updating each
client - this usually involves uninstalling Office 2003 from each
client ( you could use the utility from the Office 2003 Resource Kit
to do this! ) and then running the installation on each workstation.
Sure, you could probably do this via a logon script, but you still
have the administrative overhead ( you have to write the additional
lines in the logon script and make sure that it is run on each
machine and then rem out the additional lines in the logon script ).
So, with this solution you have a really nicely located
Administrative Installation Point that you can nicely keep up to
date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using
Group Policy to install Office 2003 to all of your computers ( or
users ). You simply make that one Administrative Installation Point
( via setup.exe /a ) - which you can still update when security
patches are releases or when a Service Pack is released - and you
have the ability to very quickly and without much administrative
overhead install this to your clients and - here comes a really neat
point - easily and quickly update the clients when those security
patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation
( say that Heinz and Hans get Excel, Word and Outlook while Ulrike
and Petra get PowerPoint, Word and Outlook ). Furthermore, you can
set a lot of the options via a GPO that will ensure that all of your
users have the settings that they need. You will not have to go to
each computer and make sure that all of those specific settings are
properly configured. Do it via the GPO and there you have it!
Also, you can control it so that your clients can not go to the
officeupdate.microsoft.com and make untested updates to the Office
2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber
das Group Policy Object haben....

HTH,

Cary
Click to expand...
Click to expand...
 
C

Chad A. Gross [SBS MVP]

I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.
Click to expand...

Because it doesn't work that way. Same reason you can't put your Chevy in
the Pacific and sail to China . . .

Windows applications require to be installed on the machine where they are
being executed. If the application is going to be executed from the PC,
then it needs to be installed there. If it is going to be executed from the
server, then it needs to be installed on the server, and you're looking at a
TS / Citrix solution. I'm sorry if you don't like that answer, but that's
the way it is.

--

Chad A. Gross - SBS MVP
SBS ROCKS!

www.msmvps.com/cgross
www.gosbs.org


Sarah said:
I think this is very inefficient. Why can I install my apps on a disk
in my server and mount that disk on my workstation and execute the
exe file from there.

If I need to upgrade, all I have to do is upgrade the server and
those 10(or 100 workstation) will get updated instantly without
clogging up the network for transferring files between the server and
those 10(or 100) client workstation.

I think you all know what I'm talking about but most of your
MVP[Microsoft ....] are avoding the issues.

Please ....


Cary Shultz said:
Sarah,

I might jump in here for a second.

First of all, the idea of a Terminal Server is generally a really
good idea. I have been using Terminal Server for the last 15 months
or so and it is generally a great thing. As Kevin mentioned, you
can no longer install Terminal Server in Application Mode ( err,
that is the WIN2000 terminology.... ) on the SBS2003 Server itself.
There are some very good reasons for this. You would need a second
server that would be the Terminal Server. On SBS2000 you can indeed
do this - but again, not generally a good idea to run Terminal
Server in Application Mode on a Domain Controller....

However, since you have powerful workstations, you have a really
good point / question as to why do you would want to turn them into
thin clients. I would probably not want to do that! Du hast schon
das Geld ausgegeben!

Secondly, you can indeed make an Administrative Installation of
Office 2003 on your Server and install that application on each
workstation from that Admin Installation. The advantages of doing
this are 1) you have a common, accessible installation point and 2)
you do not have to worry about losing the Office 2003 CD! However,
the disadvantage of doing this ( compared to my next suggestion ) is
that when you want to update the clients ( sagen wir, dass Microsoft
Office 2003 SP1 liefiert ) you have the problem of updating each
client - this usually involves uninstalling Office 2003 from each
client ( you could use the utility from the Office 2003 Resource Kit
to do this! ) and then running the installation on each workstation.
Sure, you could probably do this via a logon script, but you still
have the administrative overhead ( you have to write the additional
lines in the logon script and make sure that it is run on each
machine and then rem out the additional lines in the logon script ).
So, with this solution you have a really nicely located
Administrative Installation Point that you can nicely keep up to
date but you have the problem on the workstations.

So, I would suggest to you that you take a good long look at using
Group Policy to install Office 2003 to all of your computers ( or
users ). You simply make that one Administrative Installation Point
( via setup.exe /a ) - which you can still update when security
patches are releases or when a Service Pack is released - and you
have the ability to very quickly and without much administrative
overhead install this to your clients and - here comes a really neat
point - easily and quickly update the clients when those security
patches or Service Packs are released. Additionally, if you make
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation
( say that Heinz and Hans get Excel, Word and Outlook while Ulrike
and Petra get PowerPoint, Word and Outlook ). Furthermore, you can
set a lot of the options via a GPO that will ensure that all of your
users have the settings that they need. You will not have to go to
each computer and make sure that all of those specific settings are
properly configured. Do it via the GPO and there you have it!
Also, you can control it so that your clients can not go to the
officeupdate.microsoft.com and make untested updates to the Office
2003 installation. This is a really nice feature as well.....

Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber
das Group Policy Object haben....

HTH,

Cary
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Outlook Desktop (latest) stopped syncing IMAP accpounts from selfowned Mail server. 0
Can someone provide me with info on how Office 365 works? 2
Microsoft 365 Activations, Users or Devices? 0
Office 2003 Admin Installation Point 0
VSTO C# add in Outlook.Appointment error 0
office 2003 pro to 2007 standard 0
ODBC error 100 when accessing Bookkeeper version 15 software (accounting software using Access dbase) 0
A couple questions BEFORE using Office 365 0

Top