Re: Explain the merit of this install method



I cannot find any information on per seat/per user licensing in reference to
Office. All I found was that Office licenses are concurrent licenses.
The clients are regular (Win XP SP2) not Terminal Server clients.
The installation seems to be a full one, users see the same installation
process as if they installed from a CD where they have to choose typical or
custom and which applications to install, etc.
Couldn't the SA at least automate the Office install so that it is the same
for all of the users and they would not have to select anything the 1st time
they access one of the Office apps?

"Bob Buckland ?:-)" wrote:

Hi H.T.,

It can depend on a couple of things, such as

- Your license agreement, per seat/per user [Office licensing isn't a 'simultaneous user count' based one]
- What type of computer client (terminal server/regular)

- If it's actually installing for each new user or if it's just configuring using a roaming profile (which has some setup but not
a full one) involved.

In addition to checking your license terms (or calling a license support tech through http://microsoft.com/licensing ) you may want
to review the information on supported installation configurations in the Office resource kit for your version
http://office.microsoft.com/ork

=================
<<"HT" <HT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7B108DF5-FDB6-481E-8D6A-AB033B62620E@xxxxxxxxxxxxxxxx
A SysAdmin decided to setup a Win2k3 Network with several labs in a way that
everytime a new user sits at a workstation the Office 2k3 has to be
re-installed for that local user's profile via Add New Programs buton in
Add/Remove Program cmdlet across the network. (They also have to add a new
printer for the printer in the room).
They did this versus just adding Office as part of the workstation image or
making it part of an administrative install for all users of the workstation.
(Initially all of the workstations were setup using admin rights that
included installing Office, once users started sitting at workstating we
discovered this unusual configuration)
Because the lab workstation can be used by any of our users and they do not
neccesarily always sit at the same workstation, this method seems cumbersome.
Can anyone explain why someone would do this other than the answer I got
which was "because we could".
Can this impact our license count since every (new) user that sits at a
workstation must reinstall Office under their profile?<<
--

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*



.



Relevant Pages

  • Re: Networked Office
    ... from the server, ... > in my server and mount that disk on my workstation and execute the ... >> workstation from that Admin Installation. ... >> that when you want to update the clients (sagen wir, ...
    (microsoft.public.windows.server.general)
  • Re: Networked Office
    ... || Microsoft MVP - Sharepoint Portal Server ... those 10(or 100 workstation) will get updated instantly without ... workstation from that Admin Installation. ... my next suggestion) is that when you want to update the clients ...
    (microsoft.public.windows.server.general)
  • Re: Networked Office
    ... from the server, ... > in my server and mount that disk on my workstation and execute the ... >> workstation from that Admin Installation. ... >> that when you want to update the clients (sagen wir, ...
    (microsoft.public.windows.server.sbs)
  • Re: Networked Office
    ... || Microsoft MVP - Sharepoint Portal Server ... those 10(or 100 workstation) will get updated instantly without ... workstation from that Admin Installation. ... my next suggestion) is that when you want to update the clients ...
    (microsoft.public.windows.server.sbs)
  • Re: Networked Office
    ... from the server, ... > in my server and mount that disk on my workstation and execute the ... >> workstation from that Admin Installation. ... >> that when you want to update the clients (sagen wir, ...
    (microsoft.public.office.setup)