Re: Some more problems moving from EX 2k3 (SBS) to EX 2k7

Regarding #1, please verify that the properties of the public folder in question doesn't show the Exchange 2003 server as having a replica. Some things you might try include:

(1) adding the E2K3 replica back, changing the content of the folder (add a dummy item or something like that), wait a while for replication, then removing the replica again

(2) copying the folder content to a PST and deleting the folder, then recreating it later and copying back the content--be sure to note the folder settings, like permissions so you can restore them

As to #2, please post the complete text of the message. You didn't say, but is E2K3 a domain controller? Is DC01 also a global catalog? Are DC01 and the Exchange 2007 server in the same AD site?
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Andy" <aweaver@xxxxxx> wrote in message news:O9IG$40lJHA.1292@xxxxxxxxxxxxxxxxxxxxxxx
Okay, so I am having a few problems, I thought it would be much worse honestly but it hasn't been "too bad" yet.

Problem #1:

No matter what I do, the exchange 2003 server will not remove a PF replica for a mail-enabled folder we have. I have verified that it is replicated to the new exchange 2k7 server by simply unmounting the store and then using outlook to whiz around in the folder, it appears to work perfectly. Its driving me nuts!

The replica stays in 'public folder instances' forever, there is nothing listed under 'public folders'. If i add the replica back to the old server it appears in public folders, if i tell it to remove the replica it removes it from public folders but it __never__ removes it from public folder instances.

Problem #2:

I have a separate domain controller running/global catalog on the network called (DC01). I was doing some testing 'before business hours' this morning which basically consisted of shutting down the old exchange 2003 server to make sure I could still access everything in Outlook, etc. Once the Exchange 2003 (EX2k3) server shut down, I got an authentication box to login to the new EX2k7 server (exchange), then as I was using Outlook different notices kept popping up about Outlook trying to connect to the exchange server DC01.

Exchange isn't installed on DC01, I'm assuming it meant that it switched from using EX2k3 as its DC/GC server to using DC01 as its DC/GC server, is this normal behavior? How do i know without a doubt that everything is alright with my new setup before migrating?

I'm honestly more concerned about problem #1 just because its annoying me, but I should probably be equally concerned about problem #2.

As always, any advice is appreciated.

Thanks,
Andy


.

Loading