Q: What is the licensing cost for XenAppAudit?
A: There is no licensing cost. XenAppAudit is free for anyone to use.
Q: Where can I buy XenAppAudit?
A: XenAppAudit is not for sale. It is free for anyone to use.
Q: Is this program supported by Citrix?
A: No. This program is of my own creation. It is not supported in any way by Citrix, GlassHouse or Microsoft. This is my own pet project; however, I did leverage Citrix’s knowledge base and SDKs for XenApp.
Q: What are the requirements to run XenAppAudit?
A: You will need XenApp Farm Administrator access as well as Server-level Administrator Access. When running on Windows 2008 or higher with UAC enabled, you will need to run as an administrator. When running XenApp 6 or XenApp 6.5, you will need the associated SDK installed on the server that is running the data collection scripts.
Q: What versions of XenApp are supported?
A: This utility has been tested against Citrix Presentation Server 4.0 and all current Citrix XenApp versions (4.5, 5.0, 6.0, and 6.5). There are some data elements that may not be available for all versions.
Q: How do I use XenAppAudit?
A: After extracting the ZIP file (preferably under C:\Program Files\XenAppAudit), simply run the START.BAT file. It will inspect your system and call the necessary data collection scripts. All executions are recorded in a transcript file located under the RESULTS folder. After the data collection is complete, you can then launch the front end application by opening XenAppAudit.mdb.
Q: How long does it take XenAppAudit to run?
A: That greatly depends on how large your Farm is, how many servers are the Farm, and your network topology. I generally see between 5 and 20 minutes, but some audits have taken as long as 45 minutes. I use a lot of WMI calls in the code to gather real-time data. These calls tend to be the longest running item. If you need to run the audits quickly, you can comment out or eliminate the WMI calls.
Q: Do I need to run the XenAppAudit utility on all servers?
A: No, you only need to run it on one server in the Farm. I typically run this on a Data Collector, but that is my personal preference.
Q: Can I run it on a non-XenApp server?
A: No, I wrote the scripts assuming the execution server is a XenApp server. However, you may be able to modify the scripts to suite your need.
Q: Can I run XenAppAudit multiple times?
A: Yes. It is designed to be run multiple times to allow subsequent audits and data comparison.
Q: How can I run XenAppAudit against multiple environments?
A: There are a couple of options. You can install the utility on one server in each environment and keep them stand alone. Also, you can copy the back end database (XenAppAudit_be.mdb) between servers to have one back-end. Another option is to modify the data collection scripts to use a network path to reference the RESULTS folder, as opposed to a local path.
Q: I have a problem with the XenAppAudit utility, where can I get support?
A: This utility is delivered as-is, with no warranties. Although I cannot provide direct support, I am happy to answer any email inquiries. Contact information is available under the “About Andy…” form. You may also post questions on the XenAppAudit page. Either for of inquiry will be answered as soon as possible.
Q: What language is used to run XenAppAudit?
A: XenAppAudit uses a variety of scripts and programming objects, including Batch Files, VBScript, PowerShell, Visual Basic for Applications, and Microsoft Access.
Q: Why did you use Microsoft Access?
A: My first professional job was as a Microsoft Access database developer, so I tend to fall back on Access when possible. I find Access to be easy to use for data analysis and customization. It provides and easy to use GUI, user forms, reports, and queries.
Q: Do I need Microsoft Access to use XenAppAudit?
A: Yes and no. You DO NOT need Access to run the XenAppAudit collection utilities. The Jet Engine database ODBC connections are built into Windows, so there are no special drivers needed, so the script can open the back-end database (XenAppAudit_be.mdb) and insert all the auditing data. However, you will need Access 2003 or higher to run the front-end utility (XenAppAudit.mdb), which is written in Access 2010.
Q: Can I change the code behind XenAppAudit?
A: Absolutely! I purposely chose to use Access and various scripts as opposed to a compiled EXE for this reason. Feel free modify any of the scripts or Access objects as necessary to fit your needs. Of course, changing the scripts may make it difficult to gain assistance if need be. If you find a flaw or have improvements after looking at the scripts, you can email me the recommended changes as well. I figure share and share alike!
Q: Can I redistribute XenAppAudit?
A: Sure. The easiest way is to link to this site. However, feel free to redistribute as necessary. I only ask that you give credit where credit is due.
Q: Can I re-brand XenAppAudit?
A: Please don’t. Feel free to modify and distribute as necessary, but a lot of time and energy went into this project. I only ask that you give credit where credit is due, and re-branding this effort would take away from that philosophy.
Q: I want to modify something on Access, but I don’t see the objects.
A: The XenAppAudit.mdb contains all the logic, but the objects are hidden. If you need to see them, press F11. Alternately, you can hold down the SHIFT key when opening the file and prevent the application start-up routine. The actual tables (and data) are linked to the XenAppAudit_be.mdb. Any table changes should be made there, then the linked tabled updated in the front-end application.