Re: Issue with mailbox move
- From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxx>
- Date: Sun, 26 Oct 2008 08:59:10 -0700
I tested in my lab with a quote and got the same result. I asked about this issue and I did get a clarification, that the simple display name is a representation of the PrintableString data type in RFC 2252 (http://www.ietf.org/rfc/rfc2252.txt), and prior to Exchange 2007 validity checking wasn't performed as strictly, so quotes and commas were allowed in. However, I see from that RFC that commas are valid, but I hadn't tested with a comma and I had shut my lab down. I'll test with a comma, and if it fails also, I'll post the follow-up question about whether the type checking isn't inconsistent with RFC 2252.
Still, it's by design and not well documented, agreed.
Do you (John) use the simple display name any more? Is there any reason to not just blank it out?
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..
"Missy Koslosky" <missy@xxxxxxxxxxxxxxxxxx> wrote in message news:upfyyMzNJHA.3640@xxxxxxxxxxxxxxxxxxxxxxx
I can't find anything either. I'm surprised nobody has run across this before - I think it'd be worth a call to MSFT support. :(
Missy
"Ed Crowley [MVP]" <curspice@xxxxxxxxxx> wrote in message news:%23lfwO5jNJHA.4928@xxxxxxxxxxxxxxxxxxxxxxxI don't disagree that if it's documented, it's well hidden. I can't find anything on it either.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.
"John Beck" <JohnBeck@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7AC37729-42D8-4208-9BAF-B6261411B2E0@xxxxxxxxxxxxxxxxI understand what the error says but I could not find anything in technet or
anywhere else about this limitation and that was my concern. Do we have to
learn things though trial and error or should we read on things first on
technet which may save all of us some valuable time.
"Ed Crowley [MVP]" wrote:
It's certainly documented in the error message you get if you try to add a
simple display name with those characters.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..
"John Beck" <JohnBeck@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F5156124-E95F-46C4-A5CE-9E8847FC9695@xxxxxxxxxxxxxxxx
> Hello,
>
> I have a mixed environment 2003 and 2007. I have started moving users > from
> 2003 to 2007 and verything is fine so far. However, I came across an > issue
> with the simple disaply name attribute. If a user in exchange 2003 > has an
> apostophe in the simple disaplay name like for instance "o'brien, > john" or
> "O'Rourke, Jim" the mailbox move will error out and stop the move. > Further
> more, if you try to create a mailbox enabled user in Exchange 2007 > and
> assign
> a simple display name with an apostrophe, it will error out. Is any > one
> aware
> of this limitation? Is this documented anywhere or is it one of those
> undocumented features microsoft graces us with from time to time?
.
- Follow-Ups:
- Re: Issue with mailbox move
- From: Ed Crowley [MVP]
- Re: Issue with mailbox move
- References:
- Issue with mailbox move
- From: John Beck
- Re: Issue with mailbox move
- From: Ed Crowley [MVP]
- Re: Issue with mailbox move
- From: John Beck
- Re: Issue with mailbox move
- From: Ed Crowley [MVP]
- Re: Issue with mailbox move
- From: Missy Koslosky
- Issue with mailbox move
- Prev by Date: Re: MSEXCHANGEREPL 2094
- Next by Date: Re: General Purpose folders available for NNTP clients
- Previous by thread: Re: Issue with mailbox move
- Next by thread: Re: Issue with mailbox move
- Index(es):