Exchange 2013/2016 management tools

We have Exchange 2016 and want to install management tools. A PC has the management tools which is older than the current CU8 installed.
Do we have to have CU8 management tools in the new PC? or is it ok to have older version in a management pc?
Is there any issue with Exchange if we do not have management tools same as the server?

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

No it is fine to have the older version. There will be on issues from that. Also you can always access the ECP of the actual server running exchange if you need to access a more current version but there will be no issues. The only thing i would say is since CU8 support .netframework 4.7.1, if you have that installed on the exchange servers I would update the older version of the management tools also, but if you aren't using the latest .net, i wouldn't worry about.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.

Let me ask you this, since it is a management PC, what is the challenge in upgrading the management tools. Instead of breaking your head into issues or no issues, why not upgrade the tools on the management PC. If you don't want to upgrade, just use plain powershell on the PC and connect to Exchange server to manage.

There was an issue with an Exchange server (un-mounting the DB). Exchange admin thinks that the management server is causing that problem since it has an old version. I just want to prove that has nothing to do with.