Exchange alias with a "." not allowed??

[j.house]

I imported users into Unity and the import took the alias with a ".", but for day to day admin my client can't add a new Unity subscriber from the SA because it won't allow the "." in the alias. The workaround is to create the exchange account first and then import the user into Unity.....this is very inefficient.

Does Unity 4.0.4 correct this limitation?

[kechambe]

No, the SA does not allow a dot in the alias still. I will open a feature request in the next couple days asking for the dot to be allowed. Once I had the DDTS # I will post it out here.

On a side note, it really isn't good practice to have accounts built from Unity in a UM environment. While it might be easier it is definitely less secure and not something we would recommend as a best practice.

Thanks,

Keith

[j.house]

Thank you for following up on this issue/request.

I agree completely with your side note with regards to UM account being created from the Unity SA. This particular client is running VM only.

Thanks again...please keep me posted.

Jeff

[kechambe]

I opened a couple different defects around this issue:

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef06161

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef06217

They are too new for the URLs to work but they should shortly.

On a side note, it turned out that any ACSII combination of 64 ACSII characters is valid. The first defect also asks for dot (.) and underscore (_) to be added to the support character group. Jeff and I were talking about this and we concluded that leaving it wide open might cause a problem at some point. Dot (.) and underscore (_) are low risk characters.

The second defect (feature request) asks for the field constraints to be controller via an XML file so that we wouldn't need a code change to change how it works.

Thanks,

Keith