Office 2003 Unattended Installation Problems

[Ted Wagner]

Using the information for the Office 2003 advanced installation:

http://unattended.msfn.org/unattended.xp/view/web/50

I downloaded the ORK.exe, installed it.

I then followed the directions to the letter. No problems. Created my
batch file with my command line.

When I try to test my unattended installation of Office 2003 on a Windows XP
Professional desktop, I get the following error in a Windows MsgBox:

Window Title: Windows XP Setup
Text: Please go to the Control Panel to install and configure system
components.

My batch file is this:

start /wait setup.exe TRANSFORMS=DR.MST /qb+

The batch file is in the Office2003 directory.

Any ideas why on an unattended installation XP is telling me instead to use
the Control Panel?

I've been looking for a couple of hours with no success via google and the
MS Support knowledgebase.

Thank you

Ted

 

[neo [mvp outlook]]

Not knowing the directory/cd/network structure of how you are performing
this unattended install, you might find it better to set drive letter/paths
in your batch file. For example, I do nothing but unattended network
installs and have to use unc paths to install line of business applications
after XP finishes installing.

e.g.
start /w \\server\path\setup.exe TRANSFORMS=\\server\path\the.mst /qb-

 

[neo [mvp outlook]]

Not knowing the directory/cd/network structure of how you are performing
this unattended install, you might find it better to set drive letter/paths
in your batch file. For example, I do nothing but unattended network
installs and have to use unc paths to install line of business applications
after XP finishes installing.

e.g.
start /w \\server\path\setup.exe TRANSFORMS=\\server\path\the.mst /qb-

 

[neo [mvp outlook]]

Not knowing the directory/cd/network structure of how you are performing
this unattended install, you might find it better to set drive letter/paths
in your batch file. For example, I do nothing but unattended network
installs and have to use unc paths to install line of business applications
after XP finishes installing.

e.g.
start /w \\server\path\setup.exe TRANSFORMS=\\server\path\the.mst /qb-

 

[neo [mvp outlook]]

Not knowing the directory/cd/network structure of how you are performing
this unattended install, you might find it better to set drive letter/paths
in your batch file. For example, I do nothing but unattended network
installs and have to use unc paths to install line of business applications
after XP finishes installing.

e.g.
start /w \\server\path\setup.exe TRANSFORMS=\\server\path\the.mst /qb-

 

[neo [mvp outlook]]

Not knowing the directory/cd/network structure of how you are performing
this unattended install, you might find it better to set drive letter/paths
in your batch file. For example, I do nothing but unattended network
installs and have to use unc paths to install line of business applications
after XP finishes installing.

e.g.
start /w \\server\path\setup.exe TRANSFORMS=\\server\path\the.mst /qb-

 

[neo [mvp outlook]]

Not knowing the directory/cd/network structure of how you are performing
this unattended install, you might find it better to set drive letter/paths
in your batch file. For example, I do nothing but unattended network
installs and have to use unc paths to install line of business applications
after XP finishes installing.

e.g.
start /w \\server\path\setup.exe TRANSFORMS=\\server\path\the.mst /qb-

 

[Ted Wagner]

I've used both a unc path, local path etc. Each time I couldn't run the
install.

Ted

 

[Ted Wagner]

I've used both a unc path, local path etc. Each time I couldn't run the
install.

Ted

 

[Ted Wagner]

I've used both a unc path, local path etc. Each time I couldn't run the
install.

Ted

 

[Ted Wagner]

I've used both a unc path, local path etc. Each time I couldn't run the
install.

Ted

 

[Ted Wagner]

I've used both a unc path, local path etc. Each time I couldn't run the
install.

Ted

 

[Ted Wagner]

I've used both a unc path, local path etc. Each time I couldn't run the
install.

Ted

 

[Ted Wagner]

AHA! Ok.

Here's what I wasn't doing...that now works. I had to think a little deeper
about wha tyou were saying here:

start /wait z:\setuppro.exe TRANSFORMS=z:\DR.MST /qb+

My problem was with the setup .... needed to be setuppro.exe...works just
fine now.

Ted

 

[Ted Wagner]

AHA! Ok.

Here's what I wasn't doing...that now works. I had to think a little deeper
about wha tyou were saying here:

start /wait z:\setuppro.exe TRANSFORMS=z:\DR.MST /qb+

My problem was with the setup .... needed to be setuppro.exe...works just
fine now.

Ted

 

[Ted Wagner]

AHA! Ok.

Here's what I wasn't doing...that now works. I had to think a little deeper
about wha tyou were saying here:

start /wait z:\setuppro.exe TRANSFORMS=z:\DR.MST /qb+

My problem was with the setup .... needed to be setuppro.exe...works just
fine now.

Ted

 

[Ted Wagner]

AHA! Ok.

Here's what I wasn't doing...that now works. I had to think a little deeper
about wha tyou were saying here:

start /wait z:\setuppro.exe TRANSFORMS=z:\DR.MST /qb+

My problem was with the setup .... needed to be setuppro.exe...works just
fine now.

Ted

 

[Ted Wagner]

AHA! Ok.

Here's what I wasn't doing...that now works. I had to think a little deeper
about wha tyou were saying here:

start /wait z:\setuppro.exe TRANSFORMS=z:\DR.MST /qb+

My problem was with the setup .... needed to be setuppro.exe...works just
fine now.

Ted

 

[Ted Wagner]

AHA! Ok.

Here's what I wasn't doing...that now works. I had to think a little deeper
about wha tyou were saying here:

start /wait z:\setuppro.exe TRANSFORMS=z:\DR.MST /qb+

My problem was with the setup .... needed to be setuppro.exe...works just
fine now.

Ted