AlSolorzano.com

New to Presentation Server 4.5, Configuration Logging will log all changes made in the Citrix Access Management Console (for the Presentation Server node only) and the Presentation Server Console.  So it will log changes to published applications, farm level settings, server level settings, etc. It will not however log changes made using the Password Manager Node, Web Interface Node, or Access Gateway nodes, even though they show up in the Access Management Console. One can only hope that will come later.

Then reports can be run against the database from the Report Center in the Access Management Console.

This will be a great tool for larger organizations with multiple Citrix Administrators in the same farm or for when you really don't trust that person sitting next to you that just got back from a training course at the local CALC.
Requirements:

• The database for the configuration log must reside on a Microsoft SQL Server 2000 and 2005 and Oracle Version 9.2 and 10.2 databases.
• The database must have already been created prior to performing the next steps.
• It is recommended to use a domain service account with db_owner access to the above database.

To enable Configuration Logging:

1. Right click on the Farm in Access Management Console and select Properties.
   
   
2. Click on Configuration Logging on the left.
   
   
3. Click on the Configure Database... button.
   
4. Select the appropriate database type.
   
5. Select the database server name.
   
6. Select the Authentication Method.
   
7. Specify the windows credentials.
   Note: Unlike some of the other Citrix installers, you do not need to be logged in as the service account to install.  This wizard allows you to specify the Windows or database credentials during the setup.
   
   This example will use SQL Server as it is the most common.
   
8. Select the database and click Next.
   
9. If you are not using Database Encryption (and most people are not), then change Use Encryption to No and then click Next to the Advanced Option Screen.
   
   At this time, I have seen no reason to modify any of these settings.
   
   
10. In the Summary page, make sure to test your database connection before clicking on finish.
    
    
11. Then you will be returned to the 1^st screen. Select the appropriate options and click OK.
    
    
    Log administrative tasks to logging database - Better enable this or what you did in the prior steps was useless.
    
    Allow changes to the farm when database is disconnected - Depends on how highly available this database is. If it is on the server same database instance as the Data Store for the farm and you clearly notify the DBA that this database is just as important as the Data Store, then enable this option.
    If you think there is a risk that the Configuration database may be down... then you probably should not enable this option.
    
    Require administrators to enter database credentials before clearing log - I'd recommend enabling this so that only people with the service account credentials can clear the log, even if there are multiple Citrix Admins.
    
    

To generate a report against the Configuration Logging database:

1. Open the  Access Management Console, then click on the Report Center node on the left.
   
2. Click on Generate Report in the Common Tasks section.
   
3. Select Configuration Logging Report for the Report Type.
   
4. Create a new specification if necessary or use an existing specification.
1. To create a new specification, select Create and use a new specification. Click Next.
2. Enter a Name for the connection. (Example: Configuration Log) and click Create.
3. Select Microsoft OE DB Provider for SQL Server (SQL Server was used in the previous example) and click Next.
4. Enter the server name for the database server.
5. Select the authentication method (Note: If using Windows NT Integrated, you may need to log off and then back on as a user with rights to view the database).
6. Select the database and then click Test Connection.
7. If everything returns with Successful test, then click OK.
8. Then click Next.
   
5. Select the Farm name
   
6. Now define what you want to look for and click Next.
   You can modify the date, the type of items to look for, the name of an item or a specific username depending on what data you are looking for in the configuration log.
   
   
   
7. Unless you are planning to publish the report to a web site or file share, click Next at the Publishing Details screen.
   
8. If you are planning to run the same report multiple times, click Save specification and name it. Then click Next.
   
9. Then click finish to run the report.
   
10. After the report has finished running,  you can right click on a completed report and view it, save it, mail, etc.
    

 

Note: To clear the log, from the Farm node of the Access Management Console, select Action > All tasks > Clear configuration log