The unlicensed account originates from the Account Forest, the blocked account originates from the Resource Forest. When Azure AD Connect kicks in you’ll see two user accounts appear in Office 365 for this user.
Let’s give it a try…Ĭreate two users, one regular account in the Account Forest and one disabled account (acting as a placeholder) in the Resource Forest. The problem however is to connect the user account in the Account Forest with the disabled account in the Resource Forest. The Enable-RemoteMailbox PowerShell command seems like a much more efficient way to provision Mailboxes in Office 365. Enable-RemoteMailbox in a Resource Forest with ADSI Edit (Not Supported) Now we can move this Mailbox to Office 365, but it’s not the most efficient way to create new Mailboxes, especially when the new Mailboxes should be created in Azure Active Directory.
With commands shown in the previous blog on Linked Mailboxes we can check the objectSID and the MsExchMasterAccountSID:Īzure AD Connect will make sure (just like in the previous blog posts) based on the objectSID and MsExchMasterAccountSID that the new user account and mailbox information will be synchronized with Azure Active Directory and it will appear in the Office 365 address book. So, the command to create the Linked Mailbox and user the user account we’ve just created in the Accounts Forest should be: Get-User C.smith | Enable-Mailbox -LinkedCredential $AccountsCred -LinkedDomainController -LinkedMasterAccount "C.Smith" This is PowerShell 2.0 and generates an error when importing the Active Directory module.
#CREATE SHARED MAILBOX EXCHANGE 2010 WINDOWS#
You can also execute Import-Module ActiveDirectory in an Exchange Management Shell window on the Exchange server, but my Exchange 2010 server is running on Windows 2012. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Authentication Kerberos -Credential $AdminCred This should be executed in the Exchange Management Shell, but you can also start a Remote PowerShell session in the current regular PowerShell window using the following commands: $AdminCred = Get-Credential resources\administrator To create a new Linked Mailbox for this user account, we can execute the Enable-Mailbox with the -LinkedDomainController and -LinkedMasterAccount options against this new user account in the Resource Forest.
Next is to create a similar, but disabled user account in the Resource Forest by executing the following command: New-ADUser -Name "C.Smith" -Server -UserPrincipalName -GivenName Clyde -Surname Smith -DisplayName "Clyde Smith" -Path "OU=Users,OU=NL,DC=Resources,DC=Local" -AccountPassword $Password -Enabled:$FALSE This will create a new user account in the Accounts Forest. New-ADUser -Name "C.Smith" -Server -Credential $AccountsCred -UserPrincipalName -GivenName Clyde -Surname Smith -DisplayName "Clyde Smith" -Path "OU=Users,OU=NL,DC=Accounts,DC=Local" -AccountPassword $Password -Enabled:$TRUE $Password = ConvertTo-SecureString -String -AsPlainText -Force $AccountsCred = Get-Credential Accounts\administrator The most basic option to do this is to execute the following commands in PowerShell on a Domain Controller in the Resource Forest: Import-Module ActiveDirectory To provision a Linked Mailbox a new user account in the Account Forest need to be created and a (somewhat) identical, but disabled user account need to be created in the Resource Forest. I’ll show you the unsupported way using ADSI Edit (for educational purposes) and the supported way to achieve this.
#CREATE SHARED MAILBOX EXCHANGE 2010 HOW TO#
In this blogpost I will show you how to manually create Linked Mailboxes and the accompanying user accounts and how to create a Linked Mailbox, but directly in Office 365. In a Resource Forest model you will run into some issues though…. In a normal, single forest environment you would create a new user in Active Directory and execute the Enable-RemoteMailbox command in Exchange PowerShell to directly create a Mailbox in Office 365. In the past three blogposts I’ve showed you the basics of Linked Mailboxes in a Resource Forest, how to implement Azure AD Connect is this environment and how to setup Exchange Hybrid in a Resource Forest model.Īnother challenge is how to provision users in a Resource Forest setup, especially when it comes to provisioning mailboxes directly in Office 365.
0 kommentar(er)
