Adding Shortcut via GP - Program Files vs Program Files (x86)

Question

So I have a 32 bit MSI package that installs in Program Files on 32 bit machines and Program Files (x86) on 64 bit machines.

I am attempting to add a shortcut to this app via GP, but I'm not sure how to handle the discrepancy in the path. %PROGRAMFILES% works on the 32 bit machine, but I need to use %PROGRAMFILES(X86)% for it to work on the 64b machines.

Is there a environment variable that I can use, or how is this handled?

Are you using Preferences or a script to create the shortcut via Group Policy? — jscott, Oct 11 '11 at 15:49

score 3 · Accepted Answer · answered Oct 11 '11 at 15:49

3

You could use a WMI filter in your group policy to select 32-bit OS to use one shortcut and 64-bit to use another.

answered Oct 11 '11 at 15:49

uSlackr

6,337
21
36

So create a separate policy for each? – jeremib Oct 11 '11 at 15:54
That's correct. You would need two policies – uSlackr Oct 11 '11 at 16:57

score 0 · Answer 2 · answered Oct 11 '11 at 15:51

0

You should be able to check the value of %PROCESSOR_ARCHITECTURE% and make the decision based on that value.

answered Oct 11 '11 at 15:51

squillman

37,618
10
90
145

score 0 · Answer 3 · answered Oct 19 '11 at 06:28

My solution was to create an environment variable on every workstation, %PROGRAMFILES32%, that maps to either Program Files or Program Files (x86) as required. (I also created links to system32/syswow64 for the same reason.) As you've seen, there's no built in way to fix it. Alternately, since you need it primarily for one app, you could have the installer or a post-installation step add an environment var pointing directly to it.

I did it through Novell Zenworks, but you could just as easily create it through a group policy startup script.

Adding Shortcut via GP - Program Files vs Program Files (x86)

3 Answers3