I'm attempting to make several packages for MS Office 2007 (for different departments in our organization). I have completed one that has the basics: Word, Outlook, Excel and PowerPoint. I made a separate package (with the OCT tool) that only installs Access. When I try to run the Access installation (with a batch file pointing to the MSP) on top of the Office 2007 installation, I receive the following error message:

The /adminfile command-line option can be used only dring initial installation of the product.

I've Googled this message but was unable to find a decent explanation.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Have a look at my reply in this thread which deals with a similar query.

Basically you need to use the /modify qualifier with setup.exe to make changes to an existing Office Installation.

Regards,

Spartacus
Answered 09/11/2007 by: spartacus
Black Belt

Please log in to comment
0
Thanks for your reply, Spartacus. I have everything in place but something is still not right. Here is what I have so far:

1) I created a batch file to install Access 2007:

"%~DP0\setup.exe" /modify Enterprise /config "%~DP0\AddAccessConfig.xml"

2) The Office 2007 screen comes up but I believe its not reading the XML file correctly as it is not automated and asks what I would like to do (add/remove/repair).

Here is what my XML file looks. I'm sure this is where I have made my mistake. I copied this from the Enterprise.WW folder and renamed it to AddAccessConfig.xml.

<Configuration Product="Enterprise">

<!-- <Display Level="Basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" /> -->

<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> -->

<!-- <PIDKEY Value="XXXXXXXXXXXXXXXXXXXXXXXXX" /> -->

<!-- <USERNAME Value="Customer" /> -->

<!-- <COMPANYNAME Value="XXX" /> -->

<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

<!-- <LIS CACHEACTION="CacheOnly" /> -->

<!-- <SOURCELIST Value="\\server\share\Microsoft Office 2007" /> -->

<!-- <DistributionPoint Location="\\server\share\Microsoft Office 2007" /> -->

<!-- <OptionState Id="PubPrimary" State="Local" Children="force" /> -->

<!-- <Setting Id="Reboot" Value="IfNeeded" /> -->

<!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->
</Configuration>
Answered 09/11/2007 by: dpolishsensation
Blue Belt

Please log in to comment
0
I'm a long way from being an XML expert but I believe you need to remove the 'Comments' marks from tyhe XML elements. To take one example:

<!-- <SOURCELIST Value="\\server\share\Microsoft Office 2007" /> -->

should, I think, be:

<SOURCELIST Value="\\server\share\Microsoft Office 2007" />
Answered 09/11/2007 by: VBScab
Red Belt

Please log in to comment
0
I'm less of an expert on XML than you. I wasn't aware those were comment marks. =) Anyway, I removed all the comment marks and now receive the following error message:

The setup configuration file \\server\share\AddAccessConfig.xml is not valid. Run Setup again without using a Setup configuration file, or fix the configuration file.

I guess the issue is with the XML file. I just need to figure out what is entered incorrectly...
Answered 09/11/2007 by: dpolishsensation
Blue Belt

Please log in to comment
0
There *must* be an XML evaluator somewhere on-line...does w3 have one?
Answered 09/12/2007 by: VBScab
Red Belt

Please log in to comment
0
I notice that in the XML you posted, your OptionState line is not correct. If you wish to add Access, it should read.

<OptionState Id=”AccessFiles”
State=”Absent”
Children=”force”
/>


Also, I might be stating the obvious here, but you would need to change \\server\share wherever it occurs in the XML file to be the actual names of your server and your share.

Regards,

Spartacus
Answered 09/12/2007 by: spartacus
Black Belt

Please log in to comment
0
Well I changed the OptionState Id as you suggested Spartacus. Still no go. Getting the same error message. Oh and I just did \\server\share when posting on the forums. I have the correct info in the XML file.
Answered 09/12/2007 by: dpolishsensation
Blue Belt

Please log in to comment
0
Anyone else have any insight into this? Any help is greatly appreciated!! :)
Answered 09/14/2007 by: dpolishsensation
Blue Belt

Please log in to comment
0
The following option in CONFIG.XML will remove the ACCESS feature from the system
<OptionState Id=”AccessFiles”
State=”Absent”
Children=”force”
/>
http://technet2.microsoft.com/Office/en-us/library/e16af71c-fed4-40da-a886-95e596c3999e1033.mspx?mfr=true
=================================================================
Syntax


<OptionState
Id="optionID"
State="Absent" | "Advertise" | "Default" | "Local"
[Children="force"]
/>[/align]Attributes




Attribute
Value
Description



Id

optionID

An item that the user can choose to install.


State

Absent

The feature is not installed.




Advertise

The feature is installed the first time it is used.




Default

The feature returns to its default installation state.




Local

The feature is installed on the user's computer.


Children

force

All child features of the feature are set to the specified state. [/align]=================================================================

If you want to install only ACCESS through your package, follow the steps
- Configure OCT to install noly ACCESS feature by disabling all other features (NOT AVAILABLE option)
- Do not configure anything in CONFIG.XML
- Save the MSP file under UPDATES folder (during the installation setup will automatically installs the patch file)
- Execute Setup.exe without any commandline options.

It should work. If you have any issues, you can contact me anytime at [email=eshwar.mca@gmail.com]eshwar.mca@gmail.com[/email]. I'll be more than happy to assist you.
You really don't have to create two packages. (package without ACCESS / package with only ACCESS)
You can use one standard source with two different CONFIG.XML files to do the job
Answered 09/26/2007 by: eshwar.mca
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity