starred/dkim-exchange-Pro

Fork 0

mirror of https://github.com/Pro/dkim-exchange.git synced 2026-04-25 08:55:52 +03:00

[GH-ISSUE #41] Echange 2013 CU5 support #25

New issue

Closed

opened 2026-02-26 10:35:18 +03:00 by kerem · 13 comments

kerem commented

2026-02-26 10:35:18 +03:00

Owner

Originally created by @rconuser on GitHub (Jun 3, 2014).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/41

Exchange 2013 CU5 is out: http://blogs.technet.com/b/exchange/archive/2014/05/27/released-exchange-server-2013-cumulative-update-5.aspx
Is it supported by dkim-exchange?
Thank you!

Originally created by @rconuser on GitHub (Jun 3, 2014). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/41 Exchange 2013 CU5 is out: http://blogs.technet.com/b/exchange/archive/2014/05/27/released-exchange-server-2013-cumulative-update-5.aspx Is it supported by dkim-exchange? Thank you!

kerem

2026-02-26 10:35:18 +03:00

closed this issue
added the
bug

agent
labels

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Pro commented on GitHub (Jun 3, 2014):

Can you create a pull request with the following files from your Server install:

C:\Program Files\Microsoft\Exchange Server\V14\Public
Microsoft.Exchange.Data.Common.dll
Microsoft.Exchange.Data.Common.xml
Microsoft.Exchange.Data.Transport.dll
Microsoft.Exchange.Data.Transport.xml

and put the files into the repository:
dkim-exchange / Lib / Exchange 2013 CU5

or zip and download the files somewhere and post the link here. Then I'll compile the needed files for Exchange 2013 CU5

@Pro commented on GitHub (Jun 3, 2014): Can you create a pull request with the following files from your Server install: ``` C:\Program Files\Microsoft\Exchange Server\V14\Public Microsoft.Exchange.Data.Common.dll Microsoft.Exchange.Data.Common.xml Microsoft.Exchange.Data.Transport.dll Microsoft.Exchange.Data.Transport.xml ``` and put the files into the repository: `dkim-exchange / Lib / Exchange 2013 CU5` or zip and download the files somewhere and post the link here. Then I'll compile the needed files for Exchange 2013 CU5

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@AlexLaroche commented on GitHub (Jun 4, 2014):

The Exchange 2013 CU4 is also missing if Exchange 2013 CU5 is out.

@AlexLaroche commented on GitHub (Jun 4, 2014): The Exchange 2013 CU4 is also missing if Exchange 2013 CU5 is out.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@psdogado commented on GitHub (Jun 4, 2014):

Exchange 2013 CU4 was released as SP1.

@psdogado commented on GitHub (Jun 4, 2014): Exchange 2013 CU4 was released as SP1.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@rconuser commented on GitHub (Jun 13, 2014):

I do not understand how to put files in the directory here, Just download this .PNG file and then rename it to .ZIP
This is the files from CU5 installation you were asking for.
Thank you!

@rconuser commented on GitHub (Jun 13, 2014): I do not understand how to put files in the directory here, Just download this .PNG file and then rename it to .ZIP This is the files from CU5 installation you were asking for. Thank you! ![exchange 2013 cu5](https://cloud.githubusercontent.com/assets/7781823/3266644/5eee816a-f2b7-11e3-9b37-68193f5432d5.png)

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Pro commented on GitHub (Jun 13, 2014):

Thanks. I'll add the compiled files latest in a few days and will notify you.

@Pro commented on GitHub (Jun 13, 2014): Thanks. I'll add the compiled files latest in a few days and will notify you.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Ivan-IT commented on GitHub (Jun 24, 2014):

Hello.
Windows Server 2008 R2 fully updated, Exchange 2013 CU5.
After agent installation the Exchange Transport service fails to start. Is this issue already known? What logs should I gather to troubleshoot it?

@Ivan-IT commented on GitHub (Jun 24, 2014): Hello. Windows Server 2008 R2 fully updated, Exchange 2013 CU5. After agent installation the Exchange Transport service fails to start. Is this issue already known? What logs should I gather to troubleshoot it?

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Pro commented on GitHub (Jun 24, 2014):

Can you check the EventLog, there should be an error log with an exception text. Please post the full exception text here.

Please also note that the current master branch is note yet fully tested and shouldn't be used in production. Currently I'm short on time but I'll try to test it in the next days.

@Pro commented on GitHub (Jun 24, 2014): Can you check the EventLog, there should be an error log with an exception text. Please post the full exception text here. Please also note that the current master branch is note yet fully tested and shouldn't be used in production. Currently I'm short on time but I'll try to test it in the next days.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@tstar commented on GitHub (Jun 25, 2014):

I have the same problem.
Windows Server 2012 R2 fully updated, Exchange 2013 CU5.

@tstar commented on GitHub (Jun 25, 2014): I have the same problem. Windows Server 2012 R2 fully updated, Exchange 2013 CU5.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Pro commented on GitHub (Jun 25, 2014):

@tstar @Ivan-IT
Can you please post the Exception Message from within the EventLog? Thanks!

@Pro commented on GitHub (Jun 25, 2014): @tstar @Ivan-IT Can you please post the Exception Message from within the EventLog? Thanks!

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@tstar commented on GitHub (Jun 25, 2014):

I'm sorry, I did not think to do it immediately, but once again breaking the production server I would not venture.

@tstar commented on GitHub (Jun 25, 2014): I'm sorry, I did not think to do it immediately, but once again breaking the production server I would not venture.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Pro commented on GitHub (Jun 25, 2014):

Thanks anyway. Just to remind you: The current release for production is always under https://github.com/Pro/dkim-exchange/releases NOT the current master branch. The master branch and especially 2013 CU5 is not yet tested and the version from the master shouldn't therefore be used on a production server.

@Pro commented on GitHub (Jun 25, 2014): Thanks anyway. Just to remind you: The current release for production is always under https://github.com/Pro/dkim-exchange/releases NOT the current master branch. The master branch and especially 2013 CU5 is not yet tested and the version from the master shouldn't therefore be used on a production server.

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@Pro commented on GitHub (Jun 28, 2014):

@tstar @Ivan-IT Exchange 2013 CU5 is now supported and is currently in beta status.
Since we are now using a GUI for installation/upgrading/configuring, you need to use these steps to install the new agent version 2.0.0:
https://github.com/Pro/dkim-exchange/blob/master/INSTALL_2.md

Please report any issues if you ran into any. Thanks!

@Pro commented on GitHub (Jun 28, 2014): @tstar @Ivan-IT Exchange 2013 CU5 is now supported and is currently in beta status. Since we are now using a GUI for installation/upgrading/configuring, you need to use these steps to install the new agent version 2.0.0: https://github.com/Pro/dkim-exchange/blob/master/INSTALL_2.md Please report any issues if you ran into any. Thanks!

kerem commented

2026-02-26 10:35:18 +03:00

Author

Owner

@tstar commented on GitHub (Jul 1, 2014):

Yes! Excellent work! Now everything works fine. Thank you very much.

@tstar commented on GitHub (Jul 1, 2014): Yes! Excellent work! Now everything works fine. Thank you very much.