I see that with Windows Installer based apps as well. So, I think the question here is: What is the best way to allow users to "repair" an application that is installed via OSD? My thought is to use the application model and provide an uninstall command. Then apps can be removed and reinstalled. Anyone else have a way they manage this? Jeff Date: Tue, 8 Sep 2015 12:22:41 -0500 Subject: Re: [mssms] RE: SCCM 2012 R2 w. Nomad: MSI InstallSource invalid after OSD From: [email protected] To: [email protected]
all my windows installer based apps do that. On Tue, Sep 8, 2015 at 12:09 PM, Daniel Ratliff <[email protected]> wrote: I don’t think Nomad is doing anything special there. My machine I am on was built with OSDand Nomad and the Install Sources are all C:\_smstasksequence. An example below. C:\_SMSTaskSequence\NomadBranch\CAS00806_Cache\ I checked a package in our image (not using Nomad) and the Install Source still points to c:\_smstasksequence. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Bradley Milbauer Sent: Tuesday, September 08, 2015 12:59 PM To: [email protected] Subject: [mssms] SCCM 2012 R2 w. Nomad: MSI InstallSource invalid after OSD Hi All, I’m working in an SCCM 2012 R2 environment with Nomad integration, and I’ve run into the following problem after imaging PCs: The MSI InstallSource registry key in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\... is set to C:\_SMSTaskSequence\NomadBranch\<PackageID>\... , which is an invalid path after OSD completes. The package/applications all install just fine, but later on, if the user attempts to perform a repair install on their applications, they will receive an error stating the path to the MSI is unavailable because InstallSource refers to a path that no longer exists. I’m brand new to this environment and have no prior experience with Nomad. Any help would be greatly appreciated. Thanks, Bradley Milbauer Consultant Client Engagement Value: I am empowered to go the extra mile for my coworkers & clients ivision.com CONFIDENTIALITY STATEMENT: This email message, including any attachments, is for the sole use of the intended recipient(s) and may include privileged or otherwise confidential information. Any unauthorized review, forwarding, printing, copying, use, disclosure or distribution is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
