for any app.... Import the product code into the msi tab of the package. If it is an application you have to do a simulated deployment or it will not work.
On Tue, Sep 8, 2015 at 11:59 AM, Bradley Milbauer <[email protected]> wrote: > 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 > > [image: http://ivision.com/signatures/email_sig_logo2.png] > <http://ivision.com/> > > > > *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.* > >
