Video Screencast Help

Software installed to user's profile

Created: 17 Apr 2013 | 8 comments

Good Afternoon,

I'm fairly new to Altiris, and I'm having a bit of trouble creating a detection rule that looks for a program that installs to the user's profile.

Some of our users use Dropbox in Windows 7.  Dropbox installs to C:\Users\<username>\AppData\Roaming\Dropbox\.  I’m trying to create a detection rule, Static File Expression that starts in the AppDataFolder base folder with a File path of Roaming\Dropbox\bin\Dropbox.exe.  The detection fails, so I moved the Dropbox.exe to the Desktop to make the most simple path possible.  I used the base folder *Desktop and just had Dropbox.exe as the file path.  Again the rule fails to detect.

The descriptions on these base folders give examples that are XP profile paths like "C:\Documents and Settings\username\Application Data".  I was wondering if my rules are failing because they’re trying to look for Documents and Settings?  Is it possible to edit where these base folders point to confirm they're valid Windows 7 paths?  Any direction is much appriciated.


Operating Systems:

Comments 8 CommentsJump to latest comment

Clint's picture

I, too, am not sure how the Base Folder designation is implemented.  You'd think Symantec is using environment variables for the base folders to avoid any OS differences but you never know.

Not being aware of exactly how AppDataFolder will be translated in a rule, I'd try using StaticPath for the base folder along with an environment variable in the file path.  For example...


On Win7, %appdata% should get you to the Roaming folder although not sure whether this same file path will get you to DropBox.exe on a WinXP system.


AngelD's picture

In which (security/user) context are you executing the task/policy? Logged on user?

Clint's picture

Good question!  If Nick isn't running the task/policy under the context of the logged in user then the environment variables (whether it be via AppDataFolder or StaticPath) won't translate into the appropriate values.


Nick Albert's picture

Thanks everyone for such quick responses.  I am running the install from a policy as "Current logged-on user" with "Repeat this taks for each logged on user" checked.  I can verify a path with environment variables works by typing it in to the Windows Explorer address bar (like C:\Users\%username%\AppData\Roaming\Dropbox\bin\Dropbox.exe), but as a StaticPath in Altiris the rule doesn't detect the file.'s picture

Hi Nick,

For the detection rule, The best would be try the smart rule where you can assign the MSI code from the package which you use to deploy, That will eradicate all your probs.

Nick Albert's picture

The installer for Dropbox is a .exe, I tried finding a .msi from the developer but they don't have one.

Andrew_Shishkov's picture

Hi Nick,

If you are using EXE based installer, then try using File version standard detection rule together with user based environment variable. And make sure that you configured SW delivery task or policy to run under currently logged on user. User environment variable should return value for user under which installation is launched.



AngelD's picture

If the Detection rule doesn't support to run under the logged-on user then you may need to create a custom inventory and then base your targets to the inventory result.