Skip to main content

Resetting admin login password for GMS Application Interface of SonicWall GMS Virtual Appliance on UMA

By

If you have many SonicWall Firewall, it is not easy to manage without SonicWall GMS.

GMS have two logins for System Interface and Application Interface.

System Interface is to manage your GMS Hardware Appliance or Virtual Appliance.

Application Interface is to manage your SonicWall devices in your network.

So, you can contact to SonicWall Technical Support if you forgot the login password of GMS System Interface. But to do so, you need valid support contract/license. (So take note it and do not forget if you didn’t renew support contract/license. :P)

For application interface login password, you do not need Tech Support if you know how.

As human being, I am sure you will forget your password sometimes and here is how to reset the GMS Application Interface Password.

First, you will see like below if you forgot password.


You need MySQL Query Browser to access GMS Database in order to reset the password.

1.      Download it from below link and run it on the machine which is located in same subnet of GMS UMA or subnet which able to access of GMS UMA.

http://downloads.mysql.com/archives/query/
2.     Open MySQL Query Browser:


3.        Log into the SGMSDB database using either the ‘root’ account or the account you chose during Role Configuration:


4.     Enter this command in the top panel, then hit the ‘Execute’ button:


                
5.     The Admin password has been reset.  You can now log in to the Application Interface using the username ‘Admin’ with the password ‘password’:

I did this demonstration on GMS Virtual Appliance Version 7.2.
Have a good time.
(Be knowledgeable, pass it on then)
Labels:

Comments

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more