
- Ausdrucken
- Internen Beitrags-Link kopieren
- Externen Beitrags-Link kopieren
- Beitrag melden
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html
[content:23257647271]
Update Exchange Server , öffentliche Ordner verschwunden
wir haben auf unserem Server (Windows server 2019) einen Exchange Server installiert.
Version des Exchange Servers 15.2.11.
Dieses sowie auch schon das letzte mal verschwanden die "Öffentlichen Kalender" aus Outlook (Office2013) nach dem Exchange Update.
Man kann das Problem lösen, in dem man auf den Clients ein neues Profil anlegt. Allerdings erscheint mir das als nicht saubere, eher geflickschusterte Lösung.
Hat jemand von Euch auch solche Probleme oder gar eine Lösung?
Vielen Dank für Eure Mühe.
Content-ID: 23257647271
Url: https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html
Ausgedruckt am: 02.04.2025 um 00:04 Uhr
- Kommentarübersicht - Bitte anmelden
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-3062552907624366
[content:23257647271#3062552907624366]
ist das Problem nur mit Office 2013?
Die Datenbank mit den Publicfoldern ist aber in Ordnung? Was sagt der Exchange Healthchecker?
Gruß
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-3217130807570995
[content:23257647271#3217130807570995]
ich tippe auf Autodiscover!
hast du ein ordentliches Zertifikat?
splitDNS?
Frank
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-3312460190620064
[content:23257647271#3312460190620064]
Laut Microsoft wird das zwar supportet, es ist nur nicht benutzbar!
Wenn du Outlook 2016 oder höher einsetzt sollte es besser laufen.- Wenn der alte Exchange aber noch existiert kann es auch noch andere Ursachen geben. Z.B. sind eventuell Systempostfächer noch nicht migriert.
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-3846425268687986
[content:23257647271#3846425268687986]
Hallo,
ist das Problem nur mit Office 2013?
Die Datenbank mit den Publicfoldern ist aber in Ordnung? Was sagt der Exchange Healthchecker?
Gruß
Ja und Nein, wie ich mitbekommen habe nur Office 2013, da aber auch nicht alle.
Moin..
ich tippe auf Autodiscover!
hast du ein ordentliches Zertifikat?
splitDNS?
Frank
Ich vermute und hoffe, dass es ein ordentliches Zertifikat gibt, wurde von einer IT Firma erstellt, die Mädels und Jungs sind ganz fit.
Wenn du Outlook 2013 an Exchange 2019 betreibst garantiere ich dir das es total komische Fehler gibt, z.B. Öffentliche Ordner nicht da, Adresslisten nicht, da, Abwesenheitsassistent geht nicht, Terminplanungsassistent geht nicht, etc.
Laut Microsoft wird das zwar supportet, es ist nur nicht benutzbar!
Wenn du Outlook 2016 oder höher einsetzt sollte es besser laufen.- Wenn der alte Exchange aber noch existiert kann es auch noch andere Ursachen geben. Z.B. sind eventuell Systempostfächer noch nicht migriert.
Der Alte Exchange ist gelöscht. Wurde einst von 2010 glaub ich auf 2016 und dann auf 2019 hochgezogen, mit "Zwischenserver", weil das wohl in einem Ritt nicht geht.
Danke für Eure Hilfe.
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-3979473339087192
[content:23257647271#3979473339087192]
wenn du nur die Hälfte unserer Fragen beantwortest und jemand anders den Exchange konfiguriert hat wird das unter Umständen nichts…
Diese Aussage ist nicht böse gemeint.
Healthchecker:
https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/
SplitDNS:
https://www.msxfaq.de/konzepte/dns.htm
Gruß
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-4449587063396327
[content:23257647271#4449587063396327]
Exchange Health Checker version 23.08.15.2342
Virtual Machine detected. Certain settings about the host hardware cannot be detected from the virtual machine. Verify on the VM Host that:
- There is no more than a 1:1 Physical Core to Virtual CPU ratio (no oversubscribing)
- If Hyper-Threading is enabled do NOT count Hyper-Threaded cores as physical cores
- Do not oversubscribe memory or use dynamic memory allocation
Although Exchange technically supports up to a 2:1 physical core to vCPU ratio, a 1:1 ratio is strongly recommended for performance reasons. Certain third party Hyper-Visors such as VMWare have their own guidance.
VMWare recommends a 1:1 ratio. Their guidance can be found at https://aka.ms/HC-VMwareBP2019.
Related specifically to VMWare, if you notice you are experiencing packet loss on your VMXNET3 adapter, you may want to review the following article from VMWare: https://aka.ms/HC-VMwareLostPackets.
For further details, please review the virtualization recommendations on Microsoft Docs here: https://aka.ms/HC-Virtualization.
Exchange Information
--------------------
Name: EXCHANGE.Homedomain.local
Generation Time: 08/24/2023 07:50:02
Version: Exchange 2019 CU12 Aug23SUv2
Build Number: 15.02.1118.037
Exchange IU or Security Hotfix Detected:
Security Update for Exchange Server 2019 Cumulative Update 12 (KB5019758)
Security Update for Exchange Server 2019 Cumulative Update 12 (KB5022193)
Security Update for Exchange Server 2019 Cumulative Update 12 (KB5023038)
Security Update for Exchange Server 2019 Cumulative Update 12 (KB5024296)
Security Update for Exchange Server 2019 Cumulative Update 12 (KB5026261)
Security Update for Exchange Server 2019 Cumulative Update 12 (KB5030524)
Server Role: Mailbox
DAG Name: Standalone Server
AD Site: Standardname-des-ersten-Standorts
MRS Proxy Enabled: False
Internet Web Proxy: Not Set
Critical Services Not Running:
pla - Status: Stopped - StartType: Disabled
Misconfigured Services:
pla - Status: Stopped - StartType: Disabled - CorrectStartType: Manual
Extended Protection Enabled (Any VDir): False
Setting Overrides Detected: False
Exchange Server Maintenance: Server is not in Maintenance Mode
Organization Information
------------------------
MAPI/HTTP Enabled: True
Enable Download Domains: False
AD Split Permissions: False
Total AD Site Count: 1
Operating System Information
----------------------------
Version: Microsoft Windows Server 2019 Standard
System Up Time: 1 day(s) 16 hour(s) 39 minute(s) 5 second(s)
Time Zone: Mitteleuropäische Zeit
Dynamic Daylight Time Enabled: True
.NET Framework: 4.8
PageFile: System is set to automatically manage the PageFile Size: 0MB
Error: On Exchange 2019, the recommended PageFile size is 25% (4096MB) of the total system memory (16384MB).
More information: https://aka.ms/HC-PageFile
Power Plan: Ausbalanciert --- Error
Http Proxy Setting: None
Visual C++ 2012: Redistributable is outdated
Visual C++ 2013: Redistributable is outdated
Note: For more information about the latest C++ Redistributable please visit: https://aka.ms/HC-LatestVC
This is not a requirement to upgrade, only a notification to bring to your attention.
Server Pending Reboot: True --- Warning a reboot is pending and can cause issues on the server.
HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
More Information: https://aka.ms/HC-RebootPending
Processor/Hardware Information
------------------------------
Type: VMware
Processor: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Number of Processors: 6
Number of Physical Cores: 6
Number of Logical Cores: 6
Hyper-Threading: Disabled
All Processor Cores Visible: Passed
Max Processor Speed: 2095
Physical Memory: 16 GB
Warning: We recommend for the best performance to have a minimum of 128GB of RAM installed on the machine.
NIC Settings Per Active Adapter
-------------------------------
Interface Description: Ethernet-Adapter für vmxnet3 [Ethernet]
Driver Date: 2022-11-30
Driver Version: 1.9.12.0
MTU Size: 1500
Max Processors: 6
Max Processor Number: 5
Number of Receive Queues: 4
RSS Enabled: True
Link Speed: 10000 Mbps --- This may not be accurate due to virtualized hardware
IPv6 Enabled: True
IPv4 Address:
Address: 192.168.1.11\24 Gateway: 192.168.1.1
IPv6 Address:
DNS Server: ::1 127.0.0.1
Registered In DNS: True
Sleepy NIC Disabled: False --- Warning: It's recommended to disable NIC power saving options
More Information: https://aka.ms/HC-NICPowerManagement
Packets Received Discarded: 0
Frequent Configuration Issues
-----------------------------
TCP/IP Settings: Not Set
Error: Without this value the KeepAliveTime defaults to two hours, which can cause connectivity and performance issues between network devices such as firewalls and load balancers depending on their configuration.
More details: https://aka.ms/HC-TcpIpSettingsCheck
RPC Min Connection Timeout: 0
More Information: https://aka.ms/HC-RPCSetting
FIPS Algorithm Policy Enabled: 0
CTS Processor Affinity Percentage: 0
Disable Async Notification: 0
Credential Guard Enabled: False
EdgeTransport.exe.config Present: True
Open Relay Wild Card Domain: Not Set
DisablePreservation:
Missing Web Application Configuration File:
Web Application: 'Default Web Site/CertSrv' Attempting to use config: 'C:\inetpub\wwwroot\web.config'
Security Settings
-----------------
TLS 1.0: Disabled
RegistryKey Location Value
----------- -------- -----
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 0
1.0\Server
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1
1.0\Server
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 0
1.0\Client
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1
1.0\Client
TLS 1.1: Disabled
RegistryKey Location Value
----------- -------- -----
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 0
1.1\Server
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1
1.1\Server
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 0
1.1\Client
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1
1.1\Client
TLS 1.2: Enabled
RegistryKey Location Value
----------- -------- -----
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1
1.2\Server
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 0
1.2\Server
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1
1.2\Client
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 0
1.2\Client
TLS 1.3: Disabled
RegistryKey Location Value
----------- -------- -----
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS NULL
1.3\Server
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS NULL
1.3\Server
Enabled SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS NULL
1.3\Client
DisabledByDefault SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS NULL
1.3\Client
RegistryKey Location Value
----------- -------- -----
SystemDefaultTlsVersions SOFTWARE\Microsoft\.NETFramework\v4.0.30319 1
SchUseStrongCrypto SOFTWARE\Microsoft\.NETFramework\v4.0.30319 NULL
SystemDefaultTlsVersions SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 1
SchUseStrongCrypto SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 NULL
SystemDefaultTlsVersions SOFTWARE\Microsoft\.NETFramework\v2.0.50727 NULL
SchUseStrongCrypto SOFTWARE\Microsoft\.NETFramework\v2.0.50727 NULL
SystemDefaultTlsVersions SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727 NULL
SchUseStrongCrypto SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727 NULL
v4.0.30319 SchUseStrongCryptoValue: NULL --- Error: Value should be defined in registry for consistent results.
v4.0.30319 WowSchUseStrongCryptoValue: NULL --- Error: Value should be defined in registry for consistent results.
Error: SystemDefaultTlsVersions or SchUseStrongCrypto is not set to the recommended value. Please visit on how to properly enable TLS 1.2 https://aka.ms/HC-TLSGuide
More Information: https://aka.ms/HC-TLSConfigDocs
SecurityProtocol: Tls, Tls11, Tls12
TlsCipherSuiteName CipherSuite Cipher Certificate Protocols
------------------ ----------- ------ ----------- ---------
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 49196 AES ECDSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 49195 AES ECDSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 49200 AES RSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 49199 AES RSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 49188 AES ECDSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 49187 AES ECDSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 49192 AES RSA TLS_1_2 & DTLS_1_1
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 49191 AES RSA TLS_1_2 & DTLS_1_1
AllowInsecureRenegoClients Value: 0
AllowInsecureRenegoServers Value: 0
LmCompatibilityLevel Settings: 2
Description: Clients use only NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controller accepts LM, NTLM, and NTLMv2 authentication.
AES256-CBC Protected Content Support: True
This build supports AES256-CBC protected content, but the configuration is not complete. Exchange Server is not able to decrypt
protected messages which could impact eDiscovery and Journaling tasks. If you use Rights Management Service (RMS) on-premises,
please follow the instructions as outlined in the documentation: https://aka.ms/ExchangeCBCKB
SMB1 Installed: True
SMB1 Blocked: True
SMB1 should be uninstalled
More Information: https://aka.ms/HC-SMB1
Certificate:
FriendlyName: CN=EXCHANGE-CA, DC=Homedomain, DC=local
Thumbprint: 0CDAB3A46187FB9994CE91586073479166F70728
Lifetime in days: 344
Certificate has expired: False
Certificate status: Valid
Key size: 1024
It's recommended to use a key size of at least 2048 bit
Signature Algorithm: sha256RSA
Signature Hash Algorithm: sha256
Bound to services: SMTP
Internal Transport Certificate: False
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: False
Namespaces:
EXCHANGE.Homedomain.local
Certificate:
FriendlyName: Exchange Server Zertifikat
Thumbprint: 6B3D0475FD0CEC4D49D3D244739F877DF49ECB98
Lifetime in days: 1705
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha256RSA
Signature Hash Algorithm: sha256
Bound to services: IMAP, POP, IIS, SMTP
Internal Transport Certificate: True
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: True
Namespaces:
Serverdc2.homedomain.local
Serverdc2
ServerEX2016.homedomain.local
ServerEX2016
Exchange
EXCHANGE.homedomain.local
autodiscover.homedomain.de
autodiscover.homedomain.local
outlook.homedomain.local
outlook.homedomain.de
Certificate:
FriendlyName: Microsoft Exchange
Thumbprint: 85F4514906E43C539F3BFF131289110D2F383224
Lifetime in days: 1028
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha1RSA
Signature Hash Algorithm: sha1
It's recommended to use a hash algorithm from the SHA-2 family
More information: https://aka.ms/HC-SSLBP
Bound to services: None
Internal Transport Certificate: False
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: True
Namespaces:
EXCHANGE
EXCHANGE.homedomain.local
Certificate:
FriendlyName: WMSVC-SHA2
Thumbprint: 8DB0772674FC59F8419C89638E0C7512AD35B1B9
Lifetime in days: 2852
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha256RSA
Signature Hash Algorithm: sha256
Bound to services: None
Internal Transport Certificate: False
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: False
Namespaces:
WMSvc-SHA2-EXCHANGE
Certificate:
FriendlyName: Microsoft Exchange Server Auth Certificate
Thumbprint: 28E8757A4A3A0BF218EBB17FF0AEF23CCE3763A1
Lifetime in days: 807
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha1RSA
Signature Hash Algorithm: sha1
It's recommended to use a hash algorithm from the SHA-2 family
More information: https://aka.ms/HC-SSLBP
Bound to services: SMTP
Internal Transport Certificate: False
Current Auth Certificate: True
Next Auth Certificate: False
SAN Certificate: False
Namespaces:
Microsoft Exchange Server Auth Certificate
Certificate:
FriendlyName: CN=EXCHANGE-CA, DC=homedomain, DC=local
Thumbprint: D83890117147985C4E4F73CC96E11CCA6D5EDA5A
Lifetime in days: 10327
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha256RSA
Signature Hash Algorithm: sha256
Bound to services: None
Internal Transport Certificate: False
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: False
Namespaces:
EXCHANGE-CA
Certificate:
FriendlyName: CN=EXCHANGE-CA, DC=homedomain, DC=local
Thumbprint: 820E4DF336AC038684321945055066C3B111A27A
Lifetime in days: 10327
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha1RSA
Signature Hash Algorithm: sha1
It's recommended to use a hash algorithm from the SHA-2 family
More information: https://aka.ms/HC-SSLBP
Bound to services: None
Internal Transport Certificate: False
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: False
Namespaces:
EXCHANGE-CA
Certificate:
FriendlyName: CN=EXCHANGE-CA, DC=homedomain, DC=local
Thumbprint: 7FEF9DF0C7C63468AF194E887DD9B57834812295
Lifetime in days: 10327
Certificate has expired: False
Certificate status: Valid
Key size: 2048
Signature Algorithm: sha1RSA
Signature Hash Algorithm: sha1
It's recommended to use a hash algorithm from the SHA-2 family
More information: https://aka.ms/HC-SSLBP
Bound to services: None
Internal Transport Certificate: False
Current Auth Certificate: False
Next Auth Certificate: False
SAN Certificate: False
Namespaces:
EXCHANGE-CA
Valid Internal Transport Certificate Found On Server: True
Valid Auth Certificate Found On Server: True
AMSI Enabled: True
SerializedDataSigning Enabled: False
Strict Mode disabled: False
BaseTypeCheckForDeserialization disabled: False
Exchange Emergency Mitigation Service: Enabled
Windows service: Running
Pattern service: 200 - Reachable
Mitigation applied: PING1
Run: 'Get-Mitigations.ps1' from: 'D:\Exchange Server\scripts\' to learn more.
Telemetry enabled: False
Security Vulnerability
----------------------
IIS module anomalies detected: False
Security Vulnerability: Download Domains are not configured. You should configure them to be protected against CVE-2021-1730.
Configuration instructions: https://aka.ms/HC-DownloadDomains
Security Vulnerability: CVE-2023-21709
See: https://portal.msrc.microsoft.com/security-guidance/advisory/CVE-2023-21709 for more information.
Security Vulnerability: CVE-2022-24516, CVE-2022-21979, CVE-2022-21980, CVE-2022-24477, CVE-2022-30134
Extended Protection isn't configured as expected
Default Web Site Value SupportedValue ConfigSupported RequireSSL ClientCertificate IPFilterEnabled
---------------- ----- -------------- --------------- ---------- ----------------- ---------------
API None Require False True (128-bit) Ignore False
Autodiscover None None True True (128-bit) Ignore False
ECP None Require False True (128-bit) Ignore False
EWS None Allow True True (128-bit) Ignore False
Microsoft-Server- None Allow True True (128-bit) Ignore False
ActiveSync
OAB None Require False True (128-bit) Ignore False
Powershell None Require False False Accept False
OWA None Require False True (128-bit) Ignore False
RPC None Require False False Ignore False
MAPI None Require False True (128-bit) Ignore False
Exchange Back End Value SupportedValue ConfigSupported RequireSSL ClientCertificate IPFilterEnabled
----------------- ----- -------------- --------------- ---------- ----------------- ---------------
API None Require False True (128-bit) Ignore False
Autodiscover None None True True (128-bit) Ignore False
ECP None Require False True (128-bit) Ignore False
EWS None Require False True (128-bit) Ignore False
Microsoft-Server- None Require False True (128-bit) Ignore False
ActiveSync
OAB None Require False True (128-bit) Ignore False
Powershell None Require False True (128-bit) Accept False
OWA None Require False True (128-bit) Ignore False
RPC None Require False False Ignore False
PushNotifications None Require False True (128-bit) Ignore False
RPCWithCert None Require False False Ignore False
MAPI/emsmdb None Require False True Ignore False
MAPI/nspi None Require False True Ignore False
For more information about Extended Protection and how to configure, please read this article:
https://aka.ms/HC-ExchangeEPDoc
Exchange IIS Information
------------------------
Name State Protocol - Bindings - Certificate
---- ----- ---------------------------------
Default Web Site Started http - *:80: -
https - :443: - 6B3D0475FD0CEC4D49D3D244739F877DF49ECB98
http - 127.0.0.1:80: -
https - 127.0.0.1:443: - 6B3D0475FD0CEC4D49D3D244739F877DF49ECB98
Exchange Back End Started http - *:81: -
https - *:444: - 92F3B6DE42BA7F2256D38CC2F99B82D4B647783B
AppPoolName State GCServerEnabled RestartConditionSet
----------- ----- --------------- -------------------
MSExchangeMapiFrontEndAppPool Started False False
MSExchangeOWAAppPool Started False False
MSExchangeECPAppPool Started False False
MSExchangeRestAppPool Started False False
MSExchangeMapiAddressBookAppPool Started False False
MSExchangeRpcProxyFrontEndAppPool Started False False
MSExchangePowerShellAppPool Started False False
MSExchangePowerShellFrontEndAppPool Started False False
MSExchangeRestFrontEndAppPool Started False False
MSExchangeMapiMailboxAppPool Started False False
MSExchangeOABAppPool Started False False
MSExchangePushNotificationsAppPool Started False False
MSExchangeOWACalendarAppPool Started False False
MSExchangeAutodiscoverAppPool Started False False
MSExchangeServicesAppPool Started False False
MSExchangeSyncAppPool Started True False
MSExchangeRpcProxyAppPool Started False False
Output file written to .\HealthChecker-EXCHANGE-20230824074744.txt
Exported Data Object Written to .\HealthChecker-EXCHANGE-20230824074744.xml
- Internen Kommentar-Link kopieren
- Externen Kommentar-Link kopieren
- Zum Anfang der Kommentare
https://administrator.de/forum/update-exchange-server-oeffentliche-ordner-verschwunden-23257647271.html#comment-4974611601208416
[content:23257647271#4974611601208416]
Exchange auf nem DC zu installieren is jetzt nicht so die prickelnde Lösung....
Welcher Dienst läuft da nicht? Warum steht der auf disabled, wenn er auf manualstehen sollte?
Gruß