Public folders migration from SBS 2003 to SBS 2011

I have pretty finished my migration from SBS 2003 to 2011, but i still have some PF instances in my SBS 03 despite having set replication to urgent and 'always run". It has been 24 hours now and nothing has moved.
We were NOT using PF in SBS 03 and I am not sure they will be used in 2011 either.
Can I just delete them from SBS 03 and go on removing exchange from the source server and C promo it down without having any lingering issues on the 2011 system ?
JPD153Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
Public Folders were always used in Exchange 2003. They are used to hold the configuration.
While you can eliminate them from SBS 2011 (Exchange 2010) they need to be replicated off the Exchange 2003 server first, then remove Exchange 2003. Only then can you think about removing public folders.

24 hours isn't really much of a time to wait, I have seen it take up to a week.
If you run

get-publicfolderstatistics

on the new server, does it show any content?
If not, that could suggest that you have a problem with the replication process, as it uses SMTP to replicate. If there have been changes to the Receive Connectors or a smart host set on the SMTP virtual server, those can stop the replication from occurring.

Simon.
JPD153Author Commented:
This is the status of Exchange 2010
Exchange 2010 current status of PFsThen the status on the source server
Status of Excahnge on source serverI have pushed the replication several times but it still does not seem to go anywhere.
replication status on source server
What are the consequences of deleting these on the source server ?
Simon Butler (Sembee)ConsultantCommented:
The GUI is useless for discovering what is happening. Replication Status in Exchange 2003 is about as trustworthy as a $9 bill.

The only thing that is of any use is the results of get-publicfolderstatistics - which will show you item count, and then compare that to the item count in public folders in the source.

You cannot delete those folders, they are system folders. Exchange will not let you delete them.

Simon.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

JPD153Author Commented:
This is what I get
results of get-publicfolderstatistics
Simon Butler (Sembee)ConsultantCommented:
That means nothing has replicated.
You need to look at the source server to begin with. Ensure that there are no smart hosts on the SMTP virtual server. The FQDN on the SMTP virtual server needs to be the server's REAL FQDN, not an alias.

On the receive connector, the source server needs to be able to connect, with the FQDN set to the server's real FQDN and Exchange Server enabled on the authentication tab and on the permissions groups tab of the default receive connector.

Simon.
JPD153Author Commented:
I had a smart host on the source but removed it before the migration.
I had to put on the destination server since it is used t filter outgoing emails. Could that be the problem since it deals with outgoing on the destination and not incoming ? Also I have put the IP of the source server into the accepted senders in teh destination server as well.
Simon Butler (Sembee)ConsultantCommented:
You should have no smart hosts configured anywhere in the SMTP virtual server on the source.
You should also check the connection properties to ensure the new server is listed.

I would also telnet to the other server (both ways) and ensure that you get a connection. This is classic inference or SMTP being blocked.

Simon.
JPD153Author Commented:
And now to help things even more, the source server shuts down every 2 hours when the migration toll says I still have 15 days to deal with the process.
Simon Butler (Sembee)ConsultantCommented:
That would suggest that either the patch at the start didn't take effect properly or you have taken longer than you think.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JPD153Author Commented:
Hi Simon
I eventually removed Exchange and DCpromoed down the source and all seems to be working OK now. Those public folder replicas nver came through though and it does not seem to affect much of anything.
I really appreciated yor assistance - It was the worst migration I went through.
Wish i could allocate you more than the 500 measly points you are getting for this one.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.