maandag 05 september 2011
When you want to get a quick overview of the RAM write cache usage of your target devices you can use the following PowerShell script.
1. If not done already, allow running unsigned scripts:
Set-ExecutionPolicy RemoteSigned
2. Install the MCLI PowerShell snapin:
$installutil = $env:systemroot + ‘\Microsoft.NET\Framework64\v2.0.50727\installutil.exe’
&$installutil McliPSSnapIn.dll
3. Add the MCLI snapin to your PowerShell environment:
Add-PSSnapin -Name McliPSSnapIn
4. Run the following PowerShell script on your PVS server:
function get-value{
param([string]$strText=”",[string]$strDelimiter=”")
return $strText.SubString($strText.IndexOf($strDelimiter)+2)
}
function get-name{
param([string]$strText=”",[string]$strDelimiter=”")
return $strText.SubString(0,$strText.IndexOf($strDelimiter))
}
Add-PSSnapin McliPS* -ErrorAction SilentlyContinue
$all = @()
$obj = New-Object System.Collections.ArrayList
$lines = Mcli-Get DeviceInfo -f ServerName,`
ServerIpConnection,`
DeviceName,`
SiteName,`
CollectionName,`
Active,`
Status,`
diskLocatorName
for($i=0;$i -lt $lines.length;$i++){
if(($lines[$i].length -gt 0) -and ($lines[$i].contains(“:”)) -and -not ($lines[$i] -match “Executing: Get “)){
$name = get-name -strText $lines[$i] -strDelimiter “:”
$value = get-value -strText $lines[$i] -strDelimiter “:”
if ($name -eq “status” -and $value.Length -le 0){
$value = “0″
}
if ($value.Contains(“,”) -and $name -eq “status”){
$obj | Add-Member -membertype noteproperty -name $name -Value $value.Split(“,”)[1]
}else{
$obj | Add-Member -membertype noteproperty -name $name -Value $value
}
}
if($lines[$i].contains(“#”) -or (($i+1) -eq $lines.length)){
$all += $obj
$obj = New-Object psObject
}
}
$all | Where-Object -FilterScript { ([int] $_.status -gt “0″) -and ([int]$_.status -le “100″) } | Sort-Object {[int] $_.status} -descending | Format-Table @{Expression={$_.deviceName};Label=”Device”}, @{Expression={$_.status};Label=”RAM Cache Used (%)”} -autosize
Thanks to ctxfarmer for providing the base of the script.
vrijdag 31 december 2010
In a pooled XenDesktop 4 environment you normally want to shutdown a virtual desktop after the user logged off so every user gets a clean desktop. This Logoff Behaviour was configurable in the Desktop Group properties via the Access Management Console. In XenDesktop 5 this is not configurable via the GUI anymore so we have to use PowerShell instead:
Set-BrokerDesktopGroup -Name “Desktop Group Name” -ShutdownDesktopsAfterUse $True or $False
The default is set to False so the virtual desktop stays powered on after use.
maandag 02 augustus 2010
I recently passed the Citrix 1Y0-A16 (Architecting a Citrix Virtualization Solution) and 1Y0-A15 (Engineering a Citrix Virtualization Solution) exams. With this I now have the following titles:
Citrix Certified Enterprise Engineer (CCEE) for Virtualization
The Citrix Certified Enterprise Engineer for Virtualization certification is designed to certify breadth of knowledge across Citrix virtualization solutions. The CCEE offers experienced IT professionals the opportunity to develop and validate their ability to combine the coordination of operational planning efforts with tactical design expertise and integration know-how.
Citrix Certified Integration Architect (CCIA) for Virtualization
The Citrix Certified Integration Architect for Virtualization certification focuses on best practices for analysis and design of Citrix virtualization technologies. By testing a range of skills used to design strategic approaches to virtualization, the CCIA certifies the knowledge required for successful deployments, while providing recognition and credibility to IT professionals. In addition to the required exams, a minimum level of real-world experience is recommended for candidates who choose to pursue this certification. As the most advanced Citrix designation, CCIA expertise helps organizations lower implementation costs, increase implementation success rates and reduce implementation time.
vrijdag 26 maart 2010
If you get this error with smart card authentication on your RDP / ICA session make sure:
- Smart card middleware is installed on both client and server;
- The same smart card reader drivers are installed on both client and server;
- The key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\SmartCards contains your smart card and the key is not empty, containing an “Crypto Provider” REG_SZ filled with the CSP;
- Make sure the CSP mentioned above is defined under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Defaults\Provider and uses an existing DLL file;
- The above mentioned registry keys should be the same on client and server so a match kan be made.
Thanks to TekWorkshop
dinsdag 02 februari 2010
The Citrix Brief Troubleshooting Guide is intended as the first resource for Citrix administrators and Citrix engineers to troubleshoot technical issues for all Citrix technologies.
The Brief Troubleshooting Guide provides you with a single point of access to narrow down your technical issues and help you resolve as many issues as possible in an autonomous manner.
Citrix Technical Support expects you to perform these basic troubleshooting steps before you contact them and will request information from you based on that troubleshooting. If you have the information on hand, it proactively helps them to decrease resolution time for your issue.
Each product section includes a brief product description, supported languages, links to Citrix Knowledge Base articles, third-party articles, troubleshooting tools, and questions and information to gather to help you pinpoint your technical issues.
The Brief Troubleshooting Guide should be used when tackling any issue, especially when you are unfamiliar with a product, or a product type. The Knowledge Center continues to be a very useful resource and is constantly being updated by Citrix Technical Support engineers worldwide – and you can find articles there created after this guide has been published.
Got curious? You can download it over here.
maandag 25 januari 2010
When VMTools are upgraded/installed it sets the registry key:
HKLM\SYSTEM\CurrentControlSet\Services\vmxnet\”START” to DWORD:00000003. By resetting this to its previous value of dword:00000000 (i.e. its value before the upgrade) it stopped the BSOD. You have to upgrade VMTools and make this change before restarting the machine.
Setting the START key to 3 will cause the system to not load the vmxnet driver until someone manually starts it, ie “net start vmxnet”. The value of 0 means that the driver will be loaded at system boot along with all the other boot mode drivers and is considered critical to the system booting successfully.
To set this registry key you can boot into “last known good configuration” with F8 during the startup of Windows.
Thanks to Charles Batchelor and Keith Pasquill in this thread.
maandag 25 januari 2010
Solution: install the SVGAII driver:
- Open Device Manager from Control Panel
- Expand Display Adapters entry
- Right click on VMWare SVGA 3D (WDDM) and click properties
- Click on Uninstall Button
- Check the “Delete the driver software for this device” option
- Click OK
- Your screen may flicker as the driver is removed.
- Close Device Manager and reboot Windows 7.
- Windows will default to the Standard VGA device
- Open Device Manager, expand Display Adapters
- Right Click Standard VGA and select Properties
- Click on Update Driver
- Click on Browse my Computer
- Browse to directory C:\Program Files\Common Files\VMware\Drivers\video
- Click Next
- Confirm driver installation
- Close window and reboot
Thanks to Ryan Gallier!
