 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Design / April 2005InterOrg Migration 5.5 to 2K3 and Distribution Lists
Hey everyone, Thanks in advance for any help. Here's my issue: Distribution Lists are one major limitation with Microsoft's Inter-Org Sync Tool. Basically, the Distribution Lists are brought over as a contact, and don't contain any members. In researching possible solutions (other than expensive 3rd party software) I found KB328871 that states I can "convert the distribution list to a public folder" and then migrate the public folder. . . . . hm. Anyone have any experience with this, or know what this means? Thanks! That would be talking about putting all of the recipients into a public folder as contacts and replicating the public folder over to the other org. Why would you want to do something different remembering that remote users (Users without mail stores) are represented as mail-enabled contacts? DG's would be no different. So if you create a DG in the target and then populate with contacts, what does that accomplish for you? How would you handle it as the users get moved over and are no longer contacts? My advice? Don't stay in migratory mode any longer than you can stand it. Or go faster every chance you get. If you absolutely need it this way, check out the MIIS product. You'll need to get the full product so you can talk with 5.5, but it might have more of what you're looking for. Other tools, such as SimpleSync (www.cps-systems.com) might be useful to you as well. Al > Hey everyone, > Thanks in advance for any help. Here's my issue: [quoted text clipped - 8 lines] > > Thanks! Yeah. I actually > That would be talking about putting all of the recipients into a public > folder as contacts and replicating the public folder over to the other [quoted text clipped - 27 lines] >> >> Thanks! I actually was referred to a great script by another poster. We would be using a 3rd party tool in this case, but the head count on this particular migration is not high enough, and the entire user base is not migrating, only a subset, thus the co-existence (which i hate, and avoid as much as possible). Here's a link to the solution that was referred to me: http://www.msd2d.com/newsletter_tip.aspx?section=exchange&id=f9bcb0b1-7263-4d97- 9b49-14ac6d62ff26 > That would be talking about putting all of the recipients into a public > folder as contacts and replicating the public folder over to the other [quoted text clipped - 27 lines] >> >> Thanks! Good luck with that. Like I said, the management of keeping it that way is a real PITA even with that method. That method (BTW, I can't see the script, but the explanation looks solid) will result in a point in time creation of that DL/DG. Maybe your migration will take into account the migrating from contact to user in the target directory and maintain group membership? That just leaves you with having to maintain two DL/DG's at the same time manually. I'd be interested to see the script Rui. :) Al >I actually was referred to a great script by another poster. We would be >using a 3rd party tool in this case, but the head count on this particular [quoted text clipped - 35 lines] >>> >>> Thanks! Sorry Rui, I found the script download. Need to have more coffee prior to asking that next time :) One thing to keep in mind with this is that you *could* use ldap for this scenario. Just a lot of effort to accomplish something already done if you did, but it could be done that way and save some ldif syntax heartache. Good luck. Al > Good luck with that. Like I said, the management of keeping it that way > is a real PITA even with that method. That method (BTW, I can't see the [quoted text clipped - 47 lines] >>>> >>>> Thanks! Hi Al. I devoleped the script based on a method created by two other guys. I didn't bother to check if there was an easier way to do that. One of the guys is from Microsoft, so I believe he tried every other ways. The main reason why I did the script is because DL migration is realy a pain in the a**, and lots of people complaint about that. If you find any other way of doing it, share with us.  SignatureRui JM Silva MVP Windows Server System - Exchange Server Blog "subject: exchange", http://ehlo.blogspot.com > Sorry Rui, I found the script download. Need to have more coffee prior to > asking that next time :) [quoted text clipped - 59 lines] >>>>> >>>>> Thanks! I don't have one handy at the moment, but I've done some scripts around LDAP maintenance of Exchange 5.5 users and DL's. If I get the chance, I'll dig those out. If I don't send something shortly, feel free to ping direct. Al > Hi Al. > I devoleped the script based on a method created by two other guys. I [quoted text clipped - 67 lines] >>>>>> >>>>>> Thanks! |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.