Hi All,

 

I was looking for some assistance if possible.  I am creating an MSI that installs a "non advertised" shortcut onto a users Win7 x64 Pro desktop.  The shortcut calls a file that is located on a network path and when run, will spawn a virtualised version of Reflection to run.  We are looking to deply this shortcut via SCCM.

 

However when testing the deployment I notice that the file extension loses a letter (i.e. a .abcd file extension then becomes .abc).  This happens even if run the MSI locally.

 

The Target of the shortcut should be the following:

(DriveLetter\Folder1\Folder2\File.RDOX) - RDOX being a Reflection file extension

What i am seeing is:

(DriveLetter\Folder1\Folder2\File.RDO)

 

Any help you may be able to put forward would be gratefully recveived.

 

Cheers

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

Hi Jagadeish,

Thanks for the feedback.

I have since managed to resolve the issue.

Firstly I needed to make sure that the Property in the "Target" column of the shortcut table didn't have [ or ].

Then becuase the installer or system account that SCCM uses to install apps remotely didn't have any drive mappings associated with it, in a sense it can't find the file and as such it's file extension.  Therefore I essentially fooled SCCM by telling the relvant program that installs the app that it needs a drive letter (R for example).  This then installed remotely with no issues and the full file extension was there.

Answered 06/26/2013 by: Hillsmeister
Senior White Belt

Please log in to comment
0

Create a public property named SHORTCUTPATH and keep DriveLetter\Folder1\Folder2\File.RDOX as it's value

and

Create a command line shortcut and ensure that the "Target" column of the Shortcut table entry has [SHORTCUTPATH] as it's value..

Answered 06/07/2013 by: jagadeish
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity