Jump to content

Recommended Posts

Posted

Hello,

 

I am looking to deploy Office 2010 by SCCM 2007. We have a mix of machine running Office 2007, Office 2007 and 2010 on the same machine, these machines have outlook 2007 not 2010. Some just have 2010 on manually installed, not our custom MSP - i would like these to be reinstalled.

 

Does anyone have a system or scripts that will remove all previous version of office and install 2010. I have setup an MSP for 2010 ready. One concern i will have is removing the old version with all the mix thats outs there, when i run commands to uninstall old software the deployment reporting back as failed if it isnt installed and becuase of the mixed version.

 

If anyone can help that would be good.

 

Thanks

Posted
Part of the options in the MSP are to allow removal of any previous version. Ive used this before successfully. It should do the trick for you.

 

It wont allow you to run the installer if Office 2010 is installed. So those machines with 2007 & 2010 wont fall into that scope. I cant just run an uninstaller as it will remove Outlook 2007 and leave no Outlook installed at all.

Posted

Have a batch script which will uninstall Office2010 but by using the start /wait command it waits until you finish the original command which would be the uninstall and then run the second command which would be the reinstall.

 

Example of batch.

 

start /wait msiexec -u office2010.msi <<<< This will hold the script until its finished its current task.

msiexec -x office2010.msi

 

Not sure what the uninstall switch is for msiexec.

 

Hope that makes sense..

 

Ross

Posted
Will this work with SCCM? When i deployed the AV i had a command to remove the old AV. If it wasnt installed the job would just fail. I dont want this to happen with Office
Posted (edited)

Hi guys, I am having trouble deploying this! (well kind of) It sayings its failed but its installed on the client machine!

 

I have setup a batch file to install office 2010. If i run the batch file manaually it works a treat. When i try to deploy it in SCCM i get this error:

 

The program for advertisement "FPH20036" failed ("FPH0000E" - "Install"). A failure exit code of 1 was returned.

User context: NT AUTHORITY\SYSTEM

 

Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 1 is considered a failure.

Solution: For more information on the exit code, refer to the documentation for the program you are distributing.

 

This is my batch file. It is set to remove any existing versions off office 2010 first. I am trying to install on a machine that doesnt have it installed.

 

cscript OffScrub10.vbs ALL,OSE

 

setup.exe /adminfile "Updates\FPHS-Config.MSP"

 

set ProgramFilesPath=%ProgramFiles%

"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"

C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /act

set ProgramFilesPath=%ProgramFiles(x86)%

"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"

C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office14\ospp.vbs" /act

 

Thanks

Edited by FN-GM
Posted

One snag I ran into, and knew I needed to set this way but can be lost in all the screens for configuration, is that if you don't state the package does not require the user to be logged on (default), while creating the program for the package in SCCCM, it won't populate when you go to create the install application task sequence (whats funny is we test for this condition but not if you actually checked the "can be called from a task box directly" but I chalk that up to learning :)

Hope this helps folks!

Posted

The only pain with SCCM is that you can't make the advertisement run before the user logs on i.e. like GPO software deployment. Problem then becomes...

 

a) our machines don't sit at a login screen long enough to deploy "when no user is logged on"

b) once a user is logged on they might be using Office when the advertisement is about to start

 

In the case of b) the upgrade seems to work OK even if a 2007 program is open (although if the user tries to save the document after a certain point it crashes). SCCM doesn't let you do custom message boxes either so not helpful there either. I did find a little notifier utility from Coretech but it's all hassle that should be built into the product. Don't think 2012 is any better in that respect as far as I know?

Posted
The only pain with SCCM is that you can't make the advertisement run before the user logs on i.e. like GPO software deployment. Problem then becomes...

 

a) our machines don't sit at a login screen long enough to deploy "when no user is logged on"

b) once a user is logged on they might be using Office when the advertisement is about to start

 

In the case of b) the upgrade seems to work OK even if a 2007 program is open (although if the user tries to save the document after a certain point it crashes). SCCM doesn't let you do custom message boxes either so not helpful there either. I did find a little notifier utility from Coretech but it's all hassle that should be built into the product. Don't think 2012 is any better in that respect as far as I know?

 

We dont have that issue. The software is installing fine but just repoting back to SCCM 2007 incorrectly

Posted
We dont have that issue. The software is installing fine but just repoting back to SCCM 2007 incorrectly

 

Out of interest what settings are you using for the Program (user logged on \ not logged on etc)

Posted
Out of interest what settings are you using for the Program (user logged on \ not logged on etc)

 

not logged on

  • 2 weeks later...
Posted

This is how I get office 2010 to deploy in SCCM:

 

run the office setup.exe with the "/admin" switch to create your MSP (I called it default.msp and placed in the "updates" folder within the Office Setup Dir..)

 

In the Setup section:

 

Install Location and Organisation name: [Org Name=YOUR_ORG_NAME_HERE]

Licencing and user interface: [Key as per required (KMS/MAK)] , Accept EULA, Display Level = NONE, suppress Modal, no Cancel]

 

Everything else as you need it - I'd leave "Remove previous installations" set to default so that it removes all previous Office installs

 

Save it and update your DP in SCCM

 

Now for the Program / Advert

 

for Programs the command line just needs to be "setup.exe" (as long as you have the "default.msp" file in your Updates folder it will automatically use this)

Environment tab should be - Whether or not a user is logged in and run with admin rights and run with a UNC Name - no other settings needed here

Windows Installer - import and find "ProPlus.WW\ProPlusWW.msi" (Not really needed but good practice if using MSI's)

Other tabs as you need

 

Add a DP and update/refresh

 

When refreshed - create your advert in the same way you normally would...

  • Thanks 1
Posted

Problem is users rebooting the PC halfway through setup, had that a few times even with the notification bar showing!

 

Also Office 2007 sometimes acts silly when uninstalling and needs the Fixit \ Offscrub tool to clean it completely...

Posted
Problem is users rebooting the PC halfway through setup, had that a few times even with the notification bar showing!

 

Also Office 2007 sometimes acts silly when uninstalling and needs the Fixit \ Offscrub tool to clean it completely...

 

This is why I had a pair of secateurs nearby for this.. they soon learnt not to :D

Posted

That I'm not too sure on - but suspect that since its using an MSP file and the /P switch (patch?), then it will probably fail if Office isn't installed.

It may be worth testing this though as it might work.

 

You could create a collection query via DCM and run the above only if Office 2010 is installed on the PC (Compliant) and run the full install if its not (Non-Compliant)

  • 2 months later...
Posted
That I'm not too sure on - but suspect that since its using an MSP file and the /P switch (patch?), then it will probably fail if Office isn't installed.

It may be worth testing this though as it might work.

 

You could create a collection query via DCM and run the above only if Office 2010 is installed on the PC (Compliant) and run the full install if its not (Non-Compliant)

 

Bringing this thread back from the dead a bit..

 

I setup my office install as listed 2 posts above, and I'm using it via UDI install. The office package will load, however, it doesn't send the "done" flag ever, so basically, it loads in 10-15 minutes, then sits waiting for the 40 minute timeout before proceeding completing the build. Then upon completion, I have an exclamation point on the Office installer. It does work properly, just takes longer. I've love to get this figured out... Not sure why it wouldn't be sending the "done" flag with success back to SCCM.

 

I'm building a machine right now with the package on it, I'll post up the details from the log, but the last time I saw it, it just said "package timed out" or something similar.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...