domino-exchange

Права на импорт New-ManagementRoleAssignment –Role “Mailbox Import Export” –User exch_admin_name Get-mailbox GolovanovAS | Set-MailboxRegionalConfiguration -LocalizeDefaultFolderName:$true -Language "ru-RU" New-MailboxImportRequest -Mailbox ChichaevMA -FilePath \\10.10.10.11\c$\IMPORT.PST\backup4mchi.pst -BadItemLimit 1000 Get-MailboxImportRequest | Get-MailboxImportRequestStatistics Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest Get-MailboxImportRequest -Status Failed | Remove-MailboxImportRequest

https://www.appstorrent.ru/81-microsoft-office-2016.html

Configuring Extensible Storage Engine To work with database files, Veeam Explorer for Microsoft Exchange requires a special dynamic link library  ese.dll , which is shipped with Microsoft Exchange. The  ese.dll  file must be of the same version as the Microsoft Exchange application with which your database files have been created. Note : When restoring a VM that was backed up with application-aware image processing, the  ese.dll  file will be located automatically. The following versions of Microsoft Exchange are supported: Microsoft Exchange 2019 Microsoft Exchange 2016 Microsoft Exchange 2013 Microsoft Exchange 2010 SP1, SP2 and SP3 To specify the path to the  ese.dll  file, do the following: Go to the main menu and click the  General Options . Got to the  Extensible Storage Engine  tab. Click the link next to the Microsoft Exchange version and specify the path to the  ese.dll  file. The file can be found on the Microsoft Exchange Server distribution CD at 

Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2224). The Exchange computer srv-vm-ad-11.msk.fbk.ru does not have Audit Security Privilege on the domain controller srv-vm-ad-11.msk.fbk.ru. This domain controller will not be used by Exchange Active Directory Provider. _________________________________________________________________________________ Process w3wp.exe (AirSync) (PID=12780). WCF request (GetServerFromDomainDN DC=msk,DC=fbk,DC=ru) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details  No suitable domain controller was found in domain 'msk.fbk.ru'. Errors:    at Microsoft.Exchange.Directory.TopologyService.RemoteDomainServerDiscovery.<FindSuitableDom