asked on PowerShell help with Exchange 2010 AddressBook
So I have an SBS 2011 with Exchange 2010 in a company that is trying to keep 2x different groups separate in the contact list from seeing each other. I know in exchange 2013 how to do this, but having problems figuring out how to do it in 2010. In 2013 I would do...
New-AddressList -Name "CompanyName_Users_DGs" -RecipientFilter {((RecipientType -eq 'UserMailbox') -or (RecipientType -eq "MailUniversalDistributionGroup") -or (RecipientType -eq "DynamicDistributionGroup")) -and (CustomAttribute1 -eq "CompanyName")}
New-AddressList -Name CompanyName_Rooms -RecipientFilter {(Alias -ne $null) -and (CustomAttribute1 -eq "CompanyName")-and (RecipientDisplayType -eq 'ConferenceRoomMailbox') -or (RecipientDisplayType -eq 'SyncedConferenceRoomMailbox')}
New-GlobalAddressList -Name "GAL_CompanyName" -RecipientFilter {(CustomAttribute1 -eq "CompanyName")}
New-OfflineAddressBook -Name "OAB_CompanyName" -AddressLists "GAL_CompanyName"
New-AddressBookPolicy -Name "ABP_CompanyName" -AddressLists "CompanyName_Users_DGs","CompanyName_Rooms" -OfflineAddressBook "\OAB_CompanyName" -GlobalAddressList "\GAL_CompanyName" -RoomList "\CompanyName_Rooms"
Get-Mailbox -resultsize unlimited | where {$_.CustomAttribute1 -eq "CompanyName"} | Set-Mailbox -AddressBookPolicy "ABP_CompanyName"
PowershellExchangeSBS
Last Comment
easyworks
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
It appears though when i get to...
New-AddressBookPolicy is not a recognized as the name of a cmdlet.
New-AddressBookPolicy -Name "ABP_MyCompany" -AddressLists "MyCompany_Users_DGs","MyCompany_Rooms" -OfflineAddressBook "\OAB_MyCompany" -GlobalAddressList "\GAL_MyCompany" -RoomList "\MyCompany_Rooms"
New-AddressBookPolicy is not a recognized as the name of a cmdlet.
ASKER
Nevermind found that the exchange server is running SP1!
ASKER
Resolved my own problem.
You don't say, but I am guessing that perhaps one of those commands is not working on the Exchange 2010 box?
Is that correct?
Alan.