F
Frank
Hello All -
So the calendar entry is created on Monday at 9AM with two attendees who
accepted. Then it is moved to the next day, Tuesday at 12PM and individual
who set up new time did a Send Update and not a Save and Close. All clients
accepted the new time however on one user, the appointment still remains at
the old time - Monday- and never actually moved to the new time even though
client accepted it. What gives??
Also if if matters, the client affected also has Source LSASRV entry in the
Event Viewer,something about not being able to "established a secured
connection with" one of the "ldap" servers which could be one of the DCs.
This messages do appear on the same say the Outlook calendar issue occurred.
It appears every one did what they're supposed when a meeting is moved to
new time and everyone accepts.
Any insights certainly appreciated.
Thanks in advance
So the calendar entry is created on Monday at 9AM with two attendees who
accepted. Then it is moved to the next day, Tuesday at 12PM and individual
who set up new time did a Send Update and not a Save and Close. All clients
accepted the new time however on one user, the appointment still remains at
the old time - Monday- and never actually moved to the new time even though
client accepted it. What gives??
Also if if matters, the client affected also has Source LSASRV entry in the
Event Viewer,something about not being able to "established a secured
connection with" one of the "ldap" servers which could be one of the DCs.
This messages do appear on the same say the Outlook calendar issue occurred.
It appears every one did what they're supposed when a meeting is moved to
new time and everyone accepts.
Any insights certainly appreciated.
Thanks in advance