(imported topic written by Steve91)
Hi Chaps,
I’m deploying some new wallpaper & a screensaver to a particular group of users in our company.
I’m targeting them by their login id as we don’t have a list of their machine names i.e. (exists current user whose (name of it as lowercase = “sgreu6” OR name of it as lowercase = “whigh4” OR etc…and I’ll be running this as a policy (it also incorporates relevance to exclude them if they already have the correct wallpaper/screensaver)
As part of the action i’ll provide the users with a message… “blah, blah, if you are not part of this business area click ‘Cancel’ to reject the update”
This all works fine and the action cancels but when the user restarts their PC or logs off and back on it sends the action to them again.
I was hoping there may be a way to create a flag file locally on the machine if the user selects to cancel the action? Basically, perform an action upon cancellation of the main action.
I could then incorporate this in my relevance i.e:
not exists file “newbrand.flg” of system folder AND (exists current user whose (name of it as lowercase = “sgreu6” OR name of it as lowercase = “whigh4” OR etc…
Anyone know if this is possible?
Thanks
Steve