Deploying an MSP file

Hi,

I am trying to deploy a .msp file. I need to do this as we have migrated from on-Prem Exchange to O365 and we had used MS Office customisation tool in order to configure settings including automatically creating an outlook profile that points to the on-Prem exchange server. Now that we have migrated, it is causing issues with the outlook profile re-configuring.

Office is built into our MDT Image, so removing it from the office installation would be a giant PITA.

I have created a new OCT MSP file and when installing it manually it re-configures office and all works great. My problem is now deploying this file to all workstations. I have created a batch file with the below command.

msiexec.exe /p "\\sbpsfile01\School\School\Apps\Deploy\OfficeCustom\OfficeConfigRemove.MSP" REINSTALL=ALL REINSTALLMODE=omus /qn

I have also tried using DFS path.

The policy is applied under computer configuration and the computers are in the OU that the policy is in.

Any help would be much appreciated.

Thanks,
Warren
Warren PeartSupport EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mike TLeading EngineerCommented:
Hi Warren,

It looks fine to me but clearly it's not. You haven't actually said what is wrong though? Do you get an error message? Is there a log file? If not please add one with /L*vc:\windows\temp\Office.log at the end of the batch file.
The event log is also useful to check.

Mike
0
CoralonCommented:
I'm assuming you put this in as a Startup Script?  Is it a batch file/vbscript/powershell script?  It sounds to me like it is not running..

One other thing that occurs to me.. the GPO will run as the local system account, and it will not have access to a network share.  You may need to deploy the physical MSP file to the local system and then a script that will run that MSP file.

I.e:
A GPP that drops the file in a fixed location (like c:\temp)
Then a script that checks the registry and runs the MSP file.. something along this line:
if (test-path -path hklm:\Software\ConfigTest))
{
     #Do nothing
}
else
{
     if (test-path -path c:\temp\OfficeConfigRemove.MSP)
     {
          msiexec /p c:\temp\OfficeConfigRemove.msp REINSTALL=ALL REINSTALLMODE=omus /log /qn-
          new-item -path hklm:\software -name ConfigTest
     }
}

Open in new window



Coralon
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Warren PeartSupport EngineerAuthor Commented:
Hi Mike, Hi Coralon

I had tested it with the log parameter and the log file was not created. Nothing was showing in event viewer. Yes, it does feel like it isn't running at all.

I will try dropping the file onto the local system via GPP and then seeing if there is any difference.

Thanks,
Warren
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Vadim RappCommented:
Change /qn in the command line  to /qb, and run manually on the workstation.

Also, you can add to the command something like /l*v %temp%\mylog.txt and collect the logfile from there.

Note that you probably also want to patch the installation source, in order to avoid patching all future installations.
0
CoralonCommented:
Any luck yet Warren?  

Coralon
0
Warren PeartSupport EngineerAuthor Commented:
Hi Coralon,

I have actually been working on it today. It seems to be working now, but unfortunately the issue I was trying to fix still exists...

I took a bit of advise from yourself and mike.

I copied the file locally to the pc using GPP, then used the below script.

setlocal
 
reg query HKEY_CLASSES_ROOT\Installer\Patches\DC88D2DD20D960F4BA77A1F3D365E47D
if %errorlevel%==1 (goto Patches) else (goto End)
 
:Patches
start /wait msiexec.exe /update "C:\Temp\OfficeConfigRemove.MSP" REINSTALL=ALL REINSTALLMODE=omus /qn /l*v c:\Temp\OfficeCust.log
 
:End
 
Endlocal

Thanks,
Warren
0
CoralonCommented:
That's fantastic!   Glad to hear it is working out. :-)

Coralon
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Group Policy management

From novice to tech pro — start learning today.