Microsoft
MicrosoftNice to see work still being put into GPP!
I have a question: We are now seeing the Event ID 4117 warnings ("File error occurred when copying...") for GPP "Create" Files preferences where the file already exists in the destination. Is using Create like this this not an expected use case / result? We don't ACTUALLY want to use the "Apply Once and Do Not Re-Apply" flag on these preferences, since we would want the file to get re-copied if a user accidentally or intentionally deleted it, and we are not using Replace because we want users to have the ability to change it (most of these are "default" or starting config for programs) without those changes getting overwritten. I suppose to avoid this warning we could Item-Level Target the Create preference to only run with a file rule that the file doesn't already exist in the destination, but that is extra work to set up and potentially adds more processing time.
MicrosoftThank you Mike!
Interesting point. We will check whether there are any plans to suppress or mask non‑error messages in the future. However, I doubt that we can reliably decide what should be considered a true‑positive message (for example, a file that already existed before the GPP was applied for the first time) versus a false‑positive.
I'm not sure I understand. A Create action for the Files module shouldn't even be TRYING to replace or update the file if it already exists, correct? There is no gray area there or false/true positive potential. Alternatively, if the file does not already exist in the destination and Create tries to copy it but fails for any reason, that would by definition be a true-positive. It sounds like the GPP event logging is just not taking into account whether the destination file existed to begin with.
