Networked Office

[Sarah Tanembaum]

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.

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

 

[Sarah Tanembaum]

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.

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

 

[Sarah Tanembaum]

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.

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

 

[Sarah Tanembaum]

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.

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

 

[Sarah Tanembaum]

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.

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

 

[Sarah Tanembaum]

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.

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

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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.

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.

Please ....


Kit

to

 

[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

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

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

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.

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.

Please ....



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

 

[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

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

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

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.

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.

Please ....



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

 

[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

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

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

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.

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.

Please ....



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

 

[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

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

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

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.

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.

Please ....



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

 

[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

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

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

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.

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.

Please ....



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