In addition, the system update loader module logging can be controlled by modifying the SystemUpdate.xml file in the conf/loader directory. The different levels of logging are OFF, SEVERE, WARNING, INFO, FINE, FINER, FINEST
Ok, finally we did it.
The thing is that described in this article that you tell me https://support.microsoft.com/en-us/kb/980794 is what it has to be, but we did not apply the asked hotfix first… we only make the Registry change, and it does not work if your system does not have the hotfix applied. This hotfix is installed in Service Pack, but we didn’t have it installed.
So, install hotfix (reboot is required) and change Registry (no reboot needed) and voilá! It worked!
In Windows Server 2012, it works as well if you follow my 7 post steps.
So we can say that finally we managed to handle with VSS of all scenarios.
Thank you all!!!
DisableGPCalculation, to avoid the GPO recalculation during the re-connections and give the user the best possible experience:
Note: For the first time this registry key was intrudced to XenApp 6.5 Hotfix Rollup Pack 2 (http://support.citrix.com/article/CTX136248) . Since then, it has been added to all the Hotfix Rollup Packs, for XA 6, 6.5 and in the XA/XD 7.X.
Is there any other way on doing the policy trace.
It would be nice to have a page put in some parameters like the destination IP address / URL then run it against the policy, tool would show you the policies that it hit. Is there such a tool somewhere?
Honestly the policy trace tool is not efficient , going through the policy trace log is not that efficient as well.