Set-AdServerSettings -ViewEntireForest $true Прерывание сценария при установки первого сервера Exchange 2016 в дочерний домен
https://social.technet.microsoft.com/Forums/ie/en-US/9a585e65-563d-4fa6-bca6-a5a59b379c3f/install-exchange-2016-cu2-fails-in-child-domain-arbitration-mailbox?Ask a question
ign in to vote
I know this is a *very* late reply, but just wanted to add my 2 cents. I ran into the same error during installation of Exchange 2016 CU2 in a child domain, with an existing Exchange 2010 installation.
The problem is that Get-Mailbox -Arbitration doesn't return any results, as they are located in the root domain - this is by design. The solution was to run Set-AdServerSettings -ViewEntireForest $true. Now run Get-Mailbox -Arbitration again, it should show the bb58... system mailbox and 3 others. If so, run setup again.
Asked by:
25
Points
Top 30
LiveBTW83
Joined Dec 2012
4
LiveBTW83's threads
Show activity
Install Exchange 2016 CU2 fails in Child Domain - Arbitration mailbox
Exchange Server
>
Exchange Server 2016 - Setup, Deployment, Updates and Migration
Question
Question
Sign in to vote
0
Sign in to vote
Hello,
I am trying to upgrade from Exchange 2010 SP3 CU14 to 2016 CU2.
We have a root domain and a child domain. The Exchange 2010 arbitration mailboxes are created in the root domain.
The schema is extended for 2016, I prepared AD and the domain.
When I run the Exchange 2016 install, the install fails at the step 9 of 13: Mailbox Role: Mailbox Service with the following error message.
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
{
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
{
$sysMbx = $null;
$name = "SystemMailbox{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
{
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
{
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
{
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
}
}
}
else
{
if ($mbxs[0].DisplayName -ne $dispName )
{
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
}
$sysMbx = $mbxs[0];
}
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
{
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
}
else
{
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
}
}
else
{
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
}
}
" was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't find recipient "domain.local/Users/SystemMailbox{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}". Reason: domain.local/Users/SystemMailbox{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
isn't a mailbox user.
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Func`2 notFoundError, Func`2 multipleFoundError, ExchangeErrorCategory
errorCategory)
at Microsoft.Exchange.Management.SystemConfigurationTasks.OfflineAddressBookTaskUtility.ValidateGeneratingMailbox(IConfigDataProvider session, MailboxIdParameter generatingMailboxId, CategorizedGetDataObjectDelegate getAdUser, OfflineAddressBook
target, TaskWarningLoggingDelegate writeWarning, TaskErrorLoggingDelegate writeError)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOfflineAddressBookInternal.StampChangesOn(IConfigurable dataObject)
at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOfflineAddressBookInternal.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
The user account used to install exchange is domain admin (child domain), enterprise admin, schema admin.
Should I install Exchange with a domain admin account in the root domain ?
Thanks,
Edited by LiveBTW83 Thursday, September 1, 2016 10:47 PM
Wednesday, August 31, 2016 6:39 PM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
All replies
Question
Sign in to vote
0
Sign in to vote
I think it's because I also need to prepare the root domain since it contains the arbitration mailboxes.
I am going to test it but if someone can confirm, that would be great.
Thanks,
Wednesday, August 31, 2016 6:55 PM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
Question
Sign in to vote
1
Sign in to vote
I think it's because I also need to prepare the root domain since it contains the arbitration mailboxes.
I am going to test it but if someone can confirm, that would be great.
Thanks,
You need to domainprep all domains with mail-enabled objects.
Blog: Twitter:
Proposed as answer by Edward van BiljonMVP, Moderator Thursday, September 1, 2016 2:20 PM
Wednesday, August 31, 2016 9:35 PM
Reply
|
Quote
Avatar of Andy David
Andy David
Northwind Traders
(MCC, MVP)
133,780 Points
Moderator
Question
Sign in to vote
0
Sign in to vote
Thanks.
I did it but i still get the same error message "couldn't find recipient".
Any ideas on what could cause this issue ?
Edited by LiveBTW83 Thursday, September 1, 2016 4:05 AM
Thursday, September 1, 2016 4:05 AM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
Question
Sign in to vote
0
Sign in to vote
Please check the setup logs? Also check the other items in this table -
Prepare Active Directory and domains: https://technet.microsoft.com/en-us/library/bb125224(v=exchg.160).aspx#Verify
Install Exchange Server 2016 CU2 Prerequisites Using PowerShell:
http://www.ntweekly.com/?p=12987
Make sure that that mailbox database are pointed to a valid database. Also check Discovery mailbox. As a workaround, recreate the system mailbox and assigned a valid HOMEDB Property in ADSIEDIT.MSC and then run the installation again.
Hope this helps!
Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange
Thursday, September 1, 2016 4:50 AM
Reply
|
Quote
Avatar of nickclark985
nickclark985
3,280 Points
Question
Sign in to vote
0
Sign in to vote
Hi,
I searched around according to error "Skipping creating E15 System Mailbox because of insufficient permission", try the following things:
Open ADSIEdit on child domain, navigate to: CN=SystemMailbox{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, check the proxyAddress attribute, if it's empty, configure it as SMTP:CN=SystemMailbox{1f05a927-169a-4378-aa92-75fee472f2af}@.domain.com.
Note: There are four system mailbox created by default, change the GUID above the not listed one.
Another option is to check HOMEDB attribute for all system mailbox as suggested by nickclark985. If it's empty, you can just remove these system mailbox re-run Ad prepare to recreate them. Then re-run the setup.
Best Regards,
Lynn-Li
TechNet Community Support
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, September 1, 2016 9:12 AM
Reply
|
Quote
Avatar of Lynn-Li
Lynn-Li
24,360 Points
Moderator
Question
Sign in to vote
1
Sign in to vote
Thanks.
The message "Skipping creating E15 System Mailbox because of insufficient permission" is not really the error message. This is just part of the Powershell script that is executed during the update...I don't know why they are not just showing the relevant error message which is
was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't find recipient "domain.local/Users/SystemMailbox{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}". Reason: domain.local/Users/SystemMailbox{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
isn't a mailbox user."
Thursday, September 1, 2016 1:23 PM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
Question
Sign in to vote
0
Sign in to vote
During the install process, it seems like the "Microsoft Exchange Information Store service" service is not started automatically after the default database is created (and the arbitration mailboxes don't have a mailbox available to be mounted).
I rebooted the server and I am trying to complete the install (rerun the setup.exe), I will see how it goes.
If that doesn't work, I will try to uninstall .net framework 4.6.1 (and the hotfix KB3146715) and re-run the install with 4.5.2...
Server\V15\Mailbox\Mailbox Database XXXXXXXXXX" on server "server1.corp.lab.local".
[09/01/2016 15:13:47.0845] [2] Please restart the Microsoft Exchange Information Store service on server server1 after adding new mailbox databases.
[09/01/2016 15:13:47.0845] [2] Ending processing new-mailboxdatabase
Thursday, September 1, 2016 5:30 PM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
Question
Sign in to vote
1
Sign in to vote
Set-ExecutionPolicy Unrestricted solved the issue...
https://blogs.technet.microsoft.com/exchange/2016/06/21/released-june-2016-quarterly-exchange-updates/
Marked as answer by LiveBTW83 Friday, September 2, 2016 4:16 AM
Unmarked as answer by LiveBTW83 Wednesday, September 28, 2016 6:03 PM
Friday, September 2, 2016 4:16 AM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
Question
Sign in to vote
0
Sign in to vote
Now, I am in production. Trying to deploy Exchange 2016 and i have the exact same issue.
The System mailbox is SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}"
ErrorRecord: Couldn't find recipient "costar.local/Users/SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}". Reason: costar.local/Users/SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} isn't a mailbox user.
Wednesday, September 28, 2016 6:07 PM
Reply
|
Quote
Avatar of LiveBTW83
LiveBTW83
25 Points
Question
Sign in to vote
0
Sign in to vote
Hit this too.
LiveBTW83 was wondering if you can recall how things went after you retried the installation?
Did you just reinstall over the failed Exchange install or did you remove and reinstall
Thanks,
Michael
Friday, December 9, 2016 10:47 AM
Reply
|
Quote
Avatar of Micmaher2
Micmaher2
0 Points
Question
Sign in to vote
0
Sign in to vote
I know this is a *very* late reply, but just wanted to add my 2 cents. I ran into the same error during installation of Exchange 2016 CU2 in a child domain, with an existing Exchange 2010 installation.
The problem is that Get-Mailbox -Arbitration doesn't return any results, as they are located in the root domain - this is by design. The solution was to run Set-AdServerSettings -ViewEntireForest $true. Now run Get-Mailbox -Arbitration again, it should show the bb58... system mailbox and 3 others. If so, run setup again.
Peter Van Gils Toa Projects
Thursday, March 2, 2017 1:19 PM
Reply
|
Quote
Avatar of Peter Van Gils_
Peter Van Gils_
835 Points
Question
Sign in to vote
0
Sign in to vote
This worked for me :)
Weirdly after I had done that, I had to run the setup about 3-4 times and it created and enabled to arbitration mailboxes one at a time.
I didn't even think of this so thanks!
Monday, June 12, 2017 1:19 PM
Reply
|
Quote
Avatar of Joseph Fenly
Joseph Fenly
Northumbria University
30 Points
Question
Sign in to vote
1
Sign in to vote
Again, excuse me for the late reply. Hope this will be useful for one's who found this via search. This seems to be a bug in the Exchange 2016 installation in the multi-domain environment, then first installation is made in the child domain. It just fails to find requred user attributes, because they are not relicated yet from child to parent domain controllers. Solutions are re-run setup a lot of times, or install first Exchange 2016 server in the root domain, an then move mailboxes to the child domain and uninstall first exchange server. Quite odd. Details here: https://blogs.technet.microsoft.com/mahuynh/2017/06/16/setup-of-first-exchange-2016-server-fails-in-a-child-domain-due-to-ad-replication/
Из ослиного гнезда ... :)
Edited by bazanovv Saturday, July 21, 2018 6:37 PM
Saturday, July 21, 2018 6:35 PM
Reply
|
Quote
Avatar of bazanovv
bazanovv
SO UPS
110 Points
© 2019 Microsoft. All rights reserved.
Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback
Комментарии
Отправить комментарий