[ms office - 2007] VERY URGENT - Can Someone Make Me An XML File For Deployment Or Help Please!

[pritchardavid]

Hey guys

 

 

Right quick question

 

 

Instead of making a xml for the install configuration (Looks confusing) for group policy deployment

 

 

Would it be possible instead to make a msi that launches the main exe which will get the install configuration for the MSP in the updates folder I have already made?

 

I will use admin studio to do this, anyone know if this will work?

And do anyone know how to make it launch the exe?

Edited January 14, 2010 by pritchardavid

[pritchardavid]

Actually that may be a bad idea

 

Means I would not be able to remove it using Group Policy, so lots of problems when we upgrade to 2010

 

 

 

Can someone do me a big favour and make me an xml?

Enterprise Version

 

Would be very grateful!

 

Settings I would like:

 

Full Features Everything

No Outlook

No Infopath

No Groove

No Visio Viewer

No New & Open Microsoft Document Shorcuts

No French & Spanish Proofing Tools

No Language Settings Tool

No Research Explorer Bar

No System Information

 

And don't remove older versions of office

[pete]

Try this instead:

To perform an administrative installation use the “setup.exe /admin” switch, which opens the Office Customization tool that the figure shows. If you receive an error that components are missing, check that you have the admin folder at the root of your media. Some versions don’t have this folder so administrative setup isn’t possible.

 

Once you’ve made your desired customization changes, save the setup file to a Windows Installer Patch (.msp) file. You then pass it to setup.exe by using this command:

 

setup.exe /adminfile nameof.msp.

 

The .msp way is simpler and GUI and all the settings you need are configurable.

[pritchardavid]

Problem is I dont want to have to use scripts after deploying, just want all the software to install from group policy

 

And doing it that way, mean I can remove office from the group policy, for when we upgrade to 2010

[garethEds]

Plahying Devil's advocate here but why not write your own?

 

I'm just about to start looking into it as well so maybe we could work together writing one.

 

Gareth

[pritchardavid]

Wouldnt really know how to write one, looks confussing

 

Had enghough problems with the windows 7 attendeded file

 

 

Why does Microsoft continue to make everything hard each newer release

 

Really dont want to put office 2003 on the newly deployed Windows 7 computers

 

 

If we can somehow help other that would be good

[mac_shinobi]

 

Why does Microsoft continue to make everything hard each newer release

 

As that would be too easy and logical

[pritchardavid]

ok think I have sorted this

 

Made one (Took me all day)

 

Seems to have deployed on the room im doing

 

Just got to check if It installed the updates too (Dont think it did was too quick)

 

Looks like I will need some help tomorrow from you guys

[pritchardavid]

Ok like I thought, didnt take long enghough to install, I checked the about screen in word and it didnt say SP2. So It didnt install the updates. Any Idea what wrong with my attended xml then?

 

 

 

 

 

 

 

 

//access

//outlook

//publisher

//access db Engine replication

//Clip Organizer

//SOAP toolkit

//new,open office docu lnks

//french

//spanish

//handwriting

//docu update util

//script editor

//scanning,ocr,indexing

//picture manager

//sharepoint support

//msQuery

//visio viewer

//infopath

CheckForSUpdates="Yes"

sUpdateLocation="\\server-7\Software Distribution$\Microsoft Office 2007\Updates"

/>

 

[Tricky_Dicky]

I can only spot a couple of things that seem odd:

Why are you displaying all the info when doing a large install and why aren't you accepting the EULA? Surely that means that you have to manually go round and accept it?

 

I think:

sUpdateLocation should be SUpdateLocation. Not sure if the capital makes a difference but it might.

 

Rich

[pritchardavid]

Woops, must of not changed that whyen I decided to use pro instead of enterprise and made a new xml

 

Right changed the settings including the captial letter you said, see if that makes a difference

 

Already deployed this to 6 computers and for some reason didnt have to accept the eula

[pritchardavid]

ok for some reason it just does not want to work now any ideas? Even put back the old xml, still does want to work (I did have to remake the policy this morning because It wouldnt add to it)

 

 

 

 

 

 

 

 

//access

//outlook

//publisher

//access db Engine replication

//Clip Organizer

//SOAP toolkit

//new,open office docu lnks

//french

//spanish

//handwriting

//docu update util

//script editor

//scanning,ocr,indexing

//picture manager

//sharepoint support

//msQuery

//visio viewer

//infopath

CheckForSUpdates="Yes"

SUpdateLocation="\\server-7\Software Distribution$\Microsoft Office 2007\Updates"

/>

 

[pritchardavid]

This is the error I keep getting when I try to readd it

 

"Add operation failed. Unable to extract deployment information from

the package. Please run validation on the package to ensure that the

package is correct."

[pritchardavid]

ok found what it was to do with, seems it was that captial 'S' that i changed from non captial in the update line

[Tricky_Dicky]

Would you mind posting up the final XML file that you used?

 

Rich

[pritchardavid]

I can do that Monday for you

 

But the problem with this file

 

Is for some reason it still does not install the updates

 

 

Im gonna make a new Windows 7 Image with Office 2007 installed on it with all the updates to stop this problem. Only problem doing that I the head of ICT still want office 2003 installed has well in her room, has 2007 is install already on the image, 2003 cant be installed because 2003 needs to be installed before 2007

[garethEds]

The MS docs for Office 2007 say that the config.xml method of installing the software will not install anything in the updates folder and users deploying in this way will have to rely on WSUS or scripts to get their updates out.

 

GJE

[Tricky_Dicky]

The MS docs for Office 2007 say that the config.xml method of installing the software will not install anything in the updates folder and users deploying in this way will have to rely on WSUS or scripts to get their updates out.

 

GJE

 

Really? I've been reading them today and they seemed to imply that's exactly why the folder was there.

You have to extract them first to to make them .msp and then it should pick them up.

[pritchardavid]

Teacher still wants 2003 in her room!

 

So In the end I made a user account called o7 (Short for office 2007) in the administrator folder in its own OU and other policys disabled in that folder, the made a group policy with a log in script to lanch office 2007 setup when it logs on has its lanched with the setup.exe it installs the updates from the folder.

 

Ok its another step we have to now do when we image a computer but it doesnt take long

[AngryTechnician]

The config.xml method will install the updates but NOT if used in conjunction with GPO deployment.

 

I just use WSUS instead along with all the Windows updates. Job done.

 

Teacher still wants 2003 in her room!

 

Does she have a reason beyond "can't be bothered to learn 2007"? If not, she should be sacked. Keeping your own skills up to date is part of your job. 2010 is out in the summer and it's not like they've abandoned the ribbon.