Office 2003 SP2 Administrative Install?

[Scott]

I'm not finding one available...?

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[Scott]

I should correct that - I cannot find the MSI that you would click on in
software installations -> new package in the GPO - office is not installed
here via GPO (I found that to be incredibly unreliable - errors galore in
office apps on machine that had it pushed to them that way) and I would
prefer to not slipstream it - I just want the freakin update to run on user
machines - anyway to do this now? Or did MS make that 10 times more
difficult to do as well now (seems to be their theme lately)?

Thanks,

Scott

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[neo [mvp outlook]]

The way I understand the install and patch process can be done a couple of
ways...

1) Office 2003 installed from GPO (assuming administrative install point)
- patch admin install point with fullfile sp2 update
- redeploy Office 2003 with GPO

2) Office 2003 installed using setup.exe
- patch using Microsoft Update or Windows Server Update Services

Just so you know, MS implements a binary update process. Therefore the
updates in SP2 fullfile exe download are MSP files. I prefer option #2
because one can modify the setup ini to include references to other
applications/patches that need to be installed after Office completes. This
isn't slipstreaming and does speed up deployment. Another benny is that the
workstation/laptop ends up with a local installation source. This means the
CEO in a hotel room doesn't need access back to corporate network when it
comes time to add a feature, repair the installation, or patch.

 

[Peter Foldes]

Like Neo said the best way in my opinion is using WSUS. You can work around this by directly editing the registry on the client machines which can be scripted using REG.EXE. The WSUS documentation
lists the registry values that need to be set.



You can also use a batch file for distribution. Also read this KB
http://support.microsoft.com/kb/q296861/

Here is an example of a batch file using shortened names

@echo off
setlocal
set hotfixpath=\\servername\hotfixshare
%hotfixpath%\KB817787.EXE /Q
%hotfixpath%\KB819696.EXE -u -n -z -q
%hotfixpath%\KB905414.EXE /quiet /norestart
%hotfixpath%\KB905749.EXE /quiet /norestart
%hotfixpath%\QCHAIN.EXE C:\Hotfix.log
Shutdown /r /t 30 /f