Re: Move Exch. 2000 Ent. to New Hardware

Tech-Archive recommends: Speed Up your PC by fixing your registry

Sorry. I used the wrong acronymn in my 4th and 5th questions. I meant to
say "Recipient Update Service" instead of SRS. I have the SRS Service
Disabled already. I was wondering about the impact of changing the RUS to
the new server and moving mailboxes gradually over a few weeks. (See 4. and
5. below for my detailed questions.) Thanks again!

"Leif Pedersen [MVP]" wrote:

> Hi,
>
> This should help you troubleshoot the PF replication problems.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;842273
>
> Other answers inline.
>
> Leif
>
>
>
> "Kathy L." <KathyL@xxxxxxxxxxxxxxxxxxxxxxxxx> skrev i en meddelelse
> news:FDF33529-2F50-44D9-9C1B-9E5DFEAEE00E@xxxxxxxxxxxxxxxx
> > I am following the "Move Mailboxes" procedure. I installed Exchange on my
> > new server. I have a couple more questions:
> >
> > 1. Do you have to point the Private Info. Stores to the Public Store on
> the
> > new server BEFORE you replicate the Public Folders from the old server to
> the
> > new server? The reason I'm asking if because of 2. below.
>
> You can do this as one of the last steps.
>
> >
> > 2. After going back and forth a few times, this is the current state of
> my
> > public store and replication: The Private Info. Stores are pointing to
> the
> > public store of the OLD Exchange server. I have all of the public folders
> > set to replicate to the new Exchange server. When you look at the public
> > folders on the new server, they are there, but empty. I thought that the
> > folders and their contents would appear in both public info. stores? Am I
> > going to have a problem if I later change the Public Store to the new
> server?
> > In other words, will the folders be empty? If so, should I turn off
> > replication now, then point to the new public store, and then do the
> > replication again?
>
> When you configure replication of public folders the content should be the
> same on both servers. You will need to troubleshoot the replication problem
> to get the servers in sync.
>
> >
> > 3. Is there a way to replicate all of the Public folders at once instead
> of
> > having to do them one by one because I have lots of them and I'm getting
> > carpal tunnel!
>
> You will have to add the replica on each top level folder and then you can
> rightclick this folder, select all tasks, propagate settings and here select
> the replicas.
>
> >
> > 4. When you change the SRS to point to the new server, what does that do?
> > In other words, can I do this and then gradually move all of my mailboxes?
> > Or will the users who still have their mailbox on the old server NOT be
> able
> > to access their mailbox? (I realize that they can't access their mailbox
> > while I'm moving it, but can they access it during the day before I move
> it
> > the next weekend?)
>
> Do you need the SRS (are there any 5.5 servers left in the organization). If
> not just remove this - see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;272314
>
> If you do need this service it has no bearing on your exchange 200x
> mailboxes so these can be moved gradually.
>
> >
> > 5. If the answer to 4. is that I can change SRS, and then gradually move
> > the mailboxes, will they have a problem receiving external e-mail? In
> other
> > words, once I change my MX record to point external mail to my new e-mail
> > server, will users who still have mailboxes on the old server be able to
> > receive external e-mail?
>
> All users should still be able to receive external emails. The location of
> an user mailbox is stamped on the user object in AD and from here the
> exchange servers will know how to route these emails.
>
> >
> > Sorry for all of the questions, but I'm still a little confused, and I
> don't
> > want any unnecessary downtime for my users. Thanks!
> >
> > "Kathy L." wrote:
> >
> > > Thanks!
> > >
> > > "Leif Pedersen [MVP]" wrote:
> > >
> > > > Hi,
> > > >
> > > > That is not a dumb question - in fact a very good one.
> > > >
> > > > Mailboxes are kept in the .edb and .stm files.
> > > >
> > > > If you were to keep the same server name this should do it:
> > > > http://support.microsoft.com/default.aspx?scid=kb;en-us;297289
> > > >
> > > > You indicated that you would like to have a new servername. As the
> location
> > > > of the user mailboxes are stamped on each user you would have to
> remove
> > > > exchange attributes from each user and then reattach the mailboxes
> located
> > > > on the new server to these users again (if you succeded in mounting
> the
> > > > databases). The chance for disaster is just too great in my opinion.
> > > >
> > > > You would have to perform almost everything during non-working hours
> whereas
> > > > in the move server scenario you can install and test everything and
> then
> > > > when you are ready to move the mailboxes perform only this operation
> > > > offhours.
> > > >
> > > > Leif
> > > >
> > > > "Kathy L." <KathyL@xxxxxxxxxxxxxxxxxxxxxxxxx> skrev i en meddelelse
> > > > news:267FD828-FA20-46C8-B517-1646BE477376@xxxxxxxxxxxxxxxx
> > > > > So I have a dumb question: Are the mailboxes part of the .edb file
> that
> > > > is
> > > > > stored on my Storage Area Network OR are they stored on the Exchange
> > > > server
> > > > > itself? If they are stored in the .edb file and, thus, on the SAN,
> why
> > > > would
> > > > > I have to move the mailboxes? I have moved mailboxes from one info.
> store
> > > > to
> > > > > another (one drive on SAN to a different drive), and this takes a
> very
> > > > long
> > > > > time. If I have to use AD and "Exchange Tasks" to move the mailbox
> from 1
> > > > > server with same info. store name to a new server with the same
> info.
> > > > store
> > > > > name (and info. stores are not moving at all because they are on the
> SAN),
> > > > > will it still take as long to move? Thanks...
> > > > >
> > > > > "Leif Pedersen [MVP]" wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I would still recommend using the move server method as described
> in the
> > > > > > previous post.
> > > > > > (It is not that easy to copy mail databases from one server to
> another
> > > > and
> > > > > > mount these databases on the new server - much safer to use the
> move
> > > > server
> > > > > > method)
> > > > > > This would include moving mailboxes from one server to another
> using
> > > > > > exchange tasks.
> > > > > >
> > > > > > Leif
> > > > > >
> > > > > > "Kathy L." <KathyL@xxxxxxxxxxxxxxxxxxxxxxxxx> skrev i en
> meddelelse
> > > > > > news:528382EF-E24D-4C7C-9694-3851C120A529@xxxxxxxxxxxxxxxx
> > > > > > > We have Exchange 2000 running on a server (not a DC) and want to
> > > > install
> > > > > > it
> > > > > > > on a new server with a new name. The Information Stores are
> stored on
> > > > a
> > > > > > > storage area network and will stay there. Would you also
> recommend
> > > > the
> > > > > > > article below for me to follow? It mentions using AD to move
> the
> > > > > > mailboxes.
> > > > > > > Would I need to move any mailboxes since my info. stores are on
> a SAN?
> > > > If
> > > > > > > so, how would I do it? I've moved mailboxes between stores
> using the
> > > > > > > "Exchange Tasks" in AD. I hope I wouldn't have to move them one
> by
> > > > > > one....
> > > > > > > Please unconfuse me. Thanks!
> > > > > > >
> > > > > > > "Bob" wrote:
> > > > > > >
> > > > > > > > Hi:
> > > > > > > >
> > > > > > > > We need to move Exchange 2000 Enterprise, in Native Mode,
> running
> > > > > > > > on a Windows 2000 Domain Controller (domain is in Mixed Mode)
> to new
> > > > > > > > hardware. The new server is running Windows 2003 Standard
> Svr.,
> > > > also a
> > > > > > DC in
> > > > > > > > the same domain.
> > > > > > > >
> > > > > > > > What is the recommended migration/move method? Note that we
> do run
> > > > > > Veritas
> > > > > > > > Backup Exec. w/Exch. Agent if backup/restore is recommended.
> > > > > > > >
> > > > > > > > Thanks for any insight you may have!
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
>
>
>
.

Relevant Pages

  • Re: Public folder replication 2000 > 2003
    ... Should I be creating the folders on the new server, ... prior to enable public folder replication between two Exchange ... The replication content of public folders also goes via SMTP ...
    (microsoft.public.exchange2000.general)
  • Re: Lost public folder data
    ... Susan Conkey [MVP] ... there's no data in the public folders. ... If Replication is logged, there should be some way to replay these logs to ... uninstalling an Exchange server that's being decommissioned, ...
    (microsoft.public.exchange.admin)
  • Re: public folders are not all in sync
    ... Exchange 2003 server about the calendar connector. ... then just dismount the public store. ... Network Administrator mailboxes are supposed to be moved. ... I don't have very many folders so I ...
    (microsoft.public.exchange.admin)
  • Re: Exch 2003 -> Exch 2007 SP1 Public Folder Replication Problem
    ... The logs show that replication is being attempted, but it fails with an error 554 5.6.0, citing a property validation error. ... exist only on the original Exchange 2003 server and are not replicated to the new system). ... Outlook was able to see the content of the two folders. ...
    (microsoft.public.exchange.setup)
  • Re: Public Folders Replication Status
    ... public folders that don't replicate often but in all other cases they are ... Exchange public folder replication works on a system that almost ensures ... Point one at each server. ...
    (microsoft.public.exchange2000.admin)