Deploying Office 07 with Group Policy

T

TC

I am preparing to roll out Office 2007 Pro+ to our organisation. We
currently have Office 2000 Pro installed on all computers as well as Outlook
2003 deployed as a group policy computer assigned package - but that gp
removed. Our users are not local administrators of their computers.

I have used the customisation wizard to create an MSP file which removes all
previous versions of office and does a full install. The Office resouce kit
information seems to suggest two options for deploying to users who are not
local administrators. One is to use SMS which we don't have and the other is
to use a computer logon script through group policy where it says the script
will run as local system with the required permissions.

When I tested the deployment using a computer logon script (batch file) in
gp to my own computer where I am a local admistrator, everything worked.
When I tested it on two other computers where I was not a local
administrator, setup ran and seemed to be working but when it had finished I
ended up with no versions of office working. The files for both old and new
versions were on the computer. Both versions were lised in add/remove
programs. The shortcuts on the start menu for the old version were still
there, but not for the new verison. Neither version of Office programs would
run.

I am guessing that setup only had part of the permissions required to
complete the process. Is the information in the resource kit wrong or have I
missed something?

TC
 
E

Emily Lin [MSFT]

Hi TC,

It seems that you are using "a computer logon script". As the user doesn't
have administrator rights, we need to use "the computer startup script".
Please check it on your GPO.

1. Opens the Group Policy Object Editor console.
2. In Group Policy Object Editor, in the console tree, click Scripts
(Startup/Shutdown). This is located in the Computer Configuration\Windows
Settings node.

Did you add the script here?

For detail information, please refer to the following webpage.

Use Group Policy to assign computer startup scripts for 2007 Office
deployment
http://technet2.microsoft.com/Office/f/?en-us/library/a57c8446-b959-4025-a86
6-b690ddcaa66d1033.mspx

In addition, send the following information to me so that I can analyse and
research on this issue. My email address is (e-mail address removed).

1. Rename your computer logon script file as a *.txt file. Send it to me.
2. I think that you also define the Office 2007 setup log file location.
Plase also send the log file to me.
3. Run gpresult /s > c:\reports\gp.txt. Send the file gp.txt to me.

If anything is unclear or if you have any other concerns, please don't
hesitate to contact me.

Sincerely,

Emily Lin,
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================



--------------------
| From: "TC" <[email protected]>
| Subject: Deploying Office 07 with Group Policy
| Date: Fri, 7 Sep 2007 10:43:01 +1000
| Lines: 29
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.office.setup
| NNTP-Posting-Host: mail.connections.org.au 122.102.96.230
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6852
| X-Tomcat-NG: microsoft.public.office.setup
|
| I am preparing to roll out Office 2007 Pro+ to our organisation. We
| currently have Office 2000 Pro installed on all computers as well as
Outlook
| 2003 deployed as a group policy computer assigned package - but that gp
| removed. Our users are not local administrators of their computers.
|
| I have used the customisation wizard to create an MSP file which removes
all
| previous versions of office and does a full install. The Office resouce
kit
| information seems to suggest two options for deploying to users who are
not
| local administrators. One is to use SMS which we don't have and the other
is
| to use a computer logon script through group policy where it says the
script
| will run as local system with the required permissions.
|
| When I tested the deployment using a computer logon script (batch file)
in
| gp to my own computer where I am a local admistrator, everything worked.
| When I tested it on two other computers where I was not a local
| administrator, setup ran and seemed to be working but when it had
finished I
| ended up with no versions of office working. The files for both old and
new
| versions were on the computer. Both versions were lised in add/remove
| programs. The shortcuts on the start menu for the old version were still
| there, but not for the new verison. Neither version of Office programs
would
| run.
|
| I am guessing that setup only had part of the permissions required to
| complete the process. Is the information in the resource kit wrong or
have I
| missed something?
|
| TC
|
|
|
 
E

Emily Lin [MSFT]

Hi Tom,

Thanks for your reply. If you reply to me in Emails, please contain the
post ID 40380670. Thanks.

The error "execution of GPO scripts has timed out and have been terminated"
means that there is problem with the GPO execution.

As you tested, Office 2007 is not installed properly on two other computers
which you don't have administrator rights. Please disable the GPO. Log in
the two computers as Administrator and uninstall Office 2007. And then
enable the GPO. Login the two computers as Local Administrator (not your
domain user account). What is the result?

If it doesn't work, disable the original GPO. Create another GPO, and add
the following script to the Computer Startup Script. Test the issue again.

----------------SCRIPT STARTS---------------- REM
*********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file.
set ProductName=PROPLUs

REM Set DeployServer to a network-accessible location containing the Office
source files.
set DeployServer=\\caulsrv1\install\off2k7\

REM Set ConfigFile to the configuration file to be used for deployment REM
(required)
set ConfigFile=\\caulsrv1\install\off2k7\proplus.WW\config.xml

REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\caulsrv1\install\off2k7logs

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

reg query
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%Prod
uctName%

if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait %DeployServer%\setup.exe /config %ConfigFile% echo %date%
%time% Setup ended with error code %errorlevel%. >>
%LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error
occurred. Do nothing.
:End

If anything is unclear or if you have any other concerns, please don't
hesitate to contact me.

Sincerely,

Emily Lin,
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================


--------------------
| X-Tomcat-ID: 78731578
| References: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (e-mail address removed) (Emily Lin [MSFT])
| Organization: Microsoft
| Date: Fri, 07 Sep 2007 06:25:04 GMT
| Subject: RE: Deploying Office 07 with Group Policy
| X-Tomcat-NG: microsoft.public.office.setup
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.office.setup
| Lines: 101
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6860
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Hi TC,
|
| It seems that you are using "a computer logon script". As the user
doesn't
| have administrator rights, we need to use "the computer startup script".
| Please check it on your GPO.
|
| 1. Opens the Group Policy Object Editor console.
| 2. In Group Policy Object Editor, in the console tree, click Scripts
| (Startup/Shutdown). This is located in the Computer Configuration\Windows
| Settings node.
|
| Did you add the script here?
|
| For detail information, please refer to the following webpage.
|
| Use Group Policy to assign computer startup scripts for 2007 Office
| deployment
|
http://technet2.microsoft.com/Office/f/?en-us/library/a57c8446-b959-4025-a86
| 6-b690ddcaa66d1033.mspx
|
| In addition, send the following information to me so that I can analyse
and
| research on this issue. My email address is (e-mail address removed).
|
| 1. Rename your computer logon script file as a *.txt file. Send it to me.
| 2. I think that you also define the Office 2007 setup log file location.
| Plase also send the log file to me.
| 3. Run gpresult /s > c:\reports\gp.txt. Send the file gp.txt to me.
|
| If anything is unclear or if you have any other concerns, please don't
| hesitate to contact me.
|
| Sincerely,
|
| Emily Lin,
| Microsoft Online Partner Support
|
| Get Secure! - www.microsoft.com/security
| ======================================================
| When responding to posts, please "Reply to Group" via your newsreader
| so that others may learn and benefit from this issue.
| ======================================================
| This posting is provided "AS IS" with no warranties, and confers no
rights.
| ======================================================
|
|
|
| --------------------
| | From: "TC" <[email protected]>
| | Subject: Deploying Office 07 with Group Policy
| | Date: Fri, 7 Sep 2007 10:43:01 +1000
| | Lines: 29
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| | X-RFC2646: Format=Flowed; Original
| | Message-ID: <[email protected]>
| | Newsgroups: microsoft.public.office.setup
| | NNTP-Posting-Host: mail.connections.org.au 122.102.96.230
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6852
| | X-Tomcat-NG: microsoft.public.office.setup
| |
| | I am preparing to roll out Office 2007 Pro+ to our organisation. We
| | currently have Office 2000 Pro installed on all computers as well as
| Outlook
| | 2003 deployed as a group policy computer assigned package - but that gp
| | removed. Our users are not local administrators of their computers.
| |
| | I have used the customisation wizard to create an MSP file which
removes
| all
| | previous versions of office and does a full install. The Office resouce
| kit
| | information seems to suggest two options for deploying to users who are
| not
| | local administrators. One is to use SMS which we don't have and the
other
| is
| | to use a computer logon script through group policy where it says the
| script
| | will run as local system with the required permissions.
| |
| | When I tested the deployment using a computer logon script (batch file)
| in
| | gp to my own computer where I am a local admistrator, everything
worked.
| | When I tested it on two other computers where I was not a local
| | administrator, setup ran and seemed to be working but when it had
| finished I
| | ended up with no versions of office working. The files for both old and
| new
| | versions were on the computer. Both versions were lised in add/remove
| | programs. The shortcuts on the start menu for the old version were
still
| | there, but not for the new verison. Neither version of Office programs
| would
| | run.
| |
| | I am guessing that setup only had part of the permissions required to
| | complete the process. Is the information in the resource kit wrong or
| have I
| | missed something?
| |
| | TC
| |
| |
| |
|
|
 
T

TC

Hi Emily,

Thanks for your reply. I have done some further testing and can confirm the
following:

The computers where installation failed were older computers and took about
20 minutes to install Office 2007. Logging on as a standard user or as an
administrator makes no difference. The installaion runs smoothly for the
first 10 minutes until the time out for GP logon scripts is reached. From
this point on you get a few errors in the event log saying that office has
not installed correctly.

Setting the time out to longer fixed the problem. (Computer
Configuration/Administrative Templates/System/Scripts/Maximun wait time for
Group Policy scripts) I set it to 2400 seconds to be safe as another older
computer I tested it on took 30 minutes to install.

With the above setting, Office installed without problem even if no one logs
on to the computer.

Tom


Emily Lin said:
Hi Tom,

Thanks for your reply. If you reply to me in Emails, please contain the
post ID 40380670. Thanks.

The error "execution of GPO scripts has timed out and have been
terminated"
means that there is problem with the GPO execution.

As you tested, Office 2007 is not installed properly on two other
computers
which you don't have administrator rights. Please disable the GPO. Log in
the two computers as Administrator and uninstall Office 2007. And then
enable the GPO. Login the two computers as Local Administrator (not your
domain user account). What is the result?

If it doesn't work, disable the original GPO. Create another GPO, and add
the following script to the Computer Startup Script. Test the issue again.

----------------SCRIPT STARTS---------------- REM
*********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file.
set ProductName=PROPLUs

REM Set DeployServer to a network-accessible location containing the
Office
source files.
set DeployServer=\\caulsrv1\install\off2k7\

REM Set ConfigFile to the configuration file to be used for deployment REM
(required)
set ConfigFile=\\caulsrv1\install\off2k7\proplus.WW\config.xml

REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\caulsrv1\install\off2k7logs

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

reg query
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%Prod
uctName%

if %errorlevel%==1 (goto DeployOffice) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
start /wait %DeployServer%\setup.exe /config %ConfigFile% echo %date%
%time% Setup ended with error code %errorlevel%. >>
%LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error
occurred. Do nothing.
:End

If anything is unclear or if you have any other concerns, please don't
hesitate to contact me.

Sincerely,

Emily Lin,
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================================


--------------------
| X-Tomcat-ID: 78731578
| References: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (e-mail address removed) (Emily Lin [MSFT])
| Organization: Microsoft
| Date: Fri, 07 Sep 2007 06:25:04 GMT
| Subject: RE: Deploying Office 07 with Group Policy
| X-Tomcat-NG: microsoft.public.office.setup
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.office.setup
| Lines: 101
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6860
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Hi TC,
|
| It seems that you are using "a computer logon script". As the user
doesn't
| have administrator rights, we need to use "the computer startup script".
| Please check it on your GPO.
|
| 1. Opens the Group Policy Object Editor console.
| 2. In Group Policy Object Editor, in the console tree, click Scripts
| (Startup/Shutdown). This is located in the Computer
Configuration\Windows
| Settings node.
|
| Did you add the script here?
|
| For detail information, please refer to the following webpage.
|
| Use Group Policy to assign computer startup scripts for 2007 Office
| deployment
|
http://technet2.microsoft.com/Office/f/?en-us/library/a57c8446-b959-4025-a86
| 6-b690ddcaa66d1033.mspx
|
| In addition, send the following information to me so that I can analyse
and
| research on this issue. My email address is (e-mail address removed).
|
| 1. Rename your computer logon script file as a *.txt file. Send it to
me.
| 2. I think that you also define the Office 2007 setup log file location.
| Plase also send the log file to me.
| 3. Run gpresult /s > c:\reports\gp.txt. Send the file gp.txt to me.
|
| If anything is unclear or if you have any other concerns, please don't
| hesitate to contact me.
|
| Sincerely,
|
| Emily Lin,
| Microsoft Online Partner Support
|
| Get Secure! - www.microsoft.com/security
| ======================================================
| When responding to posts, please "Reply to Group" via your newsreader
| so that others may learn and benefit from this issue.
| ======================================================
| This posting is provided "AS IS" with no warranties, and confers no
rights.
| ======================================================
|
|
|
| --------------------
| | From: "TC" <[email protected]>
| | Subject: Deploying Office 07 with Group Policy
| | Date: Fri, 7 Sep 2007 10:43:01 +1000
| | Lines: 29
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| | X-RFC2646: Format=Flowed; Original
| | Message-ID: <[email protected]>
| | Newsgroups: microsoft.public.office.setup
| | NNTP-Posting-Host: mail.connections.org.au 122.102.96.230
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6852
| | X-Tomcat-NG: microsoft.public.office.setup
| |
| | I am preparing to roll out Office 2007 Pro+ to our organisation. We
| | currently have Office 2000 Pro installed on all computers as well as
| Outlook
| | 2003 deployed as a group policy computer assigned package - but that
gp
| | removed. Our users are not local administrators of their computers.
| |
| | I have used the customisation wizard to create an MSP file which
removes
| all
| | previous versions of office and does a full install. The Office
resouce
| kit
| | information seems to suggest two options for deploying to users who
are
| not
| | local administrators. One is to use SMS which we don't have and the
other
| is
| | to use a computer logon script through group policy where it says the
| script
| | will run as local system with the required permissions.
| |
| | When I tested the deployment using a computer logon script (batch
file)
| in
| | gp to my own computer where I am a local admistrator, everything
worked.
| | When I tested it on two other computers where I was not a local
| | administrator, setup ran and seemed to be working but when it had
| finished I
| | ended up with no versions of office working. The files for both old
and
| new
| | versions were on the computer. Both versions were lised in add/remove
| | programs. The shortcuts on the start menu for the old version were
still
| | there, but not for the new verison. Neither version of Office programs
| would
| | run.
| |
| | I am guessing that setup only had part of the permissions required to
| | complete the process. Is the information in the resource kit wrong or
| have I
| | missed something?
| |
| | TC
| |
| |
| |
|
|
 
E

Emily Lin [MSFT]

Hi Tom,

Thanks for your reply and the detail information about how you fixed the
issue. I am glad to hear that the problem has been fixed after extending
the Group Policy scripts time out setting (it is not related to the account
permission as the policy is in computer startup).

If you have any other questions or concerns, please do not hesitate to
contact me. It is always my pleasure to be of assistance.

Have a nice day!

Best regards,

Emily Lin
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================



--------------------
| From: "TC" <[email protected]>
| References: <[email protected]>
<[email protected]>
<[email protected]>
| Subject: Re: Deploying Office 07 with Group Policy
| Date: Tue, 11 Sep 2007 12:55:13 +1000
| Lines: 244
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.office.setup
| NNTP-Posting-Host: mail.connections.org.au 122.102.96.230
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6939
| X-Tomcat-NG: microsoft.public.office.setup
|
| Hi Emily,
|
| Thanks for your reply. I have done some further testing and can confirm
the
| following:
|
| The computers where installation failed were older computers and took
about
| 20 minutes to install Office 2007. Logging on as a standard user or as an
| administrator makes no difference. The installaion runs smoothly for the
| first 10 minutes until the time out for GP logon scripts is reached. From
| this point on you get a few errors in the event log saying that office
has
| not installed correctly.
|
| Setting the time out to longer fixed the problem. (Computer
| Configuration/Administrative Templates/System/Scripts/Maximun wait time
for
| Group Policy scripts) I set it to 2400 seconds to be safe as another
older
| computer I tested it on took 30 minutes to install.
|
| With the above setting, Office installed without problem even if no one
logs
| on to the computer.
|
| Tom
|
|
| | > Hi Tom,
| >
| > Thanks for your reply. If you reply to me in Emails, please contain the
| > post ID 40380670. Thanks.
| >
| > The error "execution of GPO scripts has timed out and have been
| > terminated"
| > means that there is problem with the GPO execution.
| >
| > As you tested, Office 2007 is not installed properly on two other
| > computers
| > which you don't have administrator rights. Please disable the GPO. Log
in
| > the two computers as Administrator and uninstall Office 2007. And then
| > enable the GPO. Login the two computers as Local Administrator (not your
| > domain user account). What is the result?
| >
| > If it doesn't work, disable the original GPO. Create another GPO, and
add
| > the following script to the Computer Startup Script. Test the issue
again.
| >
| > ----------------SCRIPT STARTS---------------- REM
| > *********************************************************************
| > REM Environment customization begins here. Modify variables below.
| > REM
*********************************************************************
| >
| > REM Get ProductName from the Office product's core Setup.xml file.
| > set ProductName=PROPLUs
| >
| > REM Set DeployServer to a network-accessible location containing the
| > Office
| > source files.
| > set DeployServer=\\caulsrv1\install\off2k7\
| >
| > REM Set ConfigFile to the configuration file to be used for deployment
REM
| > (required)
| > set ConfigFile=\\caulsrv1\install\off2k7\proplus.WW\config.xml
| >
| > REM Set LogLocation to a central directory to collect log files.
| > set LogLocation=\\caulsrv1\install\off2k7logs
| >
| > REM
*********************************************************************
| > REM Deployment code begins here. Do not modify anything below this line.
| > REM
*********************************************************************
| >
| > reg query
| >
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%Prod
| > uctName%
| >
| > if %errorlevel%==1 (goto DeployOffice) else (goto End)
| >
| > REM If 1 returned, the product was not found. Run setup here.
| > :DeployOffice
| > start /wait %DeployServer%\setup.exe /config %ConfigFile% echo %date%
| > %time% Setup ended with error code %errorlevel%. >>
| > %LogLocation%\%computername%.txt
| >
| > REM If 0 or other was returned, the product was found or another error
| > occurred. Do nothing.
| > :End
| >
| > If anything is unclear or if you have any other concerns, please don't
| > hesitate to contact me.
| >
| > Sincerely,
| >
| > Emily Lin,
| > Microsoft Online Partner Support
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================
| > When responding to posts, please "Reply to Group" via your newsreader so
| > that others may learn and benefit from this issue.
| > ======================================================
| > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| > ======================================================
| >
| >
| > --------------------
| > | X-Tomcat-ID: 78731578
| > | References: <[email protected]>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain
| > | Content-Transfer-Encoding: 7bit
| > | From: (e-mail address removed) (Emily Lin [MSFT])
| > | Organization: Microsoft
| > | Date: Fri, 07 Sep 2007 06:25:04 GMT
| > | Subject: RE: Deploying Office 07 with Group Policy
| > | X-Tomcat-NG: microsoft.public.office.setup
| > | Message-ID: <[email protected]>
| > | Newsgroups: microsoft.public.office.setup
| > | Lines: 101
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6860
| > | NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
| > |
| > | Hi TC,
| > |
| > | It seems that you are using "a computer logon script". As the user
| > doesn't
| > | have administrator rights, we need to use "the computer startup
script".
| > | Please check it on your GPO.
| > |
| > | 1. Opens the Group Policy Object Editor console.
| > | 2. In Group Policy Object Editor, in the console tree, click Scripts
| > | (Startup/Shutdown). This is located in the Computer
| > Configuration\Windows
| > | Settings node.
| > |
| > | Did you add the script here?
| > |
| > | For detail information, please refer to the following webpage.
| > |
| > | Use Group Policy to assign computer startup scripts for 2007 Office
| > | deployment
| > |
| >
http://technet2.microsoft.com/Office/f/?en-us/library/a57c8446-b959-4025-a86
| > | 6-b690ddcaa66d1033.mspx
| > |
| > | In addition, send the following information to me so that I can
analyse
| > and
| > | research on this issue. My email address is (e-mail address removed).
| > |
| > | 1. Rename your computer logon script file as a *.txt file. Send it to
| > me.
| > | 2. I think that you also define the Office 2007 setup log file
location.
| > | Plase also send the log file to me.
| > | 3. Run gpresult /s > c:\reports\gp.txt. Send the file gp.txt to me.
| > |
| > | If anything is unclear or if you have any other concerns, please don't
| > | hesitate to contact me.
| > |
| > | Sincerely,
| > |
| > | Emily Lin,
| > | Microsoft Online Partner Support
| > |
| > | Get Secure! - www.microsoft.com/security
| > | ======================================================
| > | When responding to posts, please "Reply to Group" via your newsreader
| > | so that others may learn and benefit from this issue.
| > | ======================================================
| > | This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| > | ======================================================
| > |
| > |
| > |
| > | --------------------
| > | | From: "TC" <[email protected]>
| > | | Subject: Deploying Office 07 with Group Policy
| > | | Date: Fri, 7 Sep 2007 10:43:01 +1000
| > | | Lines: 29
| > | | X-Priority: 3
| > | | X-MSMail-Priority: Normal
| > | | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| > | | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| > | | X-RFC2646: Format=Flowed; Original
| > | | Message-ID: <[email protected]>
| > | | Newsgroups: microsoft.public.office.setup
| > | | NNTP-Posting-Host: mail.connections.org.au 122.102.96.230
| > | | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| > | | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.office.setup:6852
| > | | X-Tomcat-NG: microsoft.public.office.setup
| > | |
| > | | I am preparing to roll out Office 2007 Pro+ to our organisation. We
| > | | currently have Office 2000 Pro installed on all computers as well as
| > | Outlook
| > | | 2003 deployed as a group policy computer assigned package - but
that
| > gp
| > | | removed. Our users are not local administrators of their computers.
| > | |
| > | | I have used the customisation wizard to create an MSP file which
| > removes
| > | all
| > | | previous versions of office and does a full install. The Office
| > resouce
| > | kit
| > | | information seems to suggest two options for deploying to users who
| > are
| > | not
| > | | local administrators. One is to use SMS which we don't have and the
| > other
| > | is
| > | | to use a computer logon script through group policy where it says
the
| > | script
| > | | will run as local system with the required permissions.
| > | |
| > | | When I tested the deployment using a computer logon script (batch
| > file)
| > | in
| > | | gp to my own computer where I am a local admistrator, everything
| > worked.
| > | | When I tested it on two other computers where I was not a local
| > | | administrator, setup ran and seemed to be working but when it had
| > | finished I
| > | | ended up with no versions of office working. The files for both old
| > and
| > | new
| > | | versions were on the computer. Both versions were lised in
add/remove
| > | | programs. The shortcuts on the start menu for the old version were
| > still
| > | | there, but not for the new verison. Neither version of Office
programs
| > | would
| > | | run.
| > | |
| > | | I am guessing that setup only had part of the permissions required
to
| > | | complete the process. Is the information in the resource kit wrong
or
| > | have I
| > | | missed something?
| > | |
| > | | TC
| > | |
| > | |
| > | |
| > |
| > |
| >
|
|
|
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top