SSGIT

I was hoping to avoid removal using the product code as the new install has the same product code. I can try reverting back, though...

Hi Jörgen, thanks for the reply! I've checked the appdiscovery.log file and it actually *does* detect the previous installation. <![LOG[ ActionType - Uninstall will use Content Id: Content_c812fa32-ad88-4d85-b6e2-4ab7dbbf18c9 + Content Version: 1 for AppDT "Checkpoint Tools for PPC - 2.2.20" [scopeId_9EA1F6D7-1D7B-4ED9-A402-AAE8DD39A13C/DeploymentType_c9c1ff61-738c-45c0-8a1e-825a1832cec5], Revision - 9]LOG]!><time="19:21:48.734+300" date="03-04-2014" component="AppDiscovery" context="" type="1" thread="3540" file="appprovider.cpp:1486"> <![LOG[ ActionType - Install will use Content Id: Content_be4e7066-16e6-45a2-b5a9-71b66fa544b2 + Content Version: 1 for AppDT "Checkpoint Tools for PPC - 2.3.21" [scopeId_9EA1F6D7-1D7B-4ED9-A402-AAE8DD39A13C/DeploymentType_3f82c6a8-eb81-4401-8e39-00b4eea427ef], Revision - 12]LOG]!><time="19:21:49.389+300" date="03-04-2014" component="AppDiscovery" context="" type="1" thread="3540" file="appprovider.cpp:1486">

Does anyone else distribute applications where an uninstall of the previous version is required for the new version to be installed? We have a couple of these products. Unfortunately, this software isn't designed that well. Each update uses the same MSI (so same unique installer code), but they change the content. Their EXE installer manually uninstalls the old and installs the new. I found a reg key that changes with each install, so I'm using that as my detection method. Which seemingly works, because if I deploy to a collection and a couple of the PCs had the update already, they show as "already compliant." I'm trying to set up supercedence to uninstall the old deployment type and install the new, but it doesn't want to work. When I deploy, I check the event log; the MSI transaction begins the install procedure and fails. Assuming this because I never see the uninstall action start in the log(s). Anyone have a similar issue and, if so, how did you get around it?

*bump*

Hi there! We have an SCCM 2012 SP1 environment and we've used it, in most cases, very successfully. However, on our of our latest application deployments, we're receiving back "Waiting for maintenance window" messages even though the application is Required, set to ASAP and the option to allow software installation outside of maintenance windows once the deadline has passed is checked.. We have a maintenance window set up for windows updates device collection(of which all of our windows 7 PCs are a member). All of these PCs are W7 PCs and are all members of the same device collections. I have 28 successful installs and 4 in the "Waiting for maintenance window" status, so it's clearly working for some of them... Any thoughts as to what the holdup could be? Thanks in advance! ~M

If this is not the correct location for this post, apologies. You can move this thread to the appropriate area if needed. Anyhow; Hi there! We've an SCCM 2012 environment and we're in the process of transitioning over from GPO-based MSI installs to Applications (Not packages/programs). I've hit a speed bump of sorts. We have an application (workstation setup for a network application) that installs from \\server\share\app\netsetup\. There's an MSI in the netsetup folder which calls an EXE among other items. The MSI *needs* to be run from this location or else environment variables will be off. For instance, I couldn't copy the netsetup folder to my desktop and run it that way. As such, I can't use DPs to house content as I could with other applications (such as Acrobat, Office, etc). I know there's a trick to use packages/programs, but I was really hoping to utilize an Applications as that's where SCCM is really going in the future. So, is there a way to create an application in SCCM to run this MSI directly from the server versus a DP? Any info you could offer would be great, thanks!