Postinstallation task problem Office
Hello,
I'm having an issue with a post installation task. We're trying to deploy Microsoft Office 2007 Pro SP3 from a scripted Windows XP Pro SP3 install. The drivers seem to install fine, Adobe Reader installs but when the Office task comes up there is a message stating "please go to the control panel and configure system components" After clicking OK all of the tasks following it complete.
This same zip file seems to work with our scripted Windows 7 installs.
The Task Details are as follows:
Type: Application
Runtime Environment: Windows
The file is a zipped file named Office2007Pro.zip with setup.exe in the root
Command Line: setup.exe
I've googled the message and it seems to typically relate to a command not being able to find it's path, however I'm not sure how to correct that on the K2000.
Thanks in advance.
I'm having an issue with a post installation task. We're trying to deploy Microsoft Office 2007 Pro SP3 from a scripted Windows XP Pro SP3 install. The drivers seem to install fine, Adobe Reader installs but when the Office task comes up there is a message stating "please go to the control panel and configure system components" After clicking OK all of the tasks following it complete.
This same zip file seems to work with our scripted Windows 7 installs.
The Task Details are as follows:
Type: Application
Runtime Environment: Windows
The file is a zipped file named Office2007Pro.zip with setup.exe in the root
Command Line: setup.exe
I've googled the message and it seems to typically relate to a command not being able to find it's path, however I'm not sure how to correct that on the K2000.
Thanks in advance.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
cserrins
12 years ago
The k2 automatically changes directories into that folder. Though you may want to use "start /wait setup.exe"
I've never seen the error you mention, can you post a screenshot?
Corey
I've never seen the error you mention, can you post a screenshot?
Corey
Posted by:
cwmarshall
12 years ago
Also make sure you are running an automated installation of Office via an admin file (.MSP)
You can create one by running "setup.exe /admin" and the deployment command line will look like "setup.exe /adminfile YOURNAME.MSP"
You can create one by running "setup.exe /admin" and the deployment command line will look like "setup.exe /adminfile YOURNAME.MSP"
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.