Assuming too much I guess...

The Economist had a "great" little blurb the other day regarding burger chain competitions in the 1980s. 

Original source. 

In summary, A&W restaurants tried to challenge McDonald's Quarter Pounder (or as Vincent Vega would say "Royale") with a third pound burger that cost less and had better taste reviews. They failed miserably. Their failure? They assumed the public would know 1/3 of a pound was greater than 1/4 of a pound. Consumers felt ripped off because they were getting "less" with the A&W burger. "Less" because the 3 in one-third is a lower number than the 4 in quarter. Fractions fail. 

I am guessing these are the same folks that continuously trend towards voting down school district tax increases. (Not that I am for tax increases - but I think there needs to be some emphasis on renewed 3rd grade curriculum for folks.) 

Any way you cut it, it is a sad indictment on our society's education level. I just need to remember to have a fifth-pound burger if I ever open a restaurant. 

Renaming a Reverse-Imaged Operating System

Often times after reverse-imaging a PVS-based member-server's *.vhd back to a "physical" disk there might be the desire to change the computer's name or domain membership.

I have seen on a few occassions that the ability to do this is compromised. Usually both the Computer name and the  Member of fields are greyed out when one of the issues outlined below is encountered. Additionally, the device may or may not let your add or remove features via either the GUI or PowerShell's Add-WindowsFeature cmdlet. You may also not be able to run SysPrep due to a "fatal error." In each instance, the host operating system may state that a reboot is pending - even after one has just completed!

Sample where the domain/workgroup affiliation cannot be changed.

Before panicking and rebuilding your image from scratch - run through these items to see if there are errors on any. Any one of these could halt your ability to rename the workstation.

1. Do you have appropriate permissions to modify these settings?
• Are you an administrator on the server? Are policies preventing this action? Try as the local device administrator - if you see the same issues here you most likely can continue.
2. Is the Workstation service running? 
• This service is required to communicate with the domain and if it is not running you will have a bad time.
3. On the device's network interface, is Client for Microsoft Networks in use?
• You will again have issues if there is a problem with this component. If it is not attached to your controller, add it. If it is, try uninstalling it (requires reboot) and reinstalling it once the server is back up.
4. Is the device "stuck" mid-rename? 
• This is a little bit trickier but still in the end fairly straight forward. When at the logon screen, if you use the local machine login characters (.\) does the machine name you see match the one in the Computer name/Domain changes GUI? If you open the CLI and type set (cmd) or $env:computername (PS) does the computername variable match both of these? If any of these are a mismatch, check out the keys in:
  HKLM//System/CurrentControlSet/Control/ComputerName
  If the values in ActiveComputerName and ComputerName do not match, the server thinks there is a pending reboot for a server name change. If a reboot has not set them to be identical, change them to match and reboot again.

Depending on the nature of failure that caused the server to not allow modifications to the Computer name/Domain changes GUI, one of these items should be the culprit. 

Just remember to keep in mind, if this is a XenApp server, if you had run the image prep tool previously, the next time IMA runs it will join the farm and you cannot simply rename a XenApp server that is joined to a farm without properly preparing it. If after you run the image prep tool you disable the IMA service so it does not run, you do not have to worry about this biting you. Just set the service back to automatic and reboot to have your renamed machine join the farm again. 

Finally, depending what you are trying to accomplish and what software is installed, don't forget about security identifiers and the need to properly prepare an image (SysPrep). 

Citrix Receiver Feature Matrix

Do you need to know what is supported for a deployment of Citrix Receiver? Want to do SSO and use Desktop Viewer? Check out the Receiver Feature matrix to make sure what you want to do is supported on the client version you are targeting.

Citrix Receiver Feature Matrix

3-D Graphics Introduction

Do you need an introductory primer on 3-D graphics over server-based computing? Need to know the differences between a vGPU, a dedicated GPU, and GPU pass-through? Check out Bridget Botelho's article on TechTarget which is a great introduction to the world of 3-D-based SBC.

Quick Reference
vGPU: A virtual GPU - it delivers shares of a physical GPU. The same concept as a vCPU.
Software 3-D: Graphics rendered on the CPU via software
GPU Pass-Through: Dedicating an actual hardware GPU to a VDI instance.

First Recommended Hotfixes for XenDesktop/XenApp 7.5 Released

On July 10th the first recommended hotfixes for XenDesktop 7.5 were released. Additionally, on today July 17th, a private hotfix to fix the policy management console was finally released. Hopefully this will go public soon as I have run into the errors outlined in that hotfix on numerous occasions. 

Citrix recommended hotfixes from are in bold. 

Delivery Controllers Hotfixes

DStudio750WX64001 

(Version 7.5.1) (For: Citrix Studio 7.1 and 7.5) (x86 if required: DStudio750WX86001)

1. This fix addresses a memory issue in an underlying component.

Limited Release: Hotfix GPMx220WX64001 

(Computers running the 64-bit version of Windows 7, Windows 8, Windows 8.1, Server 2008 R2, Server 2012, or Server 2012 R2, with the Group Policy Management Console installed)

1. The priority order of GPOs is reversed in the following scenarios:
• After upgrading from Version 1.7 to Version 2.1 of the Citrix Group Policy Management Console.
• After exporting GPOs from Version 1.7 or earlier of the Citrix Group Policy Management Console and importing them into Version 2.1 or later of the Citrix Group Policy Management Console. 
• Note: This fix does not address the issue for GPOs that were modified using Version 2.1 of the Citrix Group Policy Management Console; it will prevent the issue only with GPOs you modify going forward. To fix the reversed priority order of existing GPOs you modified in Version 2.1 of the Citrix Group Policy Management Console, you must manually adjust the priority order of the affected GPOs once you install this fix.
2. When making changes to Citrix policies in Citrix Studio the following error message appears:
• "Changes made to policies outside of this console, such as in PowerShell or management tools from previous versions, resulted in a discrepancy between policies.
• The priorities for policy [PolicyA's name] and policy [PolicyB's name] interfere with each other in the "user" and "computer" components. The priorities must be assigned in the same order for both policies."
• Note:
• This fix prevents any issues occurring with merged policies. If the error message appears before applying the fix, then you must manually adjust the priority order after installing this fix.
• For example, if two merged policies, PolicyA and PolicyB, are swapped and a user setting is added to PolicyB, the issue occurs. To prevent the issue from occurring, run the following commands on Citrix Delivery Controller:
  PS>Add-PSSnapin Citrix.Common.GroupPolicyPS>New-PSDrive Site –PSProvider CitrixGroupPolicy –Root \ -Controller localhostPS>cd Site:\Computer[Note the PolicyA's computer setting priority]PS> cd ..PS>cd Site: \UserPS>Set-ItemProperty PolicyA -Name Priority -Value [PolicyA's computer setting priority]
• You can configure user and computer settings in the same policy and both settings can have the same priority order. Occasionally, the priorities for the settings might be different. 
• For example, PolicyA and PolicyB have the same user and computer settings, but the computer setting priority of PolicyA is higher than PolicyB. In this instance, configure the user setting of PolicyA to be higher than PolicyB.
3. After editing the built-in "Unfiltered" policy, the following error message appears:
• "Changes made to policies outside of this console, such as in PowerShell or management tools from previous versions, resulted in a discrepancy between policies.
• The Enabled Flag for the "user" and "computer" components of the policy Unfiltered must have the same value."
• Note: This fix prevents any issue occurring with unfiltered policies. If the error message appears before applying the fix, you must manually enable the flag of the "Unfiltered" policy by using PowerShell commands (cmdlet) after installing this fix.
• For example, if "Unfiltered" has only computer settings configured and the Enabled flag is clear, run the following commands in Citrix Delivery Controller:
  PS>Add-PSSnapin Citrix.Common.GroupPolicyPS>New-PSDrive Site -PSProvider CitrixGroupPolicy -Root \ -Controller localhostPS>cd Site:\UserPS>cd Site:\User\UnfilteredPS>Set-ItemProperty . -Name Enabled -Value True
4. The following error message appears when opening the Citrix Studio and selecting the policy node:
• "The priority of the "user" and "computer" components of policy <policy name> must have the same value."

Desktop OS x86 & x64 Host Hotfixes

BrokerAgent750WX86001 

(Server or Desktop VDA x86) [x64 if ever needed see server section]

1. This fix addresses a session brokering issue.

XD710ICAWSWX86005 

(Desktop VDA x86) [x64 if ever needed: XD710ICAWSWX64005]

1. COM port redirection can fail after upgrading Version 5.1 of VDI-in-a-Box to Version 5.3.
2. This fix addresses various session brokering issues.

XD710ICAWSWX86004 

(Desktop VDA x86) [x64 if ever needed: XD710ICAWSWX64004]

1. This enhancement provides additional compatibility with Nvidia's GRID API related to GPU pass-through and vGPU use cases.

XD710ICAWSWX86001 

(Desktop VDA x86) [x64 if ever needed: XD710ICAWSWX64001]

1. In Cisco WAAS deployments, the session reliability feature fails to automatically reconnect sessions dropped from VDAs.
   To enable this fix, you must set the following registry key on affected VDAs and then restart those systems:
   HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XTEConfig
   Name: CgpDisableBranchRepeaterSessionReliability
   Type: REG_DWORD
   Data: 1 (enabled); 0 (disabled)

ICAWS750WX86007 

(Desktop VDA x86) [x64 if ever needed: ICAWS750WX64007] 

***Replaces XD710ICAWSWX86002, XD710ICAWSWX86003

1. In sessions on VDAs with Desktop Composition Redirection enabled (default) and Fix #LA5736 (XD710ICAWSWX86003) installed, the mouse pointer might not honor the boundaries of the desktop.
2. (from replaced hotfix) This enhancement provides better performance when running VDAs on hosts with AMD or Intel graphics (for example, physical PC, pass-through GPU, or vGPU).
3. (from replaced hotfix) Mouse pointer movement is not visible in the Lync conversation window if you share your virtual desktop.
4. (from replaced hotfix) After a virtual desktop session reconnects, the VDI log on dialog box does not appear and Lync in the virtual environment is no longer paired with the Lync VDI plug-in.

Server Session Hosts x64 Hotfixes

BrokerAgent750WX64001 

(Server or Desktop VDA x64)

1. This fix addresses a session brokering issue.

XD710ICATSWX64001 

(Server VDA x64)

1. In Cisco WAAS deployments, the session reliability feature fails to automatically reconnect sessions dropped from VDAs.
   To enable this fix, you must set the following registry key on affected VDAs and then restart those systems:
   HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XTEConfig
   Name: CgpDisableBranchRepeaterSessionReliability
   Type: REG_DWORD
   Data: 1 (enabled); 0 (disabled)

XD710ICATSWX64004 

(Server VDA x64)

1. Attempts to open Microsoft Office files in a virtual desktop session might take a longer time to open. Additionally, when a published application is started and then minimized, it can no longer be restored or maximized from the taskbar.

XD710ICATSWX64002 

(Server VDA x64)

1. Certain session time limit policies of Remote Desktop Services might fail to work on Windows Server 2012 VDAs.
2. The Citrix "Server idle timer interval" policy in Citrix Studio does not work for Windows Server 2012 VDAs.

Limited Release: Hotfix XD710ICATSWX64003 

(Server VDA x64)

1. The session graphics of certain applications can fail to update. As a result, the session appears frozen.
2. With the default graphics mode enabled, certain applications can prevent screen updates. As a result, the session can appear unresponsive.

Limited Release: Hotfix XD710ICATSWX64005 

(Server VDA x64)

1. The Citrix Audio Service exits unexpectedly when logging off from the server.

Limited Release: Hotfix ICATS750WX64007 

(Server VDA x64) 

***Replaces: XD710ICATSWX64002

1. The Windows Event Viewer occasionally displays the following error message with Event ID 9026. The error is benign and can safely be ignored.
2. "Error %1 received while obtaining a license for a Citrix XenApp client connection. A grace license has been granted."
3. (from replaced hotfix) Certain session time limit policies of Remote Desktop Services might fail to work on Windows Server 2012 VDAs.
4. (from replaced hotfix) The Citrix "Server idle timer interval" policy in Citrix Studio does not work for Windows Server 2012 VDAs.

 References:

• XenDesktop 7.5 Hotfixes