Till xa 6.5, we had direct option to remove services site shortcuts for citrix apps. From xd 7.X, we have to use command line to do the same. So, use a script like this:
if “%PROCESSOR_ARCHITECTURE%"==“AMD64” goto 64BIT
echo 32-bit OS
start "” /wait “C:\Program Files\Citrix\ICA Client\SelfServicePlugin\SelfService.exe” -logoff
goto END
:64BIT
echo 64-bit OS
start "" /wait “C:\Program Files (x86)\Citrix\ICA Client\SelfServicePlugin\SelfService.exe” -logoff
:END
Create a logoff policy via gpo or copy above script bat file to logoff folder in user’s machine.
Scenario:
In your current organization, you have different xendesktop sites, one for prod, one for dev, one for testing or one for win7, one for win10 etc. You have to add all the xendesktop controller servers in your director to populate them in your director website.
Here is how to do it:
login to your director server and open inetmgr Click on your server name, site, default web site, director as shown below: To the right, In ASP.
In XenDesktop we have the facility to enable audit logs on our site so that we can find who is doing what on our citrix site. But unfortunately in studio, under logging option,we can only see limited logs(only till last 6 months). We need to use powershell to see more logs. Use below commands to see logs on 24/Jan/2018 from 11:00 AM till 4:00 PM.
Add-pssnapin citrix*
Get-LogHighLevelOperation -Filter{ StartTime -ge “2018-01-24 11:00:00” -and EndTime -le “2018-01-24 16:00:00”}
Find Master image: We don’t have the option to view the master image used by machine catalog in citrix studio directly. We need to go through powershell to view the master image details. Here is the command:
**Add-PSSnapin citrix* ** - to load citrix commands
Get-ProvScheme - to see the provisioning scheme for all the machine catalogs
Get-ProvScheme -ProvisioningSchemeName “Machine catalog name” - to see provisioning scheme for one particular machine catalog.
User is already part of the group which is published for citrix application. But still when user tries to login, they recieve access denied error.
When you check on citrix application properties, we have a AD group, and user is already part of this AD group. Interesting point is, only one user might have this issue and all existing other users in that group, and any new users added to this AD group will not have any errors.
For any user profile issues, you’d try to delete the user profile folder from Citrix app server. When user tries to login again, it creates a new profile on the server. Every profile has a folder in C:\users folder and a registry key associated with it. When deleting the profile, if you delete the folder with username in C:\users folder, it will not delete the registry key for that user. For this, goto beloow path in My computer properties given here.
Symptoms or Error IMA Service fails to start and MFCOM Service is unresponsive in starting state.
Event ID: 7024 The Independent Management Architecture service terminated with service-specific error: 2147483649 (0x80000001).
- Or –
The IMA service terminated with service-specific error: 2147483647
Solution Complete the following steps to resolve the issue:
Stop the mfcom.exe service using the Task Manager.
Execute the following commands:
Dsmaint recreatelhc
Dsmaint recreaterade
Start the IMA Service and MFCOM Service.
If you want to change license server name in xenapp 6.5, open server role manager, edit licensing option then update your new license server name, click next and apply, and reboot.
We have seen an issue in xenapp 7.6 where some of the vms are shutdown automatically after weekend reboot. After lot of research on the delivery controller, we have identified that Delivery controller is sending the shutdown command to some of the vms(random vms every week) and esx is shutting down the vms. So we have decided to turn off power management completely in our xenapp 7.6 environment.
Here are the steps to set your power management to max for all delivery groups.
While using the imaging wizard, after rebooting the target device, it throws an error saying, Failed to snapshot instead of uploading OS into PVS vdisk.
Solution:
Enable Microsoft Software Shadow Copy Provider and Volume Shadow Copy service services. Set them to automatic.
Problem Cause:
Imaging Wizard and P2PVS require the source virtual machine to have both Volume Shadow Copy and Microsoft Software Shadow Copy Provider services enabled to perform an imaging operation.
