Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 918 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

Brute Force Upgrade - What is the best way ?

BrickMan

Currently in we have SEC4.5 and EndPoint 9.5 running in production on 5000 computers.

We have built a new SEC5 server, SQL Server (not on same server) in our dev environment.

What we would LIKE to do is move workstations, in groups at a time, from the existing SEC4.5 to the new SEC5 without performing an 'in-place' upgrade on the existing SEC4.5 server. After moving all computers to the new SEC5 we can just shut off the SEC4.5 and be done with it.

What would be some things to watch out for ? Should it just be a matter of adding the workstations (from file) to SEC5 and deleting them out of SEC4.5 prior ?

Do we need to build a custom installer package for EndPoint10 for distribution under SEC5, or should leaving it with the default package and pushing it with the console be good enough ? (XP and Win7 workstations).

We DO want to push the client from SEC5, as under SEC4.5 someone had the bright idea of distributing the EndPoint installation via Novell ZenWorks. -_-

:23789


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

    now if the new server is installed with the same certificates as the old one (you did not say if you have done so or if you intend to install SEC once more for production) the it's just configuring RMS in the CID and creating an updating policy on the old server pointing to the new one. Client groups can then be moved by just assigning this policy to the desired groups.
    Importing from a file and a pushed install should also work (provided you can successfully use Protect computers from the new server. Deleting a client from SEC has no effect - once a client contacts its management server again it is "undeleted" - in other words, deleting does not make a client unmanaged.
    Can't say in which way ZenWorks could affect the outcome though.

    Christian
    :23791
Reply
  • 0
    Hello Brickman,

    now if the new server is installed with the same certificates as the old one (you did not say if you have done so or if you intend to install SEC once more for production) the it's just configuring RMS in the CID and creating an updating policy on the old server pointing to the new one. Client groups can then be moved by just assigning this policy to the desired groups.
    Importing from a file and a pushed install should also work (provided you can successfully use Protect computers from the new server. Deleting a client from SEC has no effect - once a client contacts its management server again it is "undeleted" - in other words, deleting does not make a client unmanaged.
    Can't say in which way ZenWorks could affect the outcome though.

    Christian
    :23791
Children
No Data