[GH-ISSUE #89] Add to readme: Upgrade approach for new CU #69

Closed
opened 2026-02-26 10:35:35 +03:00 by kerem · 5 comments
Owner

Originally created by @mr-flibble on GitHub (Jul 9, 2015).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/89

Sorry for the silly question, but I did not find the answer anywhere.

What is the recommended way to upgrade to a newer Exchange CU if I have DKIM already installed?
Should I DKIM Signer before deactivate or uninstall, or update it? Or none of it and update it after upgrade to the new CU?
I think it would be good to add this information to the readme. Thank you.

Originally created by @mr-flibble on GitHub (Jul 9, 2015). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/89 Sorry for the silly question, but I did not find the answer anywhere. What is the recommended way to upgrade to a newer Exchange CU if I have DKIM already installed? Should I DKIM Signer before deactivate or uninstall, or update it? Or none of it and update it after upgrade to the new CU? I think it would be good to add this information to the readme. Thank you.
kerem closed this issue 2026-02-26 10:35:35 +03:00
Author
Owner

@gogglespisano commented on GitHub (Jul 9, 2015):

I've wondered the same thing. Since DKIM will break during the upgrade, should it be turned off before the update, then upgraded after exchange? Is there any harm in leaving it running during the exchange upgrade?

The biggest concern would be causing the exchange update to fail or exchange transport fail to start after update.

<!-- gh-comment-id:119997132 --> @gogglespisano commented on GitHub (Jul 9, 2015): I've wondered the same thing. Since DKIM will break during the upgrade, should it be turned off before the update, then upgraded after exchange? Is there any harm in leaving it running during the exchange upgrade? The biggest concern would be causing the exchange update to fail or exchange transport fail to start after update.
Author
Owner

@rbfajardo commented on GitHub (Jul 9, 2015):

If the concern is the transport service would fail to start, you can disable the DKIM transport agent prior to a CU upgrade. (Disable-TransportAgent)

You can then upgrade the DKIM transport agent using the config executable.

<!-- gh-comment-id:120000491 --> @rbfajardo commented on GitHub (Jul 9, 2015): If the concern is the transport service would fail to start, you can disable the DKIM transport agent prior to a CU upgrade. (Disable-TransportAgent) You can then upgrade the DKIM transport agent using the config executable.
Author
Owner

@gogglespisano commented on GitHub (Jul 9, 2015):

Is disabling dkim enough to keep it from literally being loaded, or just not in use?

If the dkim signer has dependencies that become incompatible during the exchange upgrade, can it cause the transport to fail to start even with the dkim signer disabled?

<!-- gh-comment-id:120007125 --> @gogglespisano commented on GitHub (Jul 9, 2015): Is disabling dkim enough to keep it from literally being loaded, or just not in use? If the dkim signer has dependencies that become incompatible during the exchange upgrade, can it cause the transport to fail to start even with the dkim signer disabled?
Author
Owner

@Pro commented on GitHub (Jul 9, 2015):

You can use the Configuration Programm shipped with the signer to disable it, the update exchange, next update DKIM, then enable it again.

Disabling DKIM will disable it entirely, thus not loading the DLL.
I'll update the Readme for the instructions

<!-- gh-comment-id:120008449 --> @Pro commented on GitHub (Jul 9, 2015): You can use the Configuration Programm shipped with the signer to disable it, the update exchange, next update DKIM, then enable it again. Disabling DKIM will disable it entirely, thus not loading the DLL. I'll update the Readme for the instructions
Author
Owner

@Pro commented on GitHub (Jul 12, 2015):

github.com/Pro/dkim-exchange@d4492979b6

<!-- gh-comment-id:120756402 --> @Pro commented on GitHub (Jul 12, 2015): https://github.com/Pro/dkim-exchange/commit/d4492979b6cbf6680f9b83fc8ac07f881af7cdbf
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dkim-exchange-Pro#69
No description provided.