Skip to content
Discussion options

You must be logged in to vote

Hi,
Yes, it is a normal behavior.

%userprofile% is not a valid macro, only the following macros are supported by the App Control engine in the OS: %OSDRIVE%, %WINDIR%, %SYSTEM32%. The reason is that an App Control policies applies to the entire system, not user accounts, so if there are more than 1 user accounts, %userprofile% wouldn't be solvable. All of them are only used by File path scan levels/rules.

When you use Publisher scan level, if a file or log is unsigned, hash rules are automatically created instead (I can provide more customization options for this area if needed). FilePublisher, Publisher or Hash levels don't rely on file paths, so yes, your policy will work on other machi…

Replies: 1 comment 14 replies

Comment options

You must be logged in to vote
14 replies
@HotCakeX
Comment options

@krunph
Comment options

@HotCakeX
Comment options

@krunph
Comment options

@HotCakeX
Comment options

Answer selected by krunph
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants