Discussion:
Networked Office
(too old to reply)
Sarah Tanembaum
2004-07-16 19:30:21 UTC
Permalink
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
Chris Jones
2004-07-16 17:55:27 UTC
Permalink
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.
Post by Sarah Tanembaum
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
Sarah Tanembaum
2004-07-17 01:38:44 UTC
Permalink
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?
Post by Chris Jones
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.
Post by Sarah Tanembaum
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.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
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
Kevin Weilbacher [SBS-MVP]
2004-07-17 01:44:26 UTC
Permalink
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"
Post by Sarah Tanembaum
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?
Post by Sarah Tanembaum
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?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
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
Post by Chris Jones
the workstations? You can setup admin install of office to install just
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Sarah Tanembaum
2004-07-17 02:02:48 UTC
Permalink
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
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
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?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to slow
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to install
on
Post by Chris Jones
the workstations? You can setup admin install of office to install just
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Kevin Weilbacher [SBS-MVP]
2004-07-17 03:26:26 UTC
Permalink
Sarah,

There's different solutions available to fit different needs. By your post
it appears that you bought your solution before determining your needs. If
your need and desire is to administer a single installation of Office for
all of your users, then Terminal Services is a valid solution.

Is this against MS idealogy? Not in my mind, since there are many, many
companies, both large and small, that have installed Terminal Services as a
solution. As with all needs/solutions, you weight the benefits, the pros and
cons, and make the best choice possible.

You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in maintaining,
upgrading, and patching standard PC's with individual copies of Windows and
Office installed on each PC to be a high priority issue. So, if you can
reduce the overhead and hassle of administering such a network, then you've
answered your own question: yes, it's economical.

Don't know what you mean by claiming that Microsoft is still ironing out how
to implement such a solution. I previously managed the IT dept for a large
health care facility that has over 200 users operating on Microsoft Windows
Terminal Server. You want to talk about economical? You want to talk about
redundancy? You want to talk about ease of administering such network? You
want to talk about implementing new security policies?

No, a TS environment is not for all ... but don't just knock it ... it is a
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'. You
are
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS server.
The
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
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?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to slow
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Sarah Tanembaum
2004-07-18 09:49:32 UTC
Permalink
Hi Kevin, as stated on my previous email. I have a very powerful server and
workstation. For ease of administration, why would I purchase another
terminal server licenses if there are such solution(which in my mind it is
very easy to implement in a client-server environment)
where make use the power of the workstation.

By using the terminal services, we are adding another cost of terminal
services license and the server does not scale well for active users.

The solution I propose(I'm sure that you know what I'm talking about) we
are make use what we have now(powerful workstation) to run an app from a
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By your post
it appears that you bought your solution before determining your needs. If
your need and desire is to administer a single installation of Office for
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many, many
companies, both large and small, that have installed Terminal Services as a
solution. As with all needs/solutions, you weight the benefits, the pros and
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in maintaining,
upgrading, and patching standard PC's with individual copies of Windows and
Office installed on each PC to be a high priority issue. So, if you can
reduce the overhead and hassle of administering such a network, then you've
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing out how
to implement such a solution. I previously managed the IT dept for a large
health care facility that has over 200 users operating on Microsoft Windows
Terminal Server. You want to talk about economical? You want to talk about
redundancy? You want to talk about ease of administering such network? You
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it ... it is a
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'. You
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does not
allow you to configure Terminal Server on the SBS server itself. You can
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS server.
The
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store all
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my workstation
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the office
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to slow
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
2004-07-19 05:30:25 UTC
Permalink
Install the Office on the workstations, save the files on the server.

If you have powerful workstations that would be the better solution anyway.
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful server and
workstation. For ease of administration, why would I purchase another
terminal server licenses if there are such solution(which in my mind it is
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of terminal
services license and the server does not scale well for active users.
The solution I propose(I'm sure that you know what I'm talking about) we
are make use what we have now(powerful workstation) to run an app from a
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By your post
it appears that you bought your solution before determining your needs. If
your need and desire is to administer a single installation of Office for
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many, many
companies, both large and small, that have installed Terminal Services as
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits, the pros
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in maintaining,
upgrading, and patching standard PC's with individual copies of Windows
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if you can
reduce the overhead and hassle of administering such a network, then
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing out
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept for a large
health care facility that has over 200 users operating on Microsoft
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to talk about
redundancy? You want to talk about ease of administering such network? You
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it ... it is
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself. You
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS server
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store all
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my workstation
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's the
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-19 08:18:55 UTC
Permalink
Susan, the point is to ease up the administration. Why would one install an
application over and over for each workstation. The file already available
in the server.

All it needs is to just execute the program at the workstation and voila!

With this method, instant update can be done easily. Just update the file on
the server and all, I mean ALL workstation, will get update instantly.

Funny that MS has only 2 choices:
1-run all in the workstation which will be an administration headache
2-run all in the server(terminal services) which does not scale so well.
I've been thru since the citrix winframe days, terminal services, metaframe
.... it's not worth waste your money.

The solution I mentioned will be much better solution. It scales so well and
it combines the best of server, workstation, and networking technology.

I wonder when MS will get there? Unless we(user community) push it, MS won't
do it. Well, they won't listen anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Install the Office on the workstations, save the files on the server.
If you have powerful workstations that would be the better solution anyway.
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful server and
workstation. For ease of administration, why would I purchase another
terminal server licenses if there are such solution(which in my mind it is
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of terminal
services license and the server does not scale well for active users.
The solution I propose(I'm sure that you know what I'm talking about) we
are make use what we have now(powerful workstation) to run an app from a
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By your post
it appears that you bought your solution before determining your needs. If
your need and desire is to administer a single installation of Office for
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many, many
companies, both large and small, that have installed Terminal Services as
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits, the pros
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in maintaining,
upgrading, and patching standard PC's with individual copies of Windows
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if you can
reduce the overhead and hassle of administering such a network, then
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing out
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept for a large
health care facility that has over 200 users operating on Microsoft
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to talk about
redundancy? You want to talk about ease of administering such network? You
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it ... it is
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself. You
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS server
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store all
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my workstation
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's the
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Cary Shultz [A.D. MVP]
2004-07-19 14:04:32 UTC
Permalink
Sarah,

Group Policy does exactly this. You make the Administrative Installation
Point and install to the workstations from this AIP. All need to do
updates? Update the AIP and then simply go to the GPO and select
'redeploy'. The next time the user logs on or the computer restarts (
depending on how you did this ) the update is deployed. Users delete a file
on their local workstation, something like WinWord.exe or an important .dll
file, and the GPO is smart enough to know this and will shoot down this file
to the particular client. It is part of the self-healing feature of
deploying applications via GPO.

Cary
Post by Sarah Tanembaum
Susan, the point is to ease up the administration. Why would one install an
application over and over for each workstation. The file already available
in the server.
All it needs is to just execute the program at the workstation and voila!
With this method, instant update can be done easily. Just update the file on
the server and all, I mean ALL workstation, will get update instantly.
1-run all in the workstation which will be an administration headache
2-run all in the server(terminal services) which does not scale so well.
I've been thru since the citrix winframe days, terminal services, metaframe
.... it's not worth waste your money.
The solution I mentioned will be much better solution. It scales so well and
it combines the best of server, workstation, and networking technology.
I wonder when MS will get there? Unless we(user community) push it, MS won't
do it. Well, they won't listen anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Install the Office on the workstations, save the files on the server.
If you have powerful workstations that would be the better solution
anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful
server
Post by Sarah Tanembaum
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
workstation. For ease of administration, why would I purchase another
terminal server licenses if there are such solution(which in my mind
it
Post by Sarah Tanembaum
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of terminal
services license and the server does not scale well for active users.
The solution I propose(I'm sure that you know what I'm talking about)
we
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
are make use what we have now(powerful workstation) to run an app from a
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By your
post
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
it appears that you bought your solution before determining your
needs.
Post by Sarah Tanembaum
If
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
your need and desire is to administer a single installation of Office
for
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many, many
companies, both large and small, that have installed Terminal Services
as
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits, the pros
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in maintaining,
upgrading, and patching standard PC's with individual copies of Windows
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if you can
reduce the overhead and hassle of administering such a network, then
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing out
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept for a
large
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
health care facility that has over 200 users operating on Microsoft
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to talk
about
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
redundancy? You want to talk about ease of administering such network?
You
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it ... it
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself. You
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS server
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store all
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my workstation
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's the
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Cary Shultz [A.D. MVP]
2004-07-19 14:36:14 UTC
Permalink
Or, instead of the updates via the GPO you could use WUS.

Cary
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
Group Policy does exactly this. You make the Administrative Installation
Point and install to the workstations from this AIP. All need to do
updates? Update the AIP and then simply go to the GPO and select
'redeploy'. The next time the user logs on or the computer restarts (
depending on how you did this ) the update is deployed. Users delete a file
on their local workstation, something like WinWord.exe or an important .dll
file, and the GPO is smart enough to know this and will shoot down this file
to the particular client. It is part of the self-healing feature of
deploying applications via GPO.
Cary
Post by Sarah Tanembaum
Susan, the point is to ease up the administration. Why would one install
an
Post by Sarah Tanembaum
application over and over for each workstation. The file already available
in the server.
All it needs is to just execute the program at the workstation and voila!
With this method, instant update can be done easily. Just update the
file
Post by Kevin Weilbacher [SBS-MVP]
on
Post by Sarah Tanembaum
the server and all, I mean ALL workstation, will get update instantly.
1-run all in the workstation which will be an administration headache
2-run all in the server(terminal services) which does not scale so well.
I've been thru since the citrix winframe days, terminal services,
metaframe
Post by Sarah Tanembaum
.... it's not worth waste your money.
The solution I mentioned will be much better solution. It scales so well
and
Post by Sarah Tanembaum
it combines the best of server, workstation, and networking technology.
I wonder when MS will get there? Unless we(user community) push it, MS
won't
Post by Sarah Tanembaum
do it. Well, they won't listen anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Install the Office on the workstations, save the files on the server.
If you have powerful workstations that would be the better solution
anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful
server
Post by Sarah Tanembaum
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
workstation. For ease of administration, why would I purchase another
terminal server licenses if there are such solution(which in my mind
it
Post by Sarah Tanembaum
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of terminal
services license and the server does not scale well for active users.
The solution I propose(I'm sure that you know what I'm talking about)
we
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
are make use what we have now(powerful workstation) to run an app
from
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By your
post
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
it appears that you bought your solution before determining your
needs.
Post by Sarah Tanembaum
If
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
your need and desire is to administer a single installation of Office
for
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many,
many
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
companies, both large and small, that have installed Terminal Services
as
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits, the
pros
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in
maintaining,
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
upgrading, and patching standard PC's with individual copies of
Windows
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if you
can
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reduce the overhead and hassle of administering such a network, then
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing
out
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept for a
large
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
health care facility that has over 200 users operating on Microsoft
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to talk
about
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
redundancy? You want to talk about ease of administering such network?
You
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it ... it
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
type
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself. You
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS server
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store
all
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my
workstation
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's the
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-19 18:05:16 UTC
Permalink
Thanks Cary.

I've use redeployment process quite often for many different OS which
include Windows as well.

For a small size of file, the push-method is quite efficient, e.g: scripts,
small files that is absolutely necessary to reside on each individual
workstation(In my view, if the apps were designed with
multi-user-multi-system-client-server in mind, there should be no(very
little)dependency on the workstation at all.

This push-method(== Redeployment == Update Service) put too much strain on
the network bandwidth(imagine if you have 1000 workstation, and you need to
update those instantaneously). Also, it adds substantial amount of disk
space(I know it does not cost much, but why waste it).

Seriously, what prevent MS cannot be executed from fileserver?

Thanks again

Sarah
Post by Cary Shultz [A.D. MVP]
Or, instead of the updates via the GPO you could use WUS.
Cary
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
Group Policy does exactly this. You make the Administrative
Installation
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Point and install to the workstations from this AIP. All need to do
updates? Update the AIP and then simply go to the GPO and select
'redeploy'. The next time the user logs on or the computer restarts (
depending on how you did this ) the update is deployed. Users delete a
file
Post by Kevin Weilbacher [SBS-MVP]
on their local workstation, something like WinWord.exe or an important
.dll
Post by Kevin Weilbacher [SBS-MVP]
file, and the GPO is smart enough to know this and will shoot down this
file
Post by Kevin Weilbacher [SBS-MVP]
to the particular client. It is part of the self-healing feature of
deploying applications via GPO.
Cary
Post by Sarah Tanembaum
Susan, the point is to ease up the administration. Why would one install
an
Post by Sarah Tanembaum
application over and over for each workstation. The file already
available
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
in the server.
All it needs is to just execute the program at the workstation and
voila!
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
With this method, instant update can be done easily. Just update the
file
Post by Kevin Weilbacher [SBS-MVP]
on
Post by Sarah Tanembaum
the server and all, I mean ALL workstation, will get update instantly.
1-run all in the workstation which will be an administration headache
2-run all in the server(terminal services) which does not scale so well.
I've been thru since the citrix winframe days, terminal services,
metaframe
Post by Sarah Tanembaum
.... it's not worth waste your money.
The solution I mentioned will be much better solution. It scales so well
and
Post by Sarah Tanembaum
it combines the best of server, workstation, and networking technology.
I wonder when MS will get there? Unless we(user community) push it, MS
won't
Post by Sarah Tanembaum
do it. Well, they won't listen anyway.
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Install the Office on the workstations, save the files on the server.
If you have powerful workstations that would be the better solution
anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful
server
Post by Sarah Tanembaum
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
workstation. For ease of administration, why would I purchase
another
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
terminal server licenses if there are such solution(which in my mind
it
Post by Sarah Tanembaum
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of
terminal
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
services license and the server does not scale well for active
users.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
The solution I propose(I'm sure that you know what I'm talking
about)
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
we
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
are make use what we have now(powerful workstation) to run an app
from
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By
your
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
post
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
it appears that you bought your solution before determining your
needs.
Post by Sarah Tanembaum
If
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
your need and desire is to administer a single installation of
Office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
for
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many,
many
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
companies, both large and small, that have installed Terminal
Services
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits, the
pros
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that
you
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
consider the time and cost of administrative overhead in
maintaining,
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
upgrading, and patching standard PC's with individual copies of
Windows
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if you
can
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reduce the overhead and hassle of administering such a network, then
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing
out
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept for a
large
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
health care facility that has over 200 users operating on Microsoft
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to talk
about
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
redundancy? You want to talk about ease of administering such
network?
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
You
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it
...
Post by Cary Shultz [A.D. MVP]
it
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
to access the terminal server. It is just not economical.
Or perhaps Microsoft is still ironing-out on how to implement this
this
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
type
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal
Server'.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003
does
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS server
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store
all
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my
workstation
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's the
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
a***@tiscali.co.uk
2004-07-19 20:46:46 UTC
Permalink
You can run office from a network share if you so choose. Create an
Administrative Install on the server, use the custom installation wizard to
create a .MST where all the options are set to "Run from the Network",
deploy via Active Directory or a login script. Not exactly rocket science.

So why is nobody advising you to do this? Simple:

1) Speed - You have "ample memory and disk space" on the client machines, so
you might as well use it. Having Office stored locally will dramatically
improve load times. Nobody will thank you if things takes ages to load.

2) Resilience - Sooner or later your network is going to experience one of
those temporary glitches. Whether it's a loose cable or a helpful building
maintainance chap who decides to unplug your router so he can plug his drill
in. Do you really want all your staff to lose access to their core
applications while it's sorted out? Worst still, what happens if the server
hardware fails? Even with an emergency call-out contract that's a lot of
business hours to be losing while your staff sit around helpless.

3) Patching - Contrary to what you might think, it's considerably easier to
patch an install point and then push out the changes than it is to patch a
potentially in-use resource. What happens if someone starts Word whilst your
in the middle of applying the latest Office service pack? I think your
mistaken in assuming that using a push method is going to be slow. Windows
is smart enough to only copy the bits that have changed so deploying an
Office patch only takes a minute or two.

4) Scalability - The number of copies of an application you can use is
limited by the bandwidth of the server. You can't easily load balance it
with, for example, DFS because that introduces potential version skewing
issues when you apply updates. Neither of these issues apply to a fully
pushed install.

I'd strongly advise you to rethink running things directly off a single
server, there are a lot of very knowledgeable people here giving you very
sound advice and you'd be wise to listen.

AndyC
Post by Sarah Tanembaum
Thanks Cary.
I've use redeployment process quite often for many different OS which
include Windows as well.
For a small size of file, the push-method is quite efficient, e.g: scripts,
small files that is absolutely necessary to reside on each individual
workstation(In my view, if the apps were designed with
multi-user-multi-system-client-server in mind, there should be no(very
little)dependency on the workstation at all.
This push-method(== Redeployment == Update Service) put too much strain on
the network bandwidth(imagine if you have 1000 workstation, and you need to
update those instantaneously). Also, it adds substantial amount of disk
space(I know it does not cost much, but why waste it).
Seriously, what prevent MS cannot be executed from fileserver?
Thanks again
Sarah
Post by Cary Shultz [A.D. MVP]
Or, instead of the updates via the GPO you could use WUS.
Cary
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
Group Policy does exactly this. You make the Administrative
Installation
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Point and install to the workstations from this AIP. All need to do
updates? Update the AIP and then simply go to the GPO and select
'redeploy'. The next time the user logs on or the computer restarts (
depending on how you did this ) the update is deployed. Users delete a
file
Post by Kevin Weilbacher [SBS-MVP]
on their local workstation, something like WinWord.exe or an important
.dll
Post by Kevin Weilbacher [SBS-MVP]
file, and the GPO is smart enough to know this and will shoot down this
file
Post by Kevin Weilbacher [SBS-MVP]
to the particular client. It is part of the self-healing feature of
deploying applications via GPO.
Cary
Post by Sarah Tanembaum
Susan, the point is to ease up the administration. Why would one
install
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
application over and over for each workstation. The file already
available
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
in the server.
All it needs is to just execute the program at the workstation and
voila!
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
With this method, instant update can be done easily. Just update the
file
Post by Kevin Weilbacher [SBS-MVP]
on
Post by Sarah Tanembaum
the server and all, I mean ALL workstation, will get update instantly.
1-run all in the workstation which will be an administration headache
2-run all in the server(terminal services) which does not scale so
well.
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
I've been thru since the citrix winframe days, terminal services,
metaframe
Post by Sarah Tanembaum
.... it's not worth waste your money.
The solution I mentioned will be much better solution. It scales so
well
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
and
Post by Sarah Tanembaum
it combines the best of server, workstation, and networking
technology.
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
I wonder when MS will get there? Unless we(user community) push it, MS
won't
Post by Sarah Tanembaum
do it. Well, they won't listen anyway.
"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Install the Office on the workstations, save the files on the
server.
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
If you have powerful workstations that would be the better solution
anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful
server
Post by Sarah Tanembaum
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
workstation. For ease of administration, why would I purchase
another
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
terminal server licenses if there are such solution(which in my
mind
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
it
Post by Sarah Tanembaum
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of
terminal
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
services license and the server does not scale well for active
users.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
The solution I propose(I'm sure that you know what I'm talking
about)
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
we
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
are make use what we have now(powerful workstation) to run an app
from
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By
your
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
post
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
it appears that you bought your solution before determining your
needs.
Post by Sarah Tanembaum
If
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
your need and desire is to administer a single installation of
Office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
for
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many,
many
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
companies, both large and small, that have installed Terminal
Services
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits,
the
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
pros
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that
you
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
consider the time and cost of administrative overhead in
maintaining,
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
upgrading, and patching standard PC's with individual copies of
Windows
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if
you
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
can
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reduce the overhead and hassle of administering such a network,
then
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still
ironing
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
out
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept
for
Post by Sarah Tanembaum
a
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
large
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
health care facility that has over 200 users operating on
Microsoft
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to
talk
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
about
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
redundancy? You want to talk about ease of administering such
network?
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
You
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it
...
Post by Cary Shultz [A.D. MVP]
it
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
We have pretty powerful workstation and server, why would I use
my
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
workstation
as a terminal(Isn't this goes again MS ideology)?
Secondly, why would I pay an additional license for each
workstation
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
to access the terminal server. It is just not economical.
Or perhaps Microsoft is still ironing-out on how to implement
this
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
this
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
type
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal
Server'.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system,
and
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003
does
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS
server
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will
store
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
all
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my
workstation
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's
the
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the
directory
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server
and
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going
to
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont
want
Post by Sarah Tanembaum
to
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the
workstation,
Post by Sarah Tanembaum
is
Post by Cary Shultz [A.D. MVP]
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Serialdj
2004-10-22 14:29:03 UTC
Permalink
If your issue is with ease of recovery, and all machines are the same
make/model then I have simple solution. Build one machine, install Windows,
Office, all updates everything. Buy Symantec Ghost Enterprise, install it as
a server.

Ghost this machine and push its image to each other machine on the network.

If one machine dies, just re-image it from Ghost and everything is back in
less then 10 minutes.
Post by Sarah Tanembaum
Susan, the point is to ease up the administration. Why would one install an
application over and over for each workstation. The file already available
in the server.
All it needs is to just execute the program at the workstation and voila!
With this method, instant update can be done easily. Just update the file on
the server and all, I mean ALL workstation, will get update instantly.
1-run all in the workstation which will be an administration headache
2-run all in the server(terminal services) which does not scale so well.
I've been thru since the citrix winframe days, terminal services, metaframe
..... it's not worth waste your money.
The solution I mentioned will be much better solution. It scales so well and
it combines the best of server, workstation, and networking technology.
I wonder when MS will get there? Unless we(user community) push it, MS won't
do it. Well, they won't listen anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Install the Office on the workstations, save the files on the server.
If you have powerful workstations that would be the better solution
anyway.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Hi Kevin, as stated on my previous email. I have a very powerful server
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
workstation. For ease of administration, why would I purchase another
terminal server licenses if there are such solution(which in my mind it
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
very easy to implement in a client-server environment)
where make use the power of the workstation.
By using the terminal services, we are adding another cost of terminal
services license and the server does not scale well for active users.
The solution I propose(I'm sure that you know what I'm talking about)
we
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
are make use what we have now(powerful workstation) to run an app from a
file server. Its just as simple as that.
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
There's different solutions available to fit different needs. By your
post
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
it appears that you bought your solution before determining your needs.
If
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
your need and desire is to administer a single installation of Office
for
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
all of your users, then Terminal Services is a valid solution.
Is this against MS idealogy? Not in my mind, since there are many, many
companies, both large and small, that have installed Terminal Services
as
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
solution. As with all needs/solutions, you weight the benefits, the pros
and
Post by Kevin Weilbacher [SBS-MVP]
cons, and make the best choice possible.
You say it's not economical. But compared to what? It appears that you
consider the time and cost of administrative overhead in maintaining,
upgrading, and patching standard PC's with individual copies of Windows
and
Post by Kevin Weilbacher [SBS-MVP]
Office installed on each PC to be a high priority issue. So, if you can
reduce the overhead and hassle of administering such a network, then
you've
Post by Kevin Weilbacher [SBS-MVP]
answered your own question: yes, it's economical.
Don't know what you mean by claiming that Microsoft is still ironing out
how
Post by Kevin Weilbacher [SBS-MVP]
to implement such a solution. I previously managed the IT dept for a
large
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
health care facility that has over 200 users operating on Microsoft
Windows
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server. You want to talk about economical? You want to talk
about
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
redundancy? You want to talk about ease of administering such network?
You
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
want to talk about implementing new security policies?
No, a TS environment is not for all ... but don't just knock it ... it
is
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
valid solution for those with the need of such a solution.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
of
technology(networked-multi-user-multi-task-apps)?
Thanks
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'.
You
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does
not
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
allow you to configure Terminal Server on the SBS server itself. You
can
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
temrinal server would house your Office apps, and your SBS server
would
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
I'm trying to use my server as a file server, where I will store all
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Office executable. If MS so willing, then they can tell us what
registry
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
setting on the local machine has to change so each of my workstation
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
run
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
Is it a technology issues that prevent this to happen? What's the
big
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
problem since other OSes can handle multi-user apps?
Imagine if I can do that, everytime the workstation crashed and
corrupted
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
upgrade, all I have to do is to upgrade the one on the server and
again,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
those 10(or for that matter 100K)workstation has their office
upgraded!
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Greg Stigers, MCSA
2004-10-24 00:08:21 UTC
Permalink
Look at Automated Deployment Services in Server 2003.
--
Greg Stigers, MCSA
remember to vote for the answers you like
Frank McCallister
2004-07-17 03:39:31 UTC
Permalink
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
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'. You
are
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS server.
The
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
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?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to slow
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Sarah Tanembaum
2004-07-18 09:51:55 UTC
Permalink
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?
Post by Frank McCallister
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
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'. You
are
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS server.
The
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
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?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to slow
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Frank McCallister
2004-07-18 16:20:22 UTC
Permalink
Hi Sarah

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

Frank
Post by Sarah Tanembaum
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?
Post by Frank McCallister
Hi Sarah
You can run the executables from the server if you wish but a certain
number
Post by Frank McCallister
of DLLs will have to be on the WS. You don't want to do this though
because
Post by Frank McCallister
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
Post by Sarah Tanembaum
Thanks Kevin. Unfortunately the terminal services are out of the
question.
Post by Frank McCallister
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Sarah, what you have described is called 'Windows Terminal Server'. You
are
Post by Kevin Weilbacher [SBS-MVP]
right about the fact that by installing Office on one system, and
letting
Post by Frank McCallister
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
everyone access it reduces administrative issues. But, SBS2003 does not
allow you to configure Terminal Server on the SBS server itself. You
can
Post by Frank McCallister
Post by Sarah Tanembaum
add
Post by Kevin Weilbacher [SBS-MVP]
a separate system to act as a terminal server alongside your SBS
server.
Post by Frank McCallister
Post by Sarah Tanembaum
The
Post by Kevin Weilbacher [SBS-MVP]
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"
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
office apps, e.g. MS Word, Excel, and other, right from their
workstation?
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
the disk, all I have to do is install the os, mount the directory
where
Post by Frank McCallister
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
office reside, and voile ... it's back up again. Also, when the
office
Post by Frank McCallister
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
need
Post by Sarah Tanembaum
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!
Post by Frank McCallister
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Any ideas?
Post by Chris Jones
I think you have the option upon installing if you want to install
Office
Post by Sarah Tanembaum
to
Post by Chris Jones
a server, but I am thinking if you have 10 users it is going to
slow
Post by Frank McCallister
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
down
Post by Sarah Tanembaum
Post by Chris Jones
your server badly. Is there a particular reason you dont want to
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
on
Post by Chris Jones
the workstations? You can setup admin install of office to install
just
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
like
Post by Chris Jones
Outlook installs on SBS client upon connection.
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Chris Jones
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Chris Jones
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Chris Jones
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Chris Jones
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Milly Staples [MVP - Outlook]
2004-07-16 18:42:19 UTC
Permalink
No, you can either run Office from a TS/Citrix environment or you can
install it locally. You can create an admin installation point on the
server and have the clients load office via a logon script when they first
start Windows. But you cannot run it from a plain server.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Sarah Tanembaum
asked:

| 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
Sarah Tanembaum
2004-07-17 01:39:51 UTC
Permalink
Why not possible?

Thanks.
Post by Milly Staples [MVP - Outlook]
No, you can either run Office from a TS/Citrix environment or you can
install it locally. You can create an admin installation point on the
server and have the clients load office via a logon script when they first
start Windows. But you cannot run it from a plain server.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.
After searching google.groups.com and finding no answer, Sarah Tanembaum
| 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
Milly Staples [MVP - Outlook]
2004-07-17 05:43:35 UTC
Permalink
Please do yourself a favor and look at the Office Resource Kit and the
Windows 2003 (or whatever version of Windows you have) Terminal Services
white papers.

What you are asking has been answered many times here - if it is not the
answer you like, then look for a different vendor/solution. We have all
told you what is and is not possible, the problems inherent in trying to
meet your requests, and have basically given up providing answers that you
do not want to hear.

Office REQUIRES specific files to be installed locally in order to run. If
you want a pure server solution, it will not work.


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Sarah Tanembaum
asked:

| Why not possible?
|
| Thanks.
|
| "Milly Staples [MVP - Outlook]"
| <***@donteventhinkaboutmailingmemvps.org> wrote in message
| news:#***@TK2MSFTNGP10.phx.gbl...
|| No, you can either run Office from a TS/Citrix environment or you can
|| install it locally. You can create an admin installation point on
|| the server and have the clients load office via a logon script when
|| they first start Windows. But you cannot run it from a plain server.
||
|| --
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. Due to
|| the (insert latest virus name here) virus, all mail sent to my
|| personal account will be deleted without reading.
||
|| After searching google.groups.com and finding no answer, Sarah
|| Tanembaum asked:
||
||| 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
catwalker63
2004-07-17 05:54:34 UTC
Permalink
Hallelujah!
--
Kelley
aka catwalker
IT Professional, MCP
Post by Milly Staples [MVP - Outlook]
Please do yourself a favor and look at the Office Resource Kit and the
Windows 2003 (or whatever version of Windows you have) Terminal Services
white papers.
What you are asking has been answered many times here - if it is not the
answer you like, then look for a different vendor/solution. We have all
told you what is and is not possible, the problems inherent in trying to
meet your requests, and have basically given up providing answers that you
do not want to hear.
Office REQUIRES specific files to be installed locally in order to run. If
you want a pure server solution, it will not work.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.
After searching google.groups.com and finding no answer, Sarah Tanembaum
| Why not possible?
|
| Thanks.
|
| "Milly Staples [MVP - Outlook]"
|| No, you can either run Office from a TS/Citrix environment or you can
|| install it locally. You can create an admin installation point on
|| the server and have the clients load office via a logon script when
|| they first start Windows. But you cannot run it from a plain server.
||
|| --
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. Due to
|| the (insert latest virus name here) virus, all mail sent to my
|| personal account will be deleted without reading.
||
|| After searching google.groups.com and finding no answer, Sarah
||
||| 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
Sarah Tanembaum
2004-07-18 09:54:25 UTC
Permalink
Post by Milly Staples [MVP - Outlook]
Office REQUIRES specific files to be installed locally in order to run. If
you want a pure server solution, it will not work.
How many specific file(s) are you talking about? Do you have a list of what
specific files are you mentioning?

Thanks
Post by Milly Staples [MVP - Outlook]
Please do yourself a favor and look at the Office Resource Kit and the
Windows 2003 (or whatever version of Windows you have) Terminal Services
white papers.
What you are asking has been answered many times here - if it is not the
answer you like, then look for a different vendor/solution. We have all
told you what is and is not possible, the problems inherent in trying to
meet your requests, and have basically given up providing answers that you
do not want to hear.
Office REQUIRES specific files to be installed locally in order to run. If
you want a pure server solution, it will not work.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.
After searching google.groups.com and finding no answer, Sarah Tanembaum
| Why not possible?
|
| Thanks.
|
| "Milly Staples [MVP - Outlook]"
|| No, you can either run Office from a TS/Citrix environment or you can
|| install it locally. You can create an admin installation point on
|| the server and have the clients load office via a logon script when
|| they first start Windows. But you cannot run it from a plain server.
||
|| --
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. Due to
|| the (insert latest virus name here) virus, all mail sent to my
|| personal account will be deleted without reading.
||
|| After searching google.groups.com and finding no answer, Sarah
||
||| 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
Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
2004-07-19 05:35:12 UTC
Permalink
Sarah Tanembaum
2004-07-19 08:41:20 UTC
Permalink
What's WUS? Thanks
What you are wanting in a TS install of Office which cannot be done on
SBS2003 without an additional server and TS cals.
You don't have the parts to do this.
So why not install office directly on the workstations? When WUS comes
out you can still centrally patch.
Post by Sarah Tanembaum
Post by Milly Staples [MVP - Outlook]
Office REQUIRES specific files to be installed locally in order to run. If
you want a pure server solution, it will not work.
How many specific file(s) are you talking about? Do you have a list of what
specific files are you mentioning?
Thanks
"Milly Staples [MVP - Outlook]"
Post by Milly Staples [MVP - Outlook]
Please do yourself a favor and look at the Office Resource Kit and the
Windows 2003 (or whatever version of Windows you have) Terminal Services
white papers.
What you are asking has been answered many times here - if it is not the
answer you like, then look for a different vendor/solution. We have all
told you what is and is not possible, the problems inherent in trying to
meet your requests, and have basically given up providing answers that you
do not want to hear.
Office REQUIRES specific files to be installed locally in order to run. If
you want a pure server solution, it will not work.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.
After searching google.groups.com and finding no answer, Sarah Tanembaum
| Why not possible?
|
| Thanks.
|
| "Milly Staples [MVP - Outlook]"
|| No, you can either run Office from a TS/Citrix environment or you can
|| install it locally. You can create an admin installation point on
|| the server and have the clients load office via a logon script when
|| they first start Windows. But you cannot run it from a plain server.
||
|| --
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. Due to
|| the (insert latest virus name here) virus, all mail sent to my
|| personal account will be deleted without reading.
||
|| After searching google.groups.com and finding no answer, Sarah
||
||| 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
--
http://www.sbslinks.com/really.htm
Kevin Weilbacher [SBS-MVP]
2004-07-19 10:01:14 UTC
Permalink
WUS = Windows Update Services
http://www.microsoft.com/windowsserversystem/sus/wusfaq.mspx
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
What's WUS? Thanks
What you are wanting in a TS install of Office which cannot be done on
SBS2003 without an additional server and TS cals.
You don't have the parts to do this.
So why not install office directly on the workstations? When WUS comes
out you can still centrally patch.
Post by Sarah Tanembaum
Post by Milly Staples [MVP - Outlook]
Office REQUIRES specific files to be installed locally in order to
run.
Post by Sarah Tanembaum
If
Post by Sarah Tanembaum
Post by Milly Staples [MVP - Outlook]
you want a pure server solution, it will not work.
How many specific file(s) are you talking about? Do you have a list of
what
Post by Sarah Tanembaum
specific files are you mentioning?
Thanks
"Milly Staples [MVP - Outlook]"
Post by Milly Staples [MVP - Outlook]
Please do yourself a favor and look at the Office Resource Kit and the
Windows 2003 (or whatever version of Windows you have) Terminal Services
white papers.
What you are asking has been answered many times here - if it is not the
answer you like, then look for a different vendor/solution. We have all
told you what is and is not possible, the problems inherent in trying to
meet your requests, and have basically given up providing answers that
you
Post by Sarah Tanembaum
Post by Milly Staples [MVP - Outlook]
do not want to hear.
Office REQUIRES specific files to be installed locally in order to
run.
Post by Sarah Tanembaum
If
Post by Sarah Tanembaum
Post by Milly Staples [MVP - Outlook]
you want a pure server solution, it will not work.
--
Milly Staples [MVP - Outlook]
Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.
After searching google.groups.com and finding no answer, Sarah Tanembaum
| Why not possible?
|
| Thanks.
|
| "Milly Staples [MVP - Outlook]"
|| No, you can either run Office from a TS/Citrix environment or you can
|| install it locally. You can create an admin installation point on
|| the server and have the clients load office via a logon script when
|| they first start Windows. But you cannot run it from a plain server.
||
|| --
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. Due to
|| the (insert latest virus name here) virus, all mail sent to my
|| personal account will be deleted without reading.
||
|| After searching google.groups.com and finding no answer, Sarah
||
||| Is it possible to run office from a server?
|||
||| We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Sarah Tanembaum
Post by Sarah Tanembaum
Post by Milly Staples [MVP - Outlook]
||| 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
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-17 01:54:51 UTC
Permalink
Technically it can be installed and run from the server,
and would save the problem of updating all 10 PCs.
How? Does MS supply a setup script for workstation to run office from
network-mounted-disk?
But as Chris mentioned, it would use huge amounts of the network.
This is not an issues for us. We have ample bandwidth to spare.
You can copy the CDs to the server and install to each
workstation from there.
This does not make any sense. Why can I just use them from network
disk(attached to each workstation), and execute the apps from there? This is
time consuming and it just plain old technology.

The only thing I can think of is if MS is collaborating with:
1. Disk vendors -- so we need to buy a lots of disk space
to store the same executable programs
2. Consultant -- more billable time(yeah.)

But seriously, why don't they(MS) make our lives(SysAdmin) a bit easier?
Once installed, don't
forget "Office Update" as opposed to "Windows Update"
-----Original Message-----
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
.
Dirk-Thomas Brown
2004-07-17 04:15:09 UTC
Permalink
If you do an admin install to the server, you then do an install from that
location on each workstation. You choose custom install and the different
applications have an option to "Run from the network"

It will be SLOW though...

Dirk-Thomas
Post by Sarah Tanembaum
Technically it can be installed and run from the server,
and would save the problem of updating all 10 PCs.
How? Does MS supply a setup script for workstation to run office from
network-mounted-disk?
But as Chris mentioned, it would use huge amounts of the network.
This is not an issues for us. We have ample bandwidth to spare.
You can copy the CDs to the server and install to each
workstation from there.
This does not make any sense. Why can I just use them from network
disk(attached to each workstation), and execute the apps from there? This is
time consuming and it just plain old technology.
1. Disk vendors -- so we need to buy a lots of disk space
to store the same executable programs
2. Consultant -- more billable time(yeah.)
But seriously, why don't they(MS) make our lives(SysAdmin) a bit easier?
Once installed, don't
forget "Office Update" as opposed to "Windows Update"
-----Original Message-----
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
.
Sarah Tanembaum
2004-07-18 09:58:11 UTC
Permalink
Well, I guess MS does not have solution of running apps from a
network-mounted-disk-from-a-server.

I am familiar with terminal services as well citrix/metaframe since the
early days up till now. It just does not scale.

What we have now that we have fast network, fast server, fast disk, and fast
workstation. If there are such solution where almost any new OS can do that
but does not include Microsoft.
Post by Dirk-Thomas Brown
If you do an admin install to the server, you then do an install from that
location on each workstation. You choose custom install and the different
applications have an option to "Run from the network"
It will be SLOW though...
Dirk-Thomas
Post by Sarah Tanembaum
Technically it can be installed and run from the server,
and would save the problem of updating all 10 PCs.
How? Does MS supply a setup script for workstation to run office from
network-mounted-disk?
But as Chris mentioned, it would use huge amounts of the network.
This is not an issues for us. We have ample bandwidth to spare.
You can copy the CDs to the server and install to each
workstation from there.
This does not make any sense. Why can I just use them from network
disk(attached to each workstation), and execute the apps from there?
This
Post by Dirk-Thomas Brown
is
Post by Sarah Tanembaum
time consuming and it just plain old technology.
1. Disk vendors -- so we need to buy a lots of disk space
to store the same executable programs
2. Consultant -- more billable time(yeah.)
But seriously, why don't they(MS) make our lives(SysAdmin) a bit easier?
Once installed, don't
forget "Office Update" as opposed to "Windows Update"
-----Original Message-----
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
.
Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
2004-07-19 05:33:33 UTC
Permalink
Yes, it's called Terminal Server.

If you bought full blown [not thin client] workstations, stick the
office on each one by using group policy push.

Normally for what you want you don't buy fast workstations.
Post by Sarah Tanembaum
Well, I guess MS does not have solution of running apps from a
network-mounted-disk-from-a-server.
I am familiar with terminal services as well citrix/metaframe since the
early days up till now. It just does not scale.
What we have now that we have fast network, fast server, fast disk, and fast
workstation. If there are such solution where almost any new OS can do that
but does not include Microsoft.
Post by Dirk-Thomas Brown
If you do an admin install to the server, you then do an install from that
location on each workstation. You choose custom install and the different
applications have an option to "Run from the network"
It will be SLOW though...
Dirk-Thomas
Post by Sarah Tanembaum
Technically it can be installed and run from the server,
and would save the problem of updating all 10 PCs.
How? Does MS supply a setup script for workstation to run office from
network-mounted-disk?
But as Chris mentioned, it would use huge amounts of the network.
This is not an issues for us. We have ample bandwidth to spare.
You can copy the CDs to the server and install to each
workstation from there.
This does not make any sense. Why can I just use them from network
disk(attached to each workstation), and execute the apps from there?
This
Post by Dirk-Thomas Brown
is
Post by Sarah Tanembaum
time consuming and it just plain old technology.
1. Disk vendors -- so we need to buy a lots of disk space
to store the same executable programs
2. Consultant -- more billable time(yeah.)
But seriously, why don't they(MS) make our lives(SysAdmin) a bit easier?
Once installed, don't
forget "Office Update" as opposed to "Windows Update"
-----Original Message-----
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
.
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-19 08:45:13 UTC
Permalink
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Yes, it's called Terminal Server.
If you bought full blown [not thin client] workstations, stick the
office on each one by using group policy push.
Why would I do that if I can just run on my workstation an executable file
located at a file server? I do not have to push anything at all, therefore
no additional disk space required on my workstation and no additional load
on the network.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Normally for what you want you don't buy fast workstations.
Funny, that now MS admitting that the thin-client is a better solution(at
least for this case) where traditionaly MS won't touch this and taught that
FAT CLIENT IS THE BEST SOLUTION!

Sarah
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Well, I guess MS does not have solution of running apps from a
network-mounted-disk-from-a-server.
I am familiar with terminal services as well citrix/metaframe since the
early days up till now. It just does not scale.
What we have now that we have fast network, fast server, fast disk, and fast
workstation. If there are such solution where almost any new OS can do that
but does not include Microsoft.
Post by Dirk-Thomas Brown
If you do an admin install to the server, you then do an install from that
location on each workstation. You choose custom install and the different
applications have an option to "Run from the network"
It will be SLOW though...
Dirk-Thomas
Post by Sarah Tanembaum
Technically it can be installed and run from the server,
and would save the problem of updating all 10 PCs.
How? Does MS supply a setup script for workstation to run office from
network-mounted-disk?
But as Chris mentioned, it would use huge amounts of the network.
This is not an issues for us. We have ample bandwidth to spare.
You can copy the CDs to the server and install to each
workstation from there.
This does not make any sense. Why can I just use them from network
disk(attached to each workstation), and execute the apps from there?
This
Post by Dirk-Thomas Brown
is
Post by Sarah Tanembaum
time consuming and it just plain old technology.
1. Disk vendors -- so we need to buy a lots of disk space
to store the same executable programs
2. Consultant -- more billable time(yeah.)
But seriously, why don't they(MS) make our lives(SysAdmin) a bit easier?
Once installed, don't
forget "Office Update" as opposed to "Windows Update"
-----Original Message-----
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
.
--
http://www.sbslinks.com/really.htm
Kevin Weilbacher [SBS-MVP]
2004-07-19 10:06:37 UTC
Permalink
Sarah, not sure what you mean to imply by saying "now MS [is] admitting" --
since Terminal Services have been provided since at least the NT 4.0 days by
Microsoft (see the 1998 article
http://www.microsoft.com/ntserver/ProductInfo/terminal/tsarchitecture.asp)
and Microsoft continues to make improvements in it every year, and companies
like Citrix continue to improve and adapt their product lines.

But then again, I know you already knew that.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Funny, that now MS admitting that the thin-client is a better solution(at
least for this case) where traditionaly MS won't touch this and taught that
FAT CLIENT IS THE BEST SOLUTION!
Sarah
Sarah Tanembaum
2004-07-20 01:13:01 UTC
Permalink
Dear Kevin,
As some of your colleage said, Terminal Services solution does not scale
well for the Enterprise.
And I do agree with them as I have direct experience with Citrix
Winframe(where Microsoft Terminal Services technology based-on), MS
Terminal Server, and Metaframe Server(a much better solution than MS
Terminal Services solution for Large Enterprise, more scalable, has more
admninstrative utilities, and best of all it is available for almost every
OS available).

As I said in my previous posting, MS has black-and-white solution only, that
is:
1- run ALL APPS in the server(Terminal Services)
2- run ALL APPS in the workstation(old technology).

Both solution is so archaic in my view as (1) is pretty much an old
mainframe solution except that we got to waste a good workstation computing
power, and (2) is only as good as home use or very small business solution.

For most large enterprise, the (3) solution that is to combine the power of
server technology, networking technology, and the workstation technology.
Ooops ... I forgot to mention that it is really good implementation of
client-server technology. But I guess MS has not yet catch on that ideas.
Otherwise, they would have solution as I mentioned earlier.

At any case, thanks for your info. I wish that MS would consider that
solution soon.

Sarah
Post by Kevin Weilbacher [SBS-MVP]
Sarah, not sure what you mean to imply by saying "now MS [is]
admitting" --
Post by Kevin Weilbacher [SBS-MVP]
since Terminal Services have been provided since at least the NT 4.0 days by
Microsoft (see the 1998 article
http://www.microsoft.com/ntserver/ProductInfo/terminal/tsarchitecture.asp)
and Microsoft continues to make improvements in it every year, and companies
like Citrix continue to improve and adapt their product lines.
But then again, I know you already knew that.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
Post by Sarah Tanembaum
Funny, that now MS admitting that the thin-client is a better solution(at
least for this case) where traditionaly MS won't touch this and taught
that
Post by Sarah Tanembaum
FAT CLIENT IS THE BEST SOLUTION!
Sarah
a***@tiscali.co.uk
2004-07-20 18:15:16 UTC
Permalink
Post by Sarah Tanembaum
As I said in my previous posting, MS has black-and-white solution only, that
1- run ALL APPS in the server(Terminal Services)
2- run ALL APPS in the workstation(old technology).
Wrong. See my previous post in this thread.

AndyC
Sarah Tanembaum
2004-07-21 13:31:42 UTC
Permalink
Post by a***@tiscali.co.uk
You can run office from a network share if you so choose. Create an
Administrative Install on the server, use the custom installation wizard to
create a .MST where all the options are set to "Run from the Network",
deploy via Active Directory or a login script. Not exactly rocket science.
Is this what you call running from the network by copying/deploying file(s)
to
workstation(s)?

Newer and more advanced OS/Apps can run any application from
network-attached
disk without any single executable copied to the workstation. The beauty
about
that advanced OS and apps, it installed only once, that is in the
file-server.

Once it installed, instantly all the workstation attached to that file
server has
instant access to that apps. It is as simple as that. Badabing badaboom.

Sarah
Post by a***@tiscali.co.uk
Post by Sarah Tanembaum
As I said in my previous posting, MS has black-and-white solution only,
that
Post by Sarah Tanembaum
1- run ALL APPS in the server(Terminal Services)
2- run ALL APPS in the workstation(old technology).
Wrong. See my previous post in this thread.
AndyC
a***@tiscali.co.uk
2004-07-21 15:56:04 UTC
Permalink
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
You can run office from a network share if you so choose. Create an
Administrative Install on the server, use the custom installation wizard to
create a .MST where all the options are set to "Run from the Network",
deploy via Active Directory or a login script. Not exactly rocket science.
Is this what you call running from the network by copying/deploying file(s)
to
workstation(s)?
Where did I say anything about copying files to the workstation?

If you deploy Office with the setting "Run from the Network" it does
precisely what it says. The only files copied are shortcuts/registry
entries, the executables and dll's etc remain on the fileserver only.

Perhaps you ought to check your facts before making wild assumptions about
the capabilities of Windows over your so-called "more advanced OS/Apps"

AndyC
Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
2004-07-21 19:43:50 UTC
Permalink
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.
Post by a***@tiscali.co.uk
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
You can run office from a network share if you so choose. Create an
Administrative Install on the server, use the custom installation wizard
to
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
create a .MST where all the options are set to "Run from the Network",
deploy via Active Directory or a login script. Not exactly rocket
science.
Post by Sarah Tanembaum
Is this what you call running from the network by copying/deploying
file(s)
Post by Sarah Tanembaum
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
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-22 02:08:30 UTC
Permalink
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.
Post by 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.
Post by a***@tiscali.co.uk
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
You can run office from a network share if you so choose. Create an
Administrative Install on the server, use the custom installation wizard
to
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
create a .MST where all the options are set to "Run from the Network",
deploy via Active Directory or a login script. Not exactly rocket
science.
Post by Sarah Tanembaum
Is this what you call running from the network by copying/deploying
file(s)
Post by Sarah Tanembaum
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
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-22 02:06:08 UTC
Permalink
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
Post by a***@tiscali.co.uk
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
You can run office from a network share if you so choose. Create an
Administrative Install on the server, use the custom installation
wizard
Post by a***@tiscali.co.uk
to
Post by Sarah Tanembaum
Post by a***@tiscali.co.uk
create a .MST where all the options are set to "Run from the Network",
deploy via Active Directory or a login script. Not exactly rocket
science.
Post by Sarah Tanembaum
Is this what you call running from the network by copying/deploying
file(s)
Post by Sarah Tanembaum
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
AndyC
2004-07-22 10:56:46 UTC
Permalink
Post by Sarah Tanembaum
Forgive me if I was mistaken.
1- I put all the executable file as well as dll on the server to share with
other workstation without
copying any exec and/or dll file on the workstation.
Almost correct. You create an Administrative Install on the server with:

msiexec /a office.msi

This creates the correct folder structure for the server. No files are
copied to the workstation.

You then use the Office Custom Installation Wizard to configure the way you
want the Office installation done. In your case this would involve selecting
"Run from the Network" for all options. However it's perfectly valid to mix
and match if, for example, you wanted Powerpoint installed locally or
Outlook to install locally on first use etc.

You then save the .mst file in your server's shared office folder (referred
to from here on in as \\server\office)
Post by Sarah Tanembaum
2- I just create a shortcut and registry setting and voila I can ran the
office apps?
PS: I'd like to see the scripts that create those shortcut(don't need
the shortcut, I'd like to just
execute it directly from the network-attached directory) and
registry setting(what setting do
I need?)
Depending on your environment you can do this one of two ways:

1) If you have Active Directory, just create a GPO containing the Office
package with the .mst transform you created earlier and assign it to the
relevant Organisational Unit.

2) Alternatively, run the msiexec utility from a startup script or similar
method, again applying the relevant transform. Something like this should do
the trick:

msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb

This will create the appropriate registry information and Windows Installer
shortcuts for the setup you decided upon in your Custom Installation. If you
don't want the shortcuts you can always opt to omit them in your .mst file,
although I don't really see and advantage in that.
Post by Sarah Tanembaum
3- Just to be sure! NO INSTALLATION PROCESS ON THE WORKSTATION AND NO
EXEC and DLL files COPIED TO WORKSTATION?
Are those correct! If they are, please forgive me, but I can bet that was
not the case!
Yes that is correct. EXE or DLL files are only copied to the local
workstation if you request it in your installation. One possible caveat to
this is that Office 2003 has a few .NET optional extras (programmer support
IIRC) which have to be installed locally if you want them (because of the
way .NET Code Access Security works), although 99% of people probably don't.

AndyC
Sarah Tanembaum
2004-07-22 15:29:47 UTC
Permalink
Post by AndyC
Post by Sarah Tanembaum
Forgive me if I was mistaken.
1- I put all the executable file as well as dll on the server to share
with
Post by Sarah Tanembaum
other workstation without
copying any exec and/or dll file on the workstation.
msiexec /a office.msi
This creates the correct folder structure for the server. No files are
copied to the workstation.
Sure, but you have to do this for all the workstation, is that correct?
Imagine if you have to do this install 1000+ times.
Why can I just install all the file in the server and executed in the
workstation.

Another thing is that it needs administrator installation, why? Again,
you are simulating workstation installation but using the network drive.
That's not the same thing.
Post by AndyC
You then use the Office Custom Installation Wizard to configure the way you
want the Office installation done. In your case this would involve selecting
"Run from the Network" for all options. However it's perfectly valid to mix
and match if, for example, you wanted Powerpoint installed locally or
Outlook to install locally on first use etc.
If this is a SMART and TRUE Network Apps, I will be able to execute the
apps as regular user where then I can customized whatever I want e.g.
location
of my personal template, my document directory, etc.etc.

And, it should not need an administrative priviledge! Again, if it does not
need
to copy or put something in the workstation, why administrative installation
has to be performed?
Post by AndyC
You then save the .mst file in your server's shared office folder (referred
to from here on in as \\server\office)
What happen if you have many users access it? How's the application manage
to
keep each user to its own space?
Post by AndyC
Post by Sarah Tanembaum
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?)
1) If you have Active Directory, just create a GPO containing the Office
package with the .mst transform you created earlier and assign it to the
relevant Organisational Unit.
Why do I have to go this trouble? I thought that all I need is install the
apps
in the file server, attach the drive to the workstation, and all users on
all
workstations can just execute the apps. No fuss.

What's so hard to do that? The point is that it is not necessary to even
need AD to control it, or GPO to control it. If you need to change
permission
on the file, change it on the server and all those 10000+ workstation can
see
it right away.

Again, you are avoiding the issues.
Post by AndyC
2) Alternatively, run the msiexec utility from a startup script or similar
method, again applying the relevant transform. Something like this should do
msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb
This will create the appropriate registry information and Windows Installer
shortcuts for the setup you decided upon in your Custom Installation. If you
don't want the shortcuts you can always opt to omit them in your .mst file,
although I don't really see and advantage in that.
Oh my! How many more step that you have to do in the workstation?
I thought that you want to show me that nothing has to be done on the
workstation,
period.

This process is just as time consuming and prone to error as installing from
a pre-packaged
CD's 1000 times(all workstations).
Post by AndyC
Post by Sarah Tanembaum
3- Just to be sure! NO INSTALLATION PROCESS ON THE WORKSTATION AND NO
EXEC and DLL files COPIED TO WORKSTATION?
Are those correct! If they are, please forgive me, but I can bet that was
not the case!
Yes that is correct. EXE or DLL files are only copied to the local
workstation if you request it in your installation. One possible caveat to
this is that Office 2003 has a few .NET optional extras (programmer support
IIRC) which have to be installed locally if you want them (because of the
way .NET Code Access Security works), although 99% of people probably don't.
AndyC, you got to admit there are room for major overhaul of how those
office apps
run and installed.

My point is, why can I just install the application in the file server and
execute that apps
in the workstation network drive! Its just as easy as that.

No administration headache.
Centralize apps administration
Patch and upgrade will be done only on the file server(instant upgrade for
ALL workstation)
And many other ....
Post by AndyC
AndyC
AndyC
2004-07-22 16:20:59 UTC
Permalink
Post by Sarah Tanembaum
Post by AndyC
msiexec /a office.msi
This creates the correct folder structure for the server. No files are
copied to the workstation.
Sure, but you have to do this for all the workstation, is that correct?
Imagine if you have to do this install 1000+ times.
Why can I just install all the file in the server and executed in the
workstation.
No. You do this on the server to unpack the installation structure from the
compressed CD image. You only need to do it once.
Post by Sarah Tanembaum
Another thing is that it needs administrator installation, why? Again,
you are simulating workstation installation but using the network drive.
That's not the same thing.
You want ordinary users to be able to install applications on the server?
Post by Sarah Tanembaum
If this is a SMART and TRUE Network Apps, I will be able to execute the
apps as regular user where then I can customized whatever I want e.g.
location
of my personal template, my document directory, etc.etc.
Per-user settings can be configured by a user as usual. *Unless* an
Administrator specifically restricts them to do otherwise.
Post by Sarah Tanembaum
What happen if you have many users access it? How's the application manage
to
keep each user to its own space?
Users files/settings are kept in their profile folder as usual. Have you
ever actually used Windows?
Post by Sarah Tanembaum
Post by AndyC
1) If you have Active Directory, just create a GPO containing the Office
package with the .mst transform you created earlier and assign it to the
relevant Organisational Unit.
Why do I have to go this trouble? I thought that all I need is install the
apps
in the file server, attach the drive to the workstation, and all users on
all
workstations can just execute the apps. No fuss.
It's hardly trouble, it takes approximately two minutes, regardless of
whether you have 1, 10 or 10,000,000 workstations. The advantage of Active
Directory is that you do not need to ever touch the actual workstation
machines at all. They don't even need to be in the same country. Heck, they
don't even need to exist yet, they'll pick up the settings when they are
added to the Domain.
Post by Sarah Tanembaum
What's so hard to do that? The point is that it is not necessary to even
need AD to control it, or GPO to control it. If you need to change
permission
on the file, change it on the server and all those 10000+ workstation can
see
it right away.
Again, you are avoiding the issues.
I haven't avoided any issues. You're either misreading what I said or really
haven't got a clue how networked applications work on any OS.
Post by Sarah Tanembaum
Post by AndyC
2) Alternatively, run the msiexec utility from a startup script or similar
method, again applying the relevant transform. Something like this
should
Post by Sarah Tanembaum
do
Post by AndyC
msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb
This will create the appropriate registry information and Windows
Installer
Post by AndyC
shortcuts for the setup you decided upon in your Custom Installation. If
you
Post by AndyC
don't want the shortcuts you can always opt to omit them in your .mst
file,
Post by AndyC
although I don't really see and advantage in that.
Oh my! How many more step that you have to do in the workstation?
I thought that you want to show me that nothing has to be done on the
workstation,
period.
What! That's one step. A single command. And only necessary if you aren't
using Active Directory. How much less do you expect to do? Even a *nix based
OS needs one command to mount a networked application drive for crying out
loud.
Post by Sarah Tanembaum
AndyC, you got to admit there are room for major overhaul of how those
office apps
run and installed.
My point is, why can I just install the application in the file server and
execute that apps
in the workstation network drive! Its just as easy as that.
That's what I just explained (several times) how to do. Why not try reading
the posts instead of assuming you know better.
Post by Sarah Tanembaum
No administration headache.
Centralize apps administration
Patch and upgrade will be done only on the file server(instant upgrade for
ALL workstation)
And many other ....
On the contrary. It's probably the one thing that Windows simply does better
than any other operating system. If you really feel the need to slag it off,
there are plenty of areas where Unix/Linux/Mac actually have a genuine
advantage. If you'd ever run a large scale network, you'd know this already.
I'm an administrator in a mixed Solaris/Linux/Mac environment, I do know
what I'm talking about.

AndyC
Cary Shultz [A.D. MVP]
2004-07-22 16:38:21 UTC
Permalink
Andy,

I am quite confident that Sarah is not going to listen / accept anything
that we suggest to her.

I wonder what NOS / Application(s) she means.

I am a big fan of Active Directory and really like what you can do with
GPOs, whether making a couple - or lot - of configuration settings or
deploying applications to either the user- or computer-side of things.

I have never worked in an environment of more than 300+ users but can tell
you that GPOs are a really big Administrative 'Extra Strength Tylenol'!

Cary
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
msiexec /a office.msi
This creates the correct folder structure for the server. No files are
copied to the workstation.
Sure, but you have to do this for all the workstation, is that correct?
Imagine if you have to do this install 1000+ times.
Why can I just install all the file in the server and executed in the
workstation.
No. You do this on the server to unpack the installation structure from the
compressed CD image. You only need to do it once.
Post by Sarah Tanembaum
Another thing is that it needs administrator installation, why? Again,
you are simulating workstation installation but using the network drive.
That's not the same thing.
You want ordinary users to be able to install applications on the server?
Post by Sarah Tanembaum
If this is a SMART and TRUE Network Apps, I will be able to execute the
apps as regular user where then I can customized whatever I want e.g.
location
of my personal template, my document directory, etc.etc.
Per-user settings can be configured by a user as usual. *Unless* an
Administrator specifically restricts them to do otherwise.
Post by Sarah Tanembaum
What happen if you have many users access it? How's the application manage
to
keep each user to its own space?
Users files/settings are kept in their profile folder as usual. Have you
ever actually used Windows?
Post by Sarah Tanembaum
Post by AndyC
1) If you have Active Directory, just create a GPO containing the Office
package with the .mst transform you created earlier and assign it to the
relevant Organisational Unit.
Why do I have to go this trouble? I thought that all I need is install the
apps
in the file server, attach the drive to the workstation, and all users on
all
workstations can just execute the apps. No fuss.
It's hardly trouble, it takes approximately two minutes, regardless of
whether you have 1, 10 or 10,000,000 workstations. The advantage of Active
Directory is that you do not need to ever touch the actual workstation
machines at all. They don't even need to be in the same country. Heck, they
don't even need to exist yet, they'll pick up the settings when they are
added to the Domain.
Post by Sarah Tanembaum
What's so hard to do that? The point is that it is not necessary to even
need AD to control it, or GPO to control it. If you need to change
permission
on the file, change it on the server and all those 10000+ workstation can
see
it right away.
Again, you are avoiding the issues.
I haven't avoided any issues. You're either misreading what I said or really
haven't got a clue how networked applications work on any OS.
Post by Sarah Tanembaum
Post by AndyC
2) Alternatively, run the msiexec utility from a startup script or
similar
Post by Sarah Tanembaum
Post by AndyC
method, again applying the relevant transform. Something like this
should
Post by Sarah Tanembaum
do
Post by AndyC
msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb
This will create the appropriate registry information and Windows
Installer
Post by AndyC
shortcuts for the setup you decided upon in your Custom Installation. If
you
Post by AndyC
don't want the shortcuts you can always opt to omit them in your .mst
file,
Post by AndyC
although I don't really see and advantage in that.
Oh my! How many more step that you have to do in the workstation?
I thought that you want to show me that nothing has to be done on the
workstation,
period.
What! That's one step. A single command. And only necessary if you aren't
using Active Directory. How much less do you expect to do? Even a *nix based
OS needs one command to mount a networked application drive for crying out
loud.
Post by Sarah Tanembaum
AndyC, you got to admit there are room for major overhaul of how those
office apps
run and installed.
My point is, why can I just install the application in the file server and
execute that apps
in the workstation network drive! Its just as easy as that.
That's what I just explained (several times) how to do. Why not try reading
the posts instead of assuming you know better.
Post by Sarah Tanembaum
No administration headache.
Centralize apps administration
Patch and upgrade will be done only on the file server(instant upgrade for
ALL workstation)
And many other ....
On the contrary. It's probably the one thing that Windows simply does better
than any other operating system. If you really feel the need to slag it off,
there are plenty of areas where Unix/Linux/Mac actually have a genuine
advantage. If you'd ever run a large scale network, you'd know this already.
I'm an administrator in a mixed Solaris/Linux/Mac environment, I do know
what I'm talking about.
AndyC
Sarah Tanembaum
2004-07-22 19:31:25 UTC
Permalink
Cary, I'm not that hard to convince if the solution is not a
patch-up/ducktape solution.
There are many things that Windows need to learn from its brothers that
has been running for large enterprises, doesn't it?

May be not! Perhaps Windows is much more superior ;)

Sarah
Post by Cary Shultz [A.D. MVP]
Andy,
I am quite confident that Sarah is not going to listen / accept anything
that we suggest to her.
I wonder what NOS / Application(s) she means.
I am a big fan of Active Directory and really like what you can do with
GPOs, whether making a couple - or lot - of configuration settings or
deploying applications to either the user- or computer-side of things.
I have never worked in an environment of more than 300+ users but can tell
you that GPOs are a really big Administrative 'Extra Strength Tylenol'!
Cary
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
msiexec /a office.msi
This creates the correct folder structure for the server. No files are
copied to the workstation.
Sure, but you have to do this for all the workstation, is that correct?
Imagine if you have to do this install 1000+ times.
Why can I just install all the file in the server and executed in the
workstation.
No. You do this on the server to unpack the installation structure from
the
Post by AndyC
compressed CD image. You only need to do it once.
Post by Sarah Tanembaum
Another thing is that it needs administrator installation, why? Again,
you are simulating workstation installation but using the network drive.
That's not the same thing.
You want ordinary users to be able to install applications on the server?
Post by Sarah Tanembaum
If this is a SMART and TRUE Network Apps, I will be able to execute the
apps as regular user where then I can customized whatever I want e.g.
location
of my personal template, my document directory, etc.etc.
Per-user settings can be configured by a user as usual. *Unless* an
Administrator specifically restricts them to do otherwise.
Post by Sarah Tanembaum
What happen if you have many users access it? How's the application
manage
Post by AndyC
Post by Sarah Tanembaum
to
keep each user to its own space?
Users files/settings are kept in their profile folder as usual. Have you
ever actually used Windows?
Post by Sarah Tanembaum
Post by AndyC
1) If you have Active Directory, just create a GPO containing the
Office
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
package with the .mst transform you created earlier and assign it to
the
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
relevant Organisational Unit.
Why do I have to go this trouble? I thought that all I need is install
the
Post by AndyC
Post by Sarah Tanembaum
apps
in the file server, attach the drive to the workstation, and all users
on
Post by AndyC
Post by Sarah Tanembaum
all
workstations can just execute the apps. No fuss.
It's hardly trouble, it takes approximately two minutes, regardless of
whether you have 1, 10 or 10,000,000 workstations. The advantage of Active
Directory is that you do not need to ever touch the actual workstation
machines at all. They don't even need to be in the same country. Heck,
they
Post by AndyC
don't even need to exist yet, they'll pick up the settings when they are
added to the Domain.
Post by Sarah Tanembaum
What's so hard to do that? The point is that it is not necessary to even
need AD to control it, or GPO to control it. If you need to change
permission
on the file, change it on the server and all those 10000+ workstation
can
Post by AndyC
Post by Sarah Tanembaum
see
it right away.
Again, you are avoiding the issues.
I haven't avoided any issues. You're either misreading what I said or
really
Post by AndyC
haven't got a clue how networked applications work on any OS.
Post by Sarah Tanembaum
Post by AndyC
2) Alternatively, run the msiexec utility from a startup script or
similar
Post by Sarah Tanembaum
Post by AndyC
method, again applying the relevant transform. Something like this
should
Post by Sarah Tanembaum
do
Post by AndyC
msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb
This will create the appropriate registry information and Windows
Installer
Post by AndyC
shortcuts for the setup you decided upon in your Custom
Installation.
Post by Cary Shultz [A.D. MVP]
If
Post by AndyC
Post by Sarah Tanembaum
you
Post by AndyC
don't want the shortcuts you can always opt to omit them in your .mst
file,
Post by AndyC
although I don't really see and advantage in that.
Oh my! How many more step that you have to do in the workstation?
I thought that you want to show me that nothing has to be done on the
workstation,
period.
What! That's one step. A single command. And only necessary if you aren't
using Active Directory. How much less do you expect to do? Even a *nix
based
Post by AndyC
OS needs one command to mount a networked application drive for crying out
loud.
Post by Sarah Tanembaum
AndyC, you got to admit there are room for major overhaul of how those
office apps
run and installed.
My point is, why can I just install the application in the file server
and
Post by AndyC
Post by Sarah Tanembaum
execute that apps
in the workstation network drive! Its just as easy as that.
That's what I just explained (several times) how to do. Why not try
reading
Post by AndyC
the posts instead of assuming you know better.
Post by Sarah Tanembaum
No administration headache.
Centralize apps administration
Patch and upgrade will be done only on the file server(instant upgrade
for
Post by AndyC
Post by Sarah Tanembaum
ALL workstation)
And many other ....
On the contrary. It's probably the one thing that Windows simply does
better
Post by AndyC
than any other operating system. If you really feel the need to slag it
off,
Post by AndyC
there are plenty of areas where Unix/Linux/Mac actually have a genuine
advantage. If you'd ever run a large scale network, you'd know this
already.
Post by AndyC
I'm an administrator in a mixed Solaris/Linux/Mac environment, I do know
what I'm talking about.
AndyC
Sarah Tanembaum
2004-07-22 19:28:02 UTC
Permalink
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
msiexec /a office.msi
This creates the correct folder structure for the server. No files are
copied to the workstation.
Sure, but you have to do this for all the workstation, is that correct?
Imagine if you have to do this install 1000+ times.
Why can I just install all the file in the server and executed in the
workstation.
No. You do this on the server to unpack the installation structure from the
compressed CD image. You only need to do it once.
Okay, you unpack and and put them in the file server.
Post by AndyC
Post by Sarah Tanembaum
Another thing is that it needs administrator installation, why? Again,
you are simulating workstation installation but using the network drive.
That's not the same thing.
You want ordinary users to be able to install applications on the server?
I'm talking in the workstation. As you stated earlier, Administrator
priviledge
(on workstation) is needed to enable users in the workstation able to run
the network apps, correct?

As you can see, you can push the file or ask the workstation to run a script
from AD, understood, but it overkill. All you need to do is a login script
to set up a search patch for that apps executable and dlls.

So, we do not have to spend on hardware(AD Server) and software(anoter
Windows 2003 Server OS) to just push that apps -- I think this would
simplify many things.
Post by AndyC
Post by Sarah Tanembaum
If this is a SMART and TRUE Network Apps, I will be able to execute the
apps as regular user where then I can customized whatever I want e.g.
location
of my personal template, my document directory, etc.etc.
Per-user settings can be configured by a user as usual. *Unless* an
Administrator specifically restricts them to do otherwise.
Okay, understood.
Post by AndyC
Post by Sarah Tanembaum
What happen if you have many users access it? How's the application manage
to
keep each user to its own space?
Users files/settings are kept in their profile folder as usual. Have you
ever actually used Windows?
Yes, I have.
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
1) If you have Active Directory, just create a GPO containing the Office
package with the .mst transform you created earlier and assign it to the
relevant Organisational Unit.
Why do I have to go this trouble? I thought that all I need is install the
apps
in the file server, attach the drive to the workstation, and all users on
all
workstations can just execute the apps. No fuss.
It's hardly trouble, it takes approximately two minutes, regardless of
whether you have 1, 10 or 10,000,000 workstations. The advantage of Active
Directory is that you do not need to ever touch the actual workstation
machines at all. They don't even need to be in the same country. Heck, they
don't even need to exist yet, they'll pick up the settings when they are
added to the Domain.
If you are talking WUS(Windows Update Services), it is not yet available
(Information Week this week).
Post by AndyC
Post by Sarah Tanembaum
What's so hard to do that? The point is that it is not necessary to even
need AD to control it, or GPO to control it. If you need to change
permission
on the file, change it on the server and all those 10000+ workstation can
see
it right away.
Again, you are avoiding the issues.
I haven't avoided any issues. You're either misreading what I said or really
haven't got a clue how networked applications work on any OS.
Let me rephrase it again:
1. There is an Apps called: AppsA
2. Install apps A in the server --- e.g: \\servername\appsdir\AppsA\
3. UserXX in WorkstationY want to access AppsA
4. UserXX in WorkstationY type: \\<servername>\appsdir\AppsA\A.exe
5. Voila, UserXX is running AppsA in his/her WorkstationYY.

In short, install appsA in the <servername>, and then 1000 users can access
those apps
in a blink by just typing \\<servername>\appsdir\AppsA\A.exe (he/she can
create
a shortcut anytime)

When there are updates, all we need to do is update those AppsA in <
servername>\appsdir\AppsA directory, and VOILA, all users/workstation
see the update.
Post by AndyC
Post by Sarah Tanembaum
Post by AndyC
2) Alternatively, run the msiexec utility from a startup script or
similar
Post by Sarah Tanembaum
Post by AndyC
method, again applying the relevant transform. Something like this
should
Post by Sarah Tanembaum
do
Post by AndyC
msiexec /i \\server\Office\office.msi
TRANSFORM=\\server\Office\my_office_transform.mst /qb
This will create the appropriate registry information and Windows
Installer
Post by AndyC
shortcuts for the setup you decided upon in your Custom Installation. If
you
Post by AndyC
don't want the shortcuts you can always opt to omit them in your .mst
file,
Post by AndyC
although I don't really see and advantage in that.
Oh my! How many more step that you have to do in the workstation?
I thought that you want to show me that nothing has to be done on the
workstation,
period.
What! That's one step. A single command. And only necessary if you aren't
using Active Directory. How much less do you expect to do? Even a *nix based
OS needs one command to mount a networked application drive for crying out
loud.
In *nix, install apps in /usr/local/AppsA, automount /usr/local/AppsA in
user workstation, then execute the /usr/local/AppsA/A.exe ...
NOW user run the apps.

When patch comes in, update the file(s) in /usr/local/AppsA.
As soon as the patch finishes in the server, all the user can see the update
right away.

Nothing has to be run on the workstation! All the user has to do is to type
in the command line:

/usr/local/AppsA/A.exe (okay, they do not use .exe for executable
extension).
Post by AndyC
Post by Sarah Tanembaum
AndyC, you got to admit there are room for major overhaul of how those
office apps
run and installed.
My point is, why can I just install the application in the file server and
execute that apps
in the workstation network drive! Its just as easy as that.
That's what I just explained (several times) how to do. Why not try reading
the posts instead of assuming you know better.
Not exactly! And by the way, I do read all your comments.
Post by AndyC
Post by Sarah Tanembaum
No administration headache.
Centralize apps administration
Patch and upgrade will be done only on the file server(instant upgrade for
ALL workstation)
And many other ....
On the contrary. It's probably the one thing that Windows simply does better
than any other operating system.
Sure! I think you know that is not true! So, I would not go there.
Post by AndyC
If you really feel the need to slag it off,
there are plenty of areas where Unix/Linux/Mac actually have a genuine
advantage. If you'd ever run a large scale network, you'd know this already.
Yes, I have.
Post by AndyC
I'm an administrator in a mixed Solaris/Linux/Mac environment, I do know
what I'm talking about.
Same here.
Post by AndyC
AndyC
AndyC
2004-07-23 09:57:50 UTC
Permalink
Post by Sarah Tanembaum
If you are talking WUS(Windows Update Services), it is not yet available
(Information Week this week).
I never mentioned WUS. I was talking about Active Directory. Please don't
put words in my mouth.
Post by Sarah Tanembaum
1. There is an Apps called: AppsA
2. Install apps A in the server --- e.g: \\servername\appsdir\AppsA\
3. UserXX in WorkstationY want to access AppsA
4. UserXX in WorkstationY type: \\<servername>\appsdir\AppsA\A.exe
5. Voila, UserXX is running AppsA in his/her WorkstationYY.
In short, install appsA in the <servername>, and then 1000 users can access
those apps
in a blink by just typing \\<servername>\appsdir\AppsA\A.exe (he/she can
create
a shortcut anytime)
When there are updates, all we need to do is update those AppsA in <
servername>\appsdir\AppsA directory, and VOILA, all users/workstation
see the update.
Which is precisely the scenario I've outlined. As Cary says though, you seem
to completely refuse to either believe or understand a fairly trivial
explanation. Contrary to your comments, Windows simply is more flexible than
*nix based operating systems in this regard and all three of the scenarios
suggested are officially supported configurations. Clearly you don't want to
know that because you're happier living in your little bubble.

I'd suggest you stick to *nix, put on your tin-foil hat and go back to
reading /. You best leave us poor Windows admins to run round installing
everything from floppy disk as that's the only way we can do it right?

*plonk*

AndyC
Cary Shultz [A.D. MVP]
2004-07-17 05:54:44 UTC
Permalink
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
Post by Sarah Tanembaum
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
Sarah Tanembaum
2004-07-18 10:03:00 UTC
Permalink
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 ....
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
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.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
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
Kevin Weilbacher [SBS-MVP]
2004-07-18 13:48:36 UTC
Permalink
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"
Post by Sarah Tanembaum
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 ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally a
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld ausgegeben!
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
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,
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
to
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation. Sure,
you
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or
when
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make sure
that
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Chad A. Gross [SBS MVP]
2004-07-18 16:24:39 UTC
Permalink
Post by Sarah Tanembaum
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.
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
Post by Sarah Tanembaum
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 ....
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
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
Chad A. Gross [SBS MVP]
2004-07-18 16:30:26 UTC
Permalink
And one other thing -

What is more inefficient - deploying via group policies and having a user
have to wait a few extra seconds on startup as updated files are pulled down
from the server (and how often do we see Office updates?), or bringing your
entire network to a crawl every day? Bottom line is that whether or not you
have gigabit ethernet, that is still slower than local disk access.

We're not hiding anything or avoiding issues - we're trying to point out
that Windows apps have to be installed. Which is the exact same reason that
you can't just copy a program folder from pc A to pc B and run the app on pc
B - because it hasn't been installed . . .
--
Chad A. Gross - SBS MVP
SBS ROCKS!

www.msmvps.com/cgross
www.gosbs.org
Post by Sarah Tanembaum
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 ....
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
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
Cary Shultz [A.D. MVP]
2004-07-19 04:00:29 UTC
Permalink
Sarah,

You think that this is very inefficient? Come on....

I have absolutely no understanding of your point of reference. What do you
want? We are not avoiding any issues. I see no issues whatsoever with
installing software via GPO at all. In fact, this ( deploying applications
via GPO ) is a God-send. Maybe you are atheist, I do not know ;-)

And you have stated in other parts of this post that you are not worried
about the network being clogged as you have a Giga Ethernet network. This
was an argument that you used to support your proposed setup. Yet, in your
response to my suggestion about installing via GPO you state that you do not
want to clog up the network. So, which one is it? You say one thing in one
part of the post and then completely contradict it in another...

It looks like you choose a bad solution when you did not yet know what the
options were. In English we say that you painted yourself into a corner.

Cary



PS. MVP stands for Microsoft Most Valuable Professional
Post by Sarah Tanembaum
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 ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally a
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld ausgegeben!
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
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,
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
to
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation. Sure,
you
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or
when
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make sure
that
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Edward Lee
2004-07-20 01:21:00 UTC
Permalink
PMFJI. I have some experience with creating an admin install of Office. I'm
looking for some info that would get me started using GPO to deploy an
upgrade to O2k3 and then deploy patches in the future.

Thanks,
--
Edward Lee
Microsoft MVP - Sharepoint Portal Server
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
You think that this is very inefficient? Come on....
I have absolutely no understanding of your point of reference. What do you
want? We are not avoiding any issues. I see no issues whatsoever with
installing software via GPO at all. In fact, this ( deploying
applications
Post by Kevin Weilbacher [SBS-MVP]
via GPO ) is a God-send. Maybe you are atheist, I do not know ;-)
And you have stated in other parts of this post that you are not worried
about the network being clogged as you have a Giga Ethernet network. This
was an argument that you used to support your proposed setup. Yet, in your
response to my suggestion about installing via GPO you state that you do not
want to clog up the network. So, which one is it? You say one thing in one
part of the post and then completely contradict it in another...
It looks like you choose a bad solution when you did not yet know what the
options were. In English we say that you painted yourself into a corner.
Cary
PS. MVP stands for Microsoft Most Valuable Professional
Post by Sarah Tanembaum
I think this is very inefficient. Why can I install my apps on a disk in
my
Post by Sarah Tanembaum
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
Post by Sarah Tanembaum
100 workstation) will get updated instantly without clogging up the
network
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
....] are avoding the issues.
Please ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reasons for this. You would need a second server that would be the
Terminal
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally a
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld ausgegeben!
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
on your Server and install that application on each workstation from
that
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Admin Installation. The advantages of doing this are 1) you have a
common,
Post by Kevin Weilbacher [SBS-MVP]
accessible installation point and 2) you do not have to worry about
losing
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the Office 2003 CD! However, the disadvantage of doing this (
compared
Post by Kevin Weilbacher [SBS-MVP]
to
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
each client ( you could use the utility from the Office 2003 Resource
Kit
Post by Sarah Tanembaum
to
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation.
Sure,
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
you
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the additional lines in the logon script ). So, with this solution you
have
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or
when
Post by Kevin Weilbacher [SBS-MVP]
a Service Pack is released - and you have the ability to very quickly
and
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
without much administrative overhead install this to your clients and -
here
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
security patches or Service Packs are released. Additionally, if you
make
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation (
say
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra
get
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make sure
that
Post by Kevin Weilbacher [SBS-MVP]
all of those specific settings are properly configured. Do it via the
GPO
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
and there you have it! Also, you can control it so that your clients
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
not go to the officeupdate.microsoft.com and make untested updates to
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Cary Shultz [A.D. MVP]
2004-07-20 04:31:29 UTC
Permalink
Edward,

What in the world does "pmfji" mean?

I would go to the MS Office Resource Kit for this. If you need / want more
help with this you can either post this in the Group Policy news group -OR-
you can e-mail me directly with the particulars and I will gladly help you.
This is really easy - assuming that you have done it a hundred and one
times! Should be really easy with a push in the right direction and a
couple of MSKB articles.

Cary
Post by Edward Lee
PMFJI. I have some experience with creating an admin install of Office. I'm
looking for some info that would get me started using GPO to deploy an
upgrade to O2k3 and then deploy patches in the future.
Thanks,
--
Edward Lee
Microsoft MVP - Sharepoint Portal Server
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
You think that this is very inefficient? Come on....
I have absolutely no understanding of your point of reference. What do
you
Post by Kevin Weilbacher [SBS-MVP]
want? We are not avoiding any issues. I see no issues whatsoever with
installing software via GPO at all. In fact, this ( deploying
applications
Post by Kevin Weilbacher [SBS-MVP]
via GPO ) is a God-send. Maybe you are atheist, I do not know ;-)
And you have stated in other parts of this post that you are not worried
about the network being clogged as you have a Giga Ethernet network.
This
Post by Edward Lee
Post by Kevin Weilbacher [SBS-MVP]
was an argument that you used to support your proposed setup. Yet, in
your
Post by Kevin Weilbacher [SBS-MVP]
response to my suggestion about installing via GPO you state that you do
not
Post by Kevin Weilbacher [SBS-MVP]
want to clog up the network. So, which one is it? You say one thing in
one
Post by Kevin Weilbacher [SBS-MVP]
part of the post and then completely contradict it in another...
It looks like you choose a bad solution when you did not yet know what the
options were. In English we say that you painted yourself into a corner.
Cary
PS. MVP stands for Microsoft Most Valuable Professional
Post by Sarah Tanembaum
I think this is very inefficient. Why can I install my apps on a disk in
my
Post by Sarah Tanembaum
server and mount that disk on my workstation and execute the exe file
from
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
there.
If I need to upgrade, all I have to do is upgrade the server and those
10(or
Post by Sarah Tanembaum
100 workstation) will get updated instantly without clogging up the
network
Post by Sarah Tanembaum
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
....] are avoding the issues.
Please ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
I have been using Terminal Server for the last 15 months or so and
it
Post by Edward Lee
is
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
generally a great thing. As Kevin mentioned, you can no longer
install
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very
good
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reasons for this. You would need a second server that would be the
Terminal
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not
generally
Post by Edward Lee
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld
ausgegeben!
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
on your Server and install that application on each workstation from
that
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Admin Installation. The advantages of doing this are 1) you have a
common,
Post by Kevin Weilbacher [SBS-MVP]
accessible installation point and 2) you do not have to worry about
losing
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the Office 2003 CD! However, the disadvantage of doing this (
compared
Post by Kevin Weilbacher [SBS-MVP]
to
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
my next suggestion ) is that when you want to update the clients (
sagen
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003
from
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
each client ( you could use the utility from the Office 2003 Resource
Kit
Post by Sarah Tanembaum
to
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation.
Sure,
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
you
Post by Kevin Weilbacher [SBS-MVP]
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in
the
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
logon script and make sure that it is run on each machine and then rem
out
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the additional lines in the logon script ). So, with this solution
you
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
have
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Policy to install Office 2003 to all of your computers ( or users ).
You
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases
or
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
when
Post by Kevin Weilbacher [SBS-MVP]
a Service Pack is released - and you have the ability to very quickly
and
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
without much administrative overhead install this to your clients
and -
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
here
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
security patches or Service Packs are released. Additionally, if you
make
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation (
say
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra
get
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make
sure
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
that
Post by Kevin Weilbacher [SBS-MVP]
all of those specific settings are properly configured. Do it via the
GPO
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
and there you have it! Also, you can control it so that your clients
can
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
not go to the officeupdate.microsoft.com and make untested updates to
the
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Office 2003 installation. This is a really nice feature as well.....
Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber
das
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Group Policy Object haben....
HTH,
Cary
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro
Pre-installed,
Post by Edward Lee
Post by Kevin Weilbacher [SBS-MVP]
an
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
Post by Kevin Weilbacher [SBS-MVP]
a
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
Milly Staples [MVP - Outlook]
2004-07-20 04:45:30 UTC
Permalink
PMFJI = Pardon Me For Jumping In.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Cary Shultz [A.D.
MVP] asked:

| Edward,
|
| What in the world does "pmfji" mean?
|
| I would go to the MS Office Resource Kit for this. If you need /
| want more help with this you can either post this in the Group Policy
| news group -OR- you can e-mail me directly with the particulars and I
| will gladly help you. This is really easy - assuming that you have
| done it a hundred and one times! Should be really easy with a push
| in the right direction and a couple of MSKB articles.
|
| Cary
|
|
| "Edward Lee" <***@ulgm.org> wrote in message
| news:***@TK2MSFTNGP09.phx.gbl...
|| PMFJI. I have some experience with creating an admin install of
|| Office. I'm looking for some info that would get me started using
|| GPO to deploy an upgrade to O2k3 and then deploy patches in the
|| future.
||
|| Thanks,
||
|| --
|| Edward Lee
|| Microsoft MVP - Sharepoint Portal Server
||
||
|| "Cary Shultz [A.D. MVP]" <***@mvps.org> wrote in message
|| news:u%***@TK2MSFTNGP12.phx.gbl...
||| Sarah,
|||
||| You think that this is very inefficient? Come on....
|||
||| I have absolutely no understanding of your point of reference.
||| What do you want? We are not avoiding any issues. I see no issues
||| whatsoever with installing software via GPO at all. In fact, this
||| ( deploying applications via GPO ) is a God-send. Maybe you are
||| atheist, I do not know ;-)
|||
||| And you have stated in other parts of this post that you are not
||| worried about the network being clogged as you have a Giga Ethernet
||| network. This was an argument that you used to support your
||| proposed setup. Yet, in your response to my suggestion about
||| installing via GPO you state that you do not want to clog up the
||| network. So, which one is it? You say one thing in one part of
||| the post and then completely contradict it in another...
|||
||| It looks like you choose a bad solution when you did not yet know
||| what the options were. In English we say that you painted yourself
||| into a corner.
|||
||| Cary
|||
|||
|||
||| PS. MVP stands for Microsoft Most Valuable Professional
|||
||| "Sarah Tanembaum" <***@yahoo.com> wrote in message
||| news:***@uni-berlin.de...
|||| 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 [A.D. MVP]" <***@mvps.org> wrote in message
|||| news:***@TK2MSFTNGP09.phx.gbl...
||||| 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
|||||
|||||
|||||
|||||
|||||
||||| "Sarah Tanembaum" <***@yahoo.com> wrote in message
||||| news:***@uni-berlin.de...
|||||| 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
Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
2004-07-19 05:38:47 UTC
Permalink
If you purchased the MOLP version you can do what's called an
administrative install on the server and PUSH it down to the workstations.

But honestly these days, Office 2003 will install without the install
point and get updates.

Creating an Administrative Installation Point (Office 2003 Editions
Resource Kit):
http://www.microsoft.com/office/ork/2003/two/ch3/DepB01.htm
Post by Sarah Tanembaum
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.
You can. It's called Terminal Server.. but you can't do this with SBS2003.
Post by Sarah Tanembaum
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.
No we're telling you

a. you can do what you want but you don't have the right products to do
it with [you need TS in application mode which SBS cannot do]

b. You can work around it with an install point on the server that
pushes out the software directly to the workstation.

We're not avoiding the issue, unfortunately, you aren't liking the
answers we are giving you which are the only ones we can give you unless you

1. Buy a second server for TS in application mode
2. Buy TS cals for those XPs

You don't have the right parts to do what you want.

You do have the right parts to do an alternative.
Post by Sarah Tanembaum
Please ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally a
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain Controller....
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ 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
Post by Kevin Weilbacher [SBS-MVP]
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,
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation. Sure,
you
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make sure
that
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed, an
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Sarah Tanembaum
2004-07-19 08:48:56 UTC
Permalink
I wonder why MS do all that fuss which in fact it is easier to just make the
apps to run from any file server and execute it on the individual
workstation.

Application will only be installed once in the file server.
What is so hard to do that? The technology is already there and it needs
only MS willingness to make it to work or not.

Sarah
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
If you purchased the MOLP version you can do what's called an
administrative install on the server and PUSH it down to the workstations.
But honestly these days, Office 2003 will install without the install
point and get updates.
Creating an Administrative Installation Point (Office 2003 Editions
http://www.microsoft.com/office/ork/2003/two/ch3/DepB01.htm
Post by Sarah Tanembaum
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.
You can. It's called Terminal Server.. but you can't do this with SBS2003.
Post by Sarah Tanembaum
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
....] are avoding the issues.
No we're telling you
a. you can do what you want but you don't have the right products to do
it with [you need TS in application mode which SBS cannot do]
b. You can work around it with an install point on the server that
pushes out the software directly to the workstation.
We're not avoiding the issue, unfortunately, you aren't liking the
answers we are giving you which are the only ones we can give you unless you
1. Buy a second server for TS in application mode
2. Buy TS cals for those XPs
You don't have the right parts to do what you want.
You do have the right parts to do an alternative.
Post by Sarah Tanembaum
Please ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally a
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld ausgegeben!
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
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,
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation. Sure,
you
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or
when
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make sure
that
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed, an
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
catwalker63
2004-07-19 09:05:06 UTC
Permalink
It's like talking to a wall. Give it up people. She's never going to
listen. Let her beat herself bloody against his problem by herself.
--
Kelley
aka catwalker
IT Professional, MCP
Post by Sarah Tanembaum
I wonder why MS do all that fuss which in fact it is easier to just make the
apps to run from any file server and execute it on the individual
workstation.
Application will only be installed once in the file server.
What is so hard to do that? The technology is already there and it needs
only MS willingness to make it to work or not.
Sarah
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
If you purchased the MOLP version you can do what's called an
administrative install on the server and PUSH it down to the
workstations.
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
But honestly these days, Office 2003 will install without the install
point and get updates.
Creating an Administrative Installation Point (Office 2003 Editions
http://www.microsoft.com/office/ork/2003/two/ch3/DepB01.htm
Post by Sarah Tanembaum
I think this is very inefficient. Why can I install my apps on a disk
in
Post by Sarah Tanembaum
my
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
server and mount that disk on my workstation and execute the exe file
from
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
there.
You can. It's called Terminal Server.. but you can't do this with
SBS2003.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
If I need to upgrade, all I have to do is upgrade the server and those
10(or
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
100 workstation) will get updated instantly without clogging up the
network
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
....] are avoding the issues.
No we're telling you
a. you can do what you want but you don't have the right products to do
it with [you need TS in application mode which SBS cannot do]
b. You can work around it with an install point on the server that
pushes out the software directly to the workstation.
We're not avoiding the issue, unfortunately, you aren't liking the
answers we are giving you which are the only ones we can give you unless
you
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
1. Buy a second server for TS in application mode
2. Buy TS cals for those XPs
You don't have the right parts to do what you want.
You do have the right parts to do an alternative.
Post by Sarah Tanembaum
Please ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reasons for this. You would need a second server that would be the
Terminal
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally a
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld ausgegeben!
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
on your Server and install that application on each workstation from
that
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Admin Installation. The advantages of doing this are 1) you have a
common,
Post by Kevin Weilbacher [SBS-MVP]
accessible installation point and 2) you do not have to worry about
losing
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the Office 2003 CD! However, the disadvantage of doing this (
compared
Post by Sarah Tanembaum
to
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
each client ( you could use the utility from the Office 2003 Resource
Kit
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
to
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation.
Sure,
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
you
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the additional lines in the logon script ). So, with this solution you
have
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases or
when
Post by Kevin Weilbacher [SBS-MVP]
a Service Pack is released - and you have the ability to very quickly
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
without much administrative overhead install this to your clients and -
here
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
security patches or Service Packs are released. Additionally, if you
make
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation (
say
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra
get
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make sure
that
Post by Kevin Weilbacher [SBS-MVP]
all of those specific settings are properly configured. Do it via the
GPO
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
and there you have it! Also, you can control it so that your clients
can
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
not go to the officeupdate.microsoft.com and make untested updates to
the
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed, an
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is there a
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
Frank McCallister
2004-07-19 12:26:15 UTC
Permalink
Frank
Post by catwalker63
It's like talking to a wall. Give it up people. She's never going to
listen. Let her beat herself bloody against his problem by herself.
--
Kelley
aka catwalker
IT Professional, MCP
Post by Sarah Tanembaum
I wonder why MS do all that fuss which in fact it is easier to just make
the
Post by Sarah Tanembaum
apps to run from any file server and execute it on the individual
workstation.
Application will only be installed once in the file server.
What is so hard to do that? The technology is already there and it needs
only MS willingness to make it to work or not.
Sarah
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
If you purchased the MOLP version you can do what's called an
administrative install on the server and PUSH it down to the
workstations.
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
But honestly these days, Office 2003 will install without the install
point and get updates.
Creating an Administrative Installation Point (Office 2003 Editions
http://www.microsoft.com/office/ork/2003/two/ch3/DepB01.htm
Post by Sarah Tanembaum
I think this is very inefficient. Why can I install my apps on a disk
in
Post by Sarah Tanembaum
my
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
server and mount that disk on my workstation and execute the exe file
from
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
there.
You can. It's called Terminal Server.. but you can't do this with
SBS2003.
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
If I need to upgrade, all I have to do is upgrade the server and those
10(or
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
100 workstation) will get updated instantly without clogging up the
network
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
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
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
....] are avoding the issues.
No we're telling you
a. you can do what you want but you don't have the right products to do
it with [you need TS in application mode which SBS cannot do]
b. You can work around it with an install point on the server that
pushes out the software directly to the workstation.
We're not avoiding the issue, unfortunately, you aren't liking the
answers we are giving you which are the only ones we can give you unless
you
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
1. Buy a second server for TS in application mode
2. Buy TS cals for those XPs
You don't have the right parts to do what you want.
You do have the right parts to do an alternative.
Post by Sarah Tanembaum
Please ....
Post by Kevin Weilbacher [SBS-MVP]
Sarah,
I might jump in here for a second.
First of all, the idea of a Terminal Server is generally a really good
idea.
Post by Kevin Weilbacher [SBS-MVP]
I have been using Terminal Server for the last 15 months or so and it
is
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
generally a great thing. As Kevin mentioned, you can no longer
install
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Terminal Server in Application Mode ( err, that is the WIN2000
terminology.... ) on the SBS2003 Server itself. There are some very
good
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
reasons for this. You would need a second server that would be the
Terminal
Post by Kevin Weilbacher [SBS-MVP]
Server. On SBS2000 you can indeed do this - but again, not generally
a
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
good
Post by Kevin Weilbacher [SBS-MVP]
idea to run Terminal Server in Application Mode on a Domain
Controller....
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
However, since you have powerful workstations, you have a really good
point
Post by Kevin Weilbacher [SBS-MVP]
/ question as to why do you would want to turn them into thin clients.
I
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
would probably not want to do that! Du hast schon das Geld
ausgegeben!
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Secondly, you can indeed make an Administrative Installation of Office
2003
Post by Kevin Weilbacher [SBS-MVP]
on your Server and install that application on each workstation from
that
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Admin Installation. The advantages of doing this are 1) you have a
common,
Post by Kevin Weilbacher [SBS-MVP]
accessible installation point and 2) you do not have to worry about
losing
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the Office 2003 CD! However, the disadvantage of doing this (
compared
Post by Sarah Tanembaum
to
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
my next suggestion ) is that when you want to update the clients (
sagen
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
wir, dass Microsoft Office 2003 SP1 liefiert ) you have the problem of
updating each client - this usually involves uninstalling Office 2003
from
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
each client ( you could use the utility from the Office 2003 Resource
Kit
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
to
Post by Kevin Weilbacher [SBS-MVP]
do this! ) and then running the installation on each workstation.
Sure,
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
you
Post by Kevin Weilbacher [SBS-MVP]
could probably do this via a logon script, but you still have the
administrative overhead ( you have to write the additional lines in
the
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
logon script and make sure that it is run on each machine and then rem
out
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
the additional lines in the logon script ). So, with this solution
you
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
have
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Policy to install Office 2003 to all of your computers ( or users ).
You
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
simply make that one Administrative Installation Point ( via setup.exe
/a ) - which you can still update when security patches are releases
or
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
when
Post by Kevin Weilbacher [SBS-MVP]
a Service Pack is released - and you have the ability to very quickly
and
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
without much administrative overhead install this to your clients
and -
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
here
Post by Kevin Weilbacher [SBS-MVP]
comes a really neat point - easily and quickly update the clients when
those
Post by Kevin Weilbacher [SBS-MVP]
security patches or Service Packs are released. Additionally, if you
make
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
use of the Office 2003 Resource Kit you can create .mst files ( aka
Transforms files ) that will allow you to customize the installation (
say
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
that Heinz and Hans get Excel, Word and Outlook while Ulrike and Petra
get
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
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
Post by Kevin Weilbacher [SBS-MVP]
that they need. You will not have to go to each computer and make
sure
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
that
Post by Kevin Weilbacher [SBS-MVP]
all of those specific settings are properly configured. Do it via the
GPO
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
and there you have it! Also, you can control it so that your clients
can
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
not go to the officeupdate.microsoft.com and make untested updates to
the
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Office 2003 installation. This is a really nice feature as well.....
Sarah, Du kannst Dich gerne an mich wenden solltest Du Fragen ueber
das
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
Group Policy Object haben....
HTH,
Cary
Post by Sarah Tanembaum
Is it possible to run office from a server?
We just purchased 10 brand new PC with Windows XP Pro Pre-installed,
an
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
a
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
server with ample of memory and disk space.
We also purchase a 15-user license of Microsoft Office 2003
Professional.
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
Instead of installing MS Office 2003 on all the workstation, is
there
a
Post by Sarah Tanembaum
Post by Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
Post by Sarah Tanembaum
Post by Kevin Weilbacher [SBS-MVP]
way
Post by Sarah Tanembaum
to run Office from a server?
I know of the terminal services/citrix way but that is out of the
question
Post by Kevin Weilbacher [SBS-MVP]
Post by Sarah Tanembaum
as it will add cost per client.
Thanks
--
http://www.sbslinks.com/really.htm
begin 666 01.dat
M1TE&.#EA$P`3`*(&`/__`````,S,`/\S`)F9`&9F`/___P```"'Y! $```8`
M+ `````3`!,```-7:+K1'BNR(("UHDE%K\=0%'RD%1J=^8T@=SEO\Z*5*=LL
MD.4`C'NWUVK%*Y&"16#,5# ""JQ&K3<%73(H8(# #?8XU<!@S,.ZM,43V&F6
+2#^[C>BAD20``#L`
`
end
Continue reading on narkive:
Loading...