Well the PST was not tied to the account at all. It is one I was
importing. During import it attaches temporarily and then detaches and
then I get this message after it looks like it finished.
I double checked it wasn't a default pst or tied to anything... well it is
in the data files now if I s
Sounds as if the new destination for the mailbox has not been moved to
Exchange, but left at PST.
From: gsaunders.myitanal...@gmail.com [mailto:gsaunders.myitanal...@gmail.com]
On Behalf Of Greg Saunders
Sent: Friday, January 25, 2013 4:08 PM
To: MS-Exchange Admin Issues
Subject: Exchange Migrat
Someone at some point turned off ESMTP on the old server, so it was never used
and thus never broke on you. The new server had it turned on by default. That
is my best bet.
> On Mon, Apr 6, 2009 at 9:46 AM, Fancher, William
> > One thing confuses me however. After the migration we were force
[mailto:kennedy...@elyriaschools.org]
Sent: Monday, April 06, 2009 1:48 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration
Someone at some point turned off ESMTP on the old server, so it was never used
and thus never broke on you. The new server had it turned on by default. That
is my
Not sure on the ultimate issue but you should turn the stupid smtp
fix-up off anyway.
One 'posible' factor (long shot, probably not) is that you may have
had an issue disguised by time. In other words, something in the
rules or routing was done to solve the issue but when you moved the ip
address
This past weekend we successfully moved our Exchange 2K3 on Win2K to a
new more robust Win2K3 box. We used the swing method as recommended by
forum members and the movement went very well. A few minor hiccups but
all in all very smooth.
One thing confuses me however. After the migration we we
-
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Friday, March 27, 2009 4:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration
Well, Cisco does not translate server name to ip. It translates
the outside IP to
27, 2009 4:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration
Thanks Sherry
It just hit me that it is not the name but the IP I want to reuse. DNS MX
points to mail.domain.com and mail.domain.com points to IP address, Cisco
translates servername to IP so I change the old server
Change the MX record and leave the old server running until all traffic
goes to the new one.
From: Fancher, William [mailto:wfanc...@invention-machine.com]
Sent: Friday, March 27, 2009 1:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration
om: Sherry Abercrombie [mailto:saber...@gmail.com]
Sent: Friday, March 27, 2009 3:47 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange Migration
No. Both Exchange servers have to be up and on the network at
the same time. Get used to a ne
name.
> -Original Message-
> From: Fancher, William [mailto:wfanc...@invention-machine.com]
> Sent: Friday, March 27, 2009 3:08 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Exchange Migration
>
> Thanks to Jim and John for the insight. The swing method or moving the
> mailboxe
-305-9250 ext 3306 voice
> 617-305-9255 fax
> wfanc...@invention-machine.com
>
>
> -Original Message-
> From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
> Sent: Friday, March 27, 2009 2:29 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Exchange Migration
I would concur with Jim. If the current Exchange server isn't dead then
don't go through the hassle of doing a restore. Move mailbox works great.
You can also use the move mailbox during normal working hours, it will only
work on 3 threads (mailboxes) at a time, and the user is only down for that
Boston, MA 02199
617-305-9250 ext 3306 voice
617-305-9255 fax
wfanc...@invention-machine.com
-Original Message-
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org]
Sent: Friday, March 27, 2009 2:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration
I would bring up
I would bring up another server in the Exch. Org and Mailbox move people to it
through Exchange, and public folders and all that. You can even schedule the
mailbox moves to happen at 3 am..
> -Original Message-
> From: Fancher, William [mailto:wfanc...@invention-machine.com]
> S
Thanks, I will put this (and all the other!) suggestions forward to the man
in charge and let him decide what he wants me to do. I think a lot of
snapshots and backups are in order first though :-)
2008/6/27 Ehren Benson <[EMAIL PROTECTED]>:
> I believe you are correct about the trust, there is
I believe you are correct about the trust, there is no way to directly migrate
(mailbox to mailbox via exchange) without one AD being able to talk to and
trust the other.
There is however a pretty workable solution via the Microsoft Transporter Suite
for Internet Mail. Using this you can copy
35 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration Wizard error
I am using a domain Administrator account.
-Original Message-
From: Jennifer Baker [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 31, 2001 12:05 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migr
You should use the Exchange 5.5 Service Account
-Original Message-
From: Reed, Russ [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 31, 2001 8:35 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration Wizard error
I am using a domain Administrator account.
-Original
I am using a domain Administrator account.
-Original Message-
From: Jennifer Baker [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 31, 2001 12:05 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange Migration Wizard error
"What permissions does your current logon user have?&q
"What permissions does your current logon user have?" Would be my first
question.
-Original Message-
From: Russ Reed [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 30, 2001 9:52 PM
To: MS-Exchange Admin Issues
Subject: Exchange Migration Wizard error
I am trying to run the Exchange
21 matches
Mail list logo
