![command to export citrix xenapp 6.5 application qfarm command to export citrix xenapp 6.5 application qfarm](https://support.citrix.com/files/public/support/article/CTX112082/images/0EM600000009Ygp.gif)
$values = import-csv Values.txt -Header $header #header value in powershell "Import-CSV" must be an array, a text variable parses as one header item $dirlist = Get-ChildItem -filter *.conf | Select-Object -ExpandProperty Name
![command to export citrix xenapp 6.5 application qfarm command to export citrix xenapp 6.5 application qfarm](https://techgenix.com/content/va/img/upl/image0081350587211159.jpg)
#* amoung all three that have had a value set. confs I started with there are 160 values #* WebInterface files and deleting all lines that start with "#" and then removing duplicates The "Values.txt" file was generated by taking the numerous #* headers then go through that file and compare if the uncommented values exist as compared This script will take the file name of the conf files to use as the CSV For the purposes of our uses I have renamed the. #* Description: This script will generate a CSV file of all the nf files that you copy into
![command to export citrix xenapp 6.5 application qfarm command to export citrix xenapp 6.5 application qfarm](http://blog.citrix24.com/wp-content/uploads/2014/01/sql-restore-8.jpg)
We suspect that something is misconfigured at ADC as BDC does not have this issue nor does it need this tweak, but this is our work around until that is resolved. To resolve this issue for us we added a startup script with the simple command “ipconfig /registerdns” and within a few seconds the IP address is registered within DNS correctly and with the correct NIC.
#COMMAND TO EXPORT CITRIX XENAPP 6.5 APPLICATION QFARM WINDOWS#
Logging into the server it was deteremined that it’s DNS was registered to the wrong NIC (it was a PVS server that was multi-homed) and even worse for some of the servers, the NIC IP address was an old address and the new address wasn’t even resolving!įor some reason it now appears our Windows 2008 servers are not registering their DNS on startup. Doing a qfarm /load showed the problematic servers had no users on them at all, and no load evaluators were applied that would be causing our issue. One set of servers at BDC was fine, the other set of servers at ADC had a subset of servers that were not. This wasn’t much help, but I was able to narrow down that this was happening on one set of our servers that are split across two DC’s.