Email Required, but never shown. The Overflow Blog. Podcast Who is building clouds for the independent developer? Exploding turkeys and how not to thaw your frozen bird: Top turkey questions Featured on Meta. Now live: A fully responsive profile. Reducing the weight of our footer. Related 0. Hot Network Questions. Question feed. Accept all cookies Customize settings. SQL Server 6.
Reason: Server is in script upgrade mode. Only administrator can connect at this time. Check the status values for detail. InvalidCastException exception when you run an application that calls the Server. The content index is corrupt. Could not redo log record" 9. NET-connected application tries to reuse a connection from the connection pool in SQL Server "The request failed to run because the batch is aborted" 9.
The entries may resemble the following:. This entry provides all the necessary information about the product, such as version, product level, bit versus bit, the edition of SQL Server, and the OS version on which SQL Server is running. The output of this query has been enhanced to show additional information, as documented in the blog post article, What build of SQL Server are you using? The output of this query has been enhanced to show additional information.
This tool gives information about all the instances of SQL Server that are installed on the system. The only thing to be aware of is that this tool can be run locally only on the system where SQL server is installed. It cannot be used to obtain information about remote servers. To determine which versions of the client tools are installed on your system, start Management Studio, and then click About on the Help menu.
See the following screenshot. The version is also displayed in the Reporting Services Configuration tool. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of Analysis Services.
Method 2: Check the version of the Msmdsrv. The default locations are shown in the following table. For more information about verifying Analysis Services build versions review Verify Analysis Services cumulative update build version.
Because replication agents may be installed on several different computers, it is important to check the installed versions on all affected computers. For example, the Distribution Agent in Transactional or Peer-to-Peer replication may exist on computers that differ from the publisher instance of SQL Server and may exist on the various subscriber instances of SQL Server in a pull subscription.
Therefore, you have replication agent files that are installed on the IIS web server. And you may have to check the version of those. For more information, see Upgrade or patch replicated databases. Except for Sqlservr. The versions of these files will change only when there is a fix to the respective component.
Generally, you can check the file version of each of these. The highest version in the list is the version of the full-text search component that is installed on the system.
You can use one of the following methods to determine the version of the full-text search component that is installed on your system. Firstly for any data to appear you need to enable AppFlow on your NetScaler Gateway virtual server s.
To make use of this, the following is required:. If you click on an individual user, you can see each HDX session, active or terminated, that the user made within the selected time frame. Other information includes several latency statistics and bandwidth consumed during the session. You can also get bandwidth information from individual virtual channels such as audio, printer mapping and client drive mapping.
Clicking the Desktops section shows latency metrics and any past or present connections to Desktop sessions. You can see what browsers were used during authentication and Operating Systems used.
You can see active user sessions, licenses consumed, terminated sessions, bandwidth uses by all or specific Gateways etc. To use Gateway Insight you must be running NetScaler v11 build Under the User Logon Activity section you get a view of the number of users who have authenticated to NetScaler Gateway over the selected period of time.
Click on the Authentication tab to get a list of user authentication failures, what gateway was used, client IP address and timestamp information is also included. If you click on an individual user MAS sorts all authentication failures in to view for that user including failure reasons etc.
Clicking on Terminated Session and Active Sessions towards the bottomg of the page gives you a list of Active and Terminated Sessions for that particular specified time frame. Click on Gateways. If you have multiple Gateways, you can click on one to get specific details such as authentication failures against this Gateway, total number of sessions etc.
This section allows you to generate a number of reports against instances such as:. And more. Click on the Infrastructure Networks tab. If you scroll down the page you will come to the Events by Severity section. This graphics shows any clear, minor or major events that have occured on any of your configured instanced in the last 5 minutes, hour, day, week or month.
In this example during the past day my NetScaler has encountered a number of minor and major events. Directly below you can also see the health and up time for the appliance over the past day. Scroll down further and you will come across models, versions, certificate expiry, NetScaler Config saved status and configuration drift. This is helpful, because if you for example have expiring certificates or you have NetScaler configurations that are not saved you will be alerted.
This shows a nice dashboard with the certificates, key strength, self signed vs CA signed and so on. If you click on to one of the sections on the dashboard such as Self Signed, you will be directed to a view containing the self-signed certificates for easy viewing and management.
If you click on one of the sections i. Config Saved you are brought to the below screen. From here you see a list of your instances that have their configuration saved. If you select an instance and click Action , you have the option to poll now, run configuration differences between points in time, and download configuration locally.
If you click on the Running Configuration button, you get a list of all configration entries currently running. The same goes for the Saved Configuration button. Audit Templates can be used to make sure certain configurations exist on your NetScaler appliances. Say for example you want to make sure all appliances have the optimal cache settings configured or have certain SNIPS or NTP servers configured, the Audit Templates runs every 12 hours and if the NetScaler appliance does not have the configuration the template is looking for, the appliance is flagged as being different from the template.
Note: Starting MAS Simply save the Audit Template as a Configuration Template, and then you can create a Configuration Job based on the saved template. Enter a template name, description optional and click Add Instances. Now under Template Commands enter the commands you want the template to check is present in ns.
The audit template is ready to go. As previously mentioned, audits run every 12 hours. We can however force an audit. Click Yes to begin a poll on ns. Click on Diff Exists. Here we can see the appliance and that a difference exists between the template and running configuration. Click on Diff Exists again. Now we can see that the template CheckforDNS has failed and the NetScaler appliance has a different configuration from what the template is looking for.
Click Diff Exists. Using the Export all the corrective commands exports the commands to a TXT file. NMAS has the ability to scan your instance and give you a list of best practice recommendations to configure on the NeScaler.
You can upload a configuration file or select and scan a managed instance. Click Select Device , choose your instance and click Get Configuration. NMAS analyzes the configuration. Once complete, a list of recommendations will be displayed in view. Check a recommendation such as the one I have below. Enter some required user information. To the right of the screen is a small icon.
Click this then choose Apply Now. The recommendation has been applied to the remote appliance. Over on the remote appliance we can see the new user has been created successfully. With this in mind, be aware that you may have to perform some final configurations on an applied recommendation.
You may need to adjust the time period to 1 month for example. From there you can see a list of events logged such as configuration changes, if the NetScaler went down, SNMP authentication from devices etc.
Select an event and click Details. NetScaler VPX. If we select the appliance, we can click View Backup. No backup exists. This is because this NetScaler was only recently discovered and automatic backups take place at am. To take a manual backup, simply select Back Up. Enter a password to protect the file if desired and click Continue. After a few moments the backup will complete.
From here you can download the file or perform a restore. Click Action. Note: You cannot change the host name to use a custom name for example. You can also replicate configuration of one device to another. Here you can upload a license to NMAS.
By default MAS can monitor up to 30 virtual servers within discovered instances. By clicking System Licenses you can see the virtual server limit of 30 and the actual number of managed virtual servers. Introduced with the Select a Virtual Server and click Mark Unlicensed. If you still want to license those virtual servers, disable Auto-select Virtual Servers. Non-addressable Virtual Servers such as Unified Gateways for example will not be automatically licensed.
In previous versions of MAS servers were licensed automatically after each polling cycle if the number of licenses servers were less than the licenses limit.
MAS Now click on Select Virtual Servers. Choose which servers you want to license and click Save and Exit. Click on Rules. Here we can create a rule based on an incoming event. Click Add. We will create a rule that sends an email based on a certain type of received critical event. Under Category choose entitydown and sslCertificateExpiry. At the bottom of the page, click Add Action. Set the Action Type to Send e-mail Action and choose your pre-created email distribution list.
You can choose to repeat the email notifications and the frequency they are repeated. The new rule is created.
The new rule can be triggered if the device is rebooted or goes offline. Click on Event Settings. Here you can alter the severity settings for any event category. Choose an event category and click Configure Severity. Use the Severity dropdown box to choose a severity other than Major. We can use this wizard to install a certificate on a remote NetScaler instance. Complete the below fields.
0コメント