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

SEC - Client re-direction to new server in a different domain

Auck30

Scenario: - One SEC server (4.0)in domain X and a new SEC server (5.1) in Domain Y.

Question: - What is the best way to get some clients (mix of win & mac) to change from the Server in domain X to be managed by server in domain Y. (without having to do a client reinstall)

:36997


This thread was automatically locked due to age.
  • 0

    Hello Auck30,

    for the Macs there's only a reinstall. For the Windows clients please see How to redirect Windows endpoints to a new management server.

    Will the clients also change their domain membership or is there a trust? Which SESC/SAV version is installed on the clients and will it be the same in the SEC5.1 environment? 

    Christian.

    :37007
  • 0

    Clients will stay in the own domain at the moment (there is a trust).  Clients have SESC 10 which in be the same in the new enironment.

    While the new server has a new setup with new policies, there are only a few test clients on there at the moment.

    Is there any options at server level which could slowly being the clients over from the old server.  Maybe by copying certs etc from the old to new.

    Any thoughts would be very helpful

    :37087
  • 0

    Hello Auck30,

    to use the same certificate on the new server you'd have to export/import them before install. As there is a trust one option would be to reprotect the clients from the new SEC and the other to redirect them (as outlined in the article referred to in my previous post). The former is probably the easier way if you can discover the clients from the new SEC. 

    Christian

    :37091
  • 0

    The reprotect option sounds like a good option.  However, while I can discover the computers on the new server when I try to reprotect can get the following:

    The applied software subscription does not contain software the computer can use.

    The machine currently has SESC on it and is pointing to the old server without any issues.

    :37097
  • 0

    Hello Auck30,

    a quick test confirmed my assumption - you get this message if you attempt to protect a Windows 8 computer with a pre-10.2 version (e.g. 10.0). Guess at the moment there is no other combination. While 10.0 works with Windows 8 (or v.v.) only 10.2 officially supports Windows 8. Upgrading the clients  to 10.2 when reprotecting them should not cause problems. Either change the subscription to 10.2 or add a 10.2 subscription solely for the Windows 8 clients.

    Christian

    :37101
  • 0

    Yes that works.  I can now discover and re-protect any windows machines.  Thank You

    The problem I have come across now is that the new server will not discover any mac machines that are not on either domain.

    I am trying to discover via IP, but no joy.  No error message, just no machines discovered.

    These none domain mac are on the old server without any problems. 

    :37121
  • 0

    Hello Auck30,

    the new server will not discover any mac machines ...

    whatever the reason it's not worth investigating: You have to (re-)protect the Macs manually (Protect Computers works for Windows only), they will the appear in the Unassigned group (AFAIK the install still does not configure the updating policy like on Windows, thus the Macs won't update unless you move them to a specific group - there is a way to pre-configure AutoUpdate though) . If you want to pre-populate the groups so the the Macs receive an updating policy after install please have a look at Import computers from a file in the Console Help.    

    Christian

    :37123