I created a video for Citrix TV some time on the Configuration Logging configuration for XenApp 5 on server 03 so now I decided to return to the subject with XenApp 6.5 in a blog.
What recording setup and why use this?
When multiple administrators make changes to a XenApp farm, Citrix recommends implementing configuration logging. By tracking changes each director to the system and the correlation of reported problems later, it is easy to identify the changes that might have to be canceled.
For example, if an administrator modifies an application properties published at 10:00 Helpdesk associated escalate issues several sessions being launched by users, it would be easy to correlate the altered change sharing session.
This feature is designed to support basic administrative logging for XenApp. This function also displays information stored in the database for logging data via the history node.
Creation of the logging database XenApp configuration
The Configuration Logging feature supports Microsoft SQL Server and Oracle databases; for information on the supported versions, see CTX114501. In this post I am using Microsoft SQL Server 08 R2 to the base of the Configuration Logging database.
Open Microsoft SQL Server Management Studio
On the Databases node and right-click New Database
Enter a name for logging XenApp 6.5 database configuration and click oK.
Definition of basic permissions Logging configuration data
the first time that the logging function configuration is enabled; it connects to the base of the Configuration Logging data and finds that there is no database schema. XenApp then creates the database schema, tables and stored procedures. To create a database schema, XenApp needs full access to the database using SQL Server authentication or Windows authentication.
Citrix recommended to use Windows authentication because it is more secure than SQL authentication.
To enable appropriate access to the database in SQL Server Management Studio expand the Security node and connection right click and select New Connection
use the search button to find windows domain account to use for authentication to the database.
In this case, we created the AD account configlogging only in order to connect to the database.
Ensure that the default database is selected as the base configuration logging data and click OK.
Then we must map the connection created configlogging a database user and assign appropriate rights.
In SQL Server Management Studio, expand the Databases node, expand the base data logging configuration that we created, expand the Security node, right-click Users and select New User
Add connection configlogging account and grant dbo_owner
once the database schema is created full access will no longer be necessary. Additional users with less permission can be created; you can read more in our edoc product or below the Defining Access Basic Configuration Logging data permissions ... More ... section
Setting database permissions for logging configuration - http :. //support.citrix .com / proddocs / topic / XenApp6-w2k8-admin / ps-keep-define-db-perms.html
Configure Database Connection Configuration Logging
now that the basic configuration of the logging database was created, we need to configure XenApp to create the database schema, tables and stored procedures.
Open the App Center Console, right-click the farm and obtain agricultural properties
Select the only available log and the node configuration open the database Set ...
Select the connection type that SQL
Select your SQL server from the list box to low, if you have connection problems try to use the IP address of SQL server.
Check Windows Integrated Security
Use the account configlogging we created earlier [ domain account ]
Specify the basic configuration logging database on the SQL server from the drop-down list
Disable the Use encryption.
Test the database connection to ensure that we have connectivity to the database.
Click Finish to complete the connection settings
Set the logging properties configuration
to enable configuration logging, select the check box connection administrative tasks logging configuration database. If you want administrators to be able to make changes to the farm when journal entries can not be recorded in the database of the Configuration Logging data, select changes to the farm when database connection check box Allow offline.
to prompt administrators to enter their credentials before clearing the log, select require administrators to enter database credentials before clearing the check check log.
Running the Configuration Logging reports
to XenApp 5.0, the configuration logging is a function that worked hand in hand with the report Center node in the XenApp management console. The Report Center has been removed from XenApp 6. Logging reports have now moved to a new node called "History".
To perform a right-click on the report History node and click Get the newspaper. This will generate an entry of administrative tasks performed in the XenApp farm configuration log.
The configuration of log entries are displayed in chronological order, details about each event can be found in the information panel below.
the Save Log option lets you save an existing configuration log in an XML file.
The Set filter allows administrators to specify certain criteria for reporting. We can filter by date and time, the administrators and the specific types of items.
Clear History delete existing entries configuration log from the console. If the administrator needs to enter the database credentials before clearing the log has been activated, you will be asked for DB credentials before the paper can be erased.
One last thing to mention in this post, you can restrict administrator access to the Configuration Logging properties at the farm level. This can be done by creating a custom management group. Apply all necessary permits required but uncheck the edit Configuration Logging settings. The administrator will still be capable of implementation reports through the crux of the story, but they can not change the Configuration Logging properties.
For more information on XenApp logging 6.5 config check edocs website here:
Registration of administrative changes to a XenApp farm
definition of basic permissions logging configuration data ... More ...
As requested by one of our readers, we will enter some details on the exact permissions required for Citrix administrators using the basic configuration logging data.
For example, in this scenario, I have a Citrix administrator called userone (this could also be an administrative group). a user needs to access the recording configuration, so here's how we'll put in place:
Open SQL Management Studio, we need to create a new connection for our admin (s ) Citrix under the security node.
In the user mapping section we need to map our user account to the logging database configuration XenApp 6.5. Click ok
Now we need to update the permissions on all stored procedures found in the logging database 6.5 XenApp configuration highlighted below -Dessous.
right click and properties of GetCounts stored procedure.
We need to add our Citrix administrator so they have executable permissions to the stored procedure. Click the search button to find the user and grant them execute permissions. Click OK to finish and repeat the steps above on all stored procedures.
Logging Database configuring permissions
This section quickly I want to discuss the approval of the database. Once the database schema is created, full access is required, we can reduce their rights to configlogging account.
Permissions can me modified by right clicking on the XenApp 6.5 database configuration logging and select Properties. In the permissions section explicitly open the tab
The authorization required minimum for connection to the base of the Configuration Logging data :.
Connect, Execute, Insert, Select and Update
Click OK to finish.
0 Komentar