Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Fri, 19 May 2006 08:55:02 -0700,    group: microsoft.public.exchange.design        back       


Organization Name   
We are performing an Inter-Organizational migration from 5.5 to 2003. Is 
there any reason why the new org cannot have the same name as the old one ? I 
have seen a poost saying that exprofre will not work if the two are the same, 
but would like confirmation of that, and whether there are any other 
considerations.

Thanks
date: Fri, 19 May 2006 08:55:02 -0700   author:   Tingeridge

Re: Organization Name   
Depends what tools you are using for your migration... for example if you 
are using the ADC for Inter-org sync I believe that requires the 
organisation names to be different. Other 3rd party tools may not care... 
not sure about exprofre I'm afraid.

-- 
HTH

Tim
Llama IT
This posting is provided in good faith, "as is" with no warranties, and 
confers no rights.

"Tingeridge"  wrote in message 
news:0AB295A6-3392-40EA-B92E-8D8C47D7D755@microsoft.com...
> We are performing an Inter-Organizational migration from 5.5 to 2003. Is
> there any reason why the new org cannot have the same name as the old one 
> ? I
> have seen a poost saying that exprofre will not work if the two are the 
> same,
> but would like confirmation of that, and whether there are any other
> considerations.
>
> Thanks
date: Fri, 19 May 2006 18:21:43 +0100   author:   Tim Coveney

Re: Organization Name   
Thanks Tim. I believe the plan is to use MIIS for synchronization during the 
migration period.

"Tim Coveney" wrote:

> Depends what tools you are using for your migration... for example if you 
> are using the ADC for Inter-org sync I believe that requires the 
> organisation names to be different. Other 3rd party tools may not care... 
> not sure about exprofre I'm afraid.
> 
> -- 
> HTH
> 
> Tim
> Llama IT
> This posting is provided in good faith, "as is" with no warranties, and 
> confers no rights.
> 
> "Tingeridge"  wrote in message 
> news:0AB295A6-3392-40EA-B92E-8D8C47D7D755@microsoft.com...
> > We are performing an Inter-Organizational migration from 5.5 to 2003. Is
> > there any reason why the new org cannot have the same name as the old one 
> > ? I
> > have seen a poost saying that exprofre will not work if the two are the 
> > same,
> > but would like confirmation of that, and whether there are any other
> > considerations.
> >
> > Thanks 
> 
> 
>
date: Fri, 19 May 2006 10:32:02 -0700   author:   Tingeridge

Re: Organization Name   
You should check out the tools from www.priasoft.com.  They support
this.

L8r


Tingeridge wrote:
> We are performing an Inter-Organizational migration from 5.5 to 2003. Is
> there any reason why the new org cannot have the same name as the old one ? I
> have seen a poost saying that exprofre will not work if the two are the same,
> but would like confirmation of that, and whether there are any other
> considerations.
> 
> Thanks
date: 19 May 2006 13:23:32 -0700   author:   unknown

Re: Organization Name   
Well, I'm not 100% as I've never tried it, but I would imagine that the way 
MIIS (or IIFP) do GAL-synch, and the way that routing uses legacyExchangeDN 
values, that you're going to run into trouble if the canonical names have 
the same base DN (if that makes any sense). i.e. if both orgs start 
o=<yourExchangeorgname> then you're going to run into difficulties... of 
course you can change the dns usiung legacydn.exe, but you're adding another 
level of 'things that can and will go wrong'

Your call of course, but if I was doing an Interorg migration, I'd make the 
orgname different... or at least test it extensively in a lab environment 
before making the choice...

-- 
HTH

Tim
Llama IT
This posting is provided in good faith, "as is" with no warranties, and 
confers no rights.

"Tingeridge"  wrote in message 
news:CDD66E24-5603-41A9-BD75-2DF432B47D7D@microsoft.com...
> Thanks Tim. I believe the plan is to use MIIS for synchronization during 
> the
> migration period.
>
> "Tim Coveney" wrote:
>
>> Depends what tools you are using for your migration... for example if you
>> are using the ADC for Inter-org sync I believe that requires the
>> organisation names to be different. Other 3rd party tools may not care...
>> not sure about exprofre I'm afraid.
>>
>> -- 
>> HTH
>>
>> Tim
>> Llama IT
>> This posting is provided in good faith, "as is" with no warranties, and
>> confers no rights.
>>
>> "Tingeridge"  wrote in message
>> news:0AB295A6-3392-40EA-B92E-8D8C47D7D755@microsoft.com...
>> > We are performing an Inter-Organizational migration from 5.5 to 2003. 
>> > Is
>> > there any reason why the new org cannot have the same name as the old 
>> > one
>> > ? I
>> > have seen a poost saying that exprofre will not work if the two are the
>> > same,
>> > but would like confirmation of that, and whether there are any other
>> > considerations.
>> >
>> > Thanks
>>
>>
>>
date: Sat, 20 May 2006 10:58:15 +0100   author:   Tim Coveney

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us