I have a lync 2010 infrastructure that works in a resource forest. this because we are still using Windows 2000 AD forest, while resource forest has AD forest 2003 with 3 DCs.
Suddenly pc out of our Domain with lync Client 2013 are having clock issue connecting to lync. I have seen that pdc in the resource forest is pointing to a NTP Server in our Company which is not responding, so the entire lync 2010 infrastructure in the reource forest has the clock running 10 minutes Forward. There is no Problem with users who are connecting with lync with the pc joined to the Company Domain.
Can someone tell me how to fix the clock inside the resource forest without breaking something?
I am not an AD Expert so I don't want to screw up everything. reading some articles I know that I can Change the pdc clock using Windows time command and then modify the clock on the other dcs to sync from the pdc, but what happens to the rest of my lync Servers if I do this?
As time skew issue is 5 minutes, will I be able to Login to the lync servers and fix the clock for my lync infrastructure?
Doing this will somehow affect my lync infrastructure?
Thanks