Re: Migration wizard permissions error

From: Alan (a_at_b.com)
Date: 12/02/04


Date: Thu, 2 Dec 2004 12:06:04 -0000

Hi Alan

As far as I can see the ADMT tool should move mailboxes. Here's a direct
quote from the help contents "Run the Exchange Directory Migration Wizard to
migrate users' mailboxes from a source domain to a target domain."

A couple of months ago I was able to do a successful mailbox migration using
this tool which is why I decided to use it now (before all the error of
course) however, i have tried and tested the ExMerge.exe tool and this
definitely is working fine, so in order not to spend too much time on this
problem, I will go with this method to do my mailbox transfer.

Thanks once again for all your input - I always fine a solution to my
Exchange problems in these user groups and I am very appreciative that the
quality of advice is always top quality and very professional.

Cheers

Alan

"Alan Sun [MSFT]" <v-asun@online.microsoft.com> wrote in message
news:8FrbivD2EHA.768@cpmsftngxa10.phx.gbl...
> Hi Alan Tilly,
>
> Thanks for your posting back and emailing.
>
> First, I would like to let you know that the ADMT tool for Exchange
> Directory Migration Wizard doesn't move Exchange mailbox and it only
> migrate ACL on the Exchange 5.5 objects with the new migrated user
accounts.
>
> To move the mailbox, you can use the ADUC snap-in according to the
> following article:
> 328810 XADM: Moving Mailboxes Between Servers
> http://support.microsoft.com/?id=328810
>
> Regarding the error you encountered, it will appear if the Exchange 5.5
> server isn't listened on port 389 for LDAP query. You may telnet to the
> Exchange 5.5 server to confirm it:
>
> 1. Start command line.
>
> 2. Type the following command:
>
> telnet (<servername> or <IP address>) 389
>
> If LDAP is configured on port 389, when you run this command, a Telnet
> window opens, but you do not see a banner response. If LDAP is not
> configured on port 389, you receive the following message:
>
> Could not open a connection to host on port 389: Connect failed.
>
> If Exchange 5.5 is not listened on port 389, you may use the following
> method to modify it. Use the Exchange Administrator | Configuration |
> Protocols | LDAP (Directory) Site Defaults to verify the site defaults for
> the LDAP (Directory).
>
> If anything is unclear, just post back to let me know. Thanks and have a
> nice day!
>
> Thanks & Regards
> Alan Sun
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
> --------------------
> From: "Alan" <a@b.com>
> Newsgroups: microsoft.public.exchange.setup
> References: <41acac79$0$9559$afc38c87@news.easynet.co.uk>
> <$bTD$601EHA.3388@cpmsftngxa10.phx.gbl>
> Subject: Re: Migration wizard permissions error
> Date: Wed, 1 Dec 2004 13:56:21 -0000
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> Lines: 153
> Message-ID: <41adcd86$0$28972$afc38c87@news.easynet.co.uk>
> Organization: [posted via Easynet UK]
> NNTP-Posting-Host: 217.207.192.210
> X-Trace: DXC=JXjnV?KS^cVS;WRJaS<22TDTW\`Z99^Z\=6nmQXi^bhVGd@W2nGf1G\
> Path:
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
>
sfeed1.ip.tiscali.net!border2.nntp.ams.giganews.com!nntp.giganews.com!pe2.ne
>
ws.blueyonder.co.uk!blueyonder!easynet-monga!easynet.net!easynet-post2!not-f
> or-mail
> Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.setup:119731
> X-Tomcat-NG: microsoft.public.exchange.setup
>
> Hi Alan
> Thanks for your reply to this. I have added my replies to the message
> below
> and emailed you the screen shot.
> It's as if the Administrator from the source domain does not have the
> necessary permissions in that domain. Is there a way i can check this
> in the
> source domain?
> I have delegated full exchange admin rights to the administrator in
the
> source domain but it does not seem to attach or list the mailboxes
> from the
> target domain, which is where i am running the ADMT tool from.
> Thanks
> Alan
>
>
> "Alan Sun [MSFT]" <v-asun@online.microsoft.com> wrote in message
> news:$bTD$601EHA.3388@cpmsftngxa10.phx.gbl...
> > Hey Alan,
> >
> > Thanks for your posting here.
> >
> > According to your desription, I suggest you perform the following
> steps to
> > narrow down the issue:
> >
> > 1. Make sure the credential has the proper permission on the target
> > Exchange server.
>
> Not sure what you mean here but i have a 2 way trust between domains
> and i
> have the administrators from both domains in eachothers
administrative
> groups.
>
> > 2. Disable all the antivirus applications 3-rd party software
> running on
> > the Exchange server.
>
> I have disabled my antivirus in both domains.
>
> >
> > 3. Check if the behavior appears for all the maiboxes.
>
> It doesn't even attach to the source domain's mailboxes so not
> possible to
> check this.
>
> > 4. Check if there is size limit on the destination server, which
can
> > prevent successful mailbox moves. Exchange Server 2000/2003
Standard
> > Edition includes a 16-gigabyte limit.
>
> I'm running Exchange 2k so this should be OK. Also the target domain
> does
> not have any user mailboxes yet.
>
> > 5. Let me know the version of the Exchange server.
>
> Exchange 2000
>
> > 6. Produce the issue, and capture a screen shot of the error
> message. You
> > can upload to the newsgroup or send to me directly at:
> v-asun@microsoft.com.
>
> I did try this but was unable to upload to the group - I will email
> you the
> screenshot.
>
> > 7. Increasing the level for diagnostic logging.
>
> I did this but nothing is showing up in the eventlog as no mailboxes
> are
> being moved yet.
>
> > a. In Exchange System Manager, right-click the source server, and
> then
> > click "Properties".
> >
> > b. Click "Diagnostics Logging".
> >
> > c. In the "Services" list, double-click "MSExchangeIS", and then
> click
> > "System".
> >
> > d. In the "Categories" list, click "Move Mailbox".
> >
> > e. Under "Logging level", click "Maximum", and then click "OK".
> >
> > f. Reproduce the issue, and check the application log again.
> >
> > Hope this helps! If anything is unclear, just post back to let me
> know.
> > Thanks and have a nice day!
> >
> > Thanks & Regards
> > Alan Sun
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> > =====================================================
> > When responding to posts, please "Reply to Group" via your
> newsreader so
> > that others may learn and benefit from your issue.
> > =====================================================
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> >
> > --------------------
> > From: "Alan" <a@b.com>
> > Newsgroups: microsoft.public.exchange.setup
> > Subject: Migration wizard permissions error
> > Date: Tue, 30 Nov 2004 17:23:05 -0000
> > X-Priority: 3
> > X-MSMail-Priority: Normal
> > X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> > Lines: 24
> > Message-ID: <41acac79$0$9559$afc38c87@news.easynet.co.uk>
> > Organization: [posted via Easynet UK]
> > NNTP-Posting-Host: 217.207.192.210
> > X-Trace: DXC=7eGR=9ROh3E78kQ4]_b>ZBMCBN^?[TfCE<7WPHok>oIA
> > Path:
> >
>
>
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fas
> >
>
>
twebnet.it!tiscali!newsfeed1.ip.tiscali.net!feed.news.tiscali.de!easynet-mon
> > ga!easynet.net!easynet-post2!not-for-mail
> > Xref: cpmsftngxa10.phx.gbl
> microsoft.public.exchange.setup:119681
> > X-Tomcat-NG: microsoft.public.exchange.setup
> >
> > Hi
> > I get the error "the specified credentials are either invalid
> or do
> > not have
> > access permission on the exchange server" when using the
Active
> > Directory
> > Migration Wizard to move mailboxes from one domain to another.
> The
> > error
> > comes up after i enter the administrative credentials in the
> Migration
> > Wizard.
> > I am using the administration account from the source domain
> who I
> > know has
> > full Exchnage rights. I've even tried my Veritas backup
account
> who
> > also has
> > full rights in order to backup mailboxes.
> > The interesting thing is that I get no errors in the event log
> > indicating
> > where the problem may be.
> >
> > Can anyone point me in the right direction please? I cannot
> find any
> > reference to this error on the MS web site or elswhere.
> >
> > Many thanks
> > Alan
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>



Relevant Pages

  • Re: Migration wizard permissions error
    ... Alan Sun ... As far as I can see the ADMT tool should move mailboxes. ... I would like to let you know that the ADMT tool for Exchange ...
    (microsoft.public.exchange.setup)
  • RE: Migration: SBS 2003 to WS2003 with Exchange 2003
    ... My plan was to use the Exchange Migration Wizard to Migrate the Mailboxes ... from the SBS2003 Server over to the New Exchange 2003 Server in the other ...
    (microsoft.public.windows.server.sbs)
  • Re: Migration wizard permissions error
    ... I would like to let you know that the ADMT tool for Exchange ... Directory Migration Wizard doesn't move Exchange mailbox and it only ... 328810 XADM: Moving Mailboxes Between Servers ... It's as if the Administrator from the source domain does not have the ...
    (microsoft.public.exchange.setup)
  • Re: no mailboxs in private foulder
    ... limited experince with exchange. ... Ping the exchange server ... Right click the mailbox store, is the first option "mount store" or is it ... Where are you seeing "Mailboxes and stuff"? ...
    (microsoft.public.exchange.admin)
  • RE: Migration: SBS 2003 to WS2003 with Exchange 2003
    ... Microsoft CSS Online Newsgroup Support ... the first thing the migration wizard does ... some such issues occurs due to incorrect server ... log on the server running exchange migration wizard for analyze. ...
    (microsoft.public.windows.server.sbs)

Loading