2 Replies Latest reply on Oct 11, 2015 7:11 AM by Malik Haider

    Upgrade Issues in UAC/Group Poilcy Environment

    Andy McBride

      Hi All,

       

      I am having a ton of issues upgrading NPM 11.0.1 to 11.5.2. Typically the web portion of the config wiz will fail. I have tried running permission checker before I do anything and this seems to help but I stall do not have a good upgrade.

       

      Can anyone share how you convinced a customer to create an open and unrestricted local admin? They seem to not want to do this at all. Any other tips are welcome.

       

      Andy

        • Re: Upgrade Issues in UAC/Group Poilcy Environment
          cjfranca

          I in place shows him the problem and the solution, show the documentation that says what he has to do and because it has to do.
          Without the permissions you can not upgrade, it is requisite in the manual. It also shows the very best in the new version to him to see what he can lose if you do not give permission for you to do your job.

          • Re: Upgrade Issues in UAC/Group Poilcy Environment
            Malik Haider

            Below recommendation / requirements are already mentioned in Orion Admin Guide and KB post below.

             

             

            SolarWinds Knowledge Base :: Disabling User Account Control (UAC)

             

             

            Disabling User Account Control (UAC)

            In some cases, having User Account Control (UAC) enabled on Windows Server 2008 and Windows Vista (evaluation-only) can lead to installation errors. The following procedure disables UAC to address these issues.

            To disable User Account Control (UAC):

            1. Using an account with administrative privileges, log on to the Windows 2008 server hosting your Orion installation.
            2. Click Start > Control Panel > User Accounts.
              Note: If you have not configured the Control Panel to display in Classic View mode, you may need to click User Accounts again.
            3. Click Turn User Account Control on or off.
            4. Click Continue to confirm that you started the User Accounts Control Panel action.
            5. Clear Use User Account Control (UAC) to help protect your computer.
            6. Click OK
            7. Click Restart Now to restart your server and apply the UAC settings change.

            To enable UAC again, repeat the procedure above, confirming that the Use User Account Control (UAC) to help protect your computer option is checked.

            This article applies to:
            Modules of Orion Network Performance Monitor version 9.5 and higher

             

             

            http://www.solarwinds.com/documentation/orion/docs/orionnpmadministratorguide.pdf

             

            Slow Performance on Windows Server 2008 If Orion is installed on Windows Server 2008 and there are any devices on your network, between your Orion server and your database server, that do not support RFC 1323, the TCP window size auto-tuning feature of Windows Server 2008 may prevent your Orion server from successfully connecting with your Orion database. This TCP auto-tuning feature is intended as a network-sensitive restriction, applied by the receiver—your SolarWinds Orion server—on the amount of data it is allowed or able to receive. If any devices along the network path between your Orion server and your Orion database do not support the TCP window scaling detailed in RFC 1323, the allowed size of the TCP window in packets sent to your Orion server may not match the TCP window size reported by packets sent from your Orion server. This mismatch may lead to failed connections between your Orion server and your Orion database. The following procedure disables this TCP auto-tuning feature, resetting the TCP receive window to 64kB. 721 To disable tcp auto-tuning: 1. Click Start > All Programs > Accessories. 2. Right-click Command Prompt, and then click Run as administrator. 3. If you are prompted by User Account Control, click Continue to open the elevated command prompt. Note: In some cases, having User Account Control (UAC) enabled on Windows Server 2008 can lead to installation errors. For more information about disabling UAC, see the article "Disabling User Account Control (UAC)" in the SolarWinds Knowledge Base.