Rolling Out Office 2003 Fails

Albert,

This is not an SMS issue, but rather an Office 2003 issue when you
deploy it from an administrative deployment point. I am having the
same exact error shown below and i'm running it from a batch file using
TRANSFORM. I still have not resolved the issue but I am pretty sure
it's a conflict between Office 2003 and Office XP. I run the same
installation on a clean Windows 2003 Server and it runs smoothly, I ran
it on a Windows XP SP2 that did not have Office XP and it works fine so
i'm thinking it's some compatibility issue when you have Office XP
installed. Even after you uninstall Office XP and then install Office
2003 it still does not work so there must be something that is being
left on the OS from Office XP that is still creating some issues and it
could simply be some registry entriese. So, i'm trying to figure out a
solution for this. If you come across a solution, please email me back
at and let me know the solution.

Matthew


Albert wrote:
I am not able to deploy Office 2003 with SMS 2003. The Office 2003
files are located in an administrative point on a DFS share. Office is
configured to run from the network.The SMS 2003 site server and site
systems are running Windows Server 2003. The clients are running
Windows XP Pro SP1. I have successfully deployed other programs. The
Advancec Client tab on the advertisement is set to "run program from
distrubution point". The program in the package is set to run "whether
or not a user is logged on", run with administrative rights, and use
Software Installation Account. The program runs a script as follows:

if not exist N:\nul net use N: \\DFS-ROOT\SHARE /persistent:no
N:\Win32App\Office11\setuppro.exe /qb- /m off11

The SMS Status Message shows the following:

The program for advertisement "MSV20004" failed ("MSV00002" -
"Install"). A failure exit code of 1603 was returned.
User context: NT AUTHORITY\SYSTEM
......

The setup is run with the /L*v logging option. The "Microsoft Office
2003 Office Setup(xxxx).txt" shows:

......
Successfully launched MsiExec....
3/11/2004 2:23:33 AM Chained install return code: 1603

Exit code was an error.
Shutting down chained setup processing.
......

The "Microsoft Office 2003 Setup(xxxx)_Task(0001).txt" shows:

......
Action start 2:23:25: SKURED.
SKURED: Source path for skured.xml:
N:\Win32App\Office11\FILES\PFILES\MSOFFICE\OFFICE1 1\1033\011\SKU011.XML
SKURED: Error 0x3: VerityXMLSignatu failed to open
N:\Win32App\Office11\FILES\PFILES\MSOFFICE\OFFICE1 1\1033\011\SKU011.XML
SKURED: ERROR: test signature verification failed for
N:\Win32App\Office11\FILES\PFILES\MSOFFICE\OFFICE1 1\1033\011\SKU011.XML
SKURED: Error 0x80004005: GetSkuRedRoot: xml signature verification
failed
SKURED: Failed to read skured data, fatal error
Error 25003. Microsoft Office Setup cannot continue because the
installation source has been corrupted.
Action ended 2:23:26: SKURED. Return value 3.
Action ended 2:23:26: INSTALL. Return value 3.
......

Below are some more information:

1. When I logged on to a client machine as a user with administrative
privilege on the client and run the script, Office installed without
any problems. Hence the source files are fine.

2. I used similar script to deploy Office XP using SMS 2.0 and it
worked.

3. Both the Advance Client Network Access account and the client
computer account (through Domain Computers) have read access (both NTFS
and share permission) to the share where the Office files are located.

4. I created a SMS package with the same configuration to run the
following script:

if not exist N:\nul net use N: \\DFS-ROOT\SHARE /persistent:no
copy
N:\Win32App\Office11\FILES\PFILES\MSOFFICE\OFFICE1 1\1033\011\SKU011.XML
D:\Windows\TEMP

and advertised with the same configuration to the client machines.
The program ran successfully and the file was copied.

5. I changed the Office advertisement to "download program from
distribution point" and it did not work either.

I would appreciate any help to work around this. Thanks.