Want to know how to find out how long it takes your citrix profile management profile has taken to be copied down on logon ? here’s how to check
First RDP to the server you logged onto with you administrative level privileges, if in an enterprise environment most likely will be a separate ID to your “every day” citrix user id
Navigate to the following folder (unless directly specified elsewhere via GPO will be the default location):
Launch the latest .log file
Do the search for the below search term
Will show in the above how long it took to copy down – as per example above was less than a second J
Was trying to find a good piece on this covering the scenarios it was useful and ones in which it wouldn’t be of assistance. Kudo’s to Andrzej for an excellent explanation
Recently needed to find this out in a quick and easy way
didn’t need to look any further than the scout tool to help me:
Got the pleasure of a 4am call last week from our support team to say issues being experienced launching an array of published applications in our xenapp 6.5 environment (usual generic “an error occurred making the requested connection” error).
As the vast majority of servers are using PVS 6.1 vDisks assumed PVS was at play here.
So RDP’ed to one of the PVS servers in question(v.slow to get in as was connecting to any of the affected provisioned VM’s) and was greeted with a ton of similar messages to the below in the application event log:
Going to the command prompt and doing a “mvadm status” could see the p01 move server was showing active
Subsequently rdp’ed to the move 01 server above and again was sluggish, key thing for me it was unresponsive coming back with information on a “mvadm status” so took the punt that it was hosed. A restart of the 01 server immediately resolved the issue.
Key takeaway here was the move server was restarted and not the PVS servers which was done in the past. Main issue of course with the PVS servers being rebooted – in our instance we have a 200 target device limit on one node so it would of knocked out a lot of target devices (about 100) which would in turn of created a boot storm subsequent bringing them back up.
Issue with move (currently on version 2.6.2) was it didn’t failover to the secondary node, believe to be hopefully addressed in new release but we’ll see.
Can be tricky this. In the “old” days of PVS 5.x and prior we had no differencing disks (or were available in cases but was a niche feature). From 6.x a lot more commonly used and extremely useful. Thing that can be tricky about is judging size.
Taken from the Citrix virtual handbook (always useful reading) – and working with this stuff day in day out can vouch for its veracity
Differencing disk growth by application size
The following formula can be used as a guide when estimating the
size of the vDisk store:
Consider the following example. You plan to deploy three vDisk
• Windows 8 (x64) image = 40GB
• Windows 7 (x64) image = 40GB
• Windows 7 (x32) image = 35GB
Each vDisk will be limited to five differencing disks. You anticipate
vDisk Change Application Install size Approximate Differencing
Small (Install 1 application –
Firefox) 20 MB 1.1 GB
Medium (Install 2 applications
– Firefox and Adobe Reader) 56 MB 1.6 GB
Large (Install MS Office 2010
Pro x86) 2.2 GB 4 GB
that the differencing disk will be 20% of the master vDisk image.
The estimated size required for the Provisioning Services store will
Was actually one I was commenting on a good while, ironically googled it back – can be useful if you don’t want your w/c to go to d: (oftentimes the default location for a device to HD) for various reasons but instead want something “out of the way”.
Have seen this in the past with using HP’s in particular and using their inbuilt installation wizard when setting up the hosts, can set the performance option but afterwards is greyed out when checking the web / traditional client.
Go to Bios settings section and need to set OS control or OS Control Mode depending on whether your using a Dell / HP