Exchange 2003 To 2007
Hello, I have an 2003 Exchange environment that is working with no issues. I recently installed Exchange 2007. I forgot to suppress the Link State and now have done so. I can send mail from a user on Exchange 2007 to the internet and to a user on 2003. I can't send mail from Exchange 2003 to 2007? Can someone help me with this? Help?
RE: Exchange 2003 To 2007
It sounds like your routing-group-connector isn't bi-directional. Open the Exchange Management Shell, enter "get-routinggroupconnector" and make sure both sides are correct. From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com] Sent: Tuesday, December 22, 2009 9:12 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 To 2007 Hello, I have an 2003 Exchange environment that is working with no issues. I recently installed Exchange 2007. I forgot to suppress the Link State and now have done so. I can send mail from a user on Exchange 2007 to the internet and to a user on 2003. I can't send mail from Exchange 2003 to 2007? Can someone help me with this? Help?
RE: Exchange 2003 To 2007
Below is what I received [PS] C:\>get-routinggroupconnector Name SourceRoutingGroup TargetRoutingGroup -- -- PG-SRV-03-PG-SRV-02 Exchange Routing Group ... First Routing Group PG-SRV-02-PG-SRV-03 First Routing GroupExchange Routing Group ... From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: December-22-09 9:30 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 To 2007 It sounds like your routing-group-connector isn't bi-directional. Open the Exchange Management Shell, enter "get-routinggroupconnector" and make sure both sides are correct. From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com] Sent: Tuesday, December 22, 2009 9:12 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 To 2007 Hello, I have an 2003 Exchange environment that is working with no issues. I recently installed Exchange 2007. I forgot to suppress the Link State and now have done so. I can send mail from a user on Exchange 2007 to the internet and to a user on 2003. I can't send mail from Exchange 2003 to 2007? Can someone help me with this? Help?
Exchange 2003 to 2007 Public Folder migration
Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
Public Folder migration from Exchange 2003 to 2007
Hello, We have 6 Exchange 2003 servers that host PFsthat are essentiallyour replacement for PST folders. We could not manage discovery items, etc when people were using PST folders. What we did was create a PF for each employee under the PF for the local office. IE: My folder would be Rick Fischer and located in the San Diego parent folder. What we would like to do is organize all offices onto the same server but on the 2003 servers they are whereverthey were created depending upon available space at the time. What I would like to do is use Move Replicas Too.. function to move all replicas from a 2003 server to a new 2007 server. I would then be able to use PoSh to do tree moves of PFsonto the servers I really want them on. Now I get to my question. If I use Move Replicas Too... will it overwhelmthe Hub server? I assume that if I set replication to only run during the hours of 8pm and 4am, that would help. Is it possible to setup a temp Hub server and force the 2003 server to use it without creating a new site in AD? Creating a new site would require changing IPs and that is not going to happen. Any ideas are greatly appreciated. If my explanation is unclear, please ask and I will clarify. Thanks, Rick
RE: Exchange 2003 to 2007 Public Folder migration
I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 -TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that's just me. After that, using get-publicfolder -recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
RE: Exchange 2003 to 2007 Public Folder migration
Have to say that I recommend the same thing as well. MoveAllReplicas moves the content, so if you have users on the old system the content availability for them will be mixed - most likely unable to get anything, which includes things like free/busy information and the offline address book. PF replication is a pain, it has a mind of its own. Message tracking is the tool to use here initially. That will show you if the content is going across, as it sticks out somewhat - SERVER-IS @ example.local Check it is being delivered. Primary reason for replication failure is a smart host on the SMTP virtual server of the originating server. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for certificates from just $23.99. Need a domain for your certificate? http://DomainsForExchange.net/<http://domainsforexchange.net/> Exchange Resources: http://exbpa.com/ From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 15 February 2010 17:26 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2007 Public Folder migration I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 -TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that's just me. After that, using get-publicfolder -recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
Re: Exchange 2003 to 2007 Public Folder migration
Thank you. From: Simon Butler To: MS-Exchange Admin Issues Sent: Mon, February 15, 2010 9:46:26 AM Subject: RE: Exchange 2003 to 2007 Public Folder migration Have to say that I recommend the same thing as well. MoveAllReplicas moves the content, so if you have users on the old system the content availability for them will be mixed – most likely unable to get anything, which includes things like free/busy information and the offline address book. PF replication is a pain, it has a mind of its own. Message tracking is the tool to use here initially. That will show you if the content is going across, as it sticks out somewhat – SERVER-IS @ example.local Check it is being delivered. Primary reason for replication failure is a smart host on the SMTP virtual server of the originating server. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://certificatesforexchange.com/ for certificates from just $23.99. Need a domain for your certificate? http://domainsforexchange.net/ Exchange Resources: http://exbpa.com/ From:Michael B. Smith [mailto:mich...@smithcons.com] Sent: 15 February 2010 17:26 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2007 Public Folder migration I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 –TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that’s just me. After that, using get-publicfolder –recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From:Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
Re: Exchange 2003 to 2007 Public Folder migration
One clairification: I am trying to move all data from our 2003 servers to 2007. There are no users that are using the server but I need to move all data off to retire the server. Can I use a PS script to move data from a 2003 to 2007? Thanks again, Rick From: Simon Butler To: MS-Exchange Admin Issues Sent: Mon, February 15, 2010 9:46:26 AM Subject: RE: Exchange 2003 to 2007 Public Folder migration Have to say that I recommend the same thing as well. MoveAllReplicas moves the content, so if you have users on the old system the content availability for them will be mixed – most likely unable to get anything, which includes things like free/busy information and the offline address book. PF replication is a pain, it has a mind of its own. Message tracking is the tool to use here initially. That will show you if the content is going across, as it sticks out somewhat – SERVER-IS @ example.local Check it is being delivered. Primary reason for replication failure is a smart host on the SMTP virtual server of the originating server. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://certificatesforexchange.com/ for certificates from just $23.99. Need a domain for your certificate? http://domainsforexchange.net/ Exchange Resources: http://exbpa.com/ From:Michael B. Smith [mailto:mich...@smithcons.com] Sent: 15 February 2010 17:26 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2007 Public Folder migration I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 –TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that’s just me. After that, using get-publicfolder –recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From:Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
RE: Exchange 2003 to 2007 Public Folder migration
No clarification required. I believe Simon and I both understood that. We were describing a process that we find WORKS BETTER IN THE REAL WORLD the MoveAllReplicas. That process is: Add the new server to the replica list (PS script). Use message tracking to see the success/failure of messages moving across (PS script or EMC). With get-publicfolderstatistics, determine when replication is complete (PS script). Remove the old server from the replica list (PS script). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 2:39 PM To: MS-Exchange Admin Issues Subject: Re: Exchange 2003 to 2007 Public Folder migration One clairification: I am trying to move all data from our 2003 servers to 2007. There are no users that are using the server but I need to move all data off to retire the server. Can I use a PS script to move data from a 2003 to 2007? Thanks again, Rick From: Simon Butler To: MS-Exchange Admin Issues Sent: Mon, February 15, 2010 9:46:26 AM Subject: RE: Exchange 2003 to 2007 Public Folder migration Have to say that I recommend the same thing as well. MoveAllReplicas moves the content, so if you have users on the old system the content availability for them will be mixed – most likely unable to get anything, which includes things like free/busy information and the offline address book. PF replication is a pain, it has a mind of its own. Message tracking is the tool to use here initially. That will show you if the content is going across, as it sticks out somewhat – SERVER-IS @ example.local Check it is being delivered. Primary reason for replication failure is a smart host on the SMTP virtual server of the originating server. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk<mailto:si...@sembee.co.uk> w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://certificatesforexchange.com/ for certificates from just $23.99. Need a domain for your certificate? http://domainsforexchange.net/ Exchange Resources: http://exbpa.com/ From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: 15 February 2010 17:26 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2007 Public Folder migration I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 –TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that’s just me. After that, using get-publicfolder –recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
Re: Exchange 2003 to 2007 Public Folder migration
Thank you. No, I meant clarification for myself. Public Folders are not my expertise. From: Michael B. Smith To: MS-Exchange Admin Issues Sent: Mon, February 15, 2010 1:16:02 PM Subject: RE: Exchange 2003 to 2007 Public Folder migration No clarification required. I believe Simon and I both understood that. We were describing a process that we find WORKS BETTER IN THE REAL WORLD the MoveAllReplicas. That process is: Add the new server to the replica list (PS script). Use message tracking to see the success/failure of messages moving across (PS script or EMC). With get-publicfolderstatistics, determine when replication is complete (PS script). Remove the old server from the replica list (PS script). Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From:Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 2:39 PM To: MS-Exchange Admin Issues Subject: Re: Exchange 2003 to 2007 Public Folder migration One clairification: I am trying to move all data from our 2003 servers to 2007. There are no users that are using the server but I need to move all data off to retire the server. Can I use a PS script to move data from a 2003 to 2007? Thanks again, Rick From:Simon Butler To: MS-Exchange Admin Issues Sent: Mon, February 15, 2010 9:46:26 AM Subject: RE: Exchange 2003 to 2007 Public Folder migration Have to say that I recommend the same thing as well. MoveAllReplicas moves the content, so if you have users on the old system the content availability for them will be mixed – most likely unable to get anything, which includes things like free/busy information and the offline address book. PF replication is a pain, it has a mind of its own. Message tracking is the tool to use here initially. That will show you if the content is going across, as it sticks out somewhat – SERVER-IS @ example.local Check it is being delivered. Primary reason for replication failure is a smart host on the SMTP virtual server of the originating server. Simon. -- Simon Butler MVP: Exchange, MCSE Sembee Ltd. e: si...@sembee.co.uk w: http://www.sembee.co.uk/ w: http://www.amset.info/ w: http://blog.sembee.co.uk/ Need cheap certificates for Exchange, compatible with Windows Mobile 5.0? http://certificatesforexchange.com/ for certificates from just $23.99. Need a domain for your certificate? http://domainsforexchange.net/ Exchange Resources: http://exbpa.com/ From:Michael B. Smith [mailto:mich...@smithcons.com] Sent: 15 February 2010 17:26 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003 to 2007 Public Folder migration I always recommend this (executed on the PF server): cd $exscripts .\AddReplicaToPFRecursive.ps1 –TopPublicFolder \ ` -ServerToAdd $env:computername Instead of using MoveAllReplicas. But that’s just me. After that, using get-publicfolder –recurse | get-publicfolderstatistics, you can tell the replication status on a per PF basis. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From:Rick Fischer [mailto:uscgolflo...@yahoo.com] Sent: Monday, February 15, 2010 12:14 PM To: MS-Exchange Admin Issues Subject: Exchange 2003 to 2007 Public Folder migration Hello, We are in the process of migrating our Public Folders from 2003 to 2007. We have setup a test of using Move All Replicas Too... by moving a couple of users folders containing about 12GB of data onto a test 2003 server to replicate to a 2007 server. Friday at 8pm PST, I went into System Manager and drilled down to the PF DB and chose Move All Replicas Too... to a 2007 server. The next morning, and still this morning, the folders have been created on the new server but they are empty. The DB on the 2003 server still has 12GB of data but when viewed in System Manager, it says there are no Public Folder Instances. How would I troubleshoot what is happening with the replication? Did we do something wrong? Thanks
looking for a good book on exchange 2003 to 2007 migration
Looking to upgrade next year and was curious if anyone had any good books with info on this? Chris Drobny Network/Systems Administrator LMS Intellibound, Inc. [EMAIL PROTECTED] 770.724.0562 Office 404.797.9710 Cell ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: looking for a good book on exchange 2003 to 2007 migration
From: Chris Drobny [mailto:[EMAIL PROTECTED] Subject: looking for a good book on exchange 2003 to 2007 migration Looking to upgrade next year and was curious if anyone had any good books with info on this? I used the various articles on MSExchange.org. http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchang e-Server-2007-Part1.html http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchang e-Server-2007-Part2.html http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchang e-Server-2007-Part3.html http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration- deployment/removing-last-exchange-2003-server-exchange-2007-part1.html http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration- deployment/removing-last-exchange-2003-server-exchange-2007-part2.html http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration- deployment/removing-last-exchange-2003-server-exchange-2007-part3.html http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration- deployment/removing-last-exchange-2003-server-exchange-2007-part4.html http://www.msexchange.org/tutorials/Removing-First-Exchange-2003-Server-Part 1.html http://www.msexchange.org/tutorials/Removing-First-Exchange-2003-Server-Part 2.html Webster ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
