Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 0 subscribers
  • Views 32528 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

Fresh Install of EC 5.3 on Windows 2012

Joetobai

Hi There,

We currently have EC 5.1 running on Windows 2003 with 2000 connecteed clients. I would like to do a fresh installation on Window 2012. Any tips

Thanks

:57859


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

    Hello J,

    updated the Mrinit.conf file

    where? On the old or the new server, in the root (SAVSCFXP) of the CID or the RMS subdirectory? Did you create an additional CID?

    the Update path which has been edited

    points to the new old server?

    Reminds me of this old article, but ... what's your updating interval? As the endpoints initially go to the Unassigned group on the new server - do you move them to a specific group once they appear?

    I'm trying to envision how the behaviour you describe could be evoked ...

    • add a CID on old, edit mrinit.conf and put it in the RMS subdirectory
    • let endpoints update from this CID on old, RMS will reconfigure (mrinit.conf.orig will be saved) and start to communicate with new
    • endpoints appear on new, are moved to a group which instructs them to update from new
    • as there is no mrinit.conf in the RMS subdirectory endpoints will fall back to mrinit.conf.orig
    • endpoints re-appear on old

    Clearly at this point the updating policy on the endpoint does not comply with that on old - wonder whether and when this is detected though. Maybe I've overlooked something though.

    Anyway, if you - on new - put  mrinit.conf also in the RMS subdirectory (running ConfigCID afterwards) the endpoints should "stay".

    Christian

    :57960
Reply
  • 0

    Hello J,

    updated the Mrinit.conf file

    where? On the old or the new server, in the root (SAVSCFXP) of the CID or the RMS subdirectory? Did you create an additional CID?

    the Update path which has been edited

    points to the new old server?

    Reminds me of this old article, but ... what's your updating interval? As the endpoints initially go to the Unassigned group on the new server - do you move them to a specific group once they appear?

    I'm trying to envision how the behaviour you describe could be evoked ...

    • add a CID on old, edit mrinit.conf and put it in the RMS subdirectory
    • let endpoints update from this CID on old, RMS will reconfigure (mrinit.conf.orig will be saved) and start to communicate with new
    • endpoints appear on new, are moved to a group which instructs them to update from new
    • as there is no mrinit.conf in the RMS subdirectory endpoints will fall back to mrinit.conf.orig
    • endpoints re-appear on old

    Clearly at this point the updating policy on the endpoint does not comply with that on old - wonder whether and when this is detected though. Maybe I've overlooked something though.

    Anyway, if you - on new - put  mrinit.conf also in the RMS subdirectory (running ConfigCID afterwards) the endpoints should "stay".

    Christian

    :57960
Children
No Data
Unfiltered HTML