Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 6 subscribers
  • Views 8231 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

Migration from 5.61 managed by SEC to SafeGuard Enterprise 6.10

WayneTaylor

I am currently doing a “Sophos Disk Encryption 5.61” to “SafeGuard Enterprise 6.10” process and following the guide I have got the Enterprise 6.10 server installed and configured and have imported the certificates from the current 5.61 server all OK.

 

I have followed the procedure and created a Configuration Package, but am struggling on how to deploy this configuration package to the endpoints. Can this be pushed out by the Console or do I have to manually run in on each workstation?

Thanks

Wayne



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

    Hello,

    Unfortunately you can't push this out from the console but you can push this out centrally via a GPO / SCCM deployment

  • 0 in reply to FormerMember

    Great thanks for that.

    So am I right in thinking that if I run the .exe file that was created by the "Safeguard Management Centre" on a workstation, it will just set that machine to talk to the new server, but the Encryption package will still be on 5.61 unless I follow the other process to upgrade the client to 6.1 too.  Are there any implications/gotcha's on what I set in the Default Encryption Policy?

    Also, I ultimately want to migrate to version 7, so do I need to get all endpoints moved over to the new server on 6.1 before I migrate the server to 7?

    Thanks for you help
    Wayne

Reply
  • 0 in reply to FormerMember

    Great thanks for that.

    So am I right in thinking that if I run the .exe file that was created by the "Safeguard Management Centre" on a workstation, it will just set that machine to talk to the new server, but the Encryption package will still be on 5.61 unless I follow the other process to upgrade the client to 6.1 too.  Are there any implications/gotcha's on what I set in the Default Encryption Policy?

    Also, I ultimately want to migrate to version 7, so do I need to get all endpoints moved over to the new server on 6.1 before I migrate the server to 7?

    Thanks for you help
    Wayne

Children
  • FormerMember
    0 FormerMember in reply to WayneTaylor

    Hi Wayne,

    Not quite, that .MSI that gets created will need to be installed along with the rest of the product.

    There is nothing special to be aware of, just take your time reading through the policy settings and make sure the settings you choose are what you want to apply, test on a machine or two before doing a mass rollout.

    Yes, get everything moved over to 6.1 then you can upgrade from there to version 7.

  • 0 in reply to FormerMember

    Thanks for the reply.

    I'm still not too clear though, I thought that the 5.61 clients can be managed by a  V6.1 or V7 server, is that correct.

    Will running the created MSI then just leave me with version 5.61 clients, but talking to the V6.1 server for management?

    I don't need to upgrade the clients unless I really have to, but we need support for Windows 10, hence the upgrade.


    Thanks
    Wayne

  • FormerMember
    0 FormerMember in reply to WayneTaylor

    Hello Wayne,

    Sorry for the delay, I've only just seen your new post.

    If you want support for Windows 10 you will need to upgrade your server to version 7.0
    The clients will need to be upgraded to 7.00.2.35, that includes support for Windows 10 and Windows 10 TH2.

Unfiltered HTML