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}                                 }         }         ...

 1. Cài bộ Cdata Code Assist MCP for Exchange, rồi bắt đầu cấu hình Cấu hình Exchange version, 2016/2019 vẫn dùng chung 2013_SP1 được Khai báo đường dẫn Exchange EWS Bấm Save & Test . Nếu khai báo đúng sẽ báo successful. Bấm Next qua bước tiếp theo 2. Chọn AI MCP tool: Chọn AI MCP phù hợp (vd: Claude Desktop). Bấm Save 3. Nếu gặp lỗi không thể save configure thì có thể do Claude Desktop cập nhật đường dẫn chứa file config Để khắc phục: tạo lại link bằng lệnh sau: mklink /D "C:\Users\{username}\AppData\Roaming\Claude" "C:\Users\{username}\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude". 4. Lúc này là đã cấu hình xong MCP server, có thể bấm Close. Sau đó khởi động lại Claude Deskop Claude Desktop sẽ tự nhận thấy MCP Server trong quá trình khởi động. Để kiểm tra Claude Desltop đã kết nối MCP Server, bạn vào Settings - Developer

 CẤU HÌNH SPF, DKIM, DMARC CHO EXCHANGE SERVER A. DKIM 1. Tải bộ ký DKIM signer 2. Tạo record Cài xong, mở Configure, đẩy mục "Exchange DKIM signer" lên đầu tiên Cấu hình DKIM Header và Body ở mức Relaxed Đặt tên Selector, bấm Generate new key, Save domain. Copy key rồi qua trang quản lý DNS của tên miền (vd: PAVN, Mắt Bão...) tạo record txt Test lại DKIM ở trang: https://dkimvalidator.com/ B. DMARC Vào trang  https://kitterman.com/dmarc/ để tạo

  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...

Source link: https://pelegit.co.il/migrate-public-folder-exchange-2010-to-exchange-2016/  Hello guys, In this post I am going to show you how to migrate Migrate public folder   Exchange 2010   to   Exchange 2016  which including step by step based Microsoft best practice, this post began due to the last project that I’ve done of Exchange servers and as part of the project the public folder is one of the steps we should perform in order to complete the project, thereby I would like to share the steps I did over there in this post. First of all, we have to download the following files in Exchange 2010 and Exchange 2016: Public Folders Migration Scripts: https://www.microsoft.com/en-us/download/details.aspx?id=38407 Prepare the migration- Follow my steps: Let’s get some information about existing or non-existing public folders. Get-PublicFolder -Recurse | Export-CliXML C:\PFMigration\Legacy_PFStructure.xml Make sure there is no PF migration...

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

 Mặc định timeout của OWA là 6hrs Chúng ta có thể set lại timeout bằng cách sau (vd 5 phút): Set-OrganizationConfig -ActivityBasedAuthenticationTimeoutInterval 00:05:00

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...