Explain the merit of this install method

[HT]

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 ?:-\)]

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

=================
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*

 

[HT]

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 ?:-\)]

Hi H.T.,

You'd need to ask your management or IT folks on the background as to the method they chose. It may be to minimize the number of
licenses used or it could be the first time installation for a specific machine or just a roaming profile setup run (it's the same
installer/configuration tool, but it usually has a shorter runtime than a full install would).

For specifics on licensing you may want to phone the MS Licensing folks.

=================
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 ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*