DynamicIT
asked on
Contacts have adopted a new last name
Hi Team.
We have a stable SBS2011 installation with 5 users utilising Exchange 2010, Outlook 2013, and recent model iPhones. Several days ago one of the users (of course it was the company owner!) reported that his iphone was not recieving new emails but his iPad was. I suggested re-entering his email password on his iphone as a reboot had not worked. This got the iPhone working again but a fault has been discovered.
Contacts that previously had only the users first name in the First Name field have adopted the Last Name of the next Contact. For example there was a Barbara and a Barbara Smith. The first Barbara now has Smith as a Last Name. Barbara Smith's email address is now appearing in Barbara's contact in the Email2 Field.
My google-fu may be letting me down, but I cannot see any more references to this happening, and therefore have no insight from others as to how this might have occurred and how it might be prevented in future. This user has 3 different Windows computers he uses running Outlook 2013, but they don't seem to have contributed to this.
Thanks in advance for any thoughts/suggestions.
Mike
We have a stable SBS2011 installation with 5 users utilising Exchange 2010, Outlook 2013, and recent model iPhones. Several days ago one of the users (of course it was the company owner!) reported that his iphone was not recieving new emails but his iPad was. I suggested re-entering his email password on his iphone as a reboot had not worked. This got the iPhone working again but a fault has been discovered.
Contacts that previously had only the users first name in the First Name field have adopted the Last Name of the next Contact. For example there was a Barbara and a Barbara Smith. The first Barbara now has Smith as a Last Name. Barbara Smith's email address is now appearing in Barbara's contact in the Email2 Field.
My google-fu may be letting me down, but I cannot see any more references to this happening, and therefore have no insight from others as to how this might have occurred and how it might be prevented in future. This user has 3 different Windows computers he uses running Outlook 2013, but they don't seem to have contributed to this.
Thanks in advance for any thoughts/suggestions.
Mike
Gareth Gudger
Are all his devices now showing this corruption? Including Outlook Web App? Or just the iPhone?
ASKER
I've restored a copy of their server from a backup taken a week ago and am looking at the Contacts on the restored server and the changed Contacts on the live server using Webmail. Because the changes display in Webmail I assume this has replicated to other devices. I have just done a check and the changes have replicated to his primary office computer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Won't fix it, but will give you some info:
1.Log into a/the DC
2.Open a cmd prompt
3.Run this command:
ldifde -l proxyAddresses,objectClass
Now you have a dump from AD of all email addresses in emaillist.txt from which to work. By including the "objectClass" the output will include whether the AD object is a real mailbox ("objectClass: user"), public folder ("objectClass: publicFolder"), or distribution group ("objectClass: group").
http://www.puryear-it.com/blog/2012/10/11/list-all-email-addresses-for-exchange/
1.Log into a/the DC
2.Open a cmd prompt
3.Run this command:
ldifde -l proxyAddresses,objectClass
Now you have a dump from AD of all email addresses in emaillist.txt from which to work. By including the "objectClass" the output will include whether the AD object is a real mailbox ("objectClass: user"), public folder ("objectClass: publicFolder"), or distribution group ("objectClass: group").
http://www.puryear-it.com/blog/2012/10/11/list-all-email-addresses-for-exchange/
ASKER
Contacts folder was restored by booting the week old backup of the server as I was unable to find a simpler solution to roll that facility back in time.
Thanks for your input, Team. Hopefully just a weird one-off issue.
Thanks for your input, Team. Hopefully just a weird one-off issue.