[PiRaT3iToR]

We have Windows XP sp3 .My wife purchased a volume edition
Office 2007 ENTERPRISE from work. The installation stalls at the installation
progress screen then a dialogue opens with the message:

'Setup cannot find cannot find office.en-us\officeLR.cab. Browse to a valid
installation source then click OK'


This file does exist on the dvd but pointing the installation to the correct location doesn’t work.

Can help me?

Edit :
Solved with microsoft installer !!

This post has been edited by PiRaT3iToR: 12 May 2009 - 06:43 AM

[Robku]

I installed Office 2007 (Dutch) on a server share. The folder looks like below...

11-05-2009 10:35 <DIR> ACCESS.NL-NL
11-05-2009 10:36 <DIR> ADMIN
13-11-2006 06:54 175 AUTORUN.INF
11-05-2009 10:29 <DIR> CATALOG
11-05-2009 10:29 <DIR> EXCEL.NL-NL
11-05-2009 10:30 <DIR> INFOPATH.NL-NL
11-05-2009 10:31 <DIR> OFFICE.NL-NL
11-05-2009 10:30 <DIR> OFFICE64.NL-NL
11-05-2009 10:31 <DIR> OUTLOOK.NL-NL
11-05-2009 10:31 <DIR> POWERPOINT.NL-NL
11-05-2009 10:31 <DIR> PROOFING.NL-NL
11-05-2009 11:10 <DIR> PROPLUS.WW
11-05-2009 10:34 <DIR> PUBLISHER.NL-NL
13-11-2006 06:53 2.503 README.HTM
11-05-2009 10:34 <DIR> ROSEBUD.NL-NL
13-11-2006 06:54 463.152 SETUP.EXE
11-05-2009 10:34 <DIR> UPDATES
11-05-2009 10:35 <DIR> WORD.NL-NL

In the PROPLUS.WW I made changes to the config.xml...
I made a GPO that installs the PROPLUSWW.MSI (located in the PROPLUS.WW)
Installations to a workstation works fine. No problem at all. The application is not installed in production yet.

Now I want to add SP2 to this installation. Can someone please explain how to do this... Can I use the Update directorie? I thought this will not work, because this directorie will only be used when you use the setup. I use the MSI. Is there a way how I can slipstream the installation of SP2 into this setup. There are no PS's installed yet.

Regards,
Rob

[prathapml]

@Robku
Yes, just extract the MSP files that you extract from the SP2 archive, into the Updates folder.
It will be used regardless of whether you use the MSI or SETUP.EXE.

Incidentally, atleast a few editions dis-allow using the MSI to install, leaving you with no other option anyway. Put in the arguments and other customizations you want into the customization MSP and into the config.xml, and just start the SETUP.EXE directly.

This post has been edited by prathapml: 16 May 2009 - 11:16 PM

[badsc9]

Hi all

I was thinking about how does the script look like if you just want to make the whope pack unattended without taking some of the programs out the reason why I ask is becuase I have been sitting and tried a few things and well it does't really look like it's installing more then like five programs out of nine sow how does the script look like bout the script where you have enabled the program to be installed but also the script where you have disabled the program to be installed if anyone know the answer plese through a line of two and maybe highlight the topics where there have been made a change

best regards

Badsc9 and thanks

PS: by the way it's a great site sow to the people behind it keep up the good work it means alot to alot of us :-)

prathapml, on Apr 14 2006, 07:11 PM, said:

Option B:
1. Go to the folder-path, "Office2007\Pro.WW" (or any ??????.WW folder for other editions such as standard/enterprise/etc)
2. Modify "config.xml", or copy it to somewhere else & modify it, using my posted code below as a sample.
3. If you modified it "in location", then setup will take up the changes automatically.
4. Otherwise, place the modified file in the same folder of setup.exe, as custom-uA.XML
5. This is the command to run setup with the customizations specified in custom-uA.XML: setup.exe /config custom-uA.XML

7. This method is also a great way to make changes to the defaults itself, so that you dont need to keep changing it upon every new time you install it. The sample XML here, makes setup fully silent, cuts down features rarely used by me, and reduces install footprint of Office 2007 Professional from 721 MB, to 303 MB (of course you can always add/remove components later); I've also removed lines that I found useless from it, you might like to keep many of the default lines & customize them. Also, be aware that the XML offers a way to chain updates & install them before or after o2k7 setup, but then you'll lose control over reboot parameters. By default, o2k7 setup wont cause an auto-reboot, so no need of "/noreboot" or "Reboot=ReallySuppress" properties. I intend this XML to be used for clean installs, with no previous version settings or profiles to be migrated. Use "start /wait" for silent installs. This file is for the main suite, you can modify it accordingly for the other component products, the options are commented with double-slashes. I obtained the OptionIds from setup.xml files, in each component folder.

Here's a tested/working config.xml file, to get you started with Option B:
(you need to put in your own key, and configuration-Product can be obtained from your current xml)

 
<Configuration Product="Pro">

	<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
	
	<PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" />
	<USERNAME Value="0wner" />
	<COMPANYNAME Value="0wn Inc." />

	
	<OptionState Id="ACCESSFiles" State="absent" Children="force" /> //access
	<OptionState Id="OUTLOOKFiles" State="absent" Children="force" /> //outlook
	<OptionState Id="PubPrimary" State="absent" Children="force" /> //publisher
	<OptionState Id="AceRepl" State="absent" Children="force" /> //access db Engine replication
	<OptionState Id="CAGFiles" State="Local" Children="force" /> //Clip Organizer
	<OptionState Id="MSSOAP3" State="absent" Children="force" /> //SOAP toolkit
	<OptionState Id="OsaNonBoot" State="Local" Children="force" /> //new,open office docu lnks
	<OptionState Id="ProofingTools_1036" State="absent" Children="force" /> //french
	<OptionState Id="ProofingTools_3082" State="absent" Children="force" /> //spanish
	<OptionState Id="WISPFiles" State="absent" Children="force" /> //handwriting
	<OptionState Id="DocServicesFiles" State="absent" Children="force" /> //docu update util
	<OptionState Id="HTMLSourceEditing" State="absent" Children="force" /> //script editor
	<OptionState Id="DocumentImagingUtils" State="absent" Children="force" /> //scanning,ocr,indexing
	<OptionState Id="OISFiles" State="absent" Children="force" /> //picture manager
	<OptionState Id="OSESupp" State="absent" Children="force" /> //sharepoint support
	<OptionState Id="QueryFiles" State="absent" Children="force" /> //msQuery
	<OptionState Id="VisioPreviewerFiles" State="absent" Children="force" /> //visio viewer
	<OptionState Id="XDOCSFiles" State="absent" Children="force" /> //infopath

	<!-- These are additionals from Enterprise RTM
<OptionState Id="GrooveFiles" State="absent" Children="force" /> //groove
<OptionState Id="OneNoteFiles" State="absent" Children="force" /> //onenote
<OptionState Id="RefIEBarFiles" State="absent" Children="force" /> //research explorer bar
<OptionState Id="WebDriveFiles" State="absent" Children="force" /> //hosted webs
<OptionState Id="VBAFiles" State="absent" Children="force" /> //VB for applications
<OptionState Id="OfficeDigitalSFiles" State="absent" Children="force" /> //vba certificates
	 -->

</Configuration> 

The procedure is same for all other editions of Office 2007. The above is just a working sample, you'd need to put in an appropriate key & modify as per your needs.


If you downloaded a single SETUP.EXE (500-MB?) from MSDN, then you might need to extract it to some folder, to get the installation source.

setup.exe /extract:D:\o2k7

[Robku]

prathapml, on May 16 2009, 11:03 PM, said:

@Robku
Yes, just extract the MSP files that you extract from the SP2 archive, into the Updates folder.
It will be used regardless of whether you use the MSI or SETUP.EXE.

Incidentally, at least a few editions dis-allow using the MSI to install, leaving you with no other option anyway. Put in the arguments and other customizations you want into the customization MSP and into the config.xml, and just start the SETUP.EXE directly.

So in my case... the extracted files from the update do not allow installing via an MSI. I tried... did not succeed... Just the standard files are installed, no updates...
I still want to use the MSI, because it is so easy to put a computer in a security group (with GPO) and the application is installed and uninstalled when I remove the SG.
If I use the setup, it will run in User context I guess? So a normal user does not have the proper rights... And... When it is installed... It can't be removed by simply removing the GPO from the computer?

Regards
Rob

[majorg]

I've created a custom.msp file, and the Office 2007 deployment is successful via group policy, but Office 2003 is not removed as requested. Having done quite a lot of research, it seems that Office 2003 will only be removed automatically if it was deployed via group policy, and not installed manually as is the case in my organisation. Any ideas how I can upgrade and remove Office 2003 at the same time?

Regards,
Geoff

[prathapml]

majorg, on May 26 2009, 06:35 PM, said:

I've created a custom.msp file, and the Office 2007 deployment is successful via group policy, but Office 2003 is not removed as requested. Having done quite a lot of research, it seems that Office 2003 will only be removed automatically if it was deployed via group policy, and not installed manually as is the case in my organisation. Any ideas how I can upgrade and remove Office 2003 at the same time?

If the old version isn't being removed, you might have to run a one-time command that all computers must execute at next logon. For example:

MsiExec.exe /X{10140000-0011-0000-0000-0000000FF1CE}

You can find the exact product components to uninstall and their GUID codes in the registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

You can also refer to this URL for GUID info and explanations - http://support.microsoft.com/kb/832672

Robku, on May 25 2009, 11:18 AM, said:

So in my case... the extracted files from the update do not allow installing via an MSI. I tried... did not succeed... Just the standard files are installed, no updates...
I still want to use the MSI, because it is so easy to put a computer in a security group (with GPO) and the application is installed and uninstalled when I remove the SG.
If I use the setup, it will run in User context I guess? So a normal user does not have the proper rights... And... When it is installed... It can't be removed by simply removing the GPO from the computer?

Hmm, for these purposes, an enterprise edition (or VLK license) is the best for ActiveDirectory environments. Other editions don't like to pickup MSP files from the Updates folder, as I mentioned. For me to suggest any workaround, may I ask which edition you are using?

badsc9, on May 23 2009, 08:21 PM, said:

I was thinking about how does the script look like if you just want to make the whole pack unattended, without taking some of the programs out

You are using Option B from the first post of this thread. The config.xml file i've posted there is just an example, and you'd have to modify it as per your needs. The XML code there, as you can see, has comments to the right side of relevant lines, which mention how to force install or NOT install specific components of the suite. You probably want to do a straight-forward install, with the default set of components installed, and no customization of removing components. Therefore, if you don't want to customize a particular setting/component, simply don't mention it in the XML file. So that is how you can go about doing what you mentioned in your post.

This post has been edited by prathapml: 26 May 2009 - 11:42 AM

[blindreaper]

How do i do an unattended setup without a product key?
It seems im always asked for one.

[DraGula0]

Hi Guys,

Do you know, how it's possible to desactivate the "pop-up" when you open Office 2007 for the first time ?

I have modified some parameters in my MSP file. But no effect.

FYI, I use Office 2007 Enterprise SP2 MUI, with MSP file and XML configuration...



Thanks
Greg


Here is the screenshot

[Salvadore]

First of all, thank you for all valuable information shared here.

prathapml, on Nov 27 2008, 09:34 AM, said:

Also, are you sure you are using a volume licensed version (non-pirated?) that supports using MSPs ?
If you're using a retail edition, use Option B.

Has anybody tried to add Admin folder into the root of Office 2007 retail version (to enable OCT). Here's a quick tutorial how to grab Admin folder: link

Followed the steps, but in my case didn't replace (cause I have Office 2007 pro retail version), just added Admin folder and "setup.exe /admin" is working, now.

However, haven't tried installation after creating custom .MSP. Just want to make sure - Is it workable solution?

EDIT: Installation went just fine. That means non-VL(K) editions of Office 2007 can use OCT with custom made .MSP!

"Admin" folder (from AdminTemplates.exe) has been available since 10/11/2007. Latest one (SP2) can be found here (4/29/2009). Update/add "Admin" folder whether you have VL(K) or non-VL(K). It requires Office 2007 with SP2, but I have doubt about it.

This post has been edited by Salvadore: 15 June 2009 - 05:30 PM

[icemanzh]

Hi guys,

First of all, thanks Prathapml for the step-by-step, tryed both with the same result, f**... GREAT !
But...

I've also added it to xp sp3 using the "Option B" ( config.xml ) and after the almost complete unattended install, the last screen still pops up giving the option to go online or close...and i really have to interact to close it.

Any solution for this?

Forgive me if this has been answered, i've missed it then...

Any sugestion or solution would be apreciated, i'm just stuck at that sh** screen...

Thanks again and in advance

IcemanZH

This post has been edited by icemanzh: 22 June 2009 - 02:24 PM

[icemanzh]

come on guys, i even asked please...
it is just a simple question... maybe the solution is simple as well....

don't tell me that nobody as seen my last post...

thanks to anybody

IcemanZH

[prathapml]

blindreaper, on May 29 2009, 06:20 PM, said:

How do i do an unattended setup without a product key?
It seems im always asked for one.

Hmm, haven't tried without a key. Maybe the VLK insists on a key because there's no other way of verification/activation after install? The Retail/OEM editions of Office 2007 probably allow for installing without a key, and run for 25 times before you need to insert a key and activate.

DraGula0, on Jun 5 2009, 09:39 PM, said:

Do you know, how it's possible to desactivate the "pop-up" when you open Office 2007 for the first time ?
I have modified some parameters in my MSP file. But no effect.
FYI, I use Office 2007 Enterprise SP2 MUI, with MSP file and XML configuration...
Thanks
Greg
Here is the screenshot

Hi Greg, I have no idea how to get rid of that "pop up" as you call it. Tried a few things in the MSP and XML initially, but didn't manage to make that part silent. Maybe this can be done through a registry entry. Try this:
1. Install Windows fresh.
2. Install Office 2007 (in your customized style, in whatever way you do it) but don't start any constituent apps just yet.
3. Use a tool that allows for comparing before/after snapshots of the Registry (like RegShot) to take a first snapshot.
4. Open any app (Excel/Word/etc), click through the "pop up" with the options you want, and then maybe close the app.
5. Now take a second snapshot of the registry (RegShot?).
6. RegShot is capable of comparing the two snapshots and showing you (in text form) which registry keys were changed.
7. Read through the log of changes (made in step 6), use process of elimination to understand which key is likely to be the one you want.
8. Visit the registry, confirm it, make a .REG file of the relevant entries.
9. Install Windows fresh again, and Office 2007 with your customizations and also apply the .REG file, see if the popup is gone.
If you hit upon the solution, please do post back to this thread to let us know.

icemanzh, on Jun 23 2009, 01:53 AM, said:

I've also added it to xp sp3 using the "Option B" ( config.xml ) and after the almost complete unattended install, the last screen still pops up giving the option to go online or close...and i really have to interact to close it.
Any solution for this?
Any sugestion or solution would be apreciated, i'm just stuck at that sh** screen...

Hi IcemanZH, immediately above is a similar issue posted by Greg. Try the same steps I've suggested to him, and please post back to let us know of the results.

Salvadore, on Jun 14 2009, 07:36 PM, said:

Has anybody tried to add Admin folder into the root of Office 2007 retail version (to enable OCT). Here's a quick tutorial how to grab Admin folder: link

Followed the steps, but in my case didn't replace (cause I have Office 2007 pro retail version), just added Admin folder and "setup.exe /admin" is working, now.
EDIT: Installation went just fine. That means non-VL(K) editions of Office 2007 can use OCT with custom made .MSP!

"Admin" folder (from AdminTemplates.exe) has been available since 10/11/2007. Latest one (SP2) can be found here (4/29/2009). Update/add "Admin" folder whether you have VL(K) or non-VL(K). It requires Office 2007 with SP2, but I have doubt about it.

@Salvadore:
Thanks for the above info, it is much appreciated. This would be very helpful to those with Retail/OEM copies of the suite.

[icemanzh]

Hi prathapml,
that is not the window i spoke about...
the one i mean is really the very last of the install, where you have the options to "Go online" or "Close" the install.

anyway, the MSP method works great, i was just wondering why the other one did not close silently....

Thanks
IcemanZH

[prathapml]

icemanzh, on Jun 25 2009, 09:49 PM, said:

that is not the window i spoke about...
The one i mean is really the very last of the install, where you have the options to "Go online" or "Close" the install.
Anyway, the MSP method works great, i was just wondering why the other one did not close silently....

You mean that when you use the CONFIG.XML method, there is a dialog box at the end of the install ? And this problem does not happen when you use the MSP method?
Now that is interesting, can you please post a screenshot of this dialog box?

[icemanzh]

Hi prathapml.
As i was told.... here is the shot from that very last Office2007 install window.
As CONFIG.XML, I used the code from MIDIBOY, Post #13

By the way, someone asked here if there would be possible to install silently o2k7 without the Key.
Well, I can't answer to that but I have a pair of recovery DVD's from some computers and maybe the answer is inside those, since near all pc's have now pre-installed office for 60 days

I'm far from being a geek but if I can help, just guide me through.

Thanks for this HOW TO.

IcemanZH

Attached File(s)

•  o2k7_last_screen.png (183.33K)
  Number of downloads: 20

This post has been edited by icemanzh: 26 June 2009 - 10:11 AM

[prathapml]

Hi icemanzh,
After seeing the screenshot posted above, I have a hunch that it is because of one of these. Are you sure you have all (and i mean ALL) of these options applied in the XML as mentioned in my first post in this thread? Quoted below, just to clarify what I mean. For any further details, please refer to my step-by-step description of both methods, in the first two posts of this thread.

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

Do post back to let me know what happens.

As for the 60-day pre-installed Office.... those are usually the result of special deals made between MS and the OEM (such as Dell, etc.). They probably install from a different installer disc, and actually use a certain key that allows for a 60-day trial.

This post has been edited by prathapml: 26 June 2009 - 10:18 AM

[icemanzh]

Hi again.
Yes, i do have that line and yes, it it just like that so the bug must come from somewhere else.

About the pre-install, I did already a couple of Recovery's and the Office is definitly in those disks.

How is it done, I don't know, but the source is the Recovery DVD so, all must be inside.

Cheers

IcemanZH

EDIT: Actualy, I did try with other codes, inclusive your's and they all result the same...
But the .MSP works like charm !!!

This post has been edited by icemanzh: 26 June 2009 - 10:25 AM

[Trigger911]

abhay, on Feb 20 2007, 02:53 AM, said:

HI

I have a bundle of office 2007 professional and Enterprise edition .
i want to install Enterprise edition through unattended installation. But after creating the MSP file also and running the command
setup.exe /adminfile filename.msp

the setup asks whether to continue with professional or Enterprise edition
office.JPG
can any body help me in this matter
thanks

[quote name='prathapml' date='Feb 21 2007, 07:15 PM' post='628490']
[quote name='abhay' post='627867' date='Feb 20 2007, 12:23 PM']I have a bundle of office 2007 professional and Enterprise edition .
i want to install Enterprise edition through unattended installation. But after creating the MSP file also and running the command
setup.exe /adminfile filename.msp


Thanks for this information I have been trying to build a network install and the place I work is a mess we still have access 2007 databases up (2007 hates them) but the installers I made kept coming up with the choose product, but I can’t wait to get to work to get this up and running. But the disc we got from MSDN has a lot more software bundled on it, but it’s pretty much every version. I just want the standard suite (Enterprise) to run but my main question that is left would you know what folders I should dump. Should I just delete all the folders with *.WW?


Thanks a ton in advance
Triggz out

[jkale]

alright so i have probably missed it but is there a way to make it so that i dont even have to press the install button so that it just automatically installs once i open up the setup.exe also i used option B and also after i get it to the point of just opening setup.exe can i then make it into an addon for windows xp to auto install while installing xp

This post has been edited by jkale: 25 November 2009 - 11:10 PM