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

best migration route to 4.5 on new tin

Currently running em3.5 and NAC 3.1 on a, getting long in the tooth, w2k3 box.  Would like to replace it with new tin (actually a VM running w2k8 on a new box)  Whats the best way forward for this?

Looking at the guides I get the impression that it'll be an in place upgrade from 3.5 to 4 and then 4.5 and then migrate to a new box which is a bit of a ball ache.  We're only running with around 250 clients so would it actually be quicker to just start afresh with a new install of 4.5?  I can see the problem being NAC (we have around 100 or more Linux boxes all of which have defined MAC exclusions) so that might be a pain and sorting out the client various policies we have as we run HIPS and Application control. 

So I was thinking of installing 4.5 on the new VM leaving 3.5 and NAC 3.1 in place and running on the old box.  Configuring 4.5 and moving our servers and win7 boxes over to it to install 9.5 (win7 boxes aren't running NAC)  I can then turn off the DHCP agents so that NAC doesn't do anything and install NAC on the new box and configure that, but I'm going to have to do some manual messing around with the NAC rules and MAC exclusions.

Comments?

:3786


This thread was automatically locked due to age.
Parents
  • ok I've done a test migration and things seem to work fine, except NAC.  The new NAC client installs ok and the clients seem to get registered with the NAC server but after a little while I get an error on the client.

    "The agent was unable to communicate with the server in order to report results"

    Sophos SEC and NAC are running on a Hyper-V virtual box with the databases running on a full fat SQL box.

    I get the issue on Vista boxes that were running NAC 3.3 and on Windows7 boxes that have never had the NAC client installed on them

    :3931
Reply
  • ok I've done a test migration and things seem to work fine, except NAC.  The new NAC client installs ok and the clients seem to get registered with the NAC server but after a little while I get an error on the client.

    "The agent was unable to communicate with the server in order to report results"

    Sophos SEC and NAC are running on a Hyper-V virtual box with the databases running on a full fat SQL box.

    I get the issue on Vista boxes that were running NAC 3.3 and on Windows7 boxes that have never had the NAC client installed on them

    :3931
Children
No Data