domino-exchange

На отдельном сервере win64 в ДМЗ не в домене: 1. качаем и ставим  Microsoft Visual C++ 2015 (!)  (64 bit)  https://www.microsoft.com/ru-ru/download/details.aspx?id=48145 2. качаем апач ( ApacheHaus )  (64 bit)   https://www.apachehaus.com/cgi-bin/download.plx 3. разархивируем aпaч в каталог C:\Apache24 4. в каталог C:\Apache24\conf\ssl кладем серверный ключ server.key и сертификат сервера server.crt а так же сертификаты   root и intermediate склеиваем в нотепаде из root и intermediate (intermediate сверху) в файл CACert.crt 5. правим конфиги апач : включаем (раскомментируем) модули по списку в C:\Apache24\conf\httpd.conf LoadModule access_compat_module modules/mod_access_compat.so LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule authz_core_module modules/mod_authz_core.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so LoadModu

Exchange Server 2013 and 2016 Standard Edition can't mount databases that are larger than 1024 GB Applies to:  Exchange Server 2013 Standard Edition Exchange Server 2016 Standard Edition This issue occurs because the default database size limit for Exchange Server 2013 Standard Edition and Exchange Server 2016 Standard Edition is 1,024 gigabytes (GB). There is no default database size limit for the Enterprise Edition. The Exchange store checks database size limits periodically and dismounts a database when the size limit is reached. Therefore, this issue may occur after the database is automatically dismounted. Additionally, when you perform a failover of the database, the failover fails, and an event that resembles the following is logged in Event Viewer: Note  The database maximum size is hard-coded as 1,024 GB in the event, even though you may have changed it to a higher value in the registry. Resolution In order to have the full

$FTE = Get-DynamicDistributionGroup DNS; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer | Out-File "F:\Group_Control\DNS.txt" $FTE = Get-DynamicDistributionGroup DUK; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer | Out-File "F:\Group_Control\DUK.txt" $FTE = Get-DynamicDistributionGroup DKUUR; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer | Out-File "F:\Group_Control\DKUUR.txt" $FTE = Get-DynamicDistributionGroup DISE; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer | Out-File "F:\Group_Control\DISE.txt" $FTE = Get-DynamicDistributionGroup BUH; Get-Recipient -RecipientPreviewFilter $FTE.RecipientFilter -OrganizationalUnit $FTE.RecipientContainer | Out-File "F:\Group_Control\BUH.txt" $FTE = Get-DynamicDistribut

Set-Mailbox -Identity itfbk2@fbk.ru -MessageCopyForSendOnBehalfEnabled $true -MessageCopyForSentAsEnabled $true Set-Mailbox -Identity spb-legal-office@fbk.ru -MessageCopyForSendOnBehalfEnabled $true -MessageCopyForSentAsEnabled $true

Внимание, если вы на лицензии Standart увеличивали в реестре макс. размер базы этот параметр может затерется при установки куммулятивного апдейта , внимание !  https://domino--exchange.blogspot.com/2020/03/db-store-1024-gb.html We are currently upgrading our Exchange 2016 servers to CU14 Exchange 2016 and started to install CU14 on servers that host only relayed copies. CU14 Exchange 2016 is a bridge CU. It is compatible with .NET 4.7.2 and compatible with .NET 4.8 as well. You can upgrade from .Net 4.7.2 to .Net 4.8 after you have CU14 Exchange 2016 in place. CU14 ( and CU15 ) both come with a vulnerability for which Microsoft released a patch in February. The patch is classified important and should be installed after CU14 has been installed. You can read more to the mentioned vulnerability and download the patch from Microsoft  here . Tasks before installing CU14 Exchange 2016: Backup your web.config files where you have modified parameters or have added new ke

Maintenance mode ON Set-ServerComponentState SRV-EXCH-2 -Component HubTransport -State Draining -Requester Maintenance Restart-Service MSExchangeTransport Restart-Service MSExchangeFrontEndTransport Redirect-Message -Server SRV-EXCH-2 -Target srv-vm-ex.msk.fbk.ru Suspend-ClusterNode SRV-EXCH-2 Set-MailboxServer SRV-EXCH-2 -DatabaseCopyActivationDisabledAndMoveNow $True Get-MailboxServer SRV-EXCH-2 | Select DatabaseCopyAutoActivationPolicy Set-MailboxServer SRV-EXCH-2 -DatabaseCopyAutoActivationPolicy Blocked Set-ServerComponentState SRV-EXCH-2 -Component ServerWideOffline -State Inactive -Requester Maintenance Get-ServerComponentState SRV-EXCH-2 | FT Component,State –Autosize Maintenance mode OFF Set-ServerComponentState SRV-EXCH-2 -Component ServerWideOffline -State Active -Requester Maintenance Resume-ClusterNode SRV-EXCH-2 Set-MailboxServer SRV-EXCH-2 -DatabaseCopyActivationDisabledAndMoveNow $False Set-MailboxServer SRV-EXCH-2 -DatabaseCopyAutoActivationPolicy U