Engineering has investigated this escalation and are declining the issue because this is a Microsoft issue. Xerox opened a case with Microsoft to investigate. Microsoft acknowledged the issue to be theirs and created a KB article. Within the KB there is a documented workaround. The workaround was tested and validated by Xerox development.
Microsoft notified Xerox a hotfix is being created to address the issue. Microsoft intends to incorporate the hotfix into an upcoming release. Please contact Microsoft support for an outlook. Please reference Xerox’s case number 116093014742830 as well as the KB article when contacting Microsoft support.
KB Link: https://support.microsoft.com/en-us/kb/3201130
@Fabio wrote:
Engineering has investigated this escalation and are declining the issue because this is a Microsoft issue. Xerox opened a case with Microsoft to investigate. Microsoft acknowledged the issue to be theirs and created a KB article. Within the KB there is a documented workaround. The workaround was tested and validated by Xerox development.
Microsoft notified Xerox a hotfix is being created to address the issue. Microsoft intends to incorporate the hotfix into an upcoming release. Please contact Microsoft support for an outlook. Please reference Xerox’s case number 116093014742830 as well as the KB article when contacting Microsoft support.
KB Link: https://support.microsoft.com/en-us/kb/3201130
Hi,
I alos confirm that, this workaround works. Thanks!