Solved

group policy upgrade package gone wrong

Posted on 2014-01-22
3
274 Views
Last Modified: 2014-01-30
Dear Experts,

We’ve made a mistake and need your help/advice!

One of our applications is deployed via Group Policy. The original version is 3.0.
We decided to put a more uptodate version (3.1) but we’ve not done it correctly. We just replaced the msi package with the new one rather than ‘upgrading’ it.
Now the application is not displaying in the taskbar and errors in the event log Event ID 0 - service cannot be started. We tried using the 'Redeploy application' in group policy but not much luck.

Any ideas?
0
Comment
Question by:Bladey001
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 40

Expert Comment

by:Vadim Rapp
ID: 39802152
So you did not change anything in the group policy element, but simply replaced the MSI package in the place from where it was published. Right?

But what happened then? Did the workstations install this replaced version? What is installed on them now? Is the installation published or assigned?

Also: what about the MSI installation package itself? Is the version 3.1 an upgrade to version 3.0?
0
 
LVL 37

Accepted Solution

by:
Mahesh earned 500 total points
ID: 39802169
You could try with deploying old package 1st and then upgrade old package with new one and check if it works

Mahesh
0
 

Author Closing Comment

by:Bladey001
ID: 39820884
Thanks. This worked.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

OfficeMate Freezes on login or does not load after login credentials are input.
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question