Workaround: Reboot VTrak Windows client before the second Windows AD user start to use it.

This issue will be addressed in SR2 release.