So they gave up on getting PF migration to work?

Did they give you a reason why?

From: [email protected] [mailto:[email protected]] On 
Behalf Of Graeme Carstairs
Sent: Wednesday, April 2, 2014 11:31 AM
To: [email protected]
Subject: Re: [Exchange] Re: Exchnage 2007 to 2013 migration threw up public 
folder issue

Nithing I think its just the current name for it.

Latest is we moved the mailboxes and are now exporting the public folders via 
outlook to pst.

We will then mount up a new public folder DB and reimport the PF's from PST via 
outlook into the Exchnage 2007

then we migrate them to 2013

This is all on a new ticket

Graeme


On 28 March 2014 18:00, J- P <[email protected]<mailto:[email protected]>> 
wrote:
Didn't even know that existed, what is the difference between that and PSS?


Jean-Paul Natola


________________________________
Date: Fri, 28 Mar 2014 15:18:56 +0000

Subject: Re: [Exchange] Re: Exchnage 2007 to 2013 migration threw up public 
folder issue
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>

It was the commercial support team on 
http://support.microsoft.com/gp/commercialsupport#u

I was refunded for this incident.

Bbut I will be charged for their help when the PF migration fails.

Graeme


On 28 March 2014 14:25, Michael B. Smith 
<[email protected]<mailto:[email protected]>> wrote:

I hope you requested a refund. That isn't a resolution!



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Graeme Carstairs
Sent: Thursday, March 27, 2014 12:56 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [Exchange] Re: Exchnage 2007 to 2013 migration threw up public 
folder issue



In case anyones interested



MS PSS tried to fix it,



They can get a new PF databse mounted and visible form client and server but 
when you mount the original one its only visible from client.



They have closed the case and suggested I continue with my migration, and when 
I get to the PF's if it doesn tmove to contact them and they will assist then.



Graeme





On 26 March 2014 09:25, Graeme Carstairs 
<[email protected]<mailto:[email protected]>> wrote:

Tried that,



no change



Need to get this resolved so placing a call with PSS.



Thanks



Graeme





On 25 March 2014 19:04, Graeme Carstairs 
<[email protected]<mailto:[email protected]>> wrote:

They were replicated from a 2003 years ago and my thoughts are that the 2003 
wasn't removed properly

Just found in adsiedit that the of hierarchy is in first administrative group

Moved that waiting on ad replication then gonna restart server and see where we 
are



Thanks

On Tuesday, 25 March 2014, Michael B. Smith 
<[email protected]<mailto:[email protected]>> wrote:

This looks an awful lot like you moved the PF root from the old Admin group to 
the new Admin group before you migrated the folders.



What else have you done with PFs?



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Graeme Carstairs
Sent: Tuesday, March 25, 2014 6:38 AM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] Exchnage 2007 to 2013 migration threw up public folder issue



We have setup our Exchange 2013 server, and setup CAS and outlook anywhere etc, 
using the legacy.domain.com<http://legacy.domain.com> setup on as detailed on 
the MS site.

Mail flow and outlook connections seems to be working great.

If I connect to OWS from outside or inside, I get the 2013 login page, login 
with a mailbox on the 2013 server, I get the 2013 OWA. Login with a mailbox on 
the 2007 server I get the 2007 OWA, as expected

I have moved a couple of mailboxes over, and they are working fine from OWA but 
when using outlook, users are constantly prompted for their password.

If they cancel this or ignore it outlook works fine until they try and access 
the public folders, which as still on the 2007 server.

Then they get "folder cannot be expanded" errors.

Googling shows this to be an issue with outlook on Windows XP but not Windows 7,

the clients all have windows 7,.

the solution was to download and install SP1, which I have done, in the hope 
that it may fix the issue. It hasnt

It looks to me like the connection to the 2013 box is fine, but when it tries 
to connect to the 2007 for the public folders that authentication does not work.

So rather than spend a long time trying to resolve this I  decided to press 
ahead and complete the migration.

So started prepping the PF migration

When I try to get the list of PFs from the 2007 server using this command



Get-PublicFolder -Recurse | Export-CliXML C:\PFMigration\Legacy_PFStructure.xml



I get the following error



Get-PublicFolder : Cannot find PublicFolderLocalReplica objects from the root ' 
2007server\Second Storage Group\Public Folder Database'. Please make sure that 
you specified the correct search root and that you have the correct permissions 
to perform the search.



At line:1 char:17



+ Get-PublicFolder <<<<  -Recurse | Export-CliXML 
f:\PFMigration\Legacy_PFStructure.xml  + CategoryInfo : NotSpecified: (0:Int32) 
[Get-PublicFolder], Mapi ObjectNotFoundException + FullyQualifiedErrorId 
:256AAB27,Microsoft.Exchange.Management.MapiTasks .GetPublicFolder





I think this may be part of the issue with the proxying but its also going to 
make migration a tad difficult.



Any ideas?



--
Good news everyone, you have just received an e-mail from me!


--
Good news everyone, you have just received an e-mail from me!





--
Good news everyone, you have just received an e-mail from me!





--
Good news everyone, you have just received an e-mail from me!



--
Good news everyone, you have just received an e-mail from me!



--
Good news everyone, you have just received an e-mail from me!

Reply via email to