Themensammlung zu Exchange-Konfigurationen
$outMessage = Get-Content "C:\temp\message.txt" Set-MailboxAutoReplyConfiguration -AutoReplyState scheduled -ExternalAudience all -InternalMessage $outMessage -ExternalMessage $outMessage -StartTime "11/01/2014" -EndDate "11/15/2014"
set-mailbox <mailbox name> -MessageCopyForSentAsEnabled $True
Front End Transport service on Mailbox servers
%ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive%ExchangeInstallPath%TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpSendTransport service on Mailbox servers:
%ExchangeInstallPath%TransportRoles\Logs\Hub\ProtocolLog\SmtpReceive%ExchangeInstallPath%TransportRoles\Logs\Hub\ProtocolLog\SmtpSendMailbox Transport Delivery service on Mailbox servers (Receive connectors):
%ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpReceive\DeliveryMailbox Transport Submission service on Mailbox servers (Send connectors):
%ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpSend\Submission
Protocol logging for side effect messages that are submitted after messages are delivered to mailboxes occurs in %ExchangeInstallPath%TransportRoles\Logs\Mailbox\ProtocolLog\SmtpSend\Delivery. For example, a message that's delivered to a mailbox triggers an Inbox rule that redirects the message to another recipient.
Transport service on Edge Transport servers:
%ExchangeInstallPath%TransportRoles\Logs\Edge\ProtocolLog\SmtpReceive%ExchangeInstallPath%TransportRoles\Logs\Edge\ProtocolLog\SmtpSendQuelle:
Set-Mailbox MarketingDept1 -Type Shared
Mögliche Werte des Parameters:
| Parameter | Bedeutung |
|---|---|
| Regular | Benutzerpostfach |
| Room | Raum |
| Equipment | Gerät |
| Shared | Freigegebenes Postfach |
Get-Recipient -Filter {RecipientTypeDetails -eq "RoomMailbox" -or RecipientTypeDetails -eq "EquipmentMailbox"}
Ab Exchange Server 2013 SP1 steht das neue Protokoll für die Anbindung von Outlook (Anywhere) zur Verfügung. Im Exchange 2013 muss aber manuell aktiviert werden. Im Exchange 2016 und höher ist es als Standardprotokoll bereits von Hause aus aktiviert.
Ob es aktiviert ist, verrät der Befehl:
Get-OrganizationConfig | fl name,mapi*
IIS virtuelles Verzeichnis konfigurieren:
Get-MapiVirtualDirectory | Set-MapiVirtualDirectory -InternalUrl "https://mail.meinedomain.de/mapi" -ExternalUrl "https://mail.meinedomain.de/mapi" -IISAuthenticationMethods Ntlm, OAuth, Negotiate
Organisationsweite Aktivierung - erfordert Neustart aller Outlook-Clients:
Set-OrganizationConfig -MapiHttpEnabled $true
Läuft die MAPI?
GET https://mail.meinedomain.de/mapi/healthcheck.htm 200 OK SERVER-01.meinedomain.DE
Das Protokoll wird ab Exchange 2016 standardmäßg genutzt. Unterstützung Outlook und Exchange 2013:
Alle inaktiven:
Get-ServerComponentState -Identity SERVER-02 | ?{$_.state -eq "Inactive"} Server Component State ------ --------- ----- SERVER-02.meinserver.de AutoDiscoverProxy Inactive SERVER-02.meinserver.de ActiveSyncProxy Inactive SERVER-02.meinserver.de EcpProxy Inactive SERVER-02.meinserver.de EwsProxy Inactive SERVER-02.meinserver.de OabProxy Inactive SERVER-02.meinserver.de OwaProxy Inactive SERVER-02.meinserver.de RpsProxy Inactive SERVER-02.meinserver.de RwsProxy Inactive SERVER-02.meinserver.de RpcProxy Inactive SERVER-02.meinserver.de ForwardSyncDaemon Inactive SERVER-02.meinserver.de ProvisioningRps Inactive
Get-OfflineAddressBook | Update-OfflineAddressBook Get-GlobalAddressList | Update-GlobalAddressList Get-AddressList | Update-AddressList