Shared Mailbox: Share Contacts Exchange 2013

I'm using Exchange 2013 and I've got several shared mailboxes setup. I've added contacts to those mailboxes. We are using Outlook 2013 and we can access the shared mailboxes just fine, but I don't know how to make the contacts show up in the Global Address
List
This is the windows that opens when adding contacts to an email. The only way i can see the contacts is by going over to the People tab.
I've tried right-clicking the share contacts but it's grayed out for all my shared mailboxes.
What am i doing wrong? Thanks for any help!

Same issue here.
It is possible to create contacts under a shared mailbox but the user cannot choose any addres because it is not shown as an address book
I had
[email protected]
Contact
A own created list
Global Address List
All Address list
All contacts
All Groups
All Rooms
All Users
Public Folders
For a personal contactlist there is a tab 'Outlook Address Book' where i can choose "Show this folder as an e-mail Address Book". This tab is not available for an shared mailbox contactlist.
It seems not possible at all, any information about this can not be found (at least not by me)

Similar Messages

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Configure legacy public folders where user mailboxes are on Exchange 2013 servers

Hello all,
I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over. I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?). The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
on the 2013 server, using the mailbox name I had created, it says it cannot be found. Of course I checked and the mailbox exists, is configured properly, and so is the new database. The 2013 EAC also sees the mailbox with no issues.
Can someone tell me why I am getting this error?
Thanks,
Shaibal

Hi Mavis,
Thank you for your response. I am the full domain admin, and check and was part of both groups mentioned above. Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
-PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
Below is the error I get:
[PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
    + CategoryInfo          : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
    4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetOrganizationConfig
    + PSComputerName        : zor-exchange01.zubatkin.lan

Error Installing Step 10 of 12 Mailbox roles: Mailbox service on Exchange 2013 CU2

Step 10 of 12 Mailbox roles: Mailbox service
Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
            $createNewOab = $false;
            $oabName = $null;
            $oabAddressList = $null;
            $oabVdirs = $null;
            $oabGlobalWebDistribution = $false;
            $oabConfiguredAttributes = $null;
            Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
            $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
            if ($defaultOab -ne $null)
              Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + ";
checking its version");
              if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
-lt 0)
                $e15Oab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
-eq 0};
                if ($e15Oab -eq $null)
                  Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older;
will create a new OAB");
                  $createNewOab = $true;
                  $oabName = $defaultOab.Name + " (Ex2013)";
                  $oabAddressList = $defaultOab.AddressLists;
                  $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                  $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
                else
                  Write-ExchangeSetupLog -Info ("Already has an existing Exchange 2013
OAB:" + $e15Oab.Name + "; will not create a new OAB");
              else
                Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2013 or newer; will not
create a new OAB");
            else
              Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
              $createNewOab = $true;
              $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
              $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController
-ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
              if ($nonDefaultOabWithDefaultName -ne $null)
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Offline address book " + `
                  $nonDefaultOabWithDefaultName.Name + `
                  " already exists: " + `
                  $nonDefaultOabWithDefaultName.DistinguishedName + `
                  ". Use administrative tools to change it to default OAB.");
              $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
              if ($allGals -eq $null -or $allGals.Count -eq 0)
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Couldn't find the default global address list. The default offline
address book can't be created.");
              elseif ($allGals.Count -gt 1)
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Found " + $allGals.Count + " default global address
lists. You can have only one default global address list in your organization. The default offline address book will not be created.");
              else
                $oabAddressList = $allGals[0];
                Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
            if ($createNewOab)
              if ($oabGlobalWebDistribution -eq $false)
                $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                $allOabVdirs = @(Get-OabVirtualDirectory -DomainController:$RoleDomainController);
                $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                  foreach ($oabVdir in $allOabVdirs)
                    if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion,
$e15MinimumServerVersion) -gt 0)
                      $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server
-DomainController:$RoleDomainController).Site.DistinguishedName;
                      if ($oabVdirSiteDn -eq $currentAdSiteDn)
                        $oabVdirs = $oabVdir;
                        break;
                      elseif ($oabVdirs -eq $null)
                        $oabVdirs = $oabVdir;
                if ($oabVdirs -ne $null)
                 Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual
directory " + $oabVdirs.Name);
                else
                  Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories;
OAB will be configured without distribution.");
              try
                Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                $newOab = New-OfflineAddressBook `
                  -Name $oabName `
                  -AddressLists $oabAddressList `
                  -VirtualDirectories $oabVdirs `
                  -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                  -IsDefault $true `
                  -DomainController:$RoleDomainController;
              catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
                Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object
already exists; it may have been created by another instance of setup.");
              if ($oabConfiguredAttributes -ne $null)
                Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " +
$oabConfiguredAttributes);
                Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
        " was run: "Cannot find an overload for "CompareTo" and the argument count: "1".".

so we're having the same issue. Installing Exchange 2013 across 2 sites in a coexistence 2007/2010 environment. Everything on one site (3x Exchange servers) installed perfectly, but only 1x Exchange servers on other site installed. Remaining 2x Exchange
servers gave the same error that Harry had. Any ideas? I checked OAB and all mailboxes had a default OAB assigned already. looked through the logs and found this in case it helps:
[02/13/2015 22:37:31.0105] [2] Found a default OAB: Default Offline Address List (Ex2013) Default Offline Address List (Ex2013)
CNF:608015af-50a4-450a-0000-91fada1a9af9; checking its version
[02/13/2015 22:37:31.0120] [2] Ending processing Write-ExchangeSetupLog
[02/13/2015 22:37:31.0151] [1] The following 1 error(s) occurred during task execution:
[02/13/2015 22:37:31.0151] [1] 0. ErrorRecord: Cannot find an overload for "CompareTo" and the argument count: "1".
[02/13/2015 22:37:31.0151] [1] 0. ErrorRecord: System.Management.Automation.MethodException: Cannot find an overload for "CompareTo" and the argument count: "1".
at CallSite.Target(Closure , CallSite , Object , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[02/13/2015 22:37:31.0151] [1] [ERROR] The following error was generated when "$error.Clear();
if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
$createNewOab = $false;
$oabName = $null;
$oabAddressList = $null;
$oabVdirs = $null;
$oabGlobalWebDistribution = $false;
$oabConfiguredAttributes = $null;
Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
$defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
if ($defaultOab -ne $null)
Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + "; checking its version");
if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -lt 0)
$e15Oab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -eq 0};
if ($e15Oab -eq $null)
Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older; will create a new OAB");
$createNewOab = $true;
$oabName = $defaultOab.Name + " (Ex2013)";
$oabAddressList = $defaultOab.AddressLists;
$oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
$oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
else
Write-ExchangeSetupLog -Info ("Already has an existing Exchange 2013 OAB:" + $e15Oab.Name + "; will not create a new OAB");
else
Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2013 or newer; will not create a new OAB");
else
Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
$createNewOab = $true;
$oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
$nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
if ($nonDefaultOabWithDefaultName -ne $null)
$createNewOab = $false;
Write-ExchangeSetupLog -Warning `
("Offline address book " + `
$nonDefaultOabWithDefaultName.Name + `
" already exists: " + `
$nonDefaultOabWithDefaultName.DistinguishedName + `
". Use administrative tools to change it to default OAB.");
$allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
if ($allGals -eq $null -or $allGals.Count -eq 0)
$createNewOab = $false;
Write-ExchangeSetupLog -Warning `
("Couldn't find the default global address list. The default offline address book can't be created.");
elseif ($allGals.Count -gt 1)
$createNewOab = $false;
Write-ExchangeSetupLog -Warning `
("Found " + $allGals.Count + " default global address lists. You can have only one default global address list in your organization. The default offline address book will
not be created.");
else
$oabAddressList = $allGals[0];
Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
if ($createNewOab)
if ($oabGlobalWebDistribution -eq $false)
$currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
$allOabVdirs = @(Get-OabVirtualDirectory -ADPropertiesOnly -DomainController:$RoleDomainController);
$e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
foreach ($oabVdir in $allOabVdirs)
if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion, $e15MinimumServerVersion) -gt 0)
$oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server -DomainController:$RoleDomainController).Site.DistinguishedName;
if ($oabVdirSiteDn -eq $currentAdSiteDn)
$oabVdirs = $oabVdir;
break;
elseif ($oabVdirs -eq $null)
$oabVdirs = $oabVdir;
if ($oabVdirs -ne $null)
Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual directory " + $oabVdirs.Name);
else
Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories; OAB will be configured without distribution.");
try
Write-ExchangeSetupLog -Info ("Creating new default OAB.");
$newOab = New-OfflineAddressBook `
-Name $oabName `
-AddressLists $oabAddressList `
-VirtualDirectories $oabVdirs `
-GlobalWebDistributionEnabled $oabGlobalWebDistribution `
-IsDefault $true `
-DomainController:$RoleDomainController;
catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object already exists; it may have been created by another instance of setup.");
if ($oabConfiguredAttributes -ne $null)
Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " + $oabConfiguredAttributes);
Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
" was run: "Cannot find an overload for "CompareTo" and the argument count: "1".".
[02/13/2015 22:37:31.0151] [1] [ERROR] Cannot find an overload for "CompareTo" and the argument count: "1".
[02/13/2015 22:37:31.0167] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___b06ea38070354e2c9f0000c2b971306a Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[02/13/2015 22:37:31.0167] [1] Setup is stopping now because of one or more critical errors.
[02/13/2015 22:37:31.0167] [1] Finished executing component tasks.
[02/13/2015 22:37:31.0214] [1] Ending processing Install-MailboxRole

Shared mailbox from field (exchange 2007)

Hi there,
I am not sure if this is the right forum to ask this question, but couldn't think of anywhere else.
My team at work has a normal exchange account and a shared mailbox they have access to. If you log on to outlook, you see 2 information stores - one for your personal mailbox and one for the shared mailbox.
If I reply from my personal mailbox, the from field gets correctly populated with my name, but when I reply to an email from the shared mailbox the from field gets populated with the shared mailbox email address, which we don't have permission to use, so
emails bounce if we do not manually change the from field.
We developed a vba solution to automatically do this for us but I was wondering if this can be somehow switched on the exchange side of things/
Does anyone know if there is?
Thanks,
B.

Hi
You can not control this behaviour from Exchange. This is controlled by Outlook.
Outlook chooses the from address from what additional mailbox you are replying from (just as you see :-))
There are a lot of registry tweaks for Outlook, but I don't think there are one to control this.
I see 3 possible sollutions.
1. The users can choose them self
2. You give the users "Send As" permissions on the mailbox
3. you use this tool
http://www.ivasoft.biz/setfrom2013.shtml
BR
Steen

Cannot edit/create new mailbox in ECP - Exchange 2013 CU6

Hello, I am currently running Exchange 2013 CU6. I cannot perform tasks related to recipients such as edit/create new mailbox. Additionally I cannot view the properties of the virtual directories.
I tried multiple browsers (Chrome, Firefox, IE) in different PCs and the result is the same
For example, I cannot click "Browse" in "new user mailbox" tab
"New local Mailbox move" page displays blank
I browsed through the event logs and found the following errors (Event 4 and Event 21):
Event 4
Current user: 'Unauthenticated'
Request for URL 'https://mailserver.address..com:444/ecp/15.0.995.28/scripts/js.axd?resources=NewMigrationBatch&v=15.0.995.28&c=en-US(https://mailserver.address..capcx.com/ecp/15.0.995.28/scripts/js.axd?resources=NewMigrationBatch&v=15.0.995.28&c=en-US)'
failed with the following error:
Microsoft.Exchange.Management.ControlPanel.BadRequestException:
The request sent by your browser was not valid. ---> Microsoft.Exchange.Management.ControlPanel.BadRequestException: The request sent by your browser was not valid. --->
System.Exception: 'ToolkitScriptManager' could not generate combined script resources file.
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at
System.Web.HttpApplication.ExecuteStep(IExecutionStepstep, Boolean&
completedSynchronously)
   at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at
System.Web.HttpApplication.ExecuteStep(IExecutionStepstep, Boolean&
completedSynchronously)
Microsoft.Exchange.Management.ControlPanel.BadRequestException:
The request sent by your browser was not valid. ---> System.Exception: 'ToolkitScriptManager' could not generate combined script
resources file.
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
System.Exception: 'ToolkitScriptManager'
could not generate combined script resources file.
Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance,
False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration,
True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging,
True],[Eac.CrossPremiseMigration, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch,
False],[Eac.DiscoverySearchStats, False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled,
False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups,
False],[Eac.Office365DIcon, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports, False],[Eac.UCCPermissions,
False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy, False],[Eac.UnlistedServices,
False],], Flights:[], Constraints:[[MACHINE, SERVER-NAME],[MODE, ENTERPRISE],[PROCESS, W3WP],],
IsGlobalSnapshot: True
Event 21
Current user: 'Unauthenticated'
Script request for URL 'https://mailserver.address.com:444/ecp/15.0.995.28/scripts/js.axd?resources=NewMigrationBatch&v=15.0.995.28&c=en-US(https://mailserver.address.com/ecp/15.0.995.28/scripts/js.axd?resources=NewMigrationBatch&v=15.0.995.28&c=en-US)'
failed with the following error:
Microsoft.Exchange.Management.ControlPanel.BadRequestException:
The request sent by your browser was not valid. ---> System.Exception: 'ToolkitScriptManager' could not generate combined script
resources file.
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
   at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
System.Exception: 'ToolkitScriptManager'
could not generate combined script resources file.
Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance,
False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration,
True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging,
True],[Eac.CrossPremiseMigration, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch,
False],[Eac.DiscoverySearchStats, False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled,
False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups,
False],[Eac.Office365DIcon, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports, False],[Eac.UCCPermissions,
False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy, False],[Eac.UnlistedServices,
False],], Flights:[], Constraints:[[MACHINE, SERVER-NAME],[MODE, ENTERPRISE],[PROCESS, W3WP],],
IsGlobalSnapshot: True
Any help?

Hello Amy,
I will try to follow your suggestions. I will update once I get access to the server.
Anyways, the whole thing was back to normal for 1 day on its own, but right now the issue is happening again. Permission-wise, the account I used is in listed Organization Management role
Update: I forgot to try the EMS, but after I recycle the
MSExchangeECPAppPool, everything works fine, except for viewing Groups and Permissions
An error in the event viewer is displayed:
Current user: 'Unauthenticated'
Script request for URL 'https://address.com:444/ecp/15.0.995.28/scripts/js.axd?resources=EditRoleAssignmentPolicy&v=15.0.995.28&c=en-US(https://address.com/ecp/15.0.995.28/scripts/js.axd?resources=EditRoleAssignmentPolicy&v=15.0.995.28&c=en-US)'
failed with the following error:
Microsoft.Exchange.Management.ControlPanel.BadRequestException: The request sent by your browser was not valid. ---> System.Exception: 'ToolkitScriptManager' could not generate combined script resources file.
--- End of inner exception stack trace ---
at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
at Microsoft.Exchange.Management.ControlPanel.CombineScriptsHandler.ProcessRequest(HttpContext context)
System.Exception: 'ToolkitScriptManager' could not generate combined script resources file.
Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance, False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration, True],[Eac.AllowRemoteOnboardingMovesOnly,
False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging, True],[Eac.CrossPremiseMigration, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch, False],[Eac.DiscoverySearchStats, False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled,
False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups, False],[Eac.Office365DIcon, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports, False],[Eac.UCCPermissions, False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy,
False],[Eac.UnlistedServices, False],], Flights:[], Constraints:[[MACHINE, SERVER-NAME],[MODE, ENTERPRISE],[PROCESS, W3WP],], IsGlobalSnapshot: True
However, after a while, things are back to normal... I don't understand what's happening..

Mailboxes migrated to Exchange 2013 - some Outlook profiles do not auto-update

** EDIT WITH SIMPLIFIED QUESTION:
Should I be able to manually create a profile in my Exchange 2013 environment without knowing the
GUID@DOMAIN server name? When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest. I am curious whether others are able to manually
create a profile without knowing the GUID@domain.
Hi all,
Our computers have Outlook configured to automatically configure a profile without any intervention. The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013. When a user logs into a computer and
launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.
I have verified that the Outlook Anywhere settings are configured correctly.
If I delete the profile and create a new one using Autodiscover, everything works fine.
Occurs on all clients - 2007, 2010, 2013, fully patched).
To troubleshoot, I attempted to manually create a new profile. I supplied the Exchange 2010 server name, and configured Outlook Anywhere. When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to
[email protected]). When I launch Outlook, the connection fails. Again, an autodiscovery succeeds.
From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect. The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names.
Any ideas?
Thanks for your hel

Thanks for the reply .
AutodiscoverInternalURI is pointing to the Exchange 2013 environment, and is working fine when auto creating the profile. The Test Autodiscover function returns the correct URL for the mailboxes. The problem comes when manually creating
a profile. Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected, but mine remains with the Ex2010 cas name listed on the database, and the creation fails.
However, if the user had previously connected to Ex2010 prior to the mailbox move, the profile successfully changes to Ex2013. Only during manual creation does it fail, which is a problem because our existing PCs are configured to create
profiles without autodiscover.

Free/Busy not working after mailbox migration to Exchange 2013

I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated. If we remove the Outlook profile and recreate it, all is good. Problem is that this is happening to more and more people. Everyone
is on Outlook 2010
Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
Autodiscover: Outlook Provider Failure
Exchange Web Services          Failure
Availability Service           Skipped
Offline Address Book           Failure
The same if I run that command against the Exchange 2007 server.
What am I doing wrong?

I should have mentioned that. Yes, OWA works perfectly for the affected users. Just as deleting their Outlook profile and recreating a new one does.
Results of Get-WebServicesVirtualDirectory:
Identity    : Exch2007Srvr\EWS (Default Web Site)
InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
Identity    : Exch2013Srvr\EWS (Default Web Site)
InternalUrl : https://mail.company.com/ews/exchange.asmx
ExternalUrl : https://mail.company.com/ews/exchange.asmx
The URL you reference above is actually the site I used to perform migration.
What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
get:
Attempting URL
https://mail.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml starting
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
Attempting URL
https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=200.
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
GetLastError=12029; httpStatus=0
Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=0
GetLastError=0; httpStatus=200
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
Local autodiscover for company.local starting
Local autodiscover for company.local Failed (0x8004010F)
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
Srv Record lookup for hydraforce.ads starting
Srv Record lookup for hydraforce.ads Failed(0x8004010F)
However, when I did this on a system that cannot see any calendars, it all works perfectly.
Browsing to
https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013

Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman

Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman
Does simply recycling the ActiveSync app pool speed things up?
Also, I would recommend installing CU6 instead of SP1.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Litigation Hold Mailbox Migration to Exchange 2013

Hello,
We have in our organization few mailboxes (Exchange 2010) which are enabled for Litigation Hold for a purpose. Now since we are moving to Exchange 2013, need to understand what happens to those mailboxes after migration.
Neilesh

Hi Neilesh,
Below cmdlet would give you the actual mailbox size including the deleted items(changed hold items etc)
Get-MailboxFolderStatistics -Identity contoso\chris | Select Name,FolderSize,ItemsinFolder
Recoverable Items 127.5 KB (130,553 bytes) 54
Deletions 0 B (0 bytes) 0
Purges 0 B (0 bytes) 0
Versions 0 B (0 bytes) 0
Reference:
Reporting Mailbox Folder Sizes with PowerShell
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

FIM Synchronization Repeat Contacts Exchange 2013 and 2010

Hey how are you?
actualemnte story with FIM
Synchronization 2010 R2
I have two organizations:
Oraganizacion 1:
Exchange 2013 S1
FIM Server
organization 2
Exchange 2010 Sp3
contacts organization number two
is possible to see them in organizavion
number one
the downside is trying to sincornizar
repeatedly contacts the organization towards each
organization's number two being
repeated and causes problems with users.
repeated contact:
contact.dominio.com
contact1.dominio.com
contact3.dominico.com
I can do ??

Hi Dominik,
thanks for pointing number 2 out :)
For my Problem on the Exchange:
I get the Event ID 12 in the Application log with:
The Forefront Identity Manager Service cannot connect to the Exchange Web Service.
In the FIM Log I find:
System.Web.Services: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote
host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
This leads me to
http://social.technet.microsoft.com/Forums/en-US/7697048b-3cf1-48ce-a8eb-b5c51104c279/error-connecting-to-exchange-2010?forum=ilm2 . This guy seems to have the same error. But I don't know exactly what he changed in IIS. As a said, my Certificate chain
is OK.
Do you have some resource for me, where to start to get rid of this?
Thanks a lot,
Martin
www.sccmfaq.ch

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Shared mailbox access from exchange 2003 to 2010 users

We'd successfully migrated from exchange 2003 to 2010. still some of the users are yet to be migrate.
The issue is only in MAC (Apple) Migrated users was unable to access the shared folder residing in 2003 environment.
but the migrated 2010 users are able to access the shared folders in the windows environment.
Any one can assist or suggest this issue.
Awaiting for ur reply.
Regards
kart26

Hi Kart26,
Please install certificate in your MAC App Client.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 users cannot open Exchange 2013 shared mailbox

Title says it all.
We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
Is this just how it is, or is there a way around it?

Hi,
I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Shared Mailbox: Share Contacts Exchange 2013

Similar Messages

Maybe you are looking for