Citrix Issus and Solutions
Xenserver Error: SR_BACKEND_FAILURE_181
Symptoms:
After installation or upgrading to Xenserver 6.0, you might experience issues with any storage related operations and following error message might appear
“SR_BACKEND_FAILURE_181 Error In metadata Volume Operation For SR.”
The following entries might appear in the log /var/log/SMlog file:
Error code: SR_BACKEND_FAILURE_181
Error parameters: , Error in Metadata volume operation for SR. opterr=VDI delete operation failed for parameters: /dev/VG_XenStorage-427796a3-6891-dcb7-681f-cc7c5463ea0a/MGT, 7b496cd3-9d9c-4cb4-b510-4613e65e7141. Error: not well-formed (invalid token): line 1, column 99,
[10146] 2011-11-27 08:05:10.977985 Raising exception [181, Error in Metadata volume operation for SR. [opterr=VDI delete operation failed for parameters: /dev/VG_XenStorage-511f729e-0f0e-a679-9b8e-4d7ed28f6537/MGT, 65f8e675-9416-4909-8cd1-b7d75af06762. Error: not well-formed (invalid token): line 1, column 65]]
[10146] 2011-11-27 08:05:10.978109 lock: released /var/lock/sm/511f729e-0f0e-a679-9b8e-4d7ed28f6537/sr [10146] 2011-11-27 08:05:10.979583 ***** sr_scan: EXCEPTION SR.SROSError, Error in Metadata volume operation for SR. [opterr=VDI delete operation failed for parameters: /dev/VG_XenStorage-511f729e-0f0e-a679-9b8e-4d7ed28f6537/MGT, 65f8e675-9416-4909-8cd1-b7d75af06762. Error: not well-formed (invalid token): line 1, column 65]
Cause:
XenServer 6.0 or 6.0.2 does not properly store the incoming virtual machine name-label and description fields in management VDI (MGT).
Workaround:
A workaround for this issue is to remove all special characters from the virtual machine name-label and description fields. Contact Citrix Technical Support to assist you in resolving the preceding issue
In cases where the preceding workaround has not worked, you will have to rebuild the SR MGT volume after removing the special characters:
1. Run lvscan and look for the MGT volume for that respective SR.
Example: ACTIVE '/dev/VG_XenStorage-c14bee2a-44da-656a-5b99-865818c0a700/MGT' [4.00 MB] inherit
2. Run a test to verify that the lv can be renamed:
lvrename –t /dev/VG_Xenstorage- <SR-uuid>/MGT /dev/VG_Xenstorage- <SR-uuid>/MGT.bak
3. When the preceding test is successful, run lvrename without the “-t” option:
lvrename /dev/VG_Xenstorage- <SR-uuid>/MGT /dev/VG_Xenstorage- <SR-uuid>/MGT.bak
4. Restart the master host in the pool or unplug and re-plug the Physical Block Device (PBD) on the Master Host for the respective SR to build a new MGT volume.
Example:
Find the Master Host UUID > xe pool-list params=master
master ( RO) : 9079cff1-c457-4e51-b924-8a9e1ec24179
To find the master PBD> xe pbd-list sr-uuid= c14bee2a-44da-656a-5b99-865818c0a700 host-uuid=9079cff1-c457-4e51-b924-8a9e1ec24179
uuid ( RO) : 99c6d7ec-75ef-1071-d925-5ff6b4667ecc
host-uuid ( RO): 9079cff1-c457-4e51-b924-8a9e1ec24179
sr-uuid ( RO): 20daa9a1-a9b2-ddc9-30a7-c4e15999a284
device-config (MRO): device: /dev/sdb
currently-attached ( RO): true
a. Unplug the PBD for the master (using the PBD UUID from previous step):
xe pbd-unplug uuid=99c6d7ec-75ef-1071-d925-5ff6b4667ecc
b. Re-Plug the PBD to attach the host to the SR again:
xe pbd-plug uuid=99c6d7ec-75ef-1071-d925-5ff6b4667ecc
This process will have rebuilt the MGT volume with the updated information without the special characters in the Virtual Machine name or description that was previously causing the errors.
If workaround will not solve your issue try Resolution given below.
Resolution:
Refer to the following Knowledge Center articles for the current updates that address.
CTX135411 - Hotfix XS60E022 - For XenServer 6.0
CTX135623 - Hot fix XS602E013 - For Xenserver 6.0.2
How to Manage Auto Archive in Outlook 2010
If you want to keep Outlook 2010 clean and run faster, one method is to set up the AutoArchive feature. Today we show you how to configure and manage the feature in Outlook 2010.
Using AutoArchive allows you to manage space in your mailbox or on the email server by moving older items to another location on your hard drive.
Enable and Configure Auto Archive
In Outlook 2010 Auto Archive is not enabled by default. To turn it on, click on the File tab to access Backstage View, then click on Options.
The Outlook Options window opens then click on Advanced then the AutoArchive Settings button.
The AutoArchive window opens and you’ll notice everything is grayed out. Check the box next to Run AutoArchive every…
Note: If you select the Permanently delete old items option, mails will not be archived.
Now you can choose the settings for how you want to manage the AutoArchive feature. Select how often you want it to run, prompt before the feature runs, where to move items, and other actions you want to happen during the process. After you’ve made your selections click OK.
Manually Configure Individual Folders
For more control over individual folders that are archived, right-click on the folder and click on Properties.
Click on the AutoArchive tab and choose the settings you want to change for that folder. For instance you might not want to archive a certain folder or move archived data to a specific folder.
If you want to manually archive and backup an item, click on the File tab, Cleanup Tools, then Archive.
Click the radio button next to Archive this folder and all subfolders. Select the folder you want to archive. In this example we want to archive this folder to a specific location of its own.
The .pst files are saved in your documents folder and if you need to access them at a later time you can.
After you’ve setup AutoArchive you can find items in the archived files. In the Navigation Pane expand the Archives folder in the list. You can then view and access your messages.
You can also access them by clicking the File tab \ Open then Open Outlook Data File.
Then you can browse to the archived file you want to open.
Archiving old emails is a good way to help keep a nice clean mailbox, help speed up your Outlook experience, and save space on the email server. The other nice thing is you can configure your email archives and specific folders to meet your email needs.
Citrix Connections gets stuck on 'Connection Established, Negotiating Capabilities'
Source: http://support.citrix.com/article/CTX123816
ICA connections become unresponsive or stop at "Connection established. \r\nNegotiating capabilities” specific to client workstation or domain user. Also \r\nconnecting to a specific server always stops at “Connection Established, \r\nNegotiating Capabilities”.
\r\nFor example:
\r\nMy machine + his\\her credentials = success
Another machine + his\\her \r\ncredentials = success
His\\Her home machine + his\\her credentials = \r\nfailure
His\\Her home machine + test ID = failure
\r\n
Cause
\r\nUsually this is caused by an inaccessible license server. Server \r\nresults in not getting a correct license, probably the license server detects \r\nthat several servers are using the same license and blocks it, especially if \r\nservers are cloned.
\r\nResolution
\r\nCaution! This procedure requires you to edit the registry. Using \r\nRegistry Editor incorrectly can cause serious problems that might require you to \r\nreinstall your operating system. Citrix cannot guarantee that problems resulting \r\nfrom the incorrect use of Registry Editor can be solved. Use Registry Editor at \r\nyour own risk. Back up the registry before you edit it.
\r\n
\r\n
1. On client workstations with this issue, change the permissions on \r\nthe registry key HKLM\\SOFTWARE\\Microsoft\\MSLicensing. Grant the \r\nUsers group Full Control or specific domain user account.
If you \r\ndelete the key, Terminal Services recreates it when it acquires a \r\nlicense. However, the permissions on this key are set to read-only by default. \r\nOnly administrators have full control rights. Stating that only an administrator \r\ncan request a Terminal Services license for this server. Once it is acquired, \r\nevery user can use it.
\r\n
2. Delete
HKLM\\Software\\Microsoft\\MSLicensing\\HardwareID \r\n
HKLM\\Software\\Microsoft\\MSLicensing\\Store keys \r\n:ClientLicense,CompanyName,LicenseScope,ProductID
ICA Connections Becomes Unresponsive or Stops at 'Connection Established, Negotiating Capabilities'
Symptoms
ICA connections become unresponsive or stop at "Connection established. Negotiating capabilities” specific to client workstation or domain user. Also connecting to a specific server always stops at “Connection Established, Negotiating Capabilities”.
For example:
My machine + his\her credentials = success
Another machine + his\her credentials = success
His\Her home machine + his\her credentials = failure
His\Her home machine + test ID = failure
Cause
Usually this is caused by an inaccessible license server. Server results in not getting a correct license, probably the license server detects that several servers are using the same license and blocks it, especially if servers are cloned.
Resolution
Caution! This procedure requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Back up the registry before you edit it.
1. On client workstations with this issue, change the permissions on the registry key HKLM\SOFTWARE\Microsoft\MSLicensing. Grant the Users group Full Control or specific domain user account.
If you delete the key, Terminal Services recreates it when it acquires a license. However, the permissions on this key are set to read-only by default. Only administrators have full control rights. Stating that only an administrator can request a Terminal Services license for this server. Once it is acquired, every user can use it.
2. Delete
HKLM\Software\Microsoft\MSLicensing\HardwareID
HKLM\Software\Microsoft\MSLicensing\Store keys :ClientLicense,CompanyName,LicenseScope,ProductID
Source: http://support.citrix.com/article/CTX123816
How to Generate Microsoft Baseline Security Analyzer (MBSA) Report:
The Microsoft Baseline Security Analyzer provides a streamlined method to identify missing security updates and common security misconfigurations. MBSA 2.3 release adds support for Windows 8.1, Windows 8, Windows Server 2012 R2, and Windows Server 2012. Windows 2000 will no longer be supported with this release.
MBSA Software is installed in 132.140.3.56 IT360 Server of Bajaj
Go to All Programs and launch MBSA 2.2
Once you launch MBSA 2.2 it will provide you below GUI mode Tool
Choose an option for the type of Scan you want
Over here I have selected Scan a Computer, if you select Scan Multiple Computer you have to provide Range of IP of the server for which you need to generate report
Over here I have provided the Server IP for which we need to Generate Report,
Click on Start Scan:
After clicking Start Scan It will start generating the report as shown below:
Once scan get complete report will get generated
We can save this report in XPS format by clicking Print this Report and provide the path where the report needs to save.
MBSA tool can be downloaded from Microsoft site using below Link:
http://www.microsoft.com/en-us/download/details.aspx?id=7558
To know more on MBSA tool, how to use it and all use below link:
http://msdn.microsoft.com/en-us/library/ff647642.aspx
Network monitor 3.4 is not showing the LAN card to capture the logs
Refernce link
http://social.technet.microsoft.com/Forums/en/netmon/thread/52bd288f-b315-4dd3-834d-f914b0e7e792
http://sgwindowsgroup.org/blogs/panda/archive/2011/05/21/resolve-why-no-network-adaptor-shows-up-in-microsoft-network-monitoring-tool-plus-bonus-issue.aspx
Resolution
After we install Netmon tool on our production machine… NO network adaptor shows up in the tool for us to capture network traffic in \ out the machine!
Findings and Solution (Part 1) – Missing Driver
After much troubleshooting, we found out that it is because that the “Microsoft Network Monitor 3 Driver is not installed as network services under the “Local Area Connection Properties”
So, we tried to add it back! But guess what?… We hit another issue! Error message pops up saying that “Filters currently installed on the system have reached the limit”
LOL~ More issue? Never mind, we always understand that there is always a workaround. How?
Finding and Solution (Side track) - Workaround to resolve "Filters Currently Installed on the System Have Reached the Limit” is as follow…
Step 1 – “Regedit” (Note: Please ensure you know what you are doing first, if not, please backup the registry key first!)
Step 2 – Locate the registry key “MaxNumFilters” under HKLM\System\Currentcontrolset\Control\Network\
Default Value is “8” that means you can have up to 9 adaptors (Count from “0” to “8”)
Step 3 – Change the Value to “A”, means the we can have up to 11 adaptors (More than enough for me~)
Step 4 – Click “Ok” and reboot the machine! (MUST REBOOT!!)
Once completes, you will see that the “Microsoft Network Monitor 3 Driver” appears!
Then, you can happily launch the Microsoft Network Monitor 3.4 tool and see the network adaptors to select from as shown below!
Other possible cause why you cannot use netmon… Rights issue!
If you install the tool with local administrator account but need to run as domain user, please remember to add the necessary account into the “Netmon User” group!
Hope above sharing is useful to anyone who is keen to use netmon!! I am getting to Love this tool
Still not appearing run below command
If you are part of that group, try running ‘sc query nm3' from the command line to see if the driver is in the running state.
If it's not running or installed try running 'nmconfig /install' as an administrator and see if that fixes the issue.
Project Learnings
Please find the some interesting observation while working with Xenserver Hypervisor.
During the installation of the Xenserver 6.0\\6.0.2 we will get a window for selecting the storage so if we are implementing the HVD solution then we should click on the below option as well, it will boost your performance and you will get huge benefits while integrating Provisioning services with Xendesktop solution.
Before installation of the Xen server hypervisor please make sure you should have the management console IP with you, once you will provide one IP and post that if you will change the MGMT console IP there 90% chances you will lose the MGMT IP and it will not allow you to reassign the IP once again, so learning here is make sure once you will assign the IP for MGMT console we should avoid changes.
Never ever bond your MGMT interface with any of the other interface it will give you lot of troubles and it would be difficult for you to track where is the issue, you will be intermittently disconnected from the VMs as well as you will be getting disconnected from the MGMT console.
Due to some challenge if you are planning to do a bonding between MGMT console and other interface then always remember golden thumb rule says you should create the bond in Active-Passive !!! as the Active-Active will give you lot of troubles.
If you want to remove a server from the Pool of Xenserver then by right clicking and selecting remove will give you trouble and will still have UUID of the removal storage and the CD-rom drive in the Master server so always remember to follow the correct sequence which is DETTACH-FORGET-REMOVE
Link to follow-http://support.citrix.com/article/CTX131328/
While creating a Pool always check the hardware details of all the server which you are planning to add and plan it properly, if you have server from different CPU family then always remember the GOLDEN THUMB RULE IS TO DEDICATE THE MASTER SERVER AS THE HIGH END SERVER WHICH IS HIGH IN CONFIGURATION AMONG ALL YOUR SERVER. If you will not follow this and you will assign any of your server as the Master server then you will not be able to add other servers into the farm !!! we faced this in our implementation.
If you have given any hardware for the Xenserver Hypervisor installation always make sure to check the server in the HAL of citrix, whereas you will find some server where the installation will complete properly but after that the server will not boot from the HDD !!! in this case it is not an issue with the hardware , we need to do the installation in a different way and we need to disable the GPT option in Xenserver.
Link to follow- http://rackerhacker.com/2012/01/13/xenserver-6-disable-gpt-and-get-a-larger-root-partition/
While creating a Bond in the Xenserver if you are getting issue then check if you have to disable the open V-switch and you can recheck it.
While configuring the HA in any pool of the Xenserver at that time make sure you should set a proper priority so that the first server which you want to make up should be start and initialize first and then the other servers in the flow… Example- during a disaster if your HA will restart the Vms in any other server then you don’t require your Citirix Secure gateway to come up first as by that time your Xenapp or Xendesktop would have not started so always plan the priority list properly before planning a HA.
While replacing any hardware for Xenserver always remember to set the server to maintaiance mode and then reboot or else it will take next 35-40 minute to come back as it will do a memory scrubbing which is known bug of Xenserver
Hi Team,
During the implementation of the IBANK, Bajaj,Edelweiss Project we came through lot of challenges and we found the solutions as well.
Please find the some interesting observation while working with Xenserver Hypervisor.
During the installation of the Xenserver 6.0\6.0.2 we will get a window for selecting the storage so if we are implementing the HVD solution then we should click on the below option as well, it will boost your performance and you will get huge benefits while integrating Provisioning services with Xendesktop solution.
Before installation of the Xen server hypervisor please make sure you should have the management console IP with you, once you will provide one IP and post that if you will change the MGMT console IP there 90% chances you will lose the MGMT IP and it will not allow you to reassign the IP once again, so learning here is make sure once you will assign the IP for MGMT console we should avoid changes.
Never ever bond your MGMT interface with any of the other interface it will give you lot of troubles and it would be difficult for you to track where is the issue, you will be intermittently disconnected from the VMs as well as you will be getting disconnected from the MGMT console.
Due to some challenge if you are planning to do a bonding between MGMT console and other interface then always remember golden thumb rule says you should create the bond in Active-Passive !!! as the Active-Active will give you lot of troubles.
If you want to remove a server from the Pool of Xenserver then by right clicking and selecting remove will give you trouble and will still have UUID of the removal storage and the CD-rom drive in the Master server so always remember to follow the correct sequence which is DETTACH-FORGET-REMOVE
Link to follow-http://support.citrix.com/article/CTX131328/
While creating a Pool always check the hardware details of all the server which you are planning to add and plan it properly, if you have server from different CPU family then always remember the GOLDEN THUMB RULE IS TO DEDICATE THE MASTER SERVER AS THE HIGH END SERVER WHICH IS HIGH IN CONFIGURATION AMONG ALL YOUR SERVER. If you will not follow this and you will assign any of your server as the Master server then you will not be able to add other servers into the farm !!! we faced this in our implementation.
If you have given any hardware for the Xenserver Hypervisor installation always make sure to check the server in the HAL of citrix, whereas you will find some server where the installation will complete properly but after that the server will not boot from the HDD !!! in this case it is not an issue with the hardware , we need to do the installation in a different way and we need to disable the GPT option in Xenserver.
Link to follow- http://rackerhacker.com/2012/01/13/xenserver-6-disable-gpt-and-get-a-larger-root-partition/
While creating a Bond in the Xenserver if you are getting issue then check if you have to disable the open V-switch and you can recheck it.
While configuring the HA in any pool of the Xenserver at that time make sure you should set a proper priority so that the first server which you want to make up should be start and initialize first and then the other servers in the flow… Example- during a disaster if your HA will restart the Vms in any other server then you don’t require your Citirix Secure gateway to come up first as by that time your Xenapp or Xendesktop would have not started so always plan the priority list properly before planning a HA.
While replacing any hardware for Xenserver always remember to set the server to maintaiance mode and then reboot or else it will take next 35-40 minute to come back as it will do a memory scrubbing which is known bug of Xenserver
MDSM Installation
Complete the following steps to install Modular Disk Storage Management (MDSM) on a host running a supported Windows operating system.
Installation of MDSM
1. You must have administrative privileges to install MDSM on a Windows host.
• Insert the MD3000i Resource CD and navigate to the main menu.
• From the main menu, select install MD3000i Storage Software
Alternatively, locate and run the MDSM setup.exe program.
2. The setup program will check for the existence of the Microsoft iSCSI Initiator and the correct Storport hot-fix revision.
NOTE:
A minimum version of the Storport driver must be installed on the host server before installing the MD Storage Manager software. A hotfix with the minimum supported version of the Storport driver is located in the \windows\Windows_2003_Server\hotfixes directory on the MD3000i Resource CD. The MD Storage Manager installation will test for the minimum Storport version and will require you to install it before proceeding.
3. The Micrososft iSCSI Initiator software should also be installed on a host before MDSM is installed. If the iSCSI initiator is not installed, at the end of the installation the user will see a warning screen advising them to uninstall MDSM, install the iSCSI Initiator software, and then reinstall the MDSM host software.
4. When all the prerequisites are met, the user will be able to proceed normally with the software installation.
5. The user will receive a popup window that requests that changes be made to the registry before proceeding. Clck OK.
6. At the opening screen of installation choose the language from the list box and press Ok.
7. At the Introduction screen click Next.
8. In the License Agreement screen choose to accept the license agreement and click Next.
9. Leave the default path for installation of the software and click Next.
10. Select Typical (Full Installation) and then click Next.
11. Select the Automatically Start Monitor radio button if you require the the event monitor to be running on this host.
Otherwise, select the Do Not Automatically Start Monitorradio button.
NOTE:
You should configure only one system to automatically restart the event monitor. Running the event monitor on mulitple systems can cause multiple alert notifications to be sent for the same error condition. Enabling event monitoring on only one system avoids this issue.
Click Next to continue.
12. Click Install.
13. The user will see the following two screens during installation.
NOTE:
Note the lines in the second screen which show the installation and loading of the MPIO driver. This is done in every installation of the MDSM on a Windows server. It is loaded regardless of whether the system has redundant pathways, and is not optional.
14. Click Done to restart the system.
Discover and Install Your MD3000i Strorage Array
The default IP addresses of the management Ethernet connectors on the RAID Controllers are as follows:
• Controller 0
o Management Port - 192.168.128.101
o iSCSI Port 0 - 192.168.130.101
o iSCSI Port 1 - 192.168.131.101
• Controller 1
o Management Port - 192.168.128.102
o iSCSI Port 0 - 192.168.130.102
o iSCSI Port 1 - 192.168.131.102
NOTE:
By default, the MD3000i controller management ports will request a DHCP-assigned IP address. If these dynamically assigned addresses are not in the same subnet as the management host, the automatic discovery process will not find the array. The discovery of arrays is only on the host's subnet through port 2463.
If a DHCP response is not acknowledged, the controller management ports will default to addresses shown above.
If the controller management ports have had IP addresses manually set, the units will no longer request DHCP addresses and will continue to operate at the manually set addresses.
If you are trying to discover and manage an MD3000i array with unknown manually assigned IP addresses, follow the procedure towards the end of this page.
Discovery and Installation of MD3000i
1. Launch the MDSM GUI. A window will immediately appear asking the user to choose between Automatic discovery or Manual. If the array is on the same subnet as the host, you may select the option button for Automatic and click OK.
If the array management IP addresses have already been determined, you may select manual and insert the two controller IP addresses.
2. The discovery screen will show a progress bar while performing discovery of out-of-band storage arrays. In-band storage management is not available until an iSCSI session is set up and operating.
3. At the end of the discovery process the user will need to close the discovery window. Click Close to close the window.
4. When the MDSM interface is focused on an MD3000i, it will add a new management tab in the window, labelled "iSCSI."
5. The newly discovered array can now be named for quicker and easier identification.
Click OK to continue
Discovering Unknown Management Port IP Addresses
The automatic discovery process may fail if your MD3000i array has unknown manually configured management port IP address. Automatic discovery will work only if the management port IP addresses are on the same subnet as the management host.
To discover the MD3000i management port IP addresses, follow these steps:
Management Port IP Address Discovery
1. Connect the MD3000i serial cable between the serial port of your host PC and the management serial port of controller 0 of your MD3000i array.
2. Open Windows HyperTerminal and enter a connection name.
Then click OK.
3. Select the host com port to which the serial cable is attached.
Then click OK.
4. Configure the port settings for the HyperTerminal session, as follows:
• Bits per second: 115200
• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
5. In the HyperTerminal session, press Control-B.You will then see the following screen.
6. Press Q and then Enter
at the screen prompt, type netCfgShow and then Enter
7. The management port settings for this controller will be shown. These include the IP Address settings for the port.
Now connect the serial port to the management port on the other MD3000i controller.
Repeat these steps to discover the IP Address settings for the remaining controller.
please refer to the following instructions to generate MD3000 support logs
1. On the Support tab, click Gather Support Information.
2. Click Browse to display the Collect All Support Data dialog box.
3. In the Save in drop-down box, navigate to the location where you want the report saved.
4. Type a meaningful name in the File name text box, and then click Save. (A combination of array name and date is helpful in logging an issue over time.)
5. Click Start to save the compressed (zip) file containing support data to the location chosen above
Please follow the below steps to add the local storage which is in different RAID group in the Xenserver 6.0.2.
Step-1
Need to go to the local console of the Xenserver and type the below command
cd/
cd dev
ls sd*
After this you will get to know which is last
Step-2
Please shoot the below command to add it where
Sdc= the newly added device
Host-UUID= you need to check it from the Xencenter and copy the host uuid
Name-label= any name for your new SR
Difference between Clone and Template
XENAPP server Shows load as 10000 with no user logged in to user
Symptoms\r\n
A XenApp Server shows a load of 10000 or full load, regardless of Load \r\nEvaluator settings and Load Evaluator or Worker Group status.
or
The server shows a QFARM /LOAD of 10000, even if no users or sessions \r\nof any kind are active on the server.
Cause\r\n
The Windows Management Instrumentation (WMI) service is required \r\nfor data collection for tools such as EdgeSight. WMI corruption can affect the \r\nservers reporting ability of the correct load.
Resolution
To resolve this issue, complete the following procedure:
\r\n
\r\n
1. Stop the Windows Management Instrumentation (WMI) \r\nService.
\r\n
\r\n
2. Run the following command:
winmgmt \r\n/salvagerepository
\r\n
\r\n
3. Run the following command:
winmgmt \r\n/resetrepository
\r\n
\r\n
4. Restart the IMA Service with WMI Service.
\r\n
\r\n
5. Verify that the load is accurate.
Referral Links
http://support.citrix.com/article/CTX132837
http://support.citrix.com/article/CTX129350
http://support.microsoft.com/kb/300956
XenServer VM Stuck Powering On / Off
On a few occasions I have been faced with a virtual machine running on a XenServer either not powering off (staying yellow), or not powering on.
The first thing to try is to force the VM to power off with the following command:
xe vm-shutdown vm=SERVER01 --force
However this does not always work if the xapi is out of sync with the pool master, which is used by XenCenter.
To resolve this the Xen Toolstack can be restarted with the following command:
xe-toolstack-restart
This will restart the xapi disconnecting XenCenter, after a 30 secs you should be able to reconnect with XenCenter.
Issuing xe-toolstack-restart does not affect any running VMs.
Now you should be able to power off / on the problematic VMs.
Refernce link for the same
http://innitec.wordpress.com/2012/03/12/xenservers-vm-cannot-shutdown-and-stuckhalt/
XENDESKTOP VM's get shutdown automatically
Symptoms
While the VM's added to Desktop group post the user logs off or kept idle the VM's Automatically Shutdown
Cause
Power managment policy was causing this issue
Resolution:
Run the below command on Xendesktop server on Windows powershell
Set-BrokerDesktopGroup -name 'GROUPNAME' -AutomaticPowerOnForAssigned $false
Set-BrokerDesktopGroup -name 'GROUPNAME' -shutdowndesktopafteruse $false
Set-BrokerDesktopGroup -name 'GROUPNAME' -peakbuffersizepercent 100
XenDesktop License Error: You cannot access this session because no licenses are available
XenDesktop License Error: You cannot access this session because no licenses are available.
A XenDesktop session fails to start, with the following error:
"You cannot access this session because no licenses are available."
The Broker log might contain the following errors:
Controller:EventLogManager decided to log event CDS_EVENT_LICENSE_NONE_CHECKED_OUT of type Warning with arguments:
This is based on event log groups LicensingCheckout
Licensing:MFLic_GetLicense result Success, request result Rejected
Licensing:License request rejected, flex code -18
Windows Events, logs the following application error:
Event ID: 9027
Event Source: Citrix ICA Service
Error 0 received while obtaining a license for a Citrix XenApp client connection.
The license request has been rejected.
Or
The license error “flex code -18” shown in the DDC log stands for “License server system does not support this feature”.
Cause
Licensing is not set up properly in XenDesktop Site; thus, licenses are not checked out on the license server when the user tries to start a new XenDesktop session.
- XENDESKTOP (DDC) server not able to communicate with Licensing server or not able to draw
- Edition/Modile of license set on the XENDESKTOP/DDC server and License server does not match
- Licensing is not setup properly on the XENDESKTOP/DDC server
- licenses are not checked out on the license server when the user tries to start a new XenDesktop session
Resolution 1
1. Check the configuration of the site:
The PowerShell command Get-BrokerSite shows license configuration for the site:
For Virtual Machine hosted apps
AppLicenseEdition
ApplicationLicenseModel
For XenDesktop sessions
DesktopLicenseEdition
DesktopLicenseModel
2. Compare your configuration with the licenses used in the environment.
You can check this in the license server.
3. Change the site configuration using the Set-BrokerSite PowerShell command.
Examples:
To configure the site to use the Platinum edition use the following command:
Set-BrokerSite -DesktopLicenseEdition PLT
To set up Virtual Machine hosted apps to use Platinum edition:
Set-BrokerSite -AppLicenseEdition PLT
Resolution 2
1. Restart the below mentioned services
On the DDC
Restart the Citrix services on the DDC.
Note: This can be done on a live system and will not affect the users.
• Citrix AD Identity Service
• Citrix Broker Service
• Citrix Configuration Service
• Citrix Diagnostic Facility COM Service
• Citrix Host Service
• Citrix Machine Creation Service
• Citrix Machine Identity Service
On the License Server
• Citrix Licensing
• Citrix Licensing Config Service
• Citrix Licensing Support Service
2. Access Desktop Studio > Configuration > Licensing > Change Licensing Server > Verify.
3. If the issue persists, restart all the DDCs in the farm one by one.
Resolution 3
1. Download and install the most recent version of the licensing sever
2. And once the new license server installed configured ready to user
3. Restart the Citrix Broker Service on the DDC server
REFERAL LINK
http://support.citrix.com/article/CTX130961
https://forums.citrix.com/message.jspa?messageID=1638166
http://forums.citrix.com/thread.jspa?threadID=306036&tstart=0
XD 7.1 Controllers getting DB Connectivity Lost.
Symptoms:
1. Event ID 8623 In the Data Base Servers.
2. Citrix Broker Service Connectivity lost in both the controllers.
3. New Users will not be able to login.
4. Need to Restart MSSQL Server Service.
Solution/Resolution
We have Installed Hotfix update 3 for XD 7.1. Post Installing we didn't observe 8623 Events in Data Base Server and Also no DB Connectivity lost events in Controllers.
http://support.citrix.com/article/CTX142021
Windows 2008 R2 hangs at "Please Wait for the System Event Notification Service" during the logoff
I have found similar problem in MS forum. Here is excerpt:
These steps MUST be performed by another domain user (since you won't be able to login to the machine yourself if you're the one experiencing the problem- obviously).
1. Login to the server
2. Open "Task Manager" and click on the "Services" tab
3. Sort all services by "Name" (first column), and find the service named "SENS"
4. Right click on this and select "Go to Process"
5. End the process this takes you to (normally an svchost.exe)
6. Open Windows Services (Start -> Run -> type "services.msc")
7. Start the "System Event Notification Service"
In order to perform these steps myself I simply created a secondary domain admin account which I can use each time I experience the issue.
I have found similar problem in MS forum. Here is excerpt:
These steps MUST be performed by another domain user (since you won't be able to login to the machine yourself if you're the one experiencing the problem- obviously).
1. Login to the server
2. Open "Task Manager" and click on the "Services" tab
3. Sort all services by "Name" (first column), and find the service named "SENS"
4. Right click on this and select "Go to Process"
5. End the process this takes you to (normally an svchost.exe)
6. Open Windows Services (Start -> Run -> type "services.msc")
7. Start the "System Event Notification Service"
In order to perform these steps myself I simply created a secondary domain admin account which I can use each time I experience the issue.
VDA Is getting Unregistered After Couple of hours.
1. Machine will be Showing as unregistered in Studio.
2. User Will be logged in and he can able to work.
3. Once he disconnect / logoff and try to reconnect back, he will not able to login.
4. logs say connectivity lost to Controller.
Resolution/Solution
update the VDA with latest hotfix . It can be downloaded from
http://support.citrix.com/article/CTX140473
Users are unable to login on HSD_32 Farm for Ratnakar Bank
Have added 4 additional XEN app (5.0)VM (2003 win server ) for manage the load and issue got resolved
Remove XEN PVDISK from Windows Safely Remove Hardware Wizard
This article explains how to remove the “XEN PVDISK SCSI Disk Device” \r\nfrom the Windows Safely Remove Hardware wizard. This removal is typically \r\ndone to provide a cleaner Windows experience for end users, particularly in a \r\nvirtual desktop scenario.
XenServer allows administrators to hot-plug and hot-unplug virtual disks into \r\nWindows virtual machines. Disk that can be hot-unplugged from Windows show up in \r\nthe Safely Remove Hardware wizard. XenServer tells Windows which virtual disks \r\ncan be hot-unplugged by the unpluggable parameter on the virtual block \r\ndevice (VBD) that the virtual disk is associated with.
http://support.citrix.com/article/CTX123961
SOLUTION
1. Identify which XenServer virtual machine (VM) or template that you \r\nwant to stop displaying the XEN PVDISK device in the Safely Remove Hardware \r\nwizard. If these steps are performed on a template, each virtual machine that is \r\nlater created from this template is affected by the change.
2. Log on to the console of a XenServer hosting the particular VM or \r\ntemplate identified in Step 1. This is typically done by selecting a XenServer \r\nin XenCenter and clicking on the Console tab.
3. Identify the Universally Unique Identifier (UUID) of the VBD that \r\nyou do not want to appear in the Safely Remove Hardware wizard. This can be \r\naccomplished by executing the following command in the XenServer \r\nconsole:
xe vbd-list vm-name-label=<Name of VM or Template> \r\ntype=Disk params=uuid
Here is an example where the VM name is “XP \r\nGolden”. The UUID reported will be different for each VBD.
If there is more than one virtual disk assigned to your VM or template, \r\nyou need to use additional commands to identify which VBD you want to apply the \r\nconfiguration to or just apply the configuration to each VBD.
4. Using the UUID identified in Step 3, change the unpluggable \r\nparameter to false by executing the following command in the XenServer \r\nconsole:
xe vbd-param-set uuid=<UUID from Previous Step> \r\nunpluggable=false
Here is an example continuing from the example in \r\nthe previous step. The UUID used is different for each VBD.
5. If the VBD is connected to a VM that is currently running, the VM \r\nmust restarted for the setting to take effect.
Best Practices for Citrix XenApp Hotfix Rollup Pack Installation and Deployment
http://support.citrix.com/article/CTX120842
FAQ : http://support.citrix.com/article/CTX127228
Considerations Prior to Installation
Order of Deployment
The order of hotfix rollup pack deployment is very important, especially in large or complex farm configurations. Before installing a hotfix rollup pack:
• Ensure that there are no existing connections on any servers
• Ensure that the Independent Management Service is running
• Back up the data store database.
After a deployment, always ensure that all servers in the farm are updated to the same hotfix rollup pack level.
Citrix recommends the following order of deployment:
1. Zone data collector
2. Backup zone data collectors
3. Database connection server (Applies only to Resource Manager for XenApp 5 for Microsoft Windows Server 2003)
4. Primary farm metric server (Applies only to Resource Manager for XenApp 5 for Microsoft Windows Server 2003)
5. Backup farm metric server (Applies only to Resource Manager for XenApp 5 for Microsoft Windows Server 2003)
6. Member servers
The hotfix rollup pack installs and updates only servers that have core XenApp (mps.msi) and/or XenApp Advanced Configuration (cmc.msi) installed.
Common Install and Uninstall Methods
There are many installation methods currently used by customers. Some of the most common installation methods include the following:
• Double-clicking the hotfix rollup pack installer file
• Command line installation by using the msiexec or cpatch commands
• Active Directory deployment by using a batch file
• Installation Manager
Installing hotfix rollup packs over an ICA session is not supported but you can install while logged in as an administrator over a remote desktop session. Also, administrative image and slipstreaming of the hotfix rollup packs is not supported.
Uninstalling hotfix rollup packs is supported. The same methods used for installing are supported for uninstalling. After uninstalling, all files are restored to the previous patch level. In certain situations, uninstalling a hotfix rollup pack prompts for the original source CD location; this happens when the offline plug-in, Streaming Profiler, Single sign-on, and the Access Management or Delivery Services Consoles are installed on the same server as the hotfix rollup pack. In these situations, it is recommended to always run a reinstall or repair on the components after you uninstall the hotfix rollup pack to restore the correct files.
Conclusion
These best practices help mitigate some of the installation issues you might experience. Testing a hotfix rollup pack thoroughly before deploying it in a production environment, while taking into consideration the information contained in the readme, is your primary task to a successful deployment. Taking into consideration a role based order of deployment and common installation methods also helps the process.
Citrix recommends that you thoroughly evaluate hotfix rollup packs on a test server or farm. Ensure that you cover some testing comparable to the tasks of an everyday user, as well as some administrator oriented tasks.
Examine the readme that accompanies the hotfix rollup pack. Readmes provide necessary information on the prerequisites and known installation issues. Common installation prerequisites might include an updated version of the license server, a particular redistributable (such as Java or .Net Framework), and so on. The readmes are kept up to date even after the hotfix rollup pack is released to the Web.
On occasion, installing a hotfix rollup pack can invalidate certain hotfixes. This happens when some of the fixes included in a hotfix are not included in the hotfix rollup pack. For a list of invalidated hotfixes and their replacements, see the Hotfix Rollup Pack readme. You can obtain or request the corresponding replacement hotfix for any invalidated hotfixes by contacting support.
Make note of the release dates of different hotfix rollup packs and components (such as plug-ins, consoles, and so on) and attempt to install these in the order they were released. You can find the release dates on the download page of each hotfix rollup pack or component. For example, the XenApp 5 for Windows Server 2003 components were released before Hotfix Rollup Pack 3; therefore, it is recommended to install the components first, followed by Hotfix Rollup Pack 3. Because hotfix rollup packs are cumulative, there is no need to install earlier hotfix rollup packs. The latest hotfix rollup pack includes the fixes from all the previously released hotfix rollup packs for that product.
Best Practices for XenApp Administrators
http://support.citrix.com/article/CTX127574
Top 10 Best Practices
# Description Relevant Links
1 Backup the Farm Data Store Regularly
This database contains the persistent farm information including published applications, servers, policies, and other settings. Should it become corrupted or the database server fail, without a current backup, the farm must be recreated. Remember to also verify the integrity of your data store backups by performing test restores on another server or instance. CTX677542
2 Build at Least One Test Environment/Farm
A test environment is critical for testing new applications, updates, and settings before rolling them out into production. Having one or more test servers in a production farm is not sufficient because they still connect to the production database and can potentially impact the production servers in the farm. Create a separate farm or farms for testing with settings that closely resemble what is used in production. None
3 Keep Current with Updates and Hotfixes
Operating system, application, and Citrix hotfixes and updates should remain current to prevent issues from arising and maintain the performance, stability, and security of the environment. Always test updates and hotfixes in a test environment prior to rolling them out into production. With XenApp, all hotfix rollup packs (HRPs) should be applied after testing and individual hotfixes applied only if denoted as critical or to address a specific problem being faced. CTX120842
CTX127228
4 Implement a Change Management Plan
Most enterprise XenApp deployments are administered by several individuals or teams which can make it challenging when trying to track down changes. Creating a change management plan within your organization makes it easier to pinpoint changes and makes troubleshooting more efficient. In addition, the Configuration Logging feature of XenApp can be enabled to record changes made within the management console for later viewing. Search “Configuration Logging” at the Product Documentation site www.citrix.com/edocs
5 Avoid Non-native/3rd-Party Printer Drivers
Printing problems are among the most frequent areas that Citrix Technical Support sees on a regular basis. One of the main factors attributed to printing problems are because of non-native or third party printer drivers which are not designed or tested to work in multi-user environments such as Terminal Services/Remote Desktop Services. Always use native/inbox printer drivers and the Citrix Universal Print Drivers to prevent printing problems. CTX111967
CTX126093
CTX119815
6 Get Familiar with Common Tools
Different tasks and problems call for different sets of tools. It is important to familiarize yourself with the Citrix and third party tools and their usage both from a proactive and reactive standpoint. CTX122827
CTX126294
7 Know the Types of Memory Dumps
Dumps are created when processes or the operating system itself crashes. Dump files can also be manually generated when troubleshooting issues such as hangs or memory leaks. It is important for administrators to understand the types of dump files available and ensure that their servers are properly configured for kernel or complete memory dumps. KB254649
CTX105888
CTX466627
8 Understand Zones and the Data Collector
Zones are groupings of XenApp servers designed to create a hierarchical structure and efficiently handle changes as they are made. Every server farm has at least one zone and the number of zones should be kept to a minimum to avoid additional complexity. Each zone has a data collector which manages the dynamic information for servers in that zone. The data collector is determined by a preference that the administrator sets. Every zone should have one server set as Most Preferred and one or more servers with a preference of Preferred to take over the role should the data collector become unavailable. Search “Zones” at the Product Documentation site www.citrix.com/edocs
CTX126335
9 Monitor Farm Health
It is important to ensure the health of all servers in a XenApp environment and be alerted when problems arise or might soon arise. XenApp includes a Health Monitoring and Recovery feature which consists of various tests on core components. If any tests should fail, alerts can be triggered along with actions such as removing a server from load balancing. In addition, standalone tools such as MedEvac can be used to periodically assess farm health. For more comprehensive monitoring, the Citrix EdgeSight product may be used. Search “Health Monitoring and Recovery” at the Product Documentation sitewww.citrix.com/edocs
CTX107935
10 Review Plug-in/Receiver Considerations
Administrators should ensure that users connecting to the XenApp environment are doing so with the appropriate plug-in or receiver type and that it is updated and properly configured. Plug-ins can be installed, updated and configured on client devices through Active Directory as well as with Receiver using Merchandising Server. Refer to the “Receiver and Plug-ins” category at the Product Documentation sitewww.citrix.com/edocs
BSOD while booting the Windows 2008 R2 on XENSERVER 6.1
xe vm-param-set uuid=<vm_uuid> platform:device_id=0001
VM uuid can be copied from the xencenter consle
Cannot start Citrix Licensing service
Issue:\r\nThe ‘Citrix Licensing’ service could not be started and while starting it, it\r\ngives below error on services console:
Solution:\r\nGo to ‘C:\\Program Files (x86)\\Citrix\\Licensing\\LS\\conf’ path of the server and\r\nrename the ‘concurrent_state.xml’ file.
Now, you’ll be\r\nable to start the ‘Citrix Licensing’ service and after sometime, a new ‘concurrent_state.xml’\r\nfile will be created on the path mentioned below.
=============================================================
Citrix ICA Client 10.15 Error 2306
The problem is specific to Internet Explorer v6 and 7 with v10.15 of the ICA client. A workaround is to make the following registry change on the Client workstation:
Change the registry value
HKEY_LOCAL_MACHINE\\SOFTWARE\\Citrix\\ICA Client\\Engine\\Lockdown Profiles\\All Regions\\Lockdown\\Client Engine\\ICA File
Reg_SZ == RemoveICAFile
Change from "*" to "False"
Value == False
Citrix log in page delay
Web Interface server built on Microsoft Windows Server 2008 R2 with IIS 7, but still had horrible response times.
Symptom
Citrix first login page getting delayed to login with screen showing "Loading One Moment"
Resolution
1.The first change comes from the Citrix Forums - disable NetBIOS over TCP/IP for each of the network cards
2. Microsoft.NET\\Framework and Microsoft.NET\\Framework64 directories:
1. Check in IIS for the ASP.net version that is in use with the Web Interface application pool, which should be version 2.0.50727
2. Edit the ASPNET.CONFIG file(C:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727\\aspnet.config)
3. Add the following GeneratePublisherEvidence line to the runtime section of the ASPNET.CONFIG file as shown
< runtime>
< generatePublisherEvidence enabled=”false”/>
< /runtime>
4. Run IISRESET for force a reread of the ASPNET.CONFIG file
Reference Link
http://virtualizationjedi.com/2011/08/16/speeding-up-web-interface/
Citrix IMA service fails to start on XENAPP servers
There are multiple error with respect to IMA service not starting, below are the refernce link with solution provided to the same
Symptom
IMA Serivce fails with error message as per the screen shot
Solution
HKLM\\Software\\Wow6432Node\\Citrix\\IMA\\Runtime\\
Deleted entries from ProductPlugins
Post which IMA service got started without any issue. PFA file for entries which were deleted from ProductPlugins
------------------------------------------------------------
Symptoms
When a domain or local user is configured, the IMA Service fails to start and the following error message appears.
“Windows could not start the Independent Management Architecture on Local Computer... Refer to service-specific error code –2147483647.”
Cause
The domain or local user must have full control for several files and registry entries. Must also have Log On As A Service right on the local machine.
Resolution
When selecting the user account in the IMA Service Logon dialog box, ensure the pop-up window The account has been granted the Logon as a Service right appears. If it does not appear, you need to manually grant the right to the user.
Post the changes run the comman dsmaint recreatelhc
Once the Command run successfully Start the Citrix IMA Service and the same would start
Reference links
http://support.citrix.com/article/CTX105292
http://support.citrix.com/article/CTX032712
http://support.citrix.com/article/CTX131946
http://support.citrix.com/article/CTX101877
http://support.citrix.com/article/CTX101917
http://support.citrix.com/article/CTX103253
http://support.citrix.com/article/CTX735338
Configure Session Limit Settings RDS/XENAPP/XENDESKTOP
How to Configure Session Limit Settings & How to Configure Idle and Disconnect Timeout Settings
below are the referal link for it
http://support.citrix.com/article/CTX127318
http://support.citrix.com/article/CTX126775
Creating/Recreating the local cache on Citrix XENAPP
http://support.citrix.com/article/CTX759510
http://support.citrix.com/proddocs/topic/xenapp5fp-w2k3/ps-maintain-recr-loc-host-cache-v2.html
To recreate the local host cache, stop the IMA Service and then run the command dsmaint recreatelhc. Running this command performs three actions:
• Sets the value of the registry key HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Citrix\\IMA\\ RUNTIME\\PSRequired to 1. This key is HKEY_LOCAL_MACHINE\\SOFTWARE\\Citrix\\IMA\\ RUNTIME\\PSRequired to 1 on XenApp, 32-bit Edition.
• Deletes the existing local host cache (Imalhc.mdb)
• Creates an empty local host cache (Imalhc.mdb)
You must restart the IMA Service after running dsmaint recreatelhc. When the IMA Service starts, the local host cache is populated with fresh data from the data store.
Disable Creation of OST file local disk while set to non-cached mode
http://forums.citrix.com/thread.jspa?threadID=289289
The following is what we use in our GPO to prevent OST creation. These GPO settings are under 'User Configuration \\ Administrative Templates'
Microsoft Outlook 2010/Account Settings/Exchangehide
Policy Setting Comment
Do not allow an OST file to be created Enabled
Synchronizing data in shared folders Disabled
Microsoft Outlook 2010/Account Settings/Exchange/Cached Exchange Modehide
Policy Setting Comment
Download Public Folder Favorites Disabled
Download shared non-mail folders Disabled
Use Cached Exchange Mode for new and existing Outlook profiles Disabled
===========================================================
Can you try to push this setting to one of your servers:
HKLM/SOFTWARE/Policies/Microsoft/Office/14.0/Outlook/OST
Create a DWORD value NoOST with value data to 2.
Disable Power Mangement on Citrix XENDESKTOP 5.5
• Set-BrokerDesktopGroup -name <DesktopGroup Name> -AutomaticPowerOnForAssigned $false
This will disable all power actions on the VM's in Desktop Group
• Set-BrokerDesktopGroup -name <DesktopGroup Name> -ShutdownDesktopsAfterUse $false
This will disable shutdown of VM after use.
Disabling Memory Ballooning on VMware VM
The problem is with VDI/VM where without opening any application\r\n 3 GB of Memory or depending on availability of resoure was getting utilized. While checking found there was\r\nproblem with Memory Ballooning (enabled) and due to which all the memory was claimed by\r\nthe ESX rather than OS. So when disabled the Memory ballooning on VDI found he utilization is to be normal
Solution
1. Log\r\n into the guest OS.
2. Click\r\n Start > Run, type regedit, and press Enter. The Registry Editor window\r\n opens.
3. Navigate\r\n to:
\r\n
\r\n \\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\services\\VMMEMCTL
4. Change\r\n the Start key from 2 to 4.
5. Save\r\n the setting and restart the guest OS.
Referral link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002586
===========================================================
Enabling/Disabling USB/USB Drive redirection XENAPP 5.0
To enable or disable USB drive mapping on XenApp 5 for Windows 2003 server use the following registry keys:
On XenApp 32-bit Edition
HKEY_LOCAL_MACHINE\\Software\\Citrix\\Policies\\DisableUSBDriveRedirection
On XenApp 64-bit Edition
HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\Citrix\\Policies\\DisableUSBDriveRedirection
Type: DWORD
Values:
1 = redirection disabled
0 = redirection enabled
Note: HDX Plug-n-Play for USB storage devices is enabled when the registry key is not present.
Changes apply to all users
Reference Link
http://support.citrix.com/article/CTX123700
Error: HTTP Error 500.22 - Internal Server Error An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode
This error indicates that your application is not coded to run in Integrated Pipeline Mode.
To resolve this issue you must either:
• Update your code to run in Integrated Pipeline Mode.
• Or log into your Control Panel and go to your Site Info Manager and change the pipeline mode from Integrated to Classic.
If you are new to IIS 7, your application that was developed for IIS 6 may not function properly using the default Integrated Application Pool Pipeline Mode. If you encounter such issues you can configure your account to use the classic .NET Application Pool Pipeline Mode using the Integrated/Classic Pipeline Mode tool, located in the Site Tools section of Control Panel.
• Go to the Site Tools section of Control Panel
• Select Classic from the drop down menu for Application Pool Pipeline Mode
• Click the Update button
Notes on the Application Pool Pipeline Mode:
• Most ASP applications should run fine
• Some ASP.NET Application may require configuration migration with an IIS 7.0 command line tool
• Integrated Mode Benefits:
o Allowing services provided by both native and managed modules to apply to all requests, regardless of handler. For example, managed Forms Authentication can be used for all content, including ASP pages, CGIs, and static files.
o Empowering ASP.NET components to provide functionality that was previously unavailable to them due to their placement in the server pipeline. For example, a managed module providing request rewriting functionality can rewrite the request prior to any server processing, including authentication, takes place.
o A single place to implement, configure, monitor and support server features. For example, single module and handler mapping configuration, single custom errors configuration, single url authorization configuration.
Error while check for new updates from WSUS server or from online
Error code when you try to use Windows Update or Microsoft Update to install updates: "0x800B0001"
When you try to install updates from the Windows Update or Microsoft Update Web site, you receive the following error code:
0x800B0001
CAUSE\r\n\r\n
This issue occurs if Windows Update or Microsoft Update determines that the cryptographic service provider is unknown
SOLUTIONS
In Windows XP, in Windows Server 2003, and in Windows 2000
\r\n\r\nTo resolve this issue, you must register the Softpub.dll, Wintrust.dll, Initpki.dll, and Mssip32.dl files. To do this, follow these steps:
1. Start Notepad. To do this, click Start, and then click Run.
2. Copy and then paste (or type) the following command in the Open box, and then press ENTER:
notepad
3. Copy and then paste (or type) the following command lines into the Notepad window:
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s
4. On the File menu, click Save As, and then type Register.bat.
5. Click Save as type, and then click All Files.
6. Save the Register.bat file to your desktop.
7. Double-click the Register.bat file to register the Windows Update files.
8. Try to install updates again.
9. If the issue is resolved, delete the Register.bat file that you created in the previous steps.
In Windows Vista and in Windows Server 2008
\r\n\r\n
Method 1: Run the System Update Readiness tool (Checksur.exe)
\r\n\r\n
1. Download and run the System Update Readiness tool (Checksur.exe). After you download this tool, it runs a one-time scan for inconsistencies that might prevent future servicing operations.
For more information about how to download and run the System Update Readiness tool, click the following article number to view the article in the Microsoft Knowledge Base:
947821
(http://support.microsoft.com/kb/947821/ )
Description of the System Update Readiness Tool for Windows Vista and for Windows Server 2008
Notes
o In article 947821, scroll down to the "Microsoft Download Center" section, and then click the associated link to download the System Update Readiness tool for your operating system.
o After you run this tool, the Checksur.log file will be saved in the following location:
%systemroot%\\Logs\\CBS
In a default installation of Windows Vista, this is the C:\\Windows\\Logs\\CBS folder.
2. After the System Update Readiness tool runs, try to install updates again.
If these steps in do not resolve the issue, go to Method 2.
Method 2: Register the Wintrust.dll
\r\n\r\n
1. Click Start
Collapse this imageExpand this image
, and then type cmd in the Start Search box.
2. In the results list, right-click cmd, and then click Run as Administrator.
Collapse this imageExpand this image
If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
3. At the command prompt, copy and then paste (or type) the following command.
regsvr32 Wintrust.dll /s
4. Close the Command Prompt window.
5. Try to install updates again.
6.
7. Force shutdown not working on XENSERVER
8. When trying to Shutdown or reboot the VM or even trying to Force Reboot or Force shutdown the VM does not work and gives the error saying “Another operation involving the object is currently in progress class: VM”
#xe vm-list to get the uuid of the VM that is hung
#list_domains to list the domain uuid's so you can determine the domain # of the VM above by matching the uuids from this output with the uuid for your VM from the previous command.
domain id of above uuid was '343' & noted down.
"/opt/xensource/debug/destroy_domain -domid XX" where XX is the domain number from the previous command
Below command issued for id 8.
#/opt/xensource/debug/destroy_domain -domid 343
"xe vm-reboot uuid=XXXX --force" where XXXX is the uuid from the first vm-list command for your VM
Below command issued for force reboot
#xe vm-reboot uuid= xxxxxxxxxxxxx –force
After that Vms reboots & is live as normal.
Still not worked restart the MGMT service of the xenserver by below command
# xe-toolstack-restart
Once the restarted MGMT service the VM would bein POwer off mode Power ON the VM
http://www.r2dtop.com/xenserver-6-virtual-machine-crash-and-hang-issue/
9.
10.
11. Google Chrome Crash Issue
12.
13.
14. To overcome the issue We need to Stop the Google chrome update as we have Observed Its Getting Crashed After update .
15.
16. To Stop the update do the Following Setting In VDISK Image.
17.
18.
19. 1) Remove the Scheduler task from task scheduler .
20.
21.
22.
23.
24.
25.
26. 2) Stop the update Trough GPO
27.
28. https://support.google.com/installer/answer/146164?hl=en
29.
30. Configuring the Group Policies
31. The Google Update policies will appear in your Group Policy editor after loading the Administrative Template. In Group Policy Editor, the Google Update polices will be in one of the following locations depending on your operating system:
32.
33. Windows XP®, Windows 2000®, Windows Server 2003®:
34. Administrative Templates
35. Google
36. Google Update
37. Windows Vista®, Windows Server 2008®:
38. Administrative Templates
39. Classic Administrative Templates (ADM)
40. Google
41. Google Update
HOTFIXES for the Citrix and Windows on RDS
http://support.microsoft.com/kb/2734642 - RDS-based applications crash in Windows 7 SP1 or Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2541119 - Applications may crash in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2479710 - Remote Desktop service crashes when Group Policy settings are refreshed in Windows Server 2008 R2 after you enable the "Required secure RPC communication" and "Set client connection encryption level" Group Policy settings
http://support.microsoft.com/kb/2601888 - Available Updates for Remote Desktop Services (Terminal Services) on Windows Server 2008 R2 SP1
http://support.citrix.com/article/CTX129229 - All the Citrix and MS OS hotfix for RDS is available
http://support.microsoft.com/kb/2620656 - Invalid redirected printers may be available in a Remote Desktop Services session that connects to a RD Session Host server that is running Windows Server 2008 or Windows Server 2008 R2
http://support.microsoft.com/kb/2778831 - "Client Side Rendering Print Provider" registry key growth on a Windows Server 2008 R2-based Remote Desktop Session Host server
http://support.microsoft.com/kb/2383928 - Remote desktop sessions do not completely exit, and you cannot establish new remote desktop sessions to a computer that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2465772 - An application or service that uses Winsock API or Winsock Kernel API may randomly stop responding in Windows Server 2008 R2 or in Windows 7
http://support.microsoft.com/kb/2719704 - "0x0000003B" or "0x000000D5" Stop error in Windows 7 or in Windows Server 2008 R2
how much disk space is being used by VSS snapshots on a volume
While some time observed that disk space used but not showing in the usage and tree size. this could be caused by VSS (Volume Shadow Copy Snapshot) so how does this can be checked and fixed
Open RUN and open Command prompt (elevated)
and run below mentioned command
vssadmin list shadows
If you do not see any Shadow Copies listed you can have vssadmin created, if there are listed then check for the storage by below mentioned command
vssadmin list shadowstorage
This will display the size and Snapshot used, if these snapshot is not required then can be deletd by below command
vssadmin delete shadows /all
This will clear all the storage used by VSS (Snapshot)
---------------------------------------
Note: if above mentioned command is not helping then try below mentioned command
---------------------------------------
In summary you have to do the following
Start an elevated commandline window
Type in wmic and press enter
wmic:root\cli is shown
Type in shadowcopy which will list the current shadow copies
Type in shadowcopy delete and confirm to delete the copies one after the other
To leave the WMI commandline type exit
Reference link
http://wiki.r1soft.com/display/kb3/How+to+view+a+Microsoft+VSS+snapshot+in+Windows+File+Explorer
http://windowsitpro.com/windows/q-how-can-i-see-how-much-disk-space-being-used-vss-snapshots-volume
How to Display or Release Licenses for Users or Devices on Citrix
http://support.citrix.com/article/CTX132341
Background
udadmin displays the licensed users and devices and releases licenses for specified users and devices.
You can release a license for a user only when the employee is no longer associated with the company or is on an extended leave of absence. You can release licenses for devices only when the devices are out of service.
Procedure
To display or release licenses for users or devices, complete the following procedure:
1. Log onto the console of the license server VPX by using the root account and password configured at the time of initial configuration.
Note: All commands are case sensitive.
2. Run the following command to change the directory to the licensing utility path:
cd /opt/citrix/licensing/LS
or
cd C:\\Program Files (x86)\\Citrix\\Licensing\\LS on 64bit server
3. Run the udadmin to list all commands:
udadmin
Following are the samples of the usage of the preceding command:
udadmin –list
The output displays all the users and devices.
udadmin -list –a
The output of the preceding command lists all features, versions, counts of licenses, and the users and devices for each feature.
udadmin -f XDT_ENT_UD -user "username" –delete
This command releases one user from one feature.
udadmin -f XDT_ENT_UD -device "DeviceName" –delete
This command releases one device from one feature.
4. Do the udadmin list command to confirm the the license is releas or not
udadmin -list –a
How To Extend the Virtual Disk Size of a XenServer Virtual Machine
ProcedureThis article contains the following procedures:
Extending the disk size in XenServer
Extending a partition size in Windows operating systems using the DiskPart utility
Extending a partition size in Linux operating systems
How to extend the size of the disk in XenServer:
1. Shut down the corresponding virtual machine.
2. Go to XenServer Command Line Interface (CLI)
3. Find the virtual disk Universally Unique Identifier (UUID) by running the following command:
# xe vm-disk-list vm=<vm name>
4. Run the following command to resize the virtual disk:
#xe vdi-resize uuid=<vdi uuid> size=<size (GiB, MiB)>
With XenCenter 5.6 you can select the VDI from the storage tab of the virtual machine click Properties, select Size and Location, then increase the size of the disk without using the command line.
Using Disk Management:
5. Right click My Computer select Manage.
6. Select Disk Management, right click on the disk you want to extend, and select Extend:
This starts the Extend Volume Wizard. Follow the prompts to complete the process.
Using the DiskPart utility (Win7 & Win2K8):
Note: DiskPart cannot extend system partitions on Windows 2003 and Windows XP Functionality restrictions of the Diskpart.exe utility to extend system and boot partitions in Windows Server 2003 and in Windows XP
7. Launch a command prompt.
8. Type diskpart and press Enter.
9. At the diskpart prompt, enter the following commands:
DISKPART>list volume
DISKPART>select volume # (For # enter the number of the volume you want to resize)
DISKPART>extend size=n (n is size in Megabytes that you are adding to the volume>
Refer to DiskPart Command-Line Options for more information.
10. After you finish your work, type exit to close DiskPart.
11. Type exit to exit the command prompt.
12. Click Restart. You might be asked to restart one more time once the operating system starts.
How to extend the partition size in Linux operating systems:
Linux operating systems supports many file system types (for example, ext3, xfs, reiserfs). To extend file systems on an extended disk you must use file system tools that correspond to a particular file system type. Recommended file systems are those that can be expanded while the system is running and mounted. For example:
If you use ext3: After resizing the disk in XenServer, start the operating system and use the resize2fs tool with the name of the partition that should be extended (refer to the manual for more details). For example to resize a data partition:
#umount /dev/xvdc1
#fdisk /dev/xvdc1
#d (Delete the partition and recreate it)
#n (New partition)
#w (Write out table)
#e2fsck -f /dev/xvdc1
#resize2fs /dev/xvdc1
#mount /dev/xvdc1 /home
To resize the Linux system partition:
1. Shutdown the virtual machine.
2. Set the virtual machine to boot into single-user mode on the XenServer host CLI:
#xe vm-param-set uuid=6f04... PV-args=single
3. Boot virtual machine and show disk list make partition table changes in the Linux virtual machine:
#fdisk -l
fdisk /dev/xvda
d -Delete Partition
n -New create new partition
p -Primary
1- Partition number
Default values for size
w -Write changes
4. Reboot the virtual machine:
reboot vm
Note: If you need to run FSCK you must boot from rescue media.
5. Resize the filesystem:
resize2fs /dev/xvda1
6. On XenServer host, remove the single-user boot mode setting:
#xe vm-param-set uuid=6f04... PV-args=
• If you use xfs: After resizing the disk in XenServer, start the operating system and use the xfs_growfs tool with the name of the partition that should be extended (refer to the manual for more details). For example:
# xfs_growfs /dev/xvda1
• If you use reiserfs: After resizing the disk in XenServer, start the operating system and use the resize_reiserfs tool with the name of the partition that should be extended (refer to the manual for more details). For example:
# resize_reiserfs /dev/xvda1
Refer the below link for further refernce
http://support.citrix.com/article/CTX116114/
http://support.citrix.com/article/CTX117630
How to generate a Support file ?
Please follow the steps mentioned below for support file generation:
1. Go to 'Support' tab.
2. Click on 'Support File'. This would create a file with extension zip.gz
3. Please mail this file to support@servicedeskplus.com
[ Valid as on ServiceDesk Plus release 7.0 ]
IMA Service Fails with the Following Events: 3989, 3634, 3614
Symptoms
"The server running Citrix Presentation Server failed to connect to the data store. The database is down or there is a network failure. Error: IMA_RESULT_DBCONNECT_FAILURE Indirect: 0 Server: DSN file: D:\\Citrix\\Independent Management Architecture\\MF20.dsn"
Due to this Citrix Desktop Delivery Controller Service, Citrix IMA Proxy Service, and Citrix Pool Management Service fail to start as the IMA service is unresponsive during start up
Resolution
Add network account permission to the following key:
HKLM\\SOFTWARE\\Microsoft\\MSSQLServer\\Client\\SuperSocketNetLib\\LastConnect
Article
http://support.citrix.com/article/CTX128971
In Design Problem-Users acessing In Design Application Facing Slowness for Multiple Locations
Issue has been resolved by disabling Antivirus update on All HSD machine. Anitvirus update will be done on weekly Basis post testing on the dat.
Income TAX india efilling site not opening on Windows 2003 with IE 8
We have incometaxindiaefiling is not working on Windows 2003 Server with IE8 on it, but rest of the server and OS it working fine
As per the below blog the site does not work on Windows 2003 server and IE 8
\r\n\r\nReference URL
http://social.technet.microsoft.com/Forums/itmanagement/en-US/18e4d880-4dad-486a-9b8f-8d3e2657267a/incometaxindiaefilinggovin-in-not-working-on-ie8-in-server-2003\r\n
http://answers.microsoft.com/en-us/ie/forum/ie8-windows_other/incometaxindiaefilinggovin-is-not-working-on-it/95d58960-94ca-4cb6-bf58-fb27fc78aa21?msgId=722f11b7-febb-49dd-8fec-502ccb2af04e
Increasing the vCPU on VM from 4 to 8 on the XENSERVER
Complete the following procedure to set the cores-per-socket parameter for Windows virtual machine:
1. Get the Universally Unique Identifier (UUID) of the Virtual Machine for which the parameter needs to be set:
xe vm-list name-label=<Name of the VM>
2. Shutdown the VM on which the vCPU has to be increased to 8 or more
3. Increase the vCPU on the VM by going to XenCenter select the VM
4. Go to Genral TAB and click on Properties
5. Select the CPU option and change to desired setting
6. Then go to XenServer Console and go to local shell and command
7. enter Root username and password then you will get the # prompt
8. Set the cores-per-socket parameter:
xe vm-param-set platform:cores-per-socket=’X’ uuid=<VM UUID from Step1>
Here, X equals 2 for dual core and 4 for quad core.
For example: To have a CPU with four cores:
xe vm-param-set platform:cores-per-socket=4 uuid=<VM UUID>
9. Set the virtual CPUs startup parameter equal to the number of virtual CPUs (number of cores) to be assigned to the virtual machine and set the VCPUs-max parameter to the total number of cores.
xe vm-param-set VCPUs-at-startup=<Number of VCPUs> uuid=<VM-UUID>
10. xe vm-param-set VCPUs-max=<Maximum number of cores>.
For a dual quad core CPUs, VCPUs-max=8
The number of virtual CPUs at startup is the number of cores to assign to the virtual machine.
If your XenServer has dual quad core CPUs and you have set the cores-per-socket=4 and VCPUs-at-startup=8, then you will see 8 CPUs in the Performance tab of Task Manager and 2 processors in the Computer Properties of the virtual machine. Here the virtual machine is using all 8 cores of the 2 Processors.
Similarly, if VCPUs-at-startup=4, then you will see 4 CPUs in the Performance tab of Task Manager but only 1 processor in the Computer Properties. Here the virtual machine is using only 4 cores and only one processor out of 2 processors. However, if the number of VCPUs-at-startup is greater than 4, then it will make use of the second processor and show 2 processors in the computer’s properties.
From the preceding discussion, you can conclude that the number of processors the virtual machine makes use of depends on the number of cores assigned to the virtual machine.
For refernce go to below mentioned link
http://support.citrix.com/article/CTX126524
Lockdown requirements in force may be conflicting
When trying to launch an application that says the following:
Citrix Receiver Configuration Manager: No value could be found for (AllowHotkey) that satisfies all lockdown requirements The lockdown requirements in force may be conflicting.
To solve this error, follow these steps.
1. Select Start, type Regedit, then press Enter to open the Registry Editor.
2. Navigate to the following path:
• HKEY_CURRENT_USER
• Software
• Citrix
• ICA Client
• Engine
• Lockdown Profiles
• All Regions
3. Double-click EnableLockdown. If you don’t find this entry, look under HKEY_LOCAL_MACHINE instead or search the registry for it under Edit > Find.
4. Set the Value data to 0.
5. Close the Registry Editor.
Now attempt to launch the application in the Citrix Receiver again.
Login issue for RB users with Error “Another instance is already open”
Hot fix has been applied on the file server for Windows 2008 Server
New Server instance Created and provided the complete rights as required.
Mail delivery is not getting changed to PST
After changing the default mail delivery path but still the mail get delivered on the Mail box rather than delivering on the PST.
below is the solution to fix the issue
SOLUTION
1.Close any messaging\r\nprograms such as Outlook, Microsoft Exchange, or Microsoft Windows Messaging.
\r\n2.Click Start, and then click Run. Copy and paste (or type) the following\r\ncommand in the Open box, and then press ENTER:
\r\ncontrol panel
\r\nControl Panel opens.
\r\n
\r\nNote If you see the Pick a category screen, click User Accounts, and then go to\r\nstep 3.
\r\n
\r\n
3.Double-click the Mail\r\nicon.
\r\n
\r\n
4.Click Show Profiles.
\r\n
\r\n
5.Click the appropriate\r\nprofile, and then click Properties.
\r\n
\r\n
6.Click Data Files.
\r\n
\r\n
7.Under Name, click the\r\nPersonal Folders Service that you want to back up. By default, this service is\r\ncalled Personal Folders. However, it may be named something else.
\r\n
\r\nNote If you have more than one Personal Folders Service in your profile, you\r\nmust back up each set of .pst files separately.
\r\n
\r\nIf there are no entries called Personal Folders and you have not yet stored any\r\ninformation such as messages, contacts, or appointments in Outlook, you\r\nprobably have not yet enabled the Personal Folders Service. Go to the\r\n"References" section for information about how to create a .pst file.
\r\n
\r\nIf you have no Personal Folders Services in your profile and you can store\r\ninformation such as messages, contacts, or appointments in Outlook, your\r\ninformation is probably being stored in a mailbox on an Exchange Server. Try\r\nusing the instructions in the "How to back up .pst file data that is\r\nlocated on a Microsoft Exchange Server" section.
\r\n
\r\n
8.Click Settings, and\r\nthen note the path and file name that appears.
\r\n
\r\nNote Because the .pst file contains all data that is stored in the MAPI folders\r\nthat Outlook uses, the file can be very large. To reduce the size of the .pst\r\nfile, click Compact Now in the Settings window.
\r\n
\r\n
9.Close all the\r\nProperties windows.
\r\n
\r\n
10.Use Windows Explorer\r\nor My Computer to copy the file that you noted in step 8. You can copy the file\r\nto another location on the hard disk drive or to any kind of removable storage\r\nmedia, such as a floppy disk, a CD-ROM, a portable hard disk drive, a magnetic\r\ntape cassette, or any other storage device.
Compact Now in the Settings window.
Modify Login screens and Logout screens
Find below the procedure to meet with your need:
1. Save the page served under http://[servername-or-ipaddress:port-number] as index.html. Copy this file onto C:\\ManageEngine\\ServiceDeskPlus-Msp\\applications\\extracted\\AdventNetServiceDesk.eear\\AdventNetServiceDeskWC.ear\\AdventNetServiceDesk.war
2. Modify the index.html page as per your needs and the save the file under the same location.
3. Keep the FORM Submit and Action options as they are.
4. Edit the Web.xml file present under C:\\ManageEngine\\ServiceDeskPlus-Msp\\applications\\extracted\\AdventNetServiceDesk.eear\\AdventNetServiceDeskWC.ear\\AdventNetServiceDesk.war\\WEB-INF and change the following:
<form-login-page>/Login.jsp</form-login-page>
should be changed as
<form-login-page>/index.html</form-login-page>
AND
<form-error-page>/Login.jsp?error=true</form-error-page>
should be changed as
<form-error-page>/index.html</form-error-page>
5. Restart ServiceDesk Plus service.
6. You can now access the modified index page as http://[servername-or-ipaddress:port-number]/index.html
Note: This file is bound to changes everytime a servicepack or hotfix is released. Hence, when you apply the hotfix or servicepack, you must redo the changes.
[ Valid as on ServiceDesk Plus release 7.0 ]
MSO (Excel) Performance Degraded
The Speedscreen Latency Reduction setting is been enabled to for EXCEL type each rate was low and will be increased afterthis settings
Multiple Duplicate session on XENAPP
Multiple session created during the initial login and it would stay idle state.
Cause
Users rapidly clicking on published application icons can initiate multiple sessions prior to the application instance counter getting updated.
http://forums.citrix.com/thread.jspa?threadID=86533
Are you sure your users are not double clicking applications so that they are actually starting two sessions at the same time therefore not the ZDC would not be updated fast enough?
investigation shows that users are not getting extra sessions due to double-click on icon
Solution
On the WFClient section of the appsrv.ini
Example of parameter setting in the APPSRV.INI or DEFAULT.ICA file:
[WFClient]
Version=2
SucConnTimeout=40
Or
On the Client desktop by doing the below registry change
Add the following registry key on the client desktop to extend this time out value:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Citrix\\ICA Client\\Engine\\Configuration\\Advanced\\Modules\\WFClient\\
SucConnTimeout = <string value>
Or
On the Web Interface 5.3 and above
1. Locate the WebInteface.conf file in this directory \\Inetpub\\wwwroot\\Citrix\\SiteName\\conf
2. Open file with Notepad and search for the following entry:
#MultiLaunchTimeout=[Number of Seconds (2)]
3. Remove (#) sign and [Number of Seconds (2)]
4. Enter the number of seconds desired.
5. The entry should look like this:
For example: MultiLaunchTimeout=2
6. Save the file and test.
For reference and furhter details go to below like or
http://support.citrix.com/article/CTX124612
http://support.citrix.com/article/CTX118656
NETAPP storage Snapshot is available but not able to retrive or review the snapshot
We found that the snapshot is working as excepted but there is option to veiw the snap shot was not visible to view/enable belwo command has to be run and configure the setting
Options cifs.show_snapshot on
Network not reachable(Server 2008 R2)
This is the solution for NIC is not taking IP address and network not reachable also
Command: netsh winsock reset
after run the command network will be reachable
Performance Object Showing Numbers instead of Names
I noticed a problem in our Dev Window 2003 box with the Performance Objects (PerfMon). One of our Windows Services uses the Performance Counter API in the code. It was failing because of not being able to measure run the Performance Counter. In short, in order to rebuild the Performance Counters on your machine, run on command prompt
lodctr /R
Printer redirection not working on XENAPP 6.5
Symptoms
Printer Auto Creation Fails on XENAPP with error message and also as a behavior from RDP the Printer auto creation is working but while login through CITRIX/ICA Printer does not auto create.
Note: This is with all Printer driver available on XENAPP Servers
Soltution
1. Verify the account that the Citrix Print Manager Service is running as. This should be the local service account. If it is not the local service account, complete the following procedure to change it:
a. Enter Local Service in the This Account field.
b. Clear the passwords field.
c. Press OK.
Note: You get two prompts, click OK and the password is recreated for that account.
2. Click Devices and Printers from Control Panel.
3. Click on any printer to display the print server properties option.
4. Click Print Server Properties in the menu bar
5. In the Printer Server Properties dialog box click the Security tab.
6. Verify that the local service account is listed and has full control. Other permissions include:
- Everyone Group: Print and View Printer
- Creator Owner Group: Manage Documents
- Local Administrators: Full Control
7. Restart the print spooler service, which also restarts the Citrix Print Manager Service.
There could be multiple causes for the for issue, please refer to the below reference link with behavior/symptoms
Reference Link
http://support.citrix.com/article/CTX130767 -- Printer Auto Creation Fails with 0x5 Error Code
http://support.citrix.com/article/CTX107838 -- Event ID 1116 Printer Auto-Creation Failure. Reason: AddPrinter() failed with status 0x3EB
http://support.citrix.com/article/CTX137114 -- Event ID 1106: Client printer auto-creation failed
http://support.citrix.com/article/CTX106683 -- Event ID 1116: Printer auto-creation failure. Reason: AddPrinter() failed with status 0x5
http://support.citrix.com/article/CTX136162 -- Printers Fail to Auto Create in an ICA Session
PST keep getting corrupted on NAS
"Delayed write failed" error message when .pst files are stored on a network file server that is running Windows Server 2008 R2
Cause
This issue occurs because the Outlook 2010 client tries to write data to an open SMBv2 file ID that has read-only access
Workaround
To work around this issue, disable the SMBv2 feature on computer B. Computer B is the file server that is running Windows Server 2008 R2. To do this, follow these steps:
1. Open Registry Editor. To do this, click Start, type regedit in the Start Search box, and then press Enter.
2. Locate and then click the following registry keys:
HKLM\\System\\CurrentControlSet\\Services\\LanmanServer\\Parameters
3. In the Edit menu, point to New, and then click DWORD (32 bit) Value.
4. Type Smb2, and then press Enter.
5. On the Edit menu, click Modify.
6. In the Value data box, type 0, and then click OK.
7. Exit Registry Editor.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
Note Install the hotfix on the computer that Outlook 2010 is installed on (computer A).
Remove the "safely remove hardware" icon for the NIC
Installing the latest client tools the "safely remove hardware" icon \r\nfor the NIC appeared. Most of our XenServer VM's are running XenApp on W2K3 \r\nEnterpise but if a user clicks the remove icon and removes the network card the \r\nserver is down
Update following reg values via GPO Preferences.
ALL DWORD32
HKLM\\SYSTEM\\CurrentControlSet\\Enum\\XEN\\VIF\\Capabilitiies=00000012
HKLM\\SYSTEM\\CurrentControlSet\\Enum\\XEN\\VIF\\1\\Capabilitiies=00000012
HKLM\\SYSTEM\\CurrentControlSet\\Enum\\XENBUS\\CLASS&VIF\\_\\Capabilitiies=00000032
HKLM\\SYSTEM\\CurrentControlSet\\Enum\\XENBUS\\CLASS&IFACE\\_\\Capabilitiies=00000032
HKLM\\SYSTEM\\CurrentControlSet\\Enum\\SCSI\\Disk&Ven_XENSRC&Prod_PVDISK&Rev_1.000000\\Capabilitiies=00000072
HKLM\\SYSTEM\\CurrentControlSet\\Enum\\SCSI\\Disk&Ven_XENSRC&Prod_PVDISK&Rev_1.000100\\Capabilitiies=00000072
Reference Link
http://smulpuru.wordpress.com/2012/01/10/hide-citrix-components-from-safely-remove-hardware-in-win7/
http://forums.citrix.com/message.jspa?messageID=1605452
Remove XEN PVDISK from Windows Safely Remove Hardware Wizard
This article explains how to remove the “XEN PVDISK SCSI Disk Device” \r\nfrom the Windows Safely Remove Hardware wizard. This removal is typically \r\ndone to provide a cleaner Windows experience for end users, particularly in a \r\nvirtual desktop scenario.
XenServer allows administrators to hot-plug and hot-unplug virtual disks into \r\nWindows virtual machines. Disk that can be hot-unplugged from Windows show up in \r\nthe Safely Remove Hardware wizard. XenServer tells Windows which virtual disks \r\ncan be hot-unplugged by the unpluggable parameter on the virtual block \r\ndevice (VBD) that the virtual disk is associated with.
http://support.citrix.com/article/CTX123961
SOLUTION
1. Identify which XenServer virtual machine (VM) or template that you \r\nwant to stop displaying the XEN PVDISK device in the Safely Remove Hardware \r\nwizard. If these steps are performed on a template, each virtual machine that is \r\nlater created from this template is affected by the change.
2. Log on to the console of a XenServer hosting the particular VM or \r\ntemplate identified in Step 1. This is typically done by selecting a XenServer \r\nin XenCenter and clicking on the Console tab.
3. Identify the Universally Unique Identifier (UUID) of the VBD that \r\nyou do not want to appear in the Safely Remove Hardware wizard. This can be \r\naccomplished by executing the following command in the XenServer \r\nconsole:
xe vbd-list vm-name-label=<Name of VM or Template> \r\ntype=Disk params=uuid
Here is an example where the VM name is “XP \r\nGolden”. The UUID reported will be different for each VBD.
If there is more than one virtual disk assigned to your VM or template, \r\nyou need to use additional commands to identify which VBD you want to apply the \r\nconfiguration to or just apply the configuration to each VBD.
4. Using the UUID identified in Step 3, change the unpluggable \r\nparameter to false by executing the following command in the XenServer \r\nconsole:
xe vbd-param-set uuid=<UUID from Previous Step> \r\nunpluggable=false
Here is an example continuing from the example in \r\nthe previous step. The UUID used is different for each VBD.
5. If the VBD is connected to a VM that is currently running, the VM \r\nmust restarted for the setting to take effect.
Roaming profile is not getting deleted after logoff
Stale user profile folders are not deleted completely in Windows 7 or in Windows Server 2008 R2
SYMPTOMS
Consider the following scenario:
•You apply the Delete user profiles older than a specified number of days on system restart Group Policy setting on a client computer that is running Windows 7 or Windows Server 2008 R2.
Or
You apply to Delete the user local cached user roaming profiles every time they log off
•The computer is in an Active Directory domain environment.
•A user in the domain logs on to the computer.
•The user logs off the computer after a user profile folder for that user is created.
•The computer is restarted after the number of days that is configured in the Group Policy setting.
•The user logs on to the computer again.
In this scenario, the stale user profile folder is not deleted completely. Therefore, you experience one or more of the following issues:
•An additional user profile folder is created. The name of this folder is appended with a NetBIOS domain name or with a three-digit suffix. For example, the folder name is Username.CONTOSO or Username.000.
•If the user has a roaming profile, some applications that rely on the "Shell Folders" paths in the registry stop responding. Additionally, when the user logs off the computer, changes to the application data that is stored in the user profile do not roam to the domain database.
•An event that resembles the following is logged in the Application log:
Event ID: 1533
Source: User Profile Service
Type: Error
Description
Windows cannot delete the profile directory C:\\Users\\username.
This error may be caused by files in this directory being used by another program.
DETAIL - The directory is not empty.
Notes
•This issue occurs when the Windows Search service is enabled.
•When this issue occurs, the registry subkey that represents the stale user profile is deleted. This subkey appears in the following location:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList
RESOLUTION
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Note This hotfix creates two registry entries under the following registry subkey:
HKEY_LOCAL_MACHINE\\System\\CurrentControlset\\Services\\ProfSvc\\Parameters
Note This hotfix creates two registry entries under the following registry subkey:
HKEY_LOCAL_MACHINE\\System\\CurrentControlset\\Services\\ProfSvc\\Parameters
Entry name
Default value
Explanation
DeleteRetryWait
1000
The interval (measured in milliseconds) between attempts to delete a user profile folder when the deletion fails
DeleteRetryAttempts
15
The maximum number of times that the deletion is retried
Note The re-attempts to delete the user profile folder are performed by a background thread in the User Profiles service. Therefore, these attempts do not delay the user logon process after the computer is restarted.
Registry information
To apply the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Reference Link
http://support.microsoft.com/kb/2661663
Server Network not working
Symptoms
While trying to reach the server from Outside/other server on network its gives "Requested time out" and while trying to reach the any IP address including the Default gateway the error message is "Destination host not reachable"
Cause
This could be caused due to IPSec driver is misbehaving or got corrputed
Resolution
By re-registering the IP Sec DLL or driver will fix the issue.
To resolve this issue, delete the following registry subkey and then rebuild the policy:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\IPSec\\Local
1. Delete the local policy registry subkey. To do this, follow these steps:
b. Click Start, click Run, type regedit, and then click OK.
c. In Registry Editor, locate and then click the following subkey:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\IPSec\\Policy\\Local
d. On the Edit menu, click Delete.
e. Click Yes to confirm that you want to delete the subkey.
f. Quit Registry Editor
g. Rebuild a new local policy store. To do this, follow this step:
a. Click Start, click Run, type regsvr32 polstore.dll, and then click OK.
The details are available on the below mentioned refernce link
Refernce Link
http://support.microsoft.com/default.aspx?scid=kb;en-us;870910
Slowness issue
QOS onfiguration has been done on the link , to give precedence to citirx traffic.
Also the traffic other than citrix has been segregated on the different link.
SREI OmniScan configuration
SREI OmniScan configuration
Configuration file not found
Temp Profile is getting loaded for Maxlife.
1. Disable the group policy configured to “Delete the Cached Roaming Profiles” from the RDS servers, as this group policy is not compatible with your environment and resulting in the multiple profile issue. Disabling this policy will not only resolve the multiple profile issue, but also improve the performance of the profile loading. (this is the quick resolution for your current multiple profile issue)
As in ideal scenario if we delete the cache profiles whenever user login on the server it downloads the complete profile from the roaming profile center. In case if this group policy will be disabled there will be user profile cache stored on the server, next time when user will log on the server it will sync and download only the changes made since the last profile was cached on this server, which will always be less in size than the complete profile of the user. This will result in downloading the profile from roaming profile center faster as well as loading will be faster.
3. Clean all the bad profiles of the users using the “sysdm.cpl” tool.
The remote computer disconnected the session because of an error in the licensing protocol on Windows XP & Windows 7
Solution for Windows 7
Just delete the "HKLM\\Software\\Microsoft\\MSLicensing" registry key...then launch remote desktop using "Run as Administrator". This worked for Windows 7. I had to launch as admin, otherwise it didn't work after deleting the key
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/remote-desktop-connection-error-message-the-remote/cc914f39-3d8e-4671-b569-b1ba5d68b380
Solution for Windows XP
To resolve this problem, follow these steps:
1. On the computer that cannot open the Remote Desktop session, click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type the following command, and then press ENTER:
NET START TERMSERVICE
3. Click Start, click Run, type regedit, and then click OK.
4. In Registry Editor, locate and then click the following key:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSLicensing
5. Delete all the keys that are located under the
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSLicensing
key.
6. On the File menu, click Exit.
7. Restart the computer.
http://support.microsoft.com/kb/921045
Few more URL/Link for solutions
http://technet.microsoft.com/en-us/library/cc783693(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/cc756826(v=ws.10).aspx
This version of Citrix Receiver does not support selected encryption. Please contact your administrator. Error 1046: The Virtual Driver is not loaded
SymptomsWhile launching a Citrix XenApp application with RES Virtual Desktop Extender (VDX) enabled the following error might occur:
Citrix Receiver Error:
"This version of Citrix Receiver does not support selected encryption. Please contact your administrator. Error 1046: The Virtual Driver is not loaded
However, the second attempt is successful to run the application without any errors. This issue only occurs when using the Citrix Receiver, using earlier ICA client versions does not display this error.
Cause
A call being blocked during startup is causing a timeout that results in the error.
Status
Disable the Antivirus installed and tryby closing the Citrix reciever and reopeningit and if still not working Disable the Antivirus and reboot/restart the system and try. Which would resolve the problem
Citrix is currently aware of this issue. If you are experiencing this issue contact Technical Support to open a service request and reference CPR LA3120
Time sync issue in DB Raipur Database server.
We don’t have the concrete resolution for the same. However,multiple changes has been performed to fix issue
Disabled the xenguestagent service on the servers.
Disabled the XEN guest agent on the servers
Installed the hotfix (2790831) which was suggested from citrix team.
Upgraded the Xentool application has been upgraded on all the VM servers Pervious Version :XenApp version 6.2.259
Update version :XenApp Version 6.2.311
To move data from one installation from another.
You can move the data from the existing server to new server. Please follow the steps mentioned below:
1. Stop ManageEngine ServiceDesk Plus service
2. Kindly Upgrade the SD+ if needed. Take the link below to check if you are in the latest version;
http://www.manageengine.com/products/service-desk/service-packs.html
Now start and stop the service once after the upgrade process.
3. In the command prompt, move to [ServiceDeskPlus-Home]\\bin directory and execute backupdata.batto start the data backup. Once the backup is over, a directory named "backup" will be created in [ServiceDeskPlus-Home], within which another directory with the name "Backup_[Versionnumber]_Monthdate_Year_Hour_Minutes" will be created and the backup file with .data extension is placed in this directory. The name of the backup file contains the date and time at which backup is taken. Example:BackUp_5501_SEP14_2006_15_51.data
cmd> [ServiceDeskPlus Home]\\bin
cmd> backUpData.bat
4. Install SD+ to the new server.
5. Copy the backup folder from the old server to [ServiceDeskPlus-Home] in the new server.
6.To restore the backed up data, Go to [ServiceDeskPlus-Home]\\bin directory and execute restoredata.bat. Choose the backup file while prompted. See example below:
cmd> [ServiceDeskPlus Home]\\bin
cmd> restoreData.bat
7. Start the SD+ server once after restoring the data in the new server.
Troubleshooting DCOM Error
'Either access denied for the user or the remote DCOM option might be disabled in the workstation.'
This error will occur if the login credentials provided for scanning is invalid or the Remote DCOM is not properly configured in the target workstation.
Given below is the procedure to troubleshoot the above mentioned error:
Step 1:
For Windows workstations 'Windows Domain Scan' mode will be more efficient than 'Network Scan' mode. Configure the login credentials for the Domain/Workgroup to which the workstations belong and scan the Domain.
Check if the login credentials are provided in correct format. For login credentials ensure that you haven't entered the DomainName along with the userName (i,e Do not Enter as DoaminName\\\\UserName). It is sufficient if only the UserName is entered in the provided text-field.
Step 2:
Ensure that the login information provided are correct and has administrator privileges in the target computers. To check if the login information provided is valid you can execute the following commands at the command prompt in the server where ServiceDesk Plus is running.
net use \\\\<RemoteComputerName>\\C$ /u:<DomainName\\UserName> '<password>'
net use \\\\<RemoteComputerName>\\ADMIN$ /u:<DomainName\\UserName> '<password>'
Note: Replace the relevant value within <>. Supply password within the quotes.
If the above commands succeeds and Scanning fails, then the problem might be in the DCOM Configurations.
Step 3:
Ensure Remote DCOM is enabled on the target workstations.
To Enable DCOM in Windows 2000 Computers
1. Select Start > Run
2. Type DCOMCNFG in the text field
3. Click OK.
4. Select Default Properties tab
5. Check the box 'Enable Distributed COM in this machine'
6. Press OK
To Enable DCOM in Windows XP Computers
1. Select Start > Run
2. Type DCOMCNFG in the text field
3. Click OK
4. Right Click on Component Services > Computers > My Computer
5. Click Properties
6. Select Default Properties tab in the frame that pops
7. Check the box 'Enable Distributed COM in this machine'
8. Press OK
Try scanning the workstation after Enabling Remote DCOM.
Step 4:
If scanning fails after enabling remote DCOM, give more DCOM permissions and try scanning the workstation.
1. Start -> Run -> DCOMCNFG
2. Choose the DEFAULT PROPERTIES tab
3. Chek the check-box Enable Remote DCOM on this computer
4. Set the Default Authentication Level as DEFAULT. NONE also can be set.
5. Set the Default Impersomation Level as IMPERSONATE.
6. Now select the DEFAULT SECURITY tab.
7. Click the Edit Default button under Default Access Permission.
8. In the Frame that pops, click the ADD button and add 'Everyone' with Allow Access permission.
9. Similarly, under the Default Launch Permission add 'Everyone' with Allow Launch permission.
10. Click OK and now try scanning the workstation.
NOTE: Sometimes DCOM Settings will be effective after restarting the server.
Step 5:
In certain cases, the problem might be due to enabling 'Simple File Sharing'. To disable 'Simple File Sharing':
1. In any of the Windows Folders Click 'Tools' > 'Folder Options'.
2. In the Folder Options window, goto 'View' tab.
3. Uncheck 'Use simple file sharing'
4. Click 'OK' to save changes.
Step 6:
If the target workstations are Windows XP try modifying the Network Access Security Model.
1. Goto Control Panel -> Administrative Tools -> Local Security Policy
2. Right Click 'Network Access : Sharing and security model for local accounts' and then select Properties
3. Choose the option 'Classic - local users authenticate as themselves' and apply
Unable to Open Outlook getting Error "MAPI32.DLL is corrupt or the wrong version"
We usually "Cannot Start Microsoft office Outlook. MAPI32.DLL is corrupt or the wrong version. Please reinstall the Outlook." when we install MS Office 2010 or Ms Office 2007 and downgrade it to Ms Office 2003 we may receive the above error while opening Outlook. It happens due to Messaging service clash.
We can Follow the below step to resolve the issue:
Goto below path:
C:\\Program Files\\Common Files\\System\\Msmapi\\LocaleID or 1033 (This folder basically relates to English Format)
In this Folder look for MSMapi32.dll file, right click on it and rename it to MSMapi32.Old
Note: MAPI32.dll and MSMAPI32.dll are two different files.
After renaming the file Launch Outlook. It will work.
User are unable to login HVD
As per suggestion from Citrix team Xentool application has been upgraded for the all HVD’s from 6.0 to 6.1 version and post which issue has been resolved.
User Data size and Quota is not matching, hence the quota size for user is not reflecting correctly
Folder owner has been changed from Administrator to the respective user & the Quota Size has been re-organized as per the data size .
To ensure correct file \ folder ownership the Designed Script will be executed monthly.
User is unable to login on HVD.
As per suggestion from citrix team latest hotfix patch has been installed on the HVD and post which issue got resolved.
Hot Fix Patch :Hotfix Rollup XD560VDA WX64500 (Version 5.6.500)
User Unable to See the Printer
The print spooler on the xenapp were going into stopping mode, hence the printer were getting disappeared on the users profile, Have implement the Print spooler restart Script post which the issue is resolved.
Users are unable to login on HSD_32 Farm for Ratnakar Bank
Have added 4 additional XEN app (5.0)VM (2003 win server ) for manage the load and issue got resolved
VDA Is getting Unregistered After Couple of hours.
1. Machine will be Showing as unregistered in Studio.
2. User Will be logged in and he can able to work.
3. Once he disconnect / logoff and try to reconnect back, he will not able to login.
4. logs say connectivity lost to Controller.
Resolution/Solution
update the VDA with latest hotfix . It can be downloaded from
http://support.citrix.com/article/CTX140473
Windows 7 I/Ops deep dive
Complete analysis of Windows 7 IOPs and calculation
Windows 2008 R2 hangs at "Please Wait for the System Event Notification Service" during the logoff
I have found similar problem in MS forum. Here is excerpt:
These steps MUST be performed by another domain user (since you won't be able to login to the machine yourself if you're the one experiencing the problem- obviously).
1. Login to the server
2. Open "Task Manager" and click on the "Services" tab
3. Sort all services by "Name" (first column), and find the service named "SENS"
4. Right click on this and select "Go to Process"
5. End the process this takes you to (normally an svchost.exe)
6. Open Windows Services (Start -> Run -> type "services.msc")
7. Start the "System Event Notification Service"
In order to perform these steps myself I simply created a secondary domain admin account which I can use each time I experience the issue.
I have found similar problem in MS forum. Here is excerpt:
These steps MUST be performed by another domain user (since you won't be able to login to the machine yourself if you're the one experiencing the problem- obviously).
1. Login to the server
2. Open "Task Manager" and click on the "Services" tab
3. Sort all services by "Name" (first column), and find the service named "SENS"
4. Right click on this and select "Go to Process"
5. End the process this takes you to (normally an svchost.exe)
6. Open Windows Services (Start -> Run -> type "services.msc")
7. Start the "System Event Notification Service"
In order to perform these steps myself I simply created a secondary domain admin account which I can use each time I experience the issue.
XenServer 6.1 - Unable to add the server to the pool – Resolved
Problem statement: We were unable to add the server in the pool.
Solution : Found Issues is from switch end.
XenDesktop 7.6 - Getting error : You are not authorize to perform this operation - Resolved
Problem statement: XenDesktop 7.6 - Getting error : You are not authorize to perform this operation.
Solution: Rebuilt XenDesktop 7.6 - Getting error : You are not authorize to site
XenDesktop 7.6 - Getting error : You are not authorize to perform this operation - Resolved
Problem statement: XenDesktop 7.6 - Getting error : You are not authorize to perform this operation.
Solution: Rebuilt XenDesktop 7.6 - Getting error : You are not authorize to site
XenServer 6.1: XS just shutdown but the log don't show any hardware issue– Resolved
Problem statement: Xen Server just shutdown but the log don't show any hardware issue
Solution: RCA being provided, xenserver were rebooted due to HA
XenDesktop 7.1 Migrating the database to SQL Express to SQL Mirroring Server – Resolved
Problem statement: XenDesktop 7.1 Migrating the database to SQL Express to SQL Mirroring Server.
Solution: Connection to DDC broke after sql mirroring was completed advised cx to manually enter the connection strings in the registry after reboot he was able to obtain the broker information archiving case
Receiver for Windows 4.2 - Users experience slow logins to launch Win7 VDA– Resloved
Problem statement: Also Receiver 4.2 - Very slow logins to Win7 VDA.
Solution: Recommend to engage HP vendor for support
Receiver for shared excel sheet having slowness in the Xendesktop 7.6 – Resloved
Problem statement: we have Xendesktop 7.6 deployed with windows 2008 R2 server published for desktop. users are facing slowness while working in shared excel file.
Solution: Issue happens in RDP. But still tried disabling excel hook but did not help.
citrix director not working – Resloved
Problem statement: Citrix director not updating session details and unable to retrieve historical data.
Solution: 1. Installed latest Citrix Director http://support.citrix.com/article/CTX200330 2. Changed "Enable Data Collection" and "Enable Detailed SQl Output" to true in MoniorConfiguration
XenApp 6.5 - Slow– Resloved
Problem statement: XenApp 6.5 - Slow.
Solution: You can read more about open vSwitch best practices in the article: http://support.citrix.com/article/CTX140764 To address this issue there are two ways:
1. Quick path to increase threshold: In XenServer 6.0.2 default value =1000; installing Hotfix XS602E024 allows customers to modify the value. Increase threshold to higher value, start with 3000 and monitor number of flow to see if it resolves the issue: To set the flow-eviction-threshold enter the following: ovs-vsctl set bridge xapi2 other-config:flow-eviction-threshold=3000 The setting is not persistent after host reboot but the command can be added to the end of the /etc/rc.local file If an upgrade or update changes the rc.local file then the commands may not persist so ? this needs to be checked. To verify if the field has been set correctly, run command ovs-vsctl get bridge xapi2 other-config:flow-eviction-threshold.
2. Upgrade to XenServer 6.5, which replaces single flow tables with megaflows, which have no hardcoded limit. see "Updated Open vSwitch" section on XenServer 6.5 page 3 http://support.citrix.com/servlet/KbServlet/download/38334-102-715141/XenServer-6.5.0_Release%20Notes.pdf
linux citrix receiver certificate error – Resloved
Problem statement: - Certificate error on SF machine.
Solution: we - Recommended the following : http://support.citrix.com/proddocs/topic/receiver-linux-13-1/linux-secure-config-client-ssl-certs.html
XenDesktop 7.1: Configure server in the XenDesktop, but not able to connect the site – Resloved
Problem statement: Configure server in the XenDesktop, but not able to connect the site.
Solution: http://kb.citrite.net/article/CTX139874
XenDesktop 7.1: Temp Profile getting loaded for user on WIN 7 HVD's – Resloved
Problem statement: Temp profile is getting loaded , when user connected to HVD VIA ICA.
Solution: Issue resolved after upgrading to UPM 5.2.1
XenDesktop 5.1: xen desktop 5.1 the host is giving maintenance mode, unable to disable it – Resloved
Problem statement: xen desktop 5.1 the host is giving maintenance mode, unable to disable it.
Solution: Work Around to retrieve production health - Yes. Update host connect with correct pool master ip.
XenDesktop 5.1: xen desktop 5.1 the host is giving maintenance mode, unable to disable it – Resloved
Problem statement: xen desktop 5.1 the host is giving maintenance mode, unable to disable it.
Solution: Work Around to retrieve production health - Yes. Update host connect with correct pool master ip.
XenDesktop 7.1: internet access denied within Citrix session – Resloved
Problem statement: In Hosted Shared environment users get access denied while accessing Internet, Whereas in physical desktop with same user ID it is working fine. We have blue coat proxy deployed in environment. Would like network engineer also to involved in this for a proper and faster resolution.
Solution: This issue is not related to Citrix at all ? this is purely Blue Coat proxy configuration. We have it proved easily by adding facebook.com to Exceptions in Proxy settings (see screenshot below) Please engage team responsible for Blue Coat proxy as this is completely outside of Citrix tech support..
XenDesktop 7.1: internet access denied within Citrix session – Resloved
Problem statement: In Hosted Shared environment users get access denied while accessing Internet, Whereas in physical desktop with same user ID it is working fine. We have blue coat proxy deployed in environment. Would like network engineer also to involved in this for a proper and faster resolution.
Solution: This issue is not related to Citrix at all ? this is purely Blue Coat proxy configuration. We have it proved easily by adding facebook.com to Exceptions in Proxy settings (see screenshot below) Please engage team responsible for Blue Coat proxy as this is completely outside of Citrix tech support..
Xen App 6.5: ica session intermittently unresponsive – Resloved
Problem statement: In XenApp 6.5 - When users login to the server it takes too long time.
Solution: This Case archived due to contact being lost.
Xen App 6.5: ica session intermittently unresponsive – Resloved
Problem statement: In XenApp 6.5 - When users login to the server it takes too long time.
Solution: This Case archived due to contact being lost.
Xen App 6.5: XenApp 6.5 - When users login to the server it takes too long time – Resloved
Problem statement: In XenApp 6.5 - When users login to the server it takes too long time.
Solution: ARCHIVING CASE: Issue currently not occurring.
Xen App 6.5: XenApp 6.5 - When users login to the server it takes too long time – Resloved
Problem statement: In XenApp 6.5 - When users login to the server it takes too long time.
Solution: ARCHIVING CASE: Issue currently not occurring.
Xen Desktop 7.1: Cx needs a hotfix http://kb.citrite.net/article/CTX141662 – Closed
Problem statement: Cx needs a hotfix http://kb.citrite.net/article/CTX141662.
Solution: http://kb.citrite.net/article/CTX141662.
XenDesktop 7.1 - Few VDIs are going un-registered and VDI is getting hung – Resloved
Problem statement: Few VDIs are going un-registered and VDI is getting hung.
Solution: Remove .NET Policy, The policy was causing the .net framework change (32/64) which caused the issue as the VDA use multiple .NET functions. Based on the architecture (32/64) - the functions would check different place in the registry. If you modify framework - the registry related calls will fail. Customer has another issue with the Server OS VDA. I offered a new case and assistance. Customer will contact the support if help is needed. Please go ahead and close the Ticket if we face any issues in Desktop OS, will reopen the Ticket. Regarding Server OS we discuss internally and we will open a Support Case if required.
XenDesktop 7.1 - Few VDIs are going un-registered and VDI is getting hung – Resloved
Problem statement: Few VDIs are going un-registered and VDI is getting hung.
Solution: Remove .NET Policy, The policy was causing the .net framework change (32/64) which caused the issue as the VDA use multiple .NET functions. Based on the architecture (32/64) - the functions would check different place in the registry. If you modify framework - the registry related calls will fail. Customer has another issue with the Server OS VDA. I offered a new case and assistance. Customer will contact the support if help is needed. Please go ahead and close the Ticket if we face any issues in Desktop OS, will reopen the Ticket. Regarding Server OS we discuss internally and we will open a Support Case if required.
XenServer 6.1 - Unable to create a memory dump – Resloved
Problem statement: Unable to create a memory dump.
Solution: --concern with MS.
XenServer 6.1 - Windows Server 2008 R2 booting to Black Screen – Resloved
Problem statement: Windows Server 2008 R2 Booting to Black Screen.
Solution: No contact from Cx. This is most likely a windows error, and should be troubleshot from the Windows side, or recover VM from backup. The Cx has been told to update their XS6.1 pool with all required updates and drivers.
Provisioning Server - Application Crash in Citrix Session on PVS VDISK – Resloved
Problem statement: PVS 7.1 Application getting crashed in Citrix session on pvs vdisk with Citrix profile management.
Solution: We collected a couple of crash dumps and got them analysed. None of them point this to be a Citrix issue..
Provisioning Server - Provisioning server 6.1 - Require RCA for PVS down – Resolved
Problem statement: Require RCA for PVS down.
Solution: Hotfix 19/21
VDA not getting registered with DDC - Resolved
Problem statement: Desktop VDA on server OS does not register with DDC
Solution : Under HKCR\TypeLib\{9A0B1570-B01D-4196-BDC9-4CE132108BA6}\1.0\0, deleted value win64
RCA for the server reboot - Resolved
Problem statement: Desktop VDA on server OS does not register with DDC
Solution : Under HKCR\TypeLib\{9A0B1570-B01D-4196-BDC9-4CE132108BA6}\1.0\0, deleted value win64
Unable to boot Xen Server 6.1 - Resolved
Problem statement: Xen server 6.1 booting not happening
Solution : The boot mode is set to the BIOS. set it to the hard drive which resolve the issue. rectified the state in the BIOS which resolved the issue.
T he host does not appear to have any network interfaces - Resolved
Problem statement: Unable to see NIC cards during fresh installation of XenServer
Solution : - - Checked compatibility of hardware, its supported. - The installation gets stuck on screen giving error that "The host has no network interfaces". - Tried to load the driver through F9, there was no driver. - Asked him if the NIC cards are showing the links as up, it was true. - He used the same ISO for other 5 servers in the rack, those servers are running successfully. - Provided him 2 GA versions for "be2net" driver and asked him to load the drivers. - Tried loading the drivers, verified them, everything was successful. - But still got same issue. - Tried with 6.1 ISO, it was giving same issue. - The server was taking 5 minutes in "detecting hardware..". - Asked him to contact HP for the correct firmware version, as discussed with senior colleague, its a driver-firmware version. - Contacted the customer later, issue was resolved from HP, later on.
Problem creating new vdisk - Resolved
Problem statement: problem creating new vdisk, vdisk is locked
Solution: Fixed file server problem
Unable to create host connection to SCVMM R2 provisioning server 7.6 - Resolved
Problem statement: Unable to create host connection to scvmm R2 from PVS 7.6 server. Error: Not authorized for connection
Solution: -Initiated GTM and looked into the environment. -Tested Connectivity to SCVMM from the SCVMM Client Console on the DDC -Successfully able to connect. -Discovered SCVMM 2012 R2 is installed on the SCVMM server but SCVMM 2012 (non-R2) is installed on the PVS server -This difference in versions creates a discrepancy in SDKs which Streamed VM Setup Wizard (and XDSW & MCS) use to communicate to the hypervisor, thus resulting in the error. -Upgrading SCVMM 2012 to R2 on the PVS server resolved the issue.
IMA service is not being started on Xen App 6.5 - Resolved
Problem statement: One of their critical servers, IMA service is not being started.
Solution: Copied over an MF20.DSN from a working server to the problem server. ? Ran DSMAINT CONFIG on the problem server with the correct username and password ? Verified good connectivity to the SQL database. ? Restarted IMA services. Verified good abilities to now start correctly.
How to check the checksum offload - Resolved
Problem statement: Disable IPv4 Checksum Offload ?
Disable IPv4 Large Send Offload (LSO) ? Enable Receive Side Scaling (RSS) ? Offload Receive IP Checksum OFF ? Offload Receive TCP Checksum OFF ? Offload TCP Segmentation OFF ? Offload Transmit IP Checksum OFF ? Offload Transmit TCP Checksum OFF ? IPv4 Checksum Offload OFF ? Flow Control - Generate & Respond ON ? Jumbo frames size ? 9000
Solution: User open for XenServer query case answered all his query and confirm us to close the case
Streaming service hung - Resolved
Problem statement: Streaming service is not responding
Solution: Provided the log analysis and recommended to install at least hot fix 19 on PVS servers: http://support.citrix.com/article/CTX137709 you can also install patch 21: http://support.citrix.com/article/CTX141063
Time drift issue on VMs - Resolved
Problem statement: Time drift issue on Windows 2012 VMs running XenServer 6.2 SP1
Solution: Customer patching MS fixes and Xentools latest on server 2012 images. This is currently in progress and customer will need some time to get all the machines to this hotfix level and observer if issue is fixed. MS to be engaged for WMI queries if needed.
Unable to add ESR virtual disk into XenVM - Closed
Problem statement: Unable to add ESR virtual disk into XenVM.
Solution: No response after 3 attempts at contacting the user.
PVS Image getting blue dump - Resolved
Problem statement: PVS Image getting blue dump while chamging to private mode.
Solution: - End customer is busy on some other issue, cannot test the solution. - last update to the customer What about diskpart? do you see the disk? diskpart -> list disk Is your working target device and non working target device in the same OU? I'm wondering if there's any computer policy applied to those machines especially something like windows bitlocker. I've found something a in forum which may fix the blue screen but the cause is unknown. http://superuser.com/questions/302603/problem-recreating-bcd-on-windows-7-64bit-the-requested-system-device-cannot-b Put the Windows 7 x64 installation disc in the disc drive, and then start the computer. Press a key when you are prompted. Select a language, a time, a currency, a keyboard or an input method, and then click Next. Click Repair your computer. Click the operating system that you want to repair, and then click Next. In the System Recovery Options dialog box, click Command Prompt. diskpart select disk 0 select part 1 active Reboot and boot back into the Windows 7 x64 install disc. bcdedit /export C:\BCD_Backup c: cd boot attrib bcd -s -h -r ren c:\boot\bcd bcd.old bootrec /RebuildBcd http://support.microsoft.com/kb/927392
Error while launching XSconsole - Resolved
Problem statement: Error while launching XSconsole
Solution: - Performed these steps:
Edit /usr/lib/xsconsole/XSConsoleData.py ->Look for this line: self.data['dmi']['memory'] += int(size.group(1)) * 1024 ->Change ?memory? field to ?memory_size? : self.data['dmi']['memory_size'] += int(size.group(1)) * 1024
NIC is not connected showing in the Xen Server 6.2 - Resolved
Problem statement: NIC is not connected showing in the Xen Server 6.2
Solution: 1) There are no FC drivers available for Broadcom netxtreme, and because of this we have this issue. 2) We can use iSCSI (cause iSCSI drivers are available for these cards. 3) As this is a feature enhancement, support don’t have any role in this, HP should raise a partner ticket with Citrix to get the required driver.
PVS HA issue - Resolved
Problem statement: PVS HA failure. 2nd server is showing done and stream service is not getting started.
Solution: Checked for the services, tried restarting service from console itself, it failed. -->Tried restarting it from the problematic server itself, it was showing fine. -->tried running config wizard again but still same. -->tried rebooting the server but again same. -->tried killing inventory on the server and restarted the soap and the stream service but no luck. -->Checked the hotfix level, he has no hotfix installed on the servers..
PDF scrolling issue - Resolved
Problem statement: PDF scrolling is very slow in Citrix VDI.
Solution: we have configured the following changes on the policies: Lossy Compression Level None Progressive Compression level low. Now it is seen that the scrolling speed in a ICA session is as good as an RDP session. Comparison with a RDP session is a Valid bench mark.
Unable to detect USB device (Wey Keyboard) in HVD - Resolved
Problem statement: We have deployed Xendesktop 5.6 with windows 7 machine published for the users, some users using Wey Keyboard USB device, but it unable to detect in HVD.
Solution: USB device not working on Remote Desktop. If device not working on Remote Desktop it won't work on Xendesktop.
Unable to access storefront website - Resolved
Problem statement: Unable to access storefront website through internet. VPX.
Solution: To make polices specific and to differentiate the receiver traffic and normal web traffic below expression we configure For Storefront Using ICA proxy Via Receiver we should have below profile and policy settings in place:\ Session policy :REQ.HTTP.HEADER User-Agent CONTAINS Citrix-Receiver && REQ.HTTP.HEADER X-Citrix-Gateway EXISTS Profile associated to this should have below settings: Clientless Access-Override Global ?Allow Plugin-In Type?Override Global-Java SSO to Web Apps ?Override Global-checked For Receiver for Web: Session policy expression:REQ.HTTP.HEADER User-Agent NOTCONTAINS CitrixReceiver && REQ.HTTP.HEADER X-Citrix-Gateway EXISTS
PVS 6.1 hanging servers - Closed
Problem statement: how far back got a pvs server got hang
Solution: > Version of PVS 6.1.0.1088 > Hotfix level - base > How many PVS servers are there? Only 1 > Recent changes on PVS server if any? NA Using PVS software version - 6.1.0.1088. The stream process may exit unexpectedly in this release. This issue has been fixed in the hotfix 19 for PVS 6.1. Please download it from http://support.citrix.com/article/CTX137709. The issues fixed in this release talk about stream process issue which has been resolved in this release. Please install it on you PVS server. For installation please follow the following steps: > Make sure there are no connections on your PVS server. > Reboot your PVS server. > Now uninstall all the PVS components from the PVS server. > Reboot the PVS server. > Reinstall the PVS server following the documentation - http://support.citrix.com/proddocs/topic/provisioning-61/pvs-install-task3-install.html > Run the configuration wizard for PVS selecting the following option - To join a farm that is already configured. > Now test if machines are successfully streaming from this PVS server. If yes, upgrade the PVS server 2 following the same steps. > The target devices will stream even if the target device software is not updated to hotfix 19 considering that the target devices are already running with version 6.1.0.1088. But it is recommended to upgrade the target device software as well. To do so you can follow the steps as mentioned in - http://support.citrix.com/article/CTX135746
Linux receiver ctrl key stick issue - Resolved
Problem statement: We have installed Linux receiver 13.0 in Ubuntu system. However we are facing ctrl or shift key stick issue.
Solution: Provided latest linux receiver which resolved this issue 13.0.2
Edgesight-5.4 "Login failure to the domain." - Resolved
Problem statement: Edgesight-5.4 "Login failure to the domain."
Solution: Created temp directory on Reporting server. Changed authentication just to Anonymous for IIS on ES server.
XenServer 6.0.2 Issue - Closed
Problem statement: Error: Database crash
Solution: Unable to reach the customer.
Performance issue in Xendesktop 7.1 - Resolved
Problem statement: Application performance issue in Windows 7 dedicated desktops
Solution: Private fix supplied
XD 7.1 - Closed
Problem statement: XD 7.1
Solution: Issue not with Citrix as the Performance is affected on a NON-Citrix box as well. Kindly contact the Application vendor for further assistance.
PVS Imaging issue on XenServer 6.2 SP1 - Resolved
Problem statement: Unable to Create Vdisk from PVS 6.1 on XenServer 6.2 SP1 platform
Solution : Uninstalled target device software 6.1 . uninstalled XS tool and reinstalled it and rebooted it. installed target device software 6.1.19 and then ran imaging wizard . After that we were able to create a new vdisk.
USB redirection problem - Resolved
Problem statement: Create policy and allowed user for USB redirection, but its not working
Solution : After a lot of troubleshooting done, we figured out that this is an issue with the AD as the AD does not provide sufficient permissions to the users to get the access via Thin Clients. Those users can access the USB from a physical machine, when the physical machine is externally given permission from the AD to access the USB. Since the issue is still pending on the AD end, we would archive this case as per your confirmation. In case you face any further issues once the AD provides complete permissions, you can get back to us and get the case reopened.
Services not responding - Resolved
Problem statement: Services seems to be crashing after some time . services are not responding.
Solution : Re-registered the services instances using powershell commands: Ran the following powershell commands to remove the connection of services to the Database : Set-ConfigDBConnection -DBConnection $null Set-AcctDBConnection -DBConnection $null Set-HypDBConnection -DBConnection $null Set-ProvDBConnection -DBConnection $null Set-PvsVmDBConnection -DBConnection $null Set-BrokerDBConnection -DBConnection $null After performing the above commands, the DDC lost connection to XD database and then we created the site and pointed it to the same DB.
XenDesktop 7.1 – Resolved
Problem statement: XenDesktop 7.1
Solution: Issue not with Citrix as the Performance is affected on a NON-Citrix box as well. Kindly contact the Application vendor for further assistance.===================
Edgesight-5.4 "Login failure to the domain." – Resolved
Problem statement: Edgesight-5.4 "Login failure to the domain."
Solution: Created temp directory on Reporting server. Changed authentication just to Anonymous for IIS on ES server.
User Sessions Problem.- Closed
Problem statement: Issue: There are lot of sessions for the same user ID on the XA Server, session IDs are different and they are not able to logoff the user sesion from AppCenter and Even from Task Manager on the XA Server. They have to reboot the XA Server to get it fixed. XA65 HRP02 Provisioned XA Servers User sessions get stuck for random users connecting to a specific XenApp server. Mostly 2 to 6 sessions of a particular user gets stuck & nothing else but only restart of server resolves it. Please assist to resolve it as we can?t restart the server on every instance.
Index
Topics Page Nos
1) Introduction 3-5
2) Description 6
3) Troubleshooting steps 7-12
1) Introduction
VI team have provided Citrix access to NOC team, Citrix server IP 192.168.82.73 located in PDM, Manila and Vijayawada centers using for production 24/7, more the 100 users are connected to Cirtix, Need to login to 192.168.81.21 and take RDP to 192.168.82.73 to connect Citrix, Role of NOC team is to reset the Citrix VDI’s. If any problem during the reset of VDI’s NOC has to take help of VI team to get it fixed.
To start Delivery services Console following are the steps.
1.1- Kindly double click on Launch Delivery services Console on desktop, wait for 2-3 minutes to get start.
OR
Kindly click on below icon to start Delivery services, wait for 2-3 minutes to get start.
After doing above steps, will get below screen
2) Description
Click on XDFSPROD and Desktop Groups to get VDI group wise details
3) Troubleshooting steps
3.1) When selecting particular center Vijayawada, VDI’s Desktop state suppose to be in all three (Not Registered, In Use, Idle) status. In this case Citrix server is working fine.
Not Registered We can use this for new user
In User Presently user logged into VDI
Idle- Ready to use
3.2) In case all the VDIs Desktop state displaying as Not Registered [as shown below diagram] then there is issue with Citrix server services.
In above Scenario need to restart below services
a) Citrix Desktop Delivery Controller Service
b) Citrix Pool Management Service
Before restarting these services need to keeping informed VDI team, as of now these services are restarting only by Veera R
3.3) VDI team observed common incidents, i.e., user unable to connect to Citrix but from Citrix end everything is fine, below example explaining about the incident.
Below VDI 94 user able to connect to VDI when we check from citrix end, but user unable to connect
As above scenario we need to take VDI Host name [INVJGHX-VD094.CADOMAIN.LOCAL], find the same hostname in VM Ware and Reset the VDI as shown below
3.4) After Reset VDI also still user unable to connect VDI, need to restart below services in user VDI
Services - “Citrix ICA Services”
Below VDI example will describe how to restart services
6.1 INVJGHX-VD094.CADOMAIN.LOCAL [VDI]
6.2 Need to login above VDI through Admin rights
6.3 Select Start Run Services.msc will get list of services Need to Restart “Citrix ICA Services”
(Unable to attach print screen for Step 6 coz, not getting support from VDI)
Troubleshooting Guide
Yes, the title of this document says it all!! OpManager is a very simple and easy-to-use application and you will simply need to install the application and get started. That still does not rule out the fact that there might be a few issues coming in the way, slowing down your objective of getting your resources monitored by OpManager. This document helps you troubleshoot the common problems that you might encounter when using OpManager..
1. Get over initial hiccups
2. Monitoring Configurations
3. Alerting and Notifications
4. Reporting
Tips to get over the initial hiccups
Following are a few tips which may be handy to get over your initial hiccups when using OpManager. For easier navigation, these are further classified as follows:
• Starting Trouble
• Discovery
• Mapping
Starting Trouble!
• Failed to establish connection with Web Server. Gracefully shutting down.
• Error Code 500: Error in applying the OpManager 6.0 license over opmanager 5.6 or the version upgraded from 5.0
• Can't create tables or not all the tables are created properly' error is displayed during OpManager startup.
• Error downloading client files from BE
Failed to establish connection with Web Server. Gracefully shutting down
Cause 1
While starting OpManager as 'root' user in Linux platform, the server goes down with the following message "Failed to establish connection with web server. Gracefully shutting down ..". This is because OpManager starts its Apache Web Server as 'nobody' user and 'nobody' group. The Apache Server may not have read and execute permissions to access the files under <OpManager Home> directory. Hence, the connection to the Apache Server will not be established and the OpManager server will gracefully shut down.
Solution
• Change the value of the parameter Group in httpd.conf file found under <OpManager Home>/apache/conf/backup/ directory.
• Group #-1 to Group nobody
• Provide executable permission to"httpd" file available under <OpManager Home>/apache/bin/ by executing the following command:
• chmod 755 httpd
OpManager server starts successfully after performing the above mentioned steps.
Cause 2
If you are using Linux 8.0/9.0 : In Linux 8.0/9.0, a file named libdb.so is not bundled. In earlier versions it was bundled. This file is needed by Apache. Without this, apache does not start in Linux 8.0. This results in the issue you are facin
Solution
The file has been bundled with the product and is present in the /lib/backup directory in the latest version of OpManager. Copy it to the /lib directory and restart OpManager.
This solution has worked for those using Fedora and Madrake Linux too.
If you continue to face the problem, then execute the script StartWebSvr (this will be a .bat file in Windows installation and .sh file in Linux installation) in the /apache folder of OpManager installation and send us the output.
If yours is a Debian Linux, then check if libgdbm.so.2 is available under /usr/lib directory. If not, you can install the stable version of libgdmg1. Download this package from the url http://packages.debian.org/stable/libs/libgdbmg1
Error Code 500: Error in applying the OpManager license
Cause
This error is encountered where there is an incompatibility between the version of application installed, and the version specified in the procured license.
Solution
Contact OpManager support with the details of the version installed including the Build number and email the license sent to you. You will be sent a compatible license after verification.
Can't create tables or not all the tables are created properly' error is displayed during OpManager startup
Cause
The database tables may be corrupted.
Solution
You can repair the corrupt tables. Run the repairdb.bat under \bin directory. After this, run the ReInitializeOpManager.bat script in the same directory. This will remove all the tables created. Restart OpManager.
Error downloading client files from BE
Cause
This error occurs when the database tables are corrupted. The corruption can happen due to improper shutdown of OpManager such as during power outages.
Solution
The database must be repaired and OpManager needs a restart. Here are the detailed steps:
1. Stop OpManager Service
2. Open a command prompt and change directory to /opmanager/bin
3. Execute RepairDB.bat/sh. This repairs all the corrupt tables.
4. After it finishes executing, run it once again to ensure all corrupt tables are repaired.
5. Restart OpManager.
Discovery
• Devices are not discovered
• Devices are identified by IP Address and not host names.
Devices are not discovered
Cause
This can happen if the ping requests to device get timed out.
Solution
To resolve this, increase the ping timeout in the file /conf/ping.properties and try again.
Devices are identified by IP addresses and not by host names
Cause
If DNS Server address is not set properly in the machine hosting OpManager, the DNS names of the managed devices cannot be obtained from the DNS server.
The other possible reasons could be:
• The DNS Server is not reachable
• The DNS Server is down during discovery.
• The DNS Server does not exist.
Solution
Ensure that the DNS Server is reachable and configure the DNS Server address properly.
Mapping
• Some of my Routers are discovered as Desktops or Servers.
• How are Servers categorized in OpManager? Some servers are classified under desktops!
Some of my Routers are discovered as Desktops or Servers
Cause
The devices may not be SNMP enabled or the SNMP agent in the device is not responding to queries from OpManager.
Solution
Enable SNMP and rediscover the device. Despite this, if you face issues, troubleshoot as follows:
• Do you see a blue star in the device icon on the maps? This implies that the device responds to SNMP request from OpManager. The device is still not classified properly? Simply edit the category from the device snapshot page.
• If SNMP agent is not running on the router, it will be classified as a server or desktop.You can verify this by the blue star appearing on the top left corner of the device icon for the SNMP-enabled devices. To categorize the device properly, start the SNMP agent in the device. Refer to Configuring SNMP agents in Cisco Devices for details. Rediscover the device with correct SNMP parameters.
• If the SNMP agent is running on the router and you still do not see the blue star in the device icon, then check if the SNMP parameters are properly specified during discovery. If not, rediscover the device with correct SNMP parameters.
• The router is discovered as a server or desktop if the IP Forwarding parameter of the device is set to false. To set the value of this parameter to true
o Invoke /opmanager/bin/MibBrowser.bat
o Expand RFC1213-MIB.
o In the ip table, click ipForwarding node.
o Type 1 in the Set Value box and click Set SNMP variable on the toolbar.
o Rediscover the device with correct SNMP parameters.
Similarly, for switches and printers too, enable SNMP in the device and rediscover.
How are Servers categorized in OpManager? Some servers are classified under desktops!
Following devices are automatically classified under servers based on response to SNMP/telnet request to the devices:
• Windows 2003 Server
• Windows 2000 Server
• Windows Terminal Server
• Windows NT Server
• Linux Servers
• Solaris Servers
Following devices are classified under desktops:
• Windows 2000 Professional
• Windows XP
• Windows NT Workstation.
• Windows Millinium Home Edition
• Devices not responding to SNMP and Telnet
If any of the servers are classified under desktops, simply import them into servers. Refer the steps mentioned to check for SNMP.
Monitoring Configurations
• SNMP Monitoring
• Telnet/SSH Monitoring
• WMI Monitoring
SNMP Monitoring
Few reasons why SNMP-based monitors may not work are:
• Agent is not enabled on the monitored system.
• OpManager is trying to contact the agent with incorrect credentials, such as a wrong password or wrong port.
• The SNMP service in the monitored system may not be configured to accept SNMP requests from the host where OpManager is installed.
• There is a delay and the queries sent by OpManager to the agents in the monitored devices are getting timed out or the devices are no longer in the network.
• The particular OID (for which the performance monitor is configured) is not implemented in the device.
Following are few common problems encountered and the detailed procedure to troubleshoot:
• Despite SNMP being enabled on the device, the dial graphs for CPU, Memory, and Disk Utilization are not seen.
• Request timed-out error
• Error # Device does not support the required MIB
• Other common SNMP errors encountered
Despite SNMP being enabled on the device, the dial graphs for CPU, Memory, and Disk Utilization are not seen.
Cause
SNMP may not be enabled, or the SNMP agent is not responding to requests.
Solution
Check the SNMP configurations, rediscover the device and re-add the monitors. Troubleshoot as follows:
The possible reasons for the graphs not appearing are:
• The Resource monitors may not have been associated to this device. Associate the monitors.
• Check if SNMP is enabled properly on this device. If Yes, the Agent may not have responded to the SNMP request. Check if the Agent is responding using the Mib Browser.
• If the device has just been added, wait for the first poll to happen.
Following are the steps to troubleshoot:
1. In the device snapshot page, scroll down to the monitors list. Click the Edit icon against a monitor. For instance, let us try the CPU Utilization monitor. Click the Test Monitor link in the resulting screen. See if the monitor responds to the test request. If it does, you will see the dial graph.
2. If there is an error message after step#1, it can be because of the snmp request to the cpu variable getting timed-out, or the oid may not be implemented in the MIB.
3. To confirm the reasons mentioned above, invoke the tool MibBrowser.bat present in /bin directory. Load the Host Resource mib and query the oid .1.3.6.1.2.1.25.3.3.1.2 for the device that is not showing the cpu dial.
4. If there is a response for the query in MibBrowser, it implies that the OID is implemented and the dial not appearing can be due to snmp timeout. So, you will need to configure the snmp timeout by including the parameter DATA_COLLECTION_SNMP_TIMEOUT 15 in the file NmsProcessesBE.conf for the process 'PROCESS com.adventnet.nms.poll.Collector'. Look for the following default entry in this file:
PROCESS com.adventnet.nms.poll.Collector
ARGS POLL_OBJECTS_IN_MEMORY 25 POLL_JDBC true MAX_OIDS_IN_ONE_POLL 15 AUTHORIZATION true DATA_COLLECTION_QUERY_INTERVAL 120000 PASS_THRO_ALL_POLLING_OBJECTS true CLEAN_DATA_INTERVAL 999999
Include the mentioned additional parameter. Now the changed entry will be as shown below:
PROCESS com.adventnet.nms.poll.Collector
ARGS POLL_OBJECTS_IN_MEMORY 25 POLL_JDBC true MAX_OIDS_IN_ONE_POLL 15 AUTHORIZATION true DATA_COLLECTION_QUERY_INTERVAL 120000 PASS_THRO_ALL_POLLING_OBJECTS true CLEAN_DATA_INTERVAL 999999 DATA_COLLECTION_SNMP_TIMEOUT 15
5. On the other hand, if there is no response in the Mib Browser, it implies that the OID is not implemented. The vendor must be requested to implement this variable for you. As an alternative, you can associate a telnet/wmi-based monitor for this device. Delete the existing SNMP-based monitor, Click the Add Monitor link again and select telnet/wmi-based monitors.
Request Timed-out
Cause
This error is encountered when the SNMP agent in the monitored device is unable to respond to requests from OpManager within 5 secs
Solution
Increase the SNMP timeout in the NMSProcessesBE.conf file as detailed in the above tip.
Error # Device does not support the required MIB
Cause
This error occurs when you are trying to monitor a variable/MIB that is not implemented in that device
Solution
Check the MIBs supported by the device and configure custom monitors for the required variables from the supported mibs.
Other SNMP Errors
Refer to the following document for detailed SNMP troubleshooting tips:
http://www.adventnet.com/products/agenttester/help/mib_browser/mb_error_messages.html
Telnet/SSH Monitoring
Following are few other errors that you might encounter when configuring CLI-based monitors.
• Telnet-based resource monitors not showing data
• Unable to connect: Connection refused:
• Unable to connect: No route to host:
• Unable to connect: Connection timed out:
• Request Timed out to <server name>
• Login Parameter incorrect. Read timed out.
• Exception in getting the command output: Timed out.
Telnet-based resource monitor is not showing any data
• If you have added a Telnet/SSH based Resource monitor, check if the UserName and Password specified are correct. Click the 'Password' link to configure the correct username and password to the device.
• Despite the correct user name and password, if you are still unable to see the dial graphs on Linux/Solaris/AIX/UX devices, try the following steps :
• Check if the login prompts, password prompts, and the command prompts are correctly specified in the CLI credentials.
• Verify the credentials by opening a remote telnet session to these devices from the machine where OpManager is installed.
• If the login credentials are correct, it is possible that the command used to retrieve the resource data does not execute on the device, or the output is different from the expected standard format. In this case, contact support with your details and you will be assisted with the configuration changes.
Unable to connect: Connection refused: connect
The possible reasons for this error could be:
• Telnet is not enabled on the monitored server. Check and enable Telnet.
• The user name and password configured as part of the CLI credential is incorrect. Configure the correct name and try configured.
• It is possible that it is not a Linux/Solaris device. It might have been categorized incorrectly. Check and change the device type.
Unable to connect: No route to host:
The above error is encountered when the monitored device is not in the network. Plug the device into the network.
Unable to connect: Connection timed out:
The above error too is encountered when the monitored device is not in the network. Plug the device into the network.
Request Timed out to <server name>
The Telnet/SSH request sent to the device gets timed out. It is possible that the device is down, or is too busy.
Login Parameter incorrect. Read timed out
This error is encountered when either the user name, the password, or the login/password prompts are incorrect. Verify by opening a telnet session to the device from the machine where OpManager is installed and try connecting.
Exception in getting the command output: Timed out
This exception occurs due to the following reasons:
1. The device is not in the network.
2. CLI connection is establised to the device but the device goes out of network at the time of gathering CLI command outputs from it.
WMI Monitoring
Some more WMI monitoring errors with error codes
• WMI-based resource monitors not showing data
• The WMI monitors are not working. Says 'error- access denied'
• 80070005 - Access is denied
• 80041064 - User credentials cannot be used for local connections
• 800706BA - The RPC server is unavailable
• 80041010 - Invalid class
• 80041003 - Access Denied
• 80040154 - WMI Components are not registered
• 80080005 - Internal execution failure in the WMI Service
• 8004106C - WMI is taking up too much memory
• 8004100E - Invalid namespace
• 80041017 - Invalid query
WMI-based resource monitor is not showing any data
• If you have added a WMI based Resource monitor, check if the UserName and Password specified are correct. Click the 'Password' link to configure the correct username and password to the device.
• Ensure that you have configured the domain administrator user name and password for WMI Monitors if the device is in a domain. Configure as <domain name>\<admin user name> in the User Name field. If the device is in a workgroup, it is sufficient to configure the device username and password.
• Despite the correct user name and password, if you are still unable to see the dial graphs in Windows devices, try the following steps
o Open a command prompt and change directory to /opmanager/conf/application/script
o Type cscript cpu.vbs <device name> <domain name\admin username> <password>
If this command returns a proper output, you should be able to see the dials. If you encounter an error such as Error # Access denied, very the login credentials once again.
o If the monitored device is Windows XP, try the following option too:
Go to Administrative Tools -->Local Security Policy Select Security Options
From the options on the right, select Network access: Sharing and security model for local accounts
Right-click and select Properties
Change the privilege from Guest to Classic.
Remove and re-add the monitors.
Check to see if the monitors are up.
WMI Monitors are not working. It always says 'error # access denied'
This error is encountered when the login credentials are incorrect.
Follow the steps below to resolve:
1. Verify if you have provided the domain administrator username and password to connect to the device as mentioned in the above tip. If the device is in a domain the user name should be like "domain name\administrator name".
2. If the login credentials as specified in step 1 are correct, then try associating a WMI based monitor ( preferably, a Free/Used Space in MB/GB graph ) to the Exchange Server using the Resource Monitors -> Add Monitor -> WMI based monitor -> Free/Used Disk Space in MB/GB. You should get the list of drives available in the device.
3. If step #2 does not go through, then try enabling the WMI, RPC services on the Windows system and try the same again.
4. This can also happen if the DCOM settings are not configured properly.
You can check the exact error for this when you run a vbs script from the command prompt as in
cmd> cd [OpManagerHome]\conf\application\scripts\
cmd> cscript cpu.vbs [machinename] [domainname]\[username] [password]
5. You can also try configuring the dcom settings as mentioned below:
From the Run Prompt of your Windows 2k Server, type \"dcomcnfg\" and expand the tree under Component Services -> Computers. Click on the My Computer Icon from the Icon bar and select Default Properties. Check the following:
Enable Distributed COM on this computer
Enable COM Internet Services on this computer
Select the Default Impersonation Level as \"Impersonate\".
You can also edit the COM Security settings if needed.
6. If the above 4 steps do not help, try changing the service Log-on details as follows
Go to Windows Service UI.
Open "Properties" dialog of the "ManageEngine OpManager" service
Go to "Log On" tab
In the "Log on as" option select "This Account" and enter domain name\username and password, which has rights to access WMI data.
Save and restart opmanager.
Note: This will make the tray icon and splash screen disappear.
The error codes and the resolutions are explained below:
80070005 - Access is denied
Cause
This error occurs when incorrect login credentials are configured.
Solution
• If the device is in a domain, ensure to configure the correct domain name, user name, and password. If the device is in a workgroup, it is sufficient to configure only the user name and password. For instance, if the domain name is BigDom, username is admin, in the user name field, type BigDom\admin.
• It is also not necessary to specify the user name and password for devices that have user access from the machine where OpManager is installed.
• Despite the correct credentials, if you still face issues, troubleshoot further using the following steps:
o Check if the user account is valid in the target machine by opening a command prompt and executing the following command:
net use \\<monitored device name>\ADMIN$ /u:"<Domain Name\User Name>" "<password>"
If this command throw errors, the provided user account is not valid on the target machine.
o Check if 'Remote DCOM' is enabled in the monitored workstation. If it is not enabled, enable it as follows:
Select Start > Run
Type dcomcnfg in the text box and click OK
Select the Default Properties tab
Select the Enable Distributed COM in this machine checkbox
Click OK
To enable DCOM on Windows XP hosts:
1. Select Start > Run
2. Type dcomcnfg in the text box and click OK
3. Click on Component Services > Computers > My Computer
4. Right-click and select Properties
5. Select the Default Properties tab
6. Select the 'Enable Distributed COM' in this machine checkbox
7. Click OK
If the above steps do not help, try changing the service Log-on details as follows:
• Go to Windows Service UI.
• Open "Properties" dialog of the "ManageEngine OpManager" service
• Go to "Log On" tab
• In the "Log on as" option select "This Account".
• Configure the user name and password here of the account which has access to the remote machine. Save and restart opmanager.
• Try the above 3 steps again.
Note :You will not find the tray icon and splash screen after you make these changes.
80041064 - User credentials cannot be used for local connections
Cause
This error is encountered when you specify the Username and password for monitoring the machine where OpManager is running.
Solution
Do not specify Username and password for the localhost. To resolve the issue, remove the configured user name and password from "Passwords" link in the device snapshot page.
800706BA - The RPC server is unavailable.
Cause
This error is encountered when the RPC and WMI services are not running and if the device is not pingable.
Solution
• Check if the device is up and running, and pingable.
• Check the Remote Procedure Call(RPC) and Windows Management Instrumentation(WMI) Services are running
o Select Start > Run
o Type 'services.msc' in the text box and click OK
o In the listed services, see if the status of RPC and WMI services are shown as started.
o Start the services if it is not started.
• A firewall might be configured on the remote computer. Such exceptions mostly occur in Windows XP (with SP 2), when the default Windows firewall is enabled. Disable the default Firewall in the Windows XP machine as follows:
o Select Start > Run
o Type Firewall.cpl and click OK
o In the General tab, click Off
o Click OK.
• If the firewall cannot be disabled, Enable Remote Administration(for administrators) by executing the following command on the remote machine : "netsh firewall set service RemoteAdmin"
• A firewall might be blocking the WMI traffic. Give access to WMI traffic in the firewall. You will need to open the ports 445,135 in the firewall.
80041010 - Invalid class
Cause
This error occurs when the required WMI class is not registered.
Solution
• Check whether the desired application is installed.
• To register all the WMI classes for the installed application. Run the below commands:
o For Windows 2000 'winmgmt /resyncperf' command from the monitored device.
o For Windows XP and 2003 'wmiadap /f' command from the monitored device.
80041003 - Access Denied
Cause
This error occurs when the user name provided does not have sufficient access privileges to perform the operation.
Solution
1. It is possible that this user does not belong to the Administrator group for this host machine.
2. Try moving the user to the Administrator Group of the workstation.
3. Try with an administrator (preferably a Domain Administrator) account.
80040154 - WMI Components are not registered
Cause
This error occurs when the WMI is not available in the remote windows workstation. This happens in Windows NT. Such error codes might also occur in higher versions of Windows if the WMI Components are not registered properly.
Solution
• Install WMI core in the remote workstation. This can be downloaded from the Microsoft web site.
• Register the WMI DLL files by executing the following command in the command prompt:
winmgmt /RegServer
• Install the WMI for Windows NT by downloading the below exe:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=C174CFB1-EF67-471D-9277- 4C2B1014A31E
80080005 - Internal execution failure in the WMI Service
Cause
This error occurs when there is some internal execution failure in the WMI Service (winmgmt.exe) running in the host machine. The last update of the WMI Repository in that workstation could have failed.
Solution
Restart the WMI Service in the remote workstation:
1. Select Start > Run.
2. Type Services.msc and click OK.
3. In the Services window that opens, select Windows Management Instrumentation service.
4. Right-click and select Restart
8004106C - WMI is taking up too much memory
Cause
This error occurs when WMI is taking up too much memory. This could be caused either by low memory availability or excessive memory consumption by WMI.
Solution
• WMI is taking up too much memory.
• This could be caused either by low memory availability or excessive memory consumption by WMI.
• Try restarting or reinstalling the wmi service.
8004100E - Invalid namespace
Cause
Invalid namespace Compiler is not a normal error. It is possible that the desired application using the namespace is not installed properly.
Solution
• Try re-installing the application or the WMI services alone.
• Contact http://support.opmanager.com with logs.
80041017 - Invalid query
Cause
'Query was not syntactically valid' is not a normal error. It is possible that the desired application using the namespace is not installed properly.
Solution
• Try reinstalling the application or the WMI services alone.
• Contact support with logs.
For any other error codes, refer the MSDN knowledge base.
Alerting and Notification
• Email notifications are not received
• Error! page is displayed when a profile is selected
• Modem-based SMS notifications are not working
Email notifications are not received
Cause
Profile may not be associated to the device, or the mail-server settings may be incorrect
Solution
• Check if the notification profile is associated to the device
• Check if the correct criterion is selected in the profile configuration
• Ensure the mail-server settings are configured correctly.
Error! page is displayed when a profile is selected.
Cause
The profile name may contain special characters or a space
Solution
You will not be able to delete the profile from the client in such case. So, follow the steps below:
1. Stop OpManager
2. Open the file /conf/alert.filters
3. Remove the <FILTER>...</FILTER> element containing the profile configuration.
4. Restart OpManager.
Modem-based SMS notifications are not working. The message 'Check the modem settings' alone is seen.
There are quite a few things that you need to take note of when configuring modem-based sms alerts. Here it goes:
Prequisites to configure SMS alerts:
• Need to have the supported mobile and modem, Sim Card, Serial Cable, and USB Driver.
• Works only on Windows OS
Required USB Driver:
The modem and the mobile vendors provide the required modem/mobile drivers. For instance, you can get the driver for Nokia from the following link:
http://www.nokia.com/A4144937
Required Cables :
This depends on your mobile phone model. For Nokia 62xx/63xx, you need DLR-3P cable. Newer Nokia models use DKU-9 USB cable. In such case you need to download the driver from Nokia's website, which creates a virtual communication port. Other brands have their own cables, usually USB ones. GSM Modems have a serial port and so you will need a standard serial cable.
Identifying the port at which the modem/mobile is connected:
1. Go to My Computer->Control Panel->System->Hardware->Device Manager- >ports.
2. Here you will find the port to which the Modem\Mobile is connected.
3. If it is not available, then
4. Go to My Computer->Control Panel->System->Hardware->Device Manager->Modems.
After the system system detects the port to which the Modem\Mobile is connected, connect it to OpManager as follows:
1. Start OpManager.
2. Go to Admin->SMS Server Settings.
3. Type the port number to which the modem/mobile is connected in the SMS Server Settings page.
4. If the Mobile\Modem is connected to the specified port, the Mobile\Modem details are shown.
5. Configure an SMS alert from Admin->Notification Profiles->SMS Alert->Modem based SMS and associate to the devices.
OpManager is ready to send the SMS notifications whenever an alarm is generated.
System detects the port to which the modem/mobile is connected but OpManager fails to detect it:
• Ensure that the mobile or modem is supported in OpManager.
• Ensure that the correct port number is correct and is of the format - COM5 or com5.
• Also check for the validity of the SIM.
Reporting
• Top N Reports shows No Data Available
• All Servers Disk Usage Report shows No Data Available
• Top N Volumes having Low/More Disk Space report shows No Data Available
• Junk Characters in Interface Reports
• NA in All Servers Disk Usage Report
• Applications Reports show No Data Available
Top N Reports shows No Data Available
To view the CPU utilization, Memory Utilization, Disk Utilization, Interface Traffic, Interface Utilization and Interface Errors reports, you need to have SNMP installed in the managed devices. Reports list only the SNMP-enabled devices. For non-SNMP servers, data can be collected using CLI (for Unix-based servers), and WMI (for Windows devices).
OpManager requires a minimum of 1 hour to plot the collected data. Try accessing the reports after 1 hour from server startup.
All Servers Disk Usage Report shows No Data Available
To view the All Server Disk Usage report, you must assign the Free Disk Space and Used Disk Space monitors to the managed devices. Assign both the Used Disk Space and Free Disk Space monitors to the devices and wait for two polling intervals and then view the report again.
Top N Volumes having Low/More Disk Space report shows No Data Available
To view the partition-wise reports, you must assign the Free Disk Space and Used Disk Space graphs to the managed devices. Refer to Assigning a Graph Profile to a Device for details.
Assign both the Used Disk Space and Free Disk Space graphs to the devices, wait for two polling intervals and then view the report again.
Junk characters in Interface Reports
In Chinese or Japanese version of OpManager, if the SNMP agents sends data as Unicode characters, OpManager might not be able to translate it properly and hence display the values as junk.
To display this properly, you need to specify the encode type of your agent in the Device Settings dialog. In the device snapshot page, select Device Properties link under Configure tab. Enter the encode type in the Encoding Box and click Save.
"NA" in All Servers Disk Usage Report
You will see NA in All Servers Disk Usage report if you have not assigned both the Used Disk Space and Free Disk Space graph profiles to the managed devices.
Assign both the Used Disk Space and Free Disk Space graphs to the devices, wait for two polling intervals and then view the report again.
Service Reports show No Data Available
The TCP Services reports such as HTTP Servers by Response Time, SMTP Servers by Response Time, and others can produce results only if the service is running in at least one of the managed devices. Otherwise, the report shows No Data Available.
Knowledgebase
For further tips to troubleshoot or find resolutions, dig into our online knowledgebase or write to us at our Support Portal.
XenServer XenServer TCP 443 Intra-host communication between
members of a Resource Pool using
XenAPI
XenServer NTP TCP/UDP 123 Time Synchronization
XenServer DNS TCP/UDP 53 DNS Server
XenServer Domain Controller TCP/UDP 389 LDAP
XenServer Domain Controller TCP/UDP 636 LDAP Over SSL
XenServer File Server TCP/UDP 139 ISO Store: NetBIOS Session Service
XenServer File Server TCP/UDP 445 ISO Store: Microsoft-DS
XenServer iSCSI TCP 3260 iSCSI Storage
XenServer NAS TCP 2049 NFS Storage
XenCenter XenServer TCP 22 SSH
XenCenter XenServer TCP 443 Management using Xen-API
XenCenter Virtual Machine(Linux) TCP 5900 VNC for Linux
XenCenter Virtual Machine(Windows) TCP 3389 RDP for Windows VM
Citrix IMA Service Issue
Issue: Citrix IMA service failed to start and giving the following error messages.
“Failed to load plugin C:\Program Files\Citrix\System32\Citrix\IMA\Subsystems\RADESessionSs.dll with error IMA_RESULT_FAILURE.”
Event Logs:
We’ll find the below system event log on the same server.
If tried to recreate RAID, we’ll not get any o/p after execution of the command as shown in below.
Solution:
Open the RadeOffline.dsn file with Notepad, or any other text editor, where it is located at C:\Program Files (x86)\Citrix\Independent Management Architecture\
If file shown like above, Copy the working file from any other server in the farm and it should contain the information like shown in below.
Filename: RadeOffline.dsn
Path : C:\Program Files (x86)\Citrix\Independent Management Architecture\
Recreate the raid on the server as shown in below.
Restart the IMA service.
Please find the same solution from Citrix in the article CTX129194
Disclaimer : Please follow the steps only if you are facing the issue mentioned in above.
-===================================
Creating a Virtual Network Connection
1. Start the Hyper-V Manager by clicking Start > Administrative Tools > Hyper-V Manager.
2. Open the Virtual Network Manager by clicking Virtual Network Manager in the right-hand window under Actions.
3. Select the Type of Network you want to create.
• External This option creates a connection from the physical adapter and the virtual machine. It allows a virtual machine to access the network through the network adapter.
• Internal This option allows communications between the virtualization servers and the virtual machines.
• Private This option provides communications only among the virtual machines and allows the virtual machines to talk to each other only.
Select External and click Create Virtual Switch
4. Give appropriate Name to the Switch and select the appropriate External NIC to bind with the same.
5. A warning box may appear stating that you are going to temporary lose your network connection while the virtual adapter is being configured. Click Yes.
6. Close the Hyper-V Manager.
7.
8. How to create a Citrix XenApp 6.5 vDisk
9. Step 1 – Create the vDisk within Provisioning Services
10. Open the Provisioning Services Console and go to Sites > “sitename” > vDisk Pool
11.
12. Right click vDisk Pool and click Create vDisk. Select the Store where the vDisk will reside, select a specific server for the vDisk (later you can change this to load balancing) and enter a Filename for the vDisk (anything you like).
13. Set the size for the vDisk. Normally I have enough of 30 to 50 gb, depending on the installed applications on the server. Set VHD type to Dynamic which means that only the space that is really needed will be used for storing the vDisk. With older versions of Provisioning Services, Dynamic vDisks could give performance problems, this is no longer the case with Provisioning Services version 6.1.
14. Click on Create vDisk. Check if the vDisk is in Private mode.
15. Step 3 – Create Target Device within PVS for the “Master Server”
16. Within the Provisioning Services Console, under Device Collections, create a Device Collection with the name Masters (or anything you like). This is not a required step but is recommended because it is easier to manage later.
17.
18. Right click the “Masters” Device Collection and click on Create Device.
19.
20. On the General tab, enter the name of the Master server. Select to Boot from Hard Desk and fill in the MAC address of the primary NIC of the Master Server (the NIC the Master server boots from).
21.
22. On the vDisk tab, Add the vDisk created in step 2 and click OK.
23. Step 4 – Running the Provisioning Services Imaging Wizard on the Master Server
24. Installing the Citrix Provisioning Services Target Device (as described here) and start the Provisioning Services Imaging Wizard.
25.
26. Click Next
27.
28. Enter the server name of the Provisioning Services server where you stored the vDisk and clickNext
29.
30. Select Use existing vDisk and select the vDisk created in step 2
31. (When receiving the error “There are no vDisks available that are in Private mode and not locked accessible by the Server specified” make sure there is no Lock on the vDisk, you can remove the Lock in the PVS console by right click the vDisk and click on the option “Manage Locks”)
32.
33. Click Next
34.
35. The errors in this dialog means that the target vDisk is smaller than the local hard disk in the Master Server. If you get this errors you have to click on Autofit.
36.
37. Click Next
38.
39. Click Next
40.
41. Click on Optimize for Provisioning Services
42.
43. What to optimize depends on your environment, for example in most cases the Windows Autoupdate services can be disabled (also recommended sins the vDisk is read-only). But if System Center 2012 Endpoint Protection is used in the environment, the Windows Autoupdate services is needed for the anti-virus updates. Apply what is applicable for your environment and click OK.
44.
45. Click Finish
46.
47. Click Yes to reboot the server.
48.
49. After the reboot, logon with the same user account. Citrix XenConvert will automatically start to convert the files from the local hard drive to the vDisk.
50.
51. Click on Finish
52. Step 5 – Configure the Master Server to boot from vDisk
53. Within the Provisioning Services Console open the properties of the Master Server.
54.
55. On the General tab and change “Boot from” to vDisk. Click OK
How to create a Virtual Machine in Hyper-V
• Open the Hyper-V Manager interface.
• In the right side click Newà Virtual Machine.
• Type a name and location for the template, then press Next.
• Select the Size of Memory for the Virtual Machine. Then press Next.
• Select the Virtual Network that you will like to use. The press Next.
• Select a location for the Virtual Hard disk.
• Right click the VM and select Settings.
• Type the location of the ISO file to install Windows Server 2012.
• Right Click the Virtual Machine and select Start.
Installing Hyper-V on a Server with a GUI Installation
1. On the server desktop, open Server Manager
2. In Server Manager, in the menu, click Manage, and then click Add Roles and Features
3. In the Add Roles and Features Wizard, on the Before You Begin page, select next.
4. On the Select Installation Type page, select Role-based or feature-based installation, and click Next.
5. On the Select Destination Server page, select the server, and click Next.
6. On the Select Server Roles page, select Hyper-V, and then click Add Features in the dialog box.
7. On the Select Server Roles page, click Next.
8. On the Select Features page, click Next.
9. On the Hyper-V Page, click Next.
10. On the Create Virtual Switches page, select a network adapter, and then click Next.
11. On the Virtual Machine Migration page, click Next.
12. On the Default Stores page, click Next.
13. On the Confirmation page, check Restart the destination server automatically if required, and then click Yes in the restart dialog box.
14. On the Confirmation page, click Install.
15. On the Installation Progress page, you can monitor the Hyper-V role installation until the server automatically restarts.
16. After the server restarts and opens the Server Manager, check the Installation Progress page to ensure that the Hyper-V role installation was successful, and then click Close.
Installing or Upgrading Xen Tools in Windows
1) Select the VM in the Resources pane, right-click, and then click Install XenServer Tools on the shortcut menu. Alternatively, on the VM menu, click Install XenServer Tools.
2) Click Install XenServer Tools on the message dialog to go to the VM's console and begin the installation.
3) If Autoplay is enabled for the VM's CD drive, installation will be started automatically after a few moments. If Autoplay is not enabled, double-click on the CD drive to begin installing XenServer Tools.
4) Follow the on-screen instructions, and reboot the VM when prompted. If you do not have dotNet 3.5 or 4 installed you will be prompted to install it before the Xen Tools installer will run.
You can install dotNet directly from the Xen tools CD by right clicking and choosing Explore.
Once you are in the CD folder double click the file that starts with 'dotNetFx'. This will take a few minutes to complete the install. Once that has completed you can start the Xen Tools install from the within the same directory by double clicking the file named 'install wizard'.
After the installation has completed you will be prompted to reboot to complete the install. The VM may actually reboot a few times but each time it will continue the install from where it left off. One thing to note is that in Windows 2008 the installation of Xen Tools may cause an issue with the public IP assigned to the VM due to Auto-configuration and DHCP.
To correct this you will need to either RDP to the private IP of the VM (if you have one assigned) or use the console. If after the install of Xen Tools completes you find that the public IP no longer responds you will need to open a command prompt on the VM and run the command `ipconfig` If you see that the Public adapter has been assigned a 169.254.x.x IP take note of the Adapter name. In my case it was Local Area Connection #4.
From the command prompt you will then run the following command `netsh interface ipv4 show inter` and find the ID number assigned to the 169.254.x.x IP. In my case the IP number is 16.
You can then remove that routing with this command "netsh interface ipv4 set interface XX dadtransmits=0 store=persistent". You will need to use the ID number instead of XX. Once you get the Ok from the command prompt go to Start >> Run >> services.mmc and disable DHCP. You will then need to reboot the VM and you are ready to go
PROVISIONING SERVER MAINTENANCE ACTIVITY PROCESS
1. Login to the Provisioning console and click on the Device collection
2. you can see all the servers which is a part of the device collection
3. You can see there are two servers in the below screen shots FCXNXA206 and FCXNXA207 . Here you can see there are two server so might be for other clients we have more servers in the same group.
4. Select any one server where we have no users logged on, if possible use the server which we have added earlier to this published application for Maintenance purpose.
5. Here in the below screen shot we have the server as FCXNXA206 and we need to shut down the server whereas before that make sure nobody logged in to that server.
6. Right click on that server and go to Target Device>Shut Down which will shut down the server
7. post shutting down click on the Vdisk tab and check the server is booting up from which Vdisk
8.As we got to know the exact name of the Vdisk now go to the PVS console and click pn stores and you can see all the Vdisk in the right hand box as per the below scree shot
9.now click on the Vdisk from where the maintenance server is getting booted up click on Version and you can see how many Vdisk version we have
10. The Vdisk which is in green is the one from where the server is getting booted up and which is the working version.
11. We need to click on the New tab and it will create a maintenance Vdisk
12. now we need to click on the device and click on the properties of the device.
13. Now click on the Type and click on "Maintenance” and make sure it is set to boot from maintenance Vdisk which we have created in point number-11
14. Once you will boot up the server you can see the there are two options available for us so we need to boot in "1" so that we can boot into the maintenance mode and do all the changes which you would like to do and then reboot the server
15. Once the server rebooted then shut the maintenance server and then click on the version of the Vdisk.
16. and select the maintenace vdisk version a and click on Promote so that this Vdisk can be the base Vdisk.
17. While selecting select Immediate so that it can take effect.
18. Once it is done we need to set the taret device properties again to production and then we need to just reboot all the other servers in the same device collection where we want to apply the changes.
PVS STAGING
1`
Download Vmware…
https://my.vmware.com/web/vmware/details?downloadGroup=VIEWCLIENTS_WIN64_352&productId=421&rPId=9427
Run -stup
Than next clik
Next
Next
next
Next
Next
Install
Wait running satup
Next and finish
Restart the system
Installation is Done..
WYSE Printing Configuration
There are 3 Scenarios where we need to map the Printer on WYSE TC / device.
USB Printing [Connected through USB]
Network / LPD Printing [Network printer]
Shared Printing [Printer which shared through any local system]
BELOW SOPs for USB Printer Configuration & Network Printer Configuration
.
Printing / Mapping to a Local USB/Parallel Printer
The WYSE Thin OS can print to locally attached printers via USB or Parallel. Some models of Wyse Thin Clients have built in parallel ports while others do not, the ones that do not can use a USB to parallel adapter if needed and will follow the same directions.
Turn ON your WYSE TC
Click on “DESKTOP” icon
Go to “System Setup” > Click on “Printer”
“Printer Setup” window will appear > Select “Ports” tab for USB Printer installation.
“Select Port” field defines as a “LPT (USB)”
“Printer Name” field defines as the name of local the printer as the Thin Client would see it. (For example if the Printer model is ‘HP LaserJet M1530 MFP’ then your “Printer name” should be ‘HP LaserJet M1530’)
“Printer Identification” field defines is the exact text of the Windows printer driver name. (For example if a printer’s driver is called ‘HP Universal Printing PCL 6’ in Server, then it must be exactly the same in the Printer Identification field on the Thin Client)
“Printer Class” field can be Blank.
“Enable the Printer device” so it shows up on the remote host.
DO NOT “Enable LPD Service”. (Enable LPD Service only when the printer turns the thin client in to a network Print server)
Click “OK” and check with “Test Print” option.
Restart WYSE TC and login to your Citrix Session. Your USB printer will redirect through this.
Please find below snaps for your ref:
(Below image is NEW DELL WYSE TC)
To find the Windows printer driver name
Click on Printers and Faxes from the start menu
Right clicking in the background of the new window and selecting ‘Server Properties’
Click on the ‘Drivers’ tab
Printing / Mapping to a Network printer
Wyse ThinOS can print to non-Windows network printers as long as the Printers can accept LPR print requests. Most HP workgroup printers and large network printers have this capability. Please check with your printer’s vendor to find out if your printer has the ability to accept LPR print requests.
Once your Wyse Thin Client is configured to print to an LPR capable printer, the client will then redirect this printer through a RDP or ICA connection to your back end infrastructure. In this way the client will connect to your back end infrastructure and this network printer will appear as the client’s local printer.
Turn ON your WYSE TC
Click on “DESKTOP” icon
Go to “System Setup” > Click on “Printer”
“Printer Setup” window will appear > Select “LPDs” tab for Network / LPD Printer installation.
“Select LPD” one by one. If in your location there were 3 Network Printers then you can add / configure them as following: 1st Printer as LPD1, 2nd Printer as LPD2 & 3rd Printer as LPD3.
“Printer Name” field defines as the name of local the printer as the Thin Client would see it. (For example if the Printer model is ‘HP LaserJet M1530 MFP’ then your “Printer name” should be ‘HP LaserJet M1530’)
“Printer Identification” field defines is the exact text of the Windows printer driver name. (For example if a printer’s driver is called ‘HP Universal Printing PCL 6’ in Server, then it must be exactly the same in the Printer Identification field on the Thin Client)
“LPD Hosts” field defines is the IP address of the printer on the network. (For example your Network Printer IP is 10.1.253.10 then you need to put this IP address on the LPD Hosts field)
“LPD Oueue Name” field defines as “auto” (The mentioned field can be different for each vendor. This is field is required and must be correct so that the network printer accepts incoming print jobs correctly. In the example above we have used auto per documentation found on HP’s website.)
“Printer Class” field can be blank.
“Enable the Printer device” so it shows up on the remote host.
Click “OK” and check with “Test Print” option.
Restart WYSE TC and login to your Citrix Session. Your Network / LPD printer will redirect through this.
Please find below snaps for your ref:
1.Type below Url in google Chrome.
Https://Yblpvdakxdc01.yesbank.com/director
2.Login with Your domain credentials.
3.Type user name/ID in search box.
4.Click on shadow to take remote control of the user.
5.Click on the Invitation and open it.
6.Tel user to accept the shadow session.
7.Click request control to get control of User’s session.
Citrix Studio
STEP 1) Log in to Anunta TS : 192.168.244.22 with your own credentials.
STEP 2) Log in to SREI TS : 192.168.30.37 with the following credentials.
User name : hsdadmin
Password : xxxxxxxxx
STEP 3) Open citrix studio from the desktop.
STEP 4) Go to licensing tab
STEP 5) Take a snap shot of the licensing window as follows.
STEP 6) Go to delivery group & double click on first delivery group i.e. SREI_XD_KSO as follows.
STEP 7) Go to delivery group & double click on second delivery group i.e. SREI_XD_MSO as follows.
STEP 8) Go to delivery group & double click on third delivery group i.e. SREI_XD_MSO_AMBIT as follows.
STEP 9) Go to delivery group & double click on fourth delivery group i.e. SREI_XD_OO as follows.
STEP 10) Take the user count from each & every delivery group, fill in the following chart.
Delivery Group Status HSD session connected? No of VMs Active users
SREI_XD_KSO Enabled Yes 3 0
SREI_XD_MSO Enabled Yes 7 0
SREI_XD_OO Enabled Yes 4 0
SREI_XD_MSO_AMBIT Enabled Yes 1 0
STEP 11) Please launch the applications through citrix reviver with test ID or following credentials.
User name : hsdadmin1
Password : xxxxxxxxxx
Note : Make sure all the applications are getting launched properly.
Step 1: Install XenServer
The current version of XenServer is available from Citrix. You will want the Product Installer ISO, which will be used to install both XenServer and its central management console, XenCenter. Additionally, if you are going to use virtual machines to run Linux, you will need the Linux Guest Support ISO. These will need to be burned to CD for installation on a bare-metal system.
Cloud review: 8 public cloud services put to the test
From Amazon to Windows Azure, IaaS clouds differ widely in features, complexity, and speed
Read Now
Installation is very straightforward, following the instructions from the guided setup. Below is a brief excerpt of the installation process. Booting from the CD, you will be met with a Citrix screen. Pressing Enter or waiting on the timeout will proceed to the installation. An abbreviated version of the questions presented is listed in the table below, along with some generic responses.
Select Keymap [qwerty] us
Welcome to XenServer Setup < OK >
EULA < Accept EULA >
Select Installation Source Local Media
Supplemental Packs Yes -- Choose Yes if you intend to run Linux VMs in my environment. If your environment is going to be purely Windows, there is no need for Supplemental Packs.
Verify Installation Source Skip verification -- If you are not confident in the downloaded iso, you can verify, but I have used these disks repeatedly and they are known to be good copies.
Set Password < choose your password >
Networking eth0 (< MAC >) -- This choice can vary depending on your system and the number of NICs you have. It is best practice to plug in the NIC you intend to use for administration, and unplug all others. The unused NIC(s) will indicate "[no link]"
Networking (cont.) Static Configuration:
IP Address: < varies >
Subnet Mask: < varies >
Gateway: < not needed >
Hostname and DNS Configuration Hostname: < what you want >
DNS: < must have at least a dummy IP >
Select Time Zone America
Select Time Zone (cont.) Los Angeles
System Time Manual time entry
Confirm Installation Install XenServer
After the basic installation you will be prompted to install supplemental packs. We installed the Linux Guest Support pack and hit <OK>. A prompt asks if you want to verify the disk, use it, or go back. Choose <Use>. It is possible to install more than one supplemental pack, so you will be prompted again. There are no other supplements that we intend to use, so <Skip>. When finished, you will be prompted to reboot: <OK>.
Naturally, this installation procedure will be repeated on as many physical hosts as you want in your environment. For our purposes, we used three physical servers that we called xennode01, xennode02, and xennode03.
Step 2: Install XenCenter
After reboot, you will see a status display. The most important piece of information here is the IP address that you assigned to XenServer during the installation. From another machine on your network, you'll need to open a browser and navigate to that IP in order to download the installer for XenCenter. XenCenter is the Windows-based central management console for all of your XenServer hosts. The installer is in an MSI format, meaning you will need to be using some version of Windows to execute it.
Optional: As an alternative to the above method, you can simply use the same CD used to install XenServer. It contains the XenCenter MSI as well. We prefer the previous method, as it gives some idea that XenServer was installed properly, and we don't have to shuffle CDs.
Page 3 of 5
Installation of XenCenter is very straightforward, following a wizard. Once this is done, launch XenCenter. From this point forward, 99 percent of your administration of XenServer will be handled from XenCenter. XenCenter allows you to create, delete, start, stop, and administer virtual machines.
Cloud review: 8 public cloud services put to the test
From Amazon to Windows Azure, IaaS clouds differ widely in features, complexity, and speed
Read Now
Step 3: Add servers using XenCenter
To administer each of the XenServer servers through XenCenter, you can simply "add a server." There are multiple shortcuts to this function, but for the sake of simplicity, using the top toolbar, select Server -> Add.
You will be prompted for the server IP and user/password credentials. Unless you changed something from the directions above, the user name will be root and the password will be as set during installation.
ADVERTISING
You may be prompted to verify the SSL certificate. <Accept>
Step 4: Create a XenServer pool
A pool in XenCenter is a collection of servers that you can manage as a group. If your physical servers are all of the same type, creating this pool will simplify administration. If you are intending to use XenServer's high-availability functions, a pool is required. By creating a pool and storing all of your virtual machines on an external share, to the virtual machines are freed from ties to any specific physical host. In the event of a physical host failure, the VMs on that host can be restarted immediately on another host in the pool.
The process for creating a pool is as follows: From the toolbar, select Pool -> New. You will be prompted to provide a name for the pool and an optional description. On the next screen, you will be asked to select a "master" server. This master server should be one that you have already connected to as a single server. Below the master server selection, you can add other members to the pool by selecting the check box next to the list.
To support high availability, your pool will need an external storage repository. You can create a pool without external storage, but doing so would be useful only for administrative purposes. If your VM's storage is hosted on the physical machine, and the physical machine goes down, there is no easy way of recovering that VM. Setting up your external storage will likely be the trickiest part of the installation. We cannot offer any help here, as this will depend on what equipment you are using. XenServer supports NFS, iSCSI, HBA, StorageLink, and CIFS.
We used an iSCSI target that could be easily referenced by each of the nodes created earlier. One could argue that the external iSCSI drive could fail, and you still have a single point of failure. In our case, our external iSCSI target is a RAID-6 with two controllers, so multiple failures would have to occur to lose the flat files that constitute the VM's virtual hard disk.
Step 5: Install virtual machines
With a pool set up with external storage, you can create virtual machines that are not tied to any physical server. During the installation, choose the option to create the virtual hard drive on the external store, as well as the option "Don't assign this VM a home server..." It should be noted that these VMs are still assigned a server, to use for processing and memory allocation, but the virtual hard disks are stored elsewhere. We chose to create both a Linux VM and a Windows VM, and our pool looked something like this:
Cloud review: 8 public cloud services put to the test
From Amazon to Windows Azure, IaaS clouds differ widely in features, complexity, and speed
Read Now
myXENpool
- xennode03
ADVERTISING
- xennode01
- Fedora Test
- Windows XP Test
- xennode02
- CIFS ISO library
- iSCSI Target
As you can see, the VMs had been assigned to xennode01. Before moving on, we verified that both machines had good network connectivity by simply pinging the network Interfaces on each.
Step 6: The true test (graceful)
Now that we had two VMs running, we could run some high-availability tests. With a ping test running against both machines, we wanted to see what happened if we stopped xennode01 (the hosting server). To do this gracefully, we would put that server into Maintenance Mode. Right-clicking xennode01 and selecting Maintenance Mode gives us a prompt about migrating the VMs -- namely, a live migration requires the installation of XenServer Tools on the VMs. Doing so on either Linux or Windows prompts a reboot (which does interrupt the ping test).
After the installation and reboot, verify that XenServer Tools has installed. You can easily see this on the General tab of the instance in question. Under "Virtualization state," you will see either "Tools not installed" or "Optimized (version 5.6 installed)." Verification is important, as the XenServer Tools did not install properly on my Linux machine the first time.
With the XenServer Tools were properly installed in our Linux and Windows VMs, right-clicking xennode01 and selecting Maintenance Mode results in a smooth migration. During the migration, ping times rise from less than 1ms to about 30ms, and the VMs land successfully on xennode03, after which the pings return to less than 1ms.
Step 7: The true test (clumsy)
So that was cool, but if there is going to be a hardware failure, it is doubtful that we will be able to switch gracefully to Maintenance Mode. Ensuring both the Linux and Windows VMs are running on xennode03 (which happens to be our master controller), we physically remove power (pull the plug) on xennode03.
Result? No surprise, the pings fail and we lose access in XenCenter. Trying to reconnect to the pool doesn't work because XenCenter accesses the pool and all nodes through the main controller. So how do we get control back? From one of the other physical servers, I use the local XenServer interface to navigate to Resource Pool Configuration. After a long wait, it would appear that we are getting nowhere here. Using SSH to access xennode01, we type:
xe pool-emergency-transition-to-master This command forces xennode01 (which we are currently SSH'ed to) to become the master controller.
xe pool-recover-slaves This command causes the master controller to find the other nodes that are part of the pool, and inform them of the master controller change.
Were back! Well, not quite. We can now see the pool, by using a different IP, but the VMs are not back online. Still using SSH:
xe host-list params=uuid,name-label,host-metrics-live This returns a list of the pool members.
Page 5 of 5
We get in return:
Cloud review: 8 public cloud services put to the test
From Amazon to Windows Azure, IaaS clouds differ widely in features, complexity, and speed
Read Now
uuid ( RO) : 5ff9245d-726d-41ee-872b-1480ab4e2a56
name-label ( RW): xennode01
host-metrics-live ( RO): true
uuid ( RO) : a1716dba-7a75-4e99-94f6-27c00b8b122d
name-label ( RW): xennode03
host-metrics-live ( RO): false
uuid ( RO) : 79285776-847d-4ce0-acd3-86934a026634
name-label ( RW): xennode02
host-metrics-live ( RO): true
So now we have the uuid for the host that is down (note the live=false): It's uuid a1716dba-7a75-4e99-94f6-27c00b8b122d. Now we enter:
xe vm-list is-control-domain=false resident-on=a1716dba-7a75-4e99-94f6-27c00b8b122d This command lists the VMs the cluster thinks are running on the downed node. (The is-control-domain=false parameter removes dom0 from the list.)
We get:
ADVERTISING
uuid ( RO) : 5d21d7e2-5cb3-5e20-4307-b69d7eea8d94
name-label ( RW): Windows XP Test
power-state ( RO): running
uuid ( RO) : 2fbb543e-aac0-4488-8e57-099d2f71f01e
name-label ( RW): Fedora13_32
power-state ( RO): running
Both VMs need to be recognized as turned off, so we enter:
xe vm-reset-powerstate resident-on=a1716dba-7a75-4e99-94f6-27c00b8b122d --force --multiple This command forces the nodes in the pool to recognize the VMs associated with this uuid to be off. (The multiple is only necessary if you need to turn off multiple VMs. Be careful, because incorrect usage can force all VMs in the cluster to be powered off.)
Returning to XenCenter, the console now shows that both the Windows VM and the Linux VM are off. Starting them moves the VMs to a different server (xennode01), and we are back in business.
Final notes
It is not difficult to create a highly available virtual server cluster using XenServer. Given the right approach, the availability can be carried even further. Within the XenServer functionality are methods to bond network cards, so the failure of any given NIC does not bring down a system. Using a different switch for each network card removes the switches from the possible failure list. Failure of the external storage can be overcome with the right RAID environment. And all this is possible with free software!
XenServer is built on a Linux kernel. A few people have suggested that we could script the recovery and even add a cron job to check for downed nodes and execution of the recovery script. This seems very plausible. One would just have to be sure that multiple copies of the script weren't getting executed from the different nodes, and that a node that went down and stayed down didn't prompt recurring script executions. If this were done properly, you would get automatic recovery of downed VMs!
As a starting point we offer the following. (Please note: We have not extensively tested this script.)
#!/bin/bash
downedhost=` xe host-list params=uuid,name-label,host-metrics-live | \
sed -e :a -e '$!N;s/\n/|/g;ta;s/|||/\n/g' | \
grep false | \
awk -F"[:,|]" '{ print $2 }'`
if [ -z "$downedhost" ]; then
echo "Hosts all good."
else
echo "$downedhost is down! Promoting myself to master."
xe pool-emergency-transition-to-master
xe pool-recover-slaves
xe vm-reset-powerstate resident-on=$downedhost --force --multiple
fi
Citrix NetScaler Gateway 10.1.118.7 – Quick Configuration Wizard
Introduction
Quick Configuration Wizard facilitates NetScaler Gateway setup for XenMobile and XenApp / XenDesktop type of deployments which enables communication with App Controller, StoreFront, or Web Interface in a secure way. Simplification of NetScaler Gateway configuration is achieved by creating various policies like Authentication, Session and Clientless Access etc. in background and binding them to a virtual server.
NetScaler Gateway Configuration
Pre-requisites:
1. NetScaler Gateway Platform License
2. Proper SSL Certificate and SSL Key
Steps to Configure through Wizard:
Step 1
When you access NetScaler management console using NSIP (NetScaler IP Address) in a browser, select ‘NetScaler Gateway’ option in ‘Deployment Type’ and login to get NetScaler Gateway persona represented by ‘Home’ tab.
Step 2
When you are accessing for the first time, an interface to add Subnet IP Address, Hostname, and DNS IPs etc. is presented. Add appropriate values and click on ‘Continue’ button.
Step 3
Upload required license file(s) and reboot as suggested.
Note – Above settings can be modified later as well by clicking on the gear icon at the top right corner.
Step 4
When NetScaler reboots and you login again by choosing ‘NetScaler Gateway’ option, an interface to configure NetScaler Gateway virtual server is presented. Click on ‘Get Started’ button.
Note – When you experience this wizard, it is advisable to go through each section and complete the wizard by clicking on ‘Done’ button at the end.
Step 5
Define NetScaler Gateway virtual server name, IP Address (VIP) and Port. Also, you can enable NetScaler Gateway to redirect HTTP connection to HTTPS secure connection. Click ‘Continue’ to get next section.
Note – You cannot configure more than one virtual server with the same IP Address (VIP) but different Ports through this wizard.
Step 6
In ‘Certificate’ section, select either
1. Already installed certificate-key pair by selecting ‘Choose Certificate’ radio option OR
2. Install a certificate-key pair by selecting ‘Install Certificate’ radio option and choosing right SSL Certificate and SSL Key OR
3. Use a self-signed test certificate from NetScaler by selecting ‘Use Test Certificate’ radio option.
Note – While using ‘Use Test Certificate’, make sure that you have not used the same FQDN earlier while configuring another virtual server. If you are deleting an existing virtual server and creating a new and want to use the same FQDN in ‘Use Test Certificate’ as used earlier then make sure you manually delete the related cert/key files in /nsconfig/ssl directory before coming to this wizard or select the already created certificate-key pair under the ‘Choose Certificate’.
Press ‘Continue’ to proceed with the wizard.
Step 7
Now, you get a section to configure authentication settings. It allows configuring primary and secondary authentication or configuring only primary authentication.
In Primary Authentication, select LDAP, RADIUS or Certificate. Depending on the primary selection, you get options in secondary authentication.
You can either choose already created authentication policy or configure a new policy.
While configuring LDAP authentication policy, it is recommended to use sAMAccountName Server Logon Name Attribute for XenApp / Xendesktop deployment and userPrincipalName Server Logon Name Attribute for XenMobile deployment but ideally both works for both deployments.
Note – You cannot create multiple LDAP authentication policies by using the same LDAP server IP address in this wizard as the LDAP auto-generated LDAP policy name and action name conflicts. For example, if you want to configure one policy that uses sAMAccountName in the Server Logon Name Attribute field and a second LDAP policy that uses the userPrincipalName (UPN) in the Server Logon Name Attribute field then it is not possible through this wizard but can be achieved by creating a LDAP policy through legacy policy manager. For this, click on ‘Configuration’ tab’ on top and navigate to NetScaler > NetScaler Gateway > Policies > Authentication/Authorization > Authentication > LDAP node. Make sure you don’t do this when in the middle of the wizard; otherwise you may lose the configuration.
Once you are done on configuring authentication settings, click on ‘Continue’ button.
Step 8
Now, you get a section to define your deployment type and settings related to that deployment type.
• XenMobile – This allows configuring your App Controller which offers access to web, SaaS, mobile applications, Windows applications & desktops and ShareFile. Please provide App Controller FQDN.
• XenApp / XenDesktop– This allows configuring Web Interface or StoreFront deployment.
In Web Interface deployment, enter the complete address of XenApp Site e.g. http://Xenapp1.systest.agee/Citrix/XenApp and XenApp Service Services Site e.g. http://Xenapp1.systest.agee/Citrix/PNAgent/Config.xml. Enter the Single Sign-on Domain and STA (Secure Ticket Authority) URL either using IP address or FQDN.
In StoreFront deployment, enter the StoreFront FQDN, Receiver for Web Path, Single Sign-on Domain and STA (Secure Ticket Authority) URL either using IP address or FQDN.
Click on ‘Done‘ button to complete the wizard successfully.
Step 9
After clicking on ‘Done‘ button, NetScaler Gateway monitoring interface is displayed.
Now, if you want to modify certain settings in already configured virtual server then hover on it and you will get an Edit icon. When you edit virtual server settings, make sure to go till end of the wizard and click on ‘Done‘ button to edit successfully.
You can delete the virtual server using the Delete icon.
You can create a new NetScaler Gateway virtual server also from here by clicking on ‘+‘ icon
Step 10
Make sure to properly configure the NetScaler Gateway call-back settings in your backend deployment like App Controller, Web Interface or StoreFront.
Comments
Post a Comment