I was told today that they wouldn't mind a new name for their external OWA address and so the co-existence stuff isn't necessary anymore. Can't say I'm mortified by this news...
On Friday we managed to get through to the installation of SP2 and so I didn't have a great deal to do. The ESM presented me with a long terrifying error but was ok after a reboot. I put on RU5v2 and begun public folder replication:
.\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
I will return to this company to remove the old public folders. I will probably run (to hurry it up):
Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
To get rid of the replicas on the old server:
.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
To check on the progress:
Get-PublicFolder -recurse |fl name,replicas
Get-PublicFolder -recurse \non_ipm_subtree |fl name, replicas
Get-PublicFolderStatistics
The Exchange server's certificate was replaced by a wildcard certificates, which seem to simplify everything a lot over SAN certificates. There must be a catch.
The setting of the "legacy" URL was now uneccessary.
On Friday we managed to get through to the installation of SP2 and so I didn't have a great deal to do. The ESM presented me with a long terrifying error but was ok after a reboot. I put on RU5v2 and begun public folder replication:
.\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
I will return to this company to remove the old public folders. I will probably run (to hurry it up):
Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
To get rid of the replicas on the old server:
.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
To check on the progress:
Get-PublicFolder -recurse |fl name,replicas
Get-PublicFolder -recurse \non_ipm_subtree |fl name, replicas
Get-PublicFolderStatistics
The Exchange server's certificate was replaced by a wildcard certificates, which seem to simplify everything a lot over SAN certificates. There must be a catch.
The setting of the "legacy" URL was now uneccessary.
Set-OwaVirtualDirectory -Identity "esp-ho-ex2010a\owa (Default Web Site)"
-Exchange2003Url https://legacy.crapulent.net/exchange
And there was no need to enable forms based authenication on the 2003 server, or for installing the Activesync hotfix to enable kerberos between the two servers.
The first Activesync test failed because of the domain admin protected group issue.
Other than that, job done for now.
No comments:
Post a Comment