Jump to content

Recommended Posts

Posted

We've done an RM deployment of office 2010, using the OCT kit to create an MSP file, we now need to do the same again on a vanilla network, but still using the customizations within the MSP. Obviously I can't deploy an MSP as it's just a file with a load of differences in it, I've read that what I need to do is merge the MSP with the original MSI to create an updated MSI containing the MSP customizations, the problem is office does not come with an MSI it comes with a setup.exe...

 

'Elp.

Posted
setlocal

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\excel"
if NOT %errorlevel%==1 (goto end)
"\\gateway\packages$\Office2010\x86\setup.exe" /adminfile "\\gateway\packages$\Office2010\x86\nooutlook.MSP"

:End

  • Thanks 1
Posted

Office 2010 was the product that led me down the route of System Center Essentials, which I then canned in favour of the free Local Update Publisher, which lets you install almost anything using your existing WSUS server.

 

Once you have it configured, you will be able to install pretty much anything you used to install using RM Package Manager. Once you've converted, you will never look back: I now do literally all my software installations using LUP, with nothing done via Group Policy any more. It's that good.

  • Thanks 1
Posted

Thankyou very much for everyone's input.

 

Honestly M$, if you create a product for installing software remotely, why in the name of do you not make all of your products compatible with it?

 

I've just forwarded that script to the guy who is doing the stuff and he is now much happier than he left yesterday!

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...