Upgrade Pending

Discussion in 'NOD32 version 2 Forum' started by Cosmo32, Jan 10, 2011.

Thread Status:
Not open for further replies.
  1. Cosmo32

    Cosmo32 Guest

    I use v2.7 Business Edition on my server ATM. My server is W2KServer. My plan is to upgrade my server to w2K3Server first...... No! I can not afford W2k8Server at this time.....:oops:...(all my clients are WinXPsp3).

    First, I plan to get my server stable with Win2003 Server.
    Second, I plan to install ESET v4 A/V Business Edition on the new Server OS.
    I have 2 questions........

    1) Are there any Un-Install/Install "gotcha's" I need to think about?

    2) Should I remove/un-install my current v2.7 BE ESET code BEFORE I backup my Server's current DATA?
    Thank you very much.
     
  2. ThomasC

    ThomasC Former ESET Support Rep

    Joined:
    Sep 8, 2008
    Posts:
    209
    Hello,

    After you upgrade your server and install ESET there are some additional considerations. Please refer to the following Knowledgebase articles as they apply to your situation.

    ESET recommended server settings:
    http://kb.eset.com/esetkb/index?page=content&id=SOLN2144

    Microsoft’s virus scanning recommendations for a server:
    http://support.microsoft.com/kb/822158

    As for uninstall / install issues, if you run into any refer to this article:
    http://kb.eset.com/esetkb/index?page=content&id=SOLN2289
     
  3. Cosmo32

    Cosmo32 Guest

    ThomasC,
    Thank you for your perspective and the links. My opening thread was focused on activities prior to the server OS upgrade. Old news! I have completed my backup and now my server runs Win2K3 Server SP2 plus 110 critical updates! I did an Upgrade Installation.
    I will use you links now as I dig into getting this new "beast" throttled back to my needs.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.