We have been testing the update from v10.2 M020 to v10.2 M030 on a cloned and rehosted copy of our production system, and have one last problem to solve with WinDU. Before the update, WinDU reports no errors or warnings but after the update it reports a block of PrincipalValidator warnings, like the ones described in CS125299 and CS186012.
We have loaded the latest patch set M030-CPS09 but that does not fix the problem, so the statement in CS186012 that the problem was corrected in M030-CPS04 appears false. We have been in discussion with our VAR and have had a support call open with PTC for 3 weeks. I gather that other customers have the same or similar problems with M030 WinDU.
PTC have just declared a Critical Bulletin for CS 222868 and recommend an urgent update to M020-CPS17 or to M030-CPS09, which would be preferable to avoid our users from having to update their WGM installation and discard all their local cache folders twice. https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS222868
Unfortunately PTC seem to be equally reluctant to solve the remaining problem with WinDU, which appears to be due to a change in how WinDU in v10.2 M030 checks the validity of Users & Groups in ADS, in particular the way it uses the binding user account credentials and/or the JNDI adapter url.
Has anyone else had this problem, and found the solution ?
Thanks in anticipation...
Nick