We are currently seeing an issue whereby an environment variable set in 'Logon' trigger is not expanded in a later node. We set a PFILES86 variable depending on the device architecture. This is set in 'Logon', Environment.
A shortcut deployed to the users desktop uses this variable in the target path, this is set to occur after explorer.exe starts.
Intermittently, the shortcut can be created as:
When checking the users environment variables on the device, we can see that the PFILES86 variable is set correctly.
I am trying to understand if what is being experience is a result of a race condition. i.e. PFILES86 being set after the shortcut is created. The reason for this thinking is that this is intermittent. It may be created correctly one day, but the next it will not.
What is the different between setting an Environment variable in 'Logon', Environment, as opposed to setting the variables in a node / node group within the 'Logon' trigger in terms of time of processing?
Could we assume that the Environment variables are the first thing above all other actions which occurs?
I understand that AppSense should "pause" the Logon until all Logon actions are completed, is it at all possible that these actions could over run?
We are using AppSense Environment Manager 8.3 & Agent 8 FR3 (Build 267)