We have setup our Exchange 2013 server, and setup CAS and outlook anywhere
etc, using the 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!

Reply via email to