2 Replies Latest reply on Oct 18, 2013 4:38 AM by ptinreston

    Login OK Button Grayed Out FMS Admin Console

    martinsorich

      Having issue with FMS Admin console OK button being grayed out after correct account name and password are set. This is for FMS 12 (VMWare Virtualized Server 2008) accessed from a Windows 7 client computer with Java 7 update 40. The FMS Admin console works fine on the server machine and the OK button is grayed out until the password is set for the login prompt.

       

      What I have tried:

      1) uninstall and reinstall Java on client computer

      2) rebooting the client computer

       

      Any suggestions?

       

      Thanks for your help.

       

      Martin

        • 1. Re: Login OK Button Grayed Out FMS Admin Console
          LyndsayHowarth

          Have you allowed remote admin?

           

          - Lyndsay

          • 2. Re: Login OK Button Grayed Out FMS Admin Console
            ptinreston

            This happened to me just yesterday. 

             

            Here's what worked for me to solve the problem… perhaps this will work for you as well… 

             

            This is going to sound foolish or rude at first, but please bear with me… I'll explain.

             

            When the Admin Console window first appears and you log in, type in the user name and then type in the password.  The "OK" button should then be enabled while you are typing the first few characters of the password. 

             

            It's my habit to copy a password from my keychain and then paste it into the password field, and then do the same for the username.  Some password systems do not work when I do this (for legimate reasons), and the Server Admin Console log-in is one of those systems.  After I tried the copy and paste method, the login window wouldn't enable the "OK" button no matter what I did.  I had to cancel out of that window and start from the beginning. 

             

            I presume that this kind of thing is done to prevent crackers from rapidly trying to log in with a list of candidate passwords.  Though that practice might be bit annoying, I think it's prudent. 

             

            I don't know that this will solve your problem, but I hope it will.