Video Screencast Help

Software Portal - Windows 7

Created: 08 Aug 2014 • Updated: 11 Aug 2014 | 4 comments
This issue has been solved. See solution.

Hi all, I am experiencing an issue deploying the Software Portal to Windows 7 machines, here is the scenario: 

We disable the agent in the tray by default, and we are looking to start using Software Portal, so I am looking into the best way to "deploy" it. 

I turned on the "Software Portal Plug-in Policy" policy, and targetted my lab, which consists of windows xp and windows 7 machines (to mimic our environment). 

Once the agents got the policy, I saw the links (shortcuts) on the desktop and in the start menu, as I specified in the policy settings. However, when I launch the shortcut on windows 7 machines, nothing happens (the browser doesn't launch), while on my winxp machines, it launches correctly. So then I checked the targets in the shortcuts, and they are different: 

Windows XP: C:\WINDOWS\system32\rundll32.exe C:\PROGRA~1\Altiris\ALTIRI~1\Agents\SOFTWA~2\SOFTWA~1.DLL,ShowSoftwarePortal

Windows 7: C:\Windows\System32\rundll32.exe C:\PROGRA~1\Altiris\Altiris Agent\Agents\Software Management Solution Plugin\SoftwareManagementSolution_Agent.dll,ShowSoftwarePortal

I noticed that this causes the Windows 7 path to have spaces in it, which usually requires quotes. I added the quotes and it worked. I cannot be the only one experiencing this, so it might be something that Symantec should look into? Or is it just me? Anyone? 

Operating Systems:

Comments 4 CommentsJump to latest comment

richietheprogrammer's picture

Well got on a call with Support, and I guess it's a known issue that is fixed in 7.5 SP1. I guess the engineers never tested the Windows 7 version of the policy, somebody probably got in trouble for that :) 

Dmitri Dragunov's picture

Hi richietheprogrammer,

Please be sure that this is a known issue. The issue connected with removing the short names from files by Fsutil 8dot3name utility. 


richietheprogrammer's picture

Thanks Dimitri. I was told this was fixed in SP1, is that correct? 

Dmitri Dragunov's picture


We are working on a more permanent solution that we hope to include in a hot fix for 7.5 SP1. 

Currently we have a workaround: 

You should taking the Portal link file from a working system and copying it to the affected systems. You may need to grab it from your test server. Any working file should work as long as you didn't have a custom Agent install path.