ITEXVN

  Script để remove hàng loạt proxy address đã tạo bởi Email Addresss Polices trong Exchange. Lý do là Email Address Policies chỉ có tác dụng add thêm, không có tác dụng remove proxy address, nên cần script này để gỡ. ============================== Get-ADUser -Properties proxyaddresses -Filter {ProxyAddresses -like '*@xxxxx.vn'} |     ForEach { # Account may have more than one email address in scope so need to loop through each one         ForEach ($proxyAddress in $_.proxyAddresses) {             If ($proxyAddress -like '*@xxxxxx.vn') {                 # Write-Host $proxyAddress                 Set-ADUser $_.SamAccountName -Remove @{ProxyAddresses=$proxyAddress}                                 }         }         ...

  https://www.stellarinfo.com/blog/use-search-mailbox-export-to-pst-in-exchange-server/ An Exchange database can be a storehouse of thousands of user mailboxes. Often, situations arise that demand database administrators (DBAs) to perform various operations on these mailboxes, such as exporting them to a PST format. It may be required to create a backup of the mailbox or migrate the mailbox to another server or Outlook account. Further, DBAs might require to export mailbox to PST in a complex situation such as following, “When setting up email forwarding, an error in the settings resulted in the sender’s mailbox not having any copy of the forwarded emails. To rectify this mistake, the user wanted to receive back all the mails sent out during the forward.” In a situation like this, DBAs require to perform search operations on the mailbox of the user where the mails were forwarded to. After finding the required mailbox, PST can be exported and then imported to the sender’s mailbox. T...

SMTP Relay gửi group có bật "Require all that senders are authenticated" không được Cần Clear "Require all that senders are authenticated" Get-DistributionGroup|where {$_.RequireSenderAuthenticationEnabled-eq$True}|Set-DistributionGroup-RequireSenderAuthenticationEnabled:$False Để bảo mật hơn (ngăn spam từ bên ngoài vào group) => Thêm chỉ nhận mail từ group A11Organization           Get-DistributionGroup | set-distributiongroup -AcceptMessagesOnlyFromDLMembers A11Organization   Quá trình clear có thể bị lỗi Open/Closed group Tra danh sách group đang set là Open: Get-DistributionGroup -resultsize unlimited |ft name,memberjoinrestriction,memberdepartrestriction Set Close cho các group: Get-DistributionGroup | set-DistributionGroup -memberjoinrestriction:closed -memberdepartrestriction:closed

Quá trình chuyển đổi mailbox từ 2010 qua 2016 sẽ cần giai đoạn trung gian. Để đảm bảo user trên 2010 và 2016 đều có thể truy cập được Public Folder trong giai đoạn trung gian này thì ta cần làm Proxy Public Folder 1. Create an empty mailbox database on each public folder server. New-MailboxDatabase -Server EXVDC3 -Name ProxyPublicFolderDB -IsExcludedFromProvisioning $true Lưu ý là database này chỉ chứa Proxy Public Folder Mailbox, không được chứa bất kỳ mailbox nào khác. 2. Create a proxy mailbox within the new mailbox database and hide the mailbox from the address book New-Mailbox -Name ProxyPublicFolder -Database ProxyPublicFolderDB Set-Mailbox -Identity ProxyPublicFolder -HiddenFromAddressListsEnabled $true 3. Enable AutoDiscover to return the proxy public folder mailboxes Set-MailboxDatabase ProxyPublicFolderDB -RPCClientAccessServer EXVDC3 4. Configure the user mailboxes to allow access to the legacy on-premises public folders Set-OrganizationConfig -PublicFoldersEnabled Remote -R...

  Lỗi do chưa set Permission cho Exchange Authentication trong Receive Connector : Default Connector Relay Connector

  Solution for a valid Migration mailbox could not be found for this organization To address this issue, we will: Delete Migration mailbox in Active Directory Users and Computers Recreate Migration mailbox with /PrepareAD command Enable Migration mailbox with Exchange Management Shell 1. Delete Migration mailbox in Active Directory Users and Computers We do see the mailbox in ADUC, let’s remove it. If you don’t see it, search for it. It might be in a different container than the default container  Users . We can always verify in Exchange Management Shell if the Migration mailbox is present. If it shows up in the output, it means that it’s present and enabled. The output should be empty. [PS] C:\> Set - ADServerSettings - ViewEntireForest $true ; Get - Mailbox - Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" - Arbitration | Format-Table Name , ServerName , Database , AdminDisplayVersion , ProhibitSendQuota Copy 2. Recreate Migration mailbox with /Prepare...

 CẤU HÌNH MESSAGE TRACKING & LOG TRÊN EXCHANGE 2010 Có 2 loại log: - Message Tracking log : ghi nhận mail in/out qua lệnh gửi trực tiếp. Mặc định là lưu 30 ngày Ta có thể điều chỉnh lại số ngày, kích thước tối đa của file log, thư mục log - Protocol Log : ghi nhận log của các connector (Send, Receiver, Relay) - Đường dẫn mặc định Lệnh đổi đường dẫn lưu log: Set-TransportServer “TRANSPORT SERVER NAME” -ReceiveProtocolLogPath “D:\New SmtpReceive Log File Directory” Set-TransportServer “TRANSPORT SERVER NAME” -SendProtocolLogPath “D:\New SmtpSend Log File Directory” - EXTRA: + Tìm kiếm message Get-MessageTrackingLog -ResultSize Unlimited | Where-Object {$_.Recipients -like "*@domain.com"} | Select-Object Timestamp, Sender, {$_.Recipients}, MessageSubject, EventId | Export-Csv -Path "C:\Reports\RecipientDomainReport.csv" -NoTypeInformation

 Move by command (Allow large data loss) New-MoveRequest -Identity UserID -AcceptLargeDataLoss -BadItemLimit 200 -TargetDatabase DB-MB-EX03 -ArchiveTargetDatabase DB-Archive-EX03

 Fatal error MapiExceptionNotFound has occurred. Error details: MapiExceptionNotFound: Unable to synchronize manifest. (hr=0x8004010f, ec=-2147221233) This error will appear due to mailbox corruption to eliminate the above error need repair the mailbox  execute the following shell command then clear the move request and initiate again move request   New-MailboxRepairRequest -Mailbox userID -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

  Prerequisites An RDB must be created. The database and log files containing the recovered data must be restored or copied into the RDB folder structure that was created when the RDB was created. The database must be in a clean shutdown state. Because an RDB is an alternate restore location for all databases, all restored databases will be in a dirty shutdown state. You can use Eseutil /R to put the database in a clean shutdown state. (Text copied from technet) Step 1 Start up DPM 2010 and go to the Recovery section, select the appropriate database, also make sure to select a date very the user mailbox should be recovered from. Right click the database and select “Recover”. Check so that the date and time are correct and press “Next”. Select “copy to network folder” and select “Next”. Copy destination, select the appropriate server and folder press “Next”. On the next selection window we got a very nice option to select, it’s called “Bring the database to a clean state after copyi...