What problem could I have if I migrate nms415 users with UID's like user@domain to iMS5.2?

Hi,

We are planning an upgrade from NMS4.15 to iMS5.2

On the release notes of iMS52 is a list of UID invalid characters. One of this characters is the @ sign.

The UID's on our nMS415 are like username@domain, and if we want to keep our store partitions for the new iMS52 we must keep the username as is, so hashdir points to the right place.

I've made an upgrade test with UID's containing the @, and everything seems to work OK.

What problems could we have by using the @ character on the UID?

I've seen that iDA and MTA don't accept creation of users with UID containing the @. For the MTA we can use the LDAP_UID_INVALID_CHARS option to allow the @ sign. But this don't work for iDA. What can I do to solve that?

Does anyone have another solution to do the migration removing the @domain part from the UID and keep users mailboxes intact? I know I can use the moveuser utility, but we are talking of 200 000 users. That takes to long.

Best Regards,

Sergio Sousa

[1054 byte] By [pqp] at [2007-11-25 7:13:59]
# 1

Hi Sergio, Even we are faced with a similar problem here at work. What makes the matter even worse is that the servers are installed on Windows NT where our scripting skills cannot save us. You mentioned that you had no problems when you did a test run. Do you mean that the migration went through smoothly and there is no change as far as the end users are concerned? I have no idea about iDA because I have never used it. Please do keep me updated on this.

Thanks !!

708281 at 2007-6-29 17:48:35 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...