Imitkov17
Contributor
Contributor

Environment Variables are set after UEM processes it's conditions

Hi,

I have two environments:

     1. Horizon 6.2.1 with UEM 9.0.0.156 and App Volumes 2.11.0.122

     2. Horizon 7.1 with UEM 9.2 and App Volumes 2.12.1.103

I am migrating from environment #1 to environment #2. I have an existing Windows 7 golden image that I cloned and updated with the latest View, UEM and App Volumes agents. I also migrated the existing UEM config. There are some conditions and condition sets that are looking for the ViewClient_Machine_Name variable to map printers, map drives etc. Everything is working fine in the old 6.2 environment but in the new 7.1 environment the Environment Variables are set after UEM processes it's conditions. In the log files I see many of the following lines right after logon:

2017-06-12 14:46:54.925 [DEBUG] Conditions: Check for environment variable 'ViewClient_Machine_Name' = false (variable not set)

If I execute "UEM User Environment Refresh" after logon - all printers and drives are mapped correctly.

Then in the logs I see the following  lines:

2017-06-12 14:07:41.666 [DEBUG] Conditions: Check for environment variable 'ViewClient_Machine_Name' = false ('ZC-0030' is not equal to 'ZC-0011')

Which is the expected behavior.

Also I have a shortcut that is added to the startup folder. The application starts automatically in environment #1. In environment #2 the application is added to the startup folder but it doesn't start automatically.

Any help will be greatly appreciated.