Pro / dkim-exchange

DKIM Signing Agent for Microsoft Exchange Server
Other
408 stars 143 forks source link

Can't install on Exchange 2019 CU8 #347

Open pcware24 opened 3 years ago

pcware24 commented 3 years ago

Versions

Description

Installer crashed with error: [PS] C:\Program Files\Exchange DkimSigner>.\install.ps1 Exchange DkimSigner Install Script Detecting Exchange version ... Found Exchange 2019 CU8 Creating registry key for EventLog Registry key for EventLog already exists. Continuing... Stopping Edge Transport Service... Microsoft Exchange-Transport wird beendet... Microsoft Exchange-Transport wurde erfolgreich beendet.

WARNUNG: Warten auf Beendigung des Diensts "WWW-Publishingdienst (W3SVC)"... Stopping W3SVC (World Wide Web Publishing Service...) Creating install directory: 'C:\Program Files\Exchange DkimSigner' and copying data from 'Src\Exchange.DkimSigner\bin\Exchange 2019 CU8' Registering agent Neue Sitzung für implizite Remotevorgänge des Befehls "Install-TransportAgent" wird erstellt... Der TransportAgentFactory-Typ "Exchange.DkimSigner.DkimSigningRoutingAgentFactory" ist nicht vorhanden. Er muss dem Microsoft .NET-Klassentyp der Transport-Agentfactory entsprechen. Parametername: TransportAgentFactory

Enabling agent Der Transport-Agent "Exchange DkimSigner" wurde nicht gefunden. Parametername: Identity

Identity Enabled Priority


Transport Rule Agent True 1 Malware Agent True 2 Content Filter Agent True 3 Sender Id Agent True 4 Sender Filter Agent True 5 Recipient Filter Agent True 6 Protocol Analysis Agent True 7 Starting Edge Transport Service... Microsoft Exchange-Transport wird gestartet... Microsoft Exchange-Transport wurde erfolgreich gestartet.

W3SVC found, but it is already running. Installation complete. Check previous outputs for any errors!

It isn't possible to install.

noija commented 3 years ago

Note that Exchange 2019 CU8 is no longer supported by Microsoft. You need to be on Exchange 2019 CU10+security update 1 or CU11. If your exchange servers (owa,ecp or ews) are published and internet accessible you can count on them being compromised and remote shells are probably installed. If that is the case you need to do a complete rebuild of the Exchange environment before the rest of your infrastructure is hacked and/or ransomed.

I'm guessing localization of the Exchange is the problem here. Somewhere in the code the installer has hardcoded names and if you are running localized versions of exchange (and there aren't many) then you need to install manually.

DJBenson commented 3 years ago

v3.3.4 is in pre-release - please try updating to this version and see if the issue is resolved.