Solved

SCCM - cache folder missing .msi required for un-install of previous version of a piece of software

Posted on 2015-02-10
3
349 Views
Last Modified: 2015-02-12
Hi, I've encountered a weird issue with a recent deployment, one of our remote sites to which an application deployed, had an ,msi stripped out of the cache folder, this .msi was required to un-install the previous version of the application, SCCM install on client would fail as the previous version of the software would not un-install because it couldn't find the missing msi in it's SCCM cache folder, about +20 users out of a total of around 50 users in that office affected by this problem, I got around this by manually placing the missing msi into the required cache folder, time consuming to say the least, any ideas what could have caused this, how do I get around this issue should it happen again?
0
Comment
Question by:craigleenz
3 Comments
 
LVL 22

Assisted Solution

by:Adam Leinss
Adam Leinss earned 100 total points
ID: 40601553
That's pretty common actually.  The MSI install source should be in the registry...you should be able to point it to a central folder location through a registry hack.  Or as part of your new package just bundle the MSI file?
0
 
LVL 17

Accepted Solution

by:
Mike T earned 400 total points
ID: 40602929
Hi,

One thing you need to make sure you do is that all applications have the MSI product code added so that CM can manage it. By default when you create an application and go through the wizard Microsoft do everything for you except that bit.

To check open Deployment Types, click Edit and on the Programs tab, check the Program Code field. If it's empty CM will not actively manage the MSI source (i.e. point the machine to it's own copy). The feature is controlled by the "Windows Installer Source List Update Cycle" in the client actions.

If you don't enable the feature or make a point of adding the product codes you will see the "where's my MSI gone, I can't repair" issue, especially if you built the machine with OSD as the source path will be C:\_SMStask-sequence which gets deleted, orphaning the apps.

There are scripts out there that you can use to redirect the installer path to elsewhere as a workaround.

Mike
0
 

Author Closing Comment

by:craigleenz
ID: 40606749
thanks Mike T,
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Lync meeting or Lync conferencing is what many organizations would like to deploy to allow them save money. But companies are now giving up for various reasons, one of which is that they cannot join external meetings (non-federated company meetings)…
The new Microsoft OS looks great, is easier than ever to upgrade to, it is even free.  So what's the catch?  If you don't change the privacy settings, Microsoft will, in accordance with the (EULA) you clicked okay to without reading, collect all the…
Viewers will learn how to maximize accessibility options in an Excel workbook for users with accessibility issues.
The view will learn how to download and install SIMTOOLS and FORMLIST into Excel, how to use SIMTOOLS to generate a Monte Carlo simulation of 30 sales calls, and how to calculate the conditional probability based on the results of the Monte Carlo …

911 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

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now