Office won't install for all users - KNow what but not why?

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----

For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Brandon Smith]

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is not a
viable option as we use a variety of packages for users.

message news:[email protected]...

Are you using the GPO and assign it to PC? Then the instaler just pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry entries and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install to get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all others are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above command
line.

 

[Bruce Musgrove]

Okay, that makes sense. I feel stupid for not thinking of that
I guess I will use ZAP files, as the main reason I use this is to make the
programs easily acccessible form the computer for installs. I do not want to
publish and force installs at this time

Bruce, what you are doing is considered a per user installation of Office
when you assign/publish with a user GPO. In this scenario the GPO
overrides
your allusers=2 in your transform. You will have to assign per machine in
order for all users to receive Office 2003. Also, if you continue to use
per
user GPOs and 3 different users have Office 2003 installed on the machine,
you are going to run into serious issues with patching as well.

As followup, if I put it into GPO using a ZAPFILE, with the same command
line below, it works fine.

Using the USER GPO policy and publishing it so it can be installed trhough
ADD REMOVE PROGRAMS >Add new programs

First user (an admin) runs the installer to do the initial install
Subsequent users SHOULD have shortcuts on START and START PROGRAMS for
office, so that the first time they click on any document or office
program, a mini install runs and finializes the office install for that
user. This IS NOT what happens. Instead , every subsequent users must
go
into ADD REMOVE PROGRAMS >ADD NEW PROGRAMS and start the installer as
if was
a first time install for published software. Then it will run the mini setup
and make office available.

If I install from the command line using \server1\xpadmin\Settup.exe
TRANSFORMS=\\server1\xpadmin\neuro.MST /qb, it works as expected. IE it
advertises it to all users. Yes, this is the same transform I apply through
the GPO software policy.

What I would like to understand is why the difference? Either way it should
install and advertise to all users, but it does not. The only I have
found
to do that is to ASSIGN it to a PC instead of publish it. Assigning is
not a
viable option as we use a variety of packages for users.

"Roady [MVP]" <newsgroups_DELETE_@_DELETE_sparnaaij_NO_._SPAM_net>
wrote in
message Are you using the GPO and assign it to PC? Then the instaler just
pops up
for several seconds (depending a bit on the speed of your PC) to finalize
the installation for that user; creating shortcuts and registry
entries
and
such.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

-----
message For awhile I have been trying to discover why Office would not install
for all users.

I have been deploying it by assigning it in GPO and using a custom
transform that disables Outlook , and sets the ALLUSERS property
to 2
(which is the default anyway)

When we install on a PC, Every users has to run the windows install
to
get
access to the programs. You cannot just click on the icons as you expect
when it is advertised. The first install is a full install, all
others
are
the mini setup you would expect if it is advertised.

BUT if I install it from a command line, instead of gpo, using
\\server1\xpadmin\Settup.exe TRANSFORMS=\\server1\xpadmin\neuro.MST /qb-

Then it installs , advertises to all users, and works beautifully. Can
anyone shed a little insight on this? I would think advertising in GPO
with a transform, would be essentially the same as the above
command
line.