Replies: 1 comment
-
|
This is a good suggestion, @SlyInH3ll. Would it meet your requirements if I replaced the user's profile with %userprofile% and tied it to this setting in the Wizard? When this setting is checked the following FriendlyName would be replaced with: FriendlyName="C:\Users\jordan\AppData\Local*" would be replaced with: FriendlyName="C:%userprofile%\AppData\Local*" |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
When creating a file name based rule, you get the option to edit the path to use wildcards, etc. When creating a file hash, the file's full path is grabbed without the option to edit. and when the file is from the user's profile structure, it can't be deployed like that on several computers, the XML need to be edited, to correct the FriendlyName and remove the path, keeping only the file name. This behaviour prompt unwanted manual interventions prone to introduce errors in the policy. It would be nice to have an option to edit file name/ file path before creating the rule, cleaning it from the start.
Beta Was this translation helpful? Give feedback.
All reactions