Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 0 subscribers
  • Views 8206 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hello world, The best way from SEC 4.7 Win 2003 R2 --> SEC 5.2 Win 2012 R2

baptiste

Hello world,
I'm curently using the SEC 4.7 on a windows server 2003 R2. I want to use the last version on a windows server 2012 R2. The curent configuration is very basic, so my question is what is the quickest method to get that done ? If I install the new version, do I need to redeploy the clients or can I re-use the old ones ?

Bonjour tout le monde,
J'utilise actuellement SEC en version 4.7 sur un windows server 2003 R2. J'aimerai utiliser la version la plus récente sur windows server 2012 R2. Sachant que la configuration actuelle est basique, quelle est la méthode la méthode la plus rapide pour avoir cela ? Si j'installe la nouvelle version séparément, aurai-je besoin de redéployer les clients ou pourrai-je me servir des anciens ?



This thread was automatically locked due to age.
Parents
  • 0

    Hello baptiste,

    there's no direct upgrade path from 4.7 to 5.3.1 and as you also use a new server it's probably less effort to install from scratch and redo all policies.

    Reprotection of the endpoints is recommended (for a "clean" reinitialization of RMS) but not absolutely required. By exporting and importing (before the 5.3 install) the RMS certificates and configuring the new CIDs (scenario B in Consideration ...) you can "move" the endpoints by simply changing the updating policy on the old server to point to the new (note this will work for Windows endpoints only).

    Christian 

Reply
  • 0

    Hello baptiste,

    there's no direct upgrade path from 4.7 to 5.3.1 and as you also use a new server it's probably less effort to install from scratch and redo all policies.

    Reprotection of the endpoints is recommended (for a "clean" reinitialization of RMS) but not absolutely required. By exporting and importing (before the 5.3 install) the RMS certificates and configuring the new CIDs (scenario B in Consideration ...) you can "move" the endpoints by simply changing the updating policy on the old server to point to the new (note this will work for Windows endpoints only).

    Christian 

Children
Unfiltered HTML