To integrate your current Redirected Folders into the new Xendesktop 7.1 environment, you would need to configure the Folder Redirection GPO settings from within your Xendesktop 7 "Desktop lockdown GPO"--remember that these OUs are recommended to be processed with a loopback policy applied, which is why these settings need to be configured in your desktop lockdown GPO again instead.  (Unless your loopback policy configured for these Xendesktop 7 hosts is set to "MERGE" mode)

Apply these settings in the Desktop lockdown GPO for each folder that you wish to redirect:

I am using Citrix Profile Manager to redirect my user profile to a network share when a user logs on.  However, you will need to exlcude the folders that you would like to be redirected from the Citrix Profile Management policy, otherwise it will cause a conflict and redirection may not work correctly. so set the exclusion from within the Citrix Studio Console (Policy Node):

This is something that I need to share, especially for those of you who plan to implement Xendesktop 7 and APP-V integration.


So, you've just spent a few days putting the Xendesktop site together, the wheels are on and polished, it's looking pretty good--the only problem is that you have no seats! I'm referring to APP-V 5 packages not being seen on your hosted shared desktop.  You're probably wondering why this is, because you've rolled this solution out before and you've used "Application & Desktop" Delivery group types before too.  But you may want to check that group type again, because the chances are that you've setup a "Desktop" delivery group type, thinking that everything will work exactly the same as an "Application" or "Application & Desktop" delivery group type, but that isn't the case:


When you create an "Application" or "Application & Desktop" Delivery group type, the App-V 5 management and publishing server setting are inherited from the site level configuration.  But Desktop delivery groups do not inherit these settings by default, because desktop delivery groups are unable to publish applications and do not inherit the App-V 5 settings from the site configuration.  Instead, you have to tell a Desktop delivery group to use the specific App-v 5 site policy (Link them)


You would follow this procedure to link your Desktop Delivery group type to the site App-V policy:


Open the Citrix Studio Console and click on the "Powershell Tab", followed by the Powershell button, located on the tab and type these commands:




1)  Get-BrokerDesktopGroup    -adminaddress *yourdeliverycontroller*


2)  Get-BrokerMachineConfiguration –Name AppV*
(Displays the site's app-v policy name)


3)  Add-BrokerMachineConfiguration –Name AppV\XYZ –DesktopGroup UID
 (Replace the AppV\XYZ with the app-v policy name found from the previous command output. Then add the UID of the delivery group, found within the first command output.)


It's prudent to do a reboot of the servers after this.


Log back again, and Bob's your uncle! Your seat are back in the motor!

But before you go, you'll also need to be aware that if you're using folder redirection, you'll need to exclude App-V directories and settings from that process.  If you don't do this, then you're likely to see the app's only once, at first logon. So do the following in Citrix Policies:

"You must exclude the following items using Profile management exclusions:

• Profile Management\File system\Exclusion list\directories:
  • AppData\Roaming\Microsoft\AppV\Client\Catalog
  • AppData\Local\Microsoft\AppV
• Profile Management\Registry\Exclusion list:
• Software\Microsoft\AppV\Client\Integration
• Software\Microsoft\AppV\Client\Publishing"

Sources:

 http://support.citrix.com/proddocs/topic/user-profile-manager-5-x/upm-using-with-app-v.html

http://support.citrix.com/article/CTX138139

Open PowerShell on the controller and type add-pssnapin citrix.*

To mount the policies, type new-psdrive “Mysite” –psprovider CitrixGroupPolicy –Root \ -controller *yourcontroller*

Note: “Mysite” is the name of the psdrive you are creating, so it could be anything.
Type cd mysite:\.

Type dir, and find the location of your policy.

In this example, user container is being used, so type Cd user first

Check the number of policies and note the priority number. Then do the same cd.. and cd computer and check if there are conflicting policy
priorities, check for duplication of policies that are in user and computer containers.

To locate name of the policy which is causing the issue, type dir.

In the preceding image, the policy name is CPM PROFILE, so to remove it, type Rd “.\CPM PROFILE”.

Go back to the Studio, click Policy > Refresh.

You will now be able to see the rest of the policies and can modify/create once more.

You might want to remove them all except the unfiltered policy and a start again. This is what I did to get this working again.  Why the duplication happens? That's something I don't have an answer to at the moment

I encountered an issue with Citrix Profile Management recently.  The session was constantly creating a temporary profile.  This profiles had been working previous to this, so I knew that the NTFS and SHARE permissions were correct.  I decided to fault find the issue using the CPM log files, as mentioned previous to this post, but there was nothing obvious.

The Citrix Profile Management service is hosted on each Hosting server, but this service is installed on the master image by the Virtual Desktop Agent.  I uninstalled the VDA & Patch from the Master image, rebooted and then reinstalled them again.  After that, I decided to remove the VM images that were currently published within the console, and create them again. 

The Profiles worked fine after this

I discovered an unusual problem when accessing the Citrix Policy node in the Studio console.  It should be noted that nothing had changed on the policy side, and the policies were viewable, earlier on in the day.  There were no conflicting Group Policy settings being applied and no powershell scripts had been run.

 

 

1 ) From studio console, click on Powershell button
2)  Type in  add-pssnapin citrix.* (not usually required)
3)  Type in

new-psdrive "Mysite" -psprovider CitrixGroupPolicy -Root \ -controller *nameofyourcontroller*

4)  Type cd mysite: 5)  Type dir, and find the location of your policy.
6)  Type Cd user. check, then dir.  Check the policy names and priority
7)  Type Cd..
8)  Type CD Computer, check the policy names and priority

You may find that there are duplicate policy names in each container, both with different policy priorities. I found this, and decided to remove all of the policies except the unfiltered policy, and start again:

9)  To locate name of the policy and remove:

For example, the name of my policy was Citrix Profile Management.    To remove it, I type Rd "CITRIX PROFILE MANAGEMENT"
.
10)  Go back to the Studio, click Policy > Refresh.

The Active Directory Computer object password is usually changed automatically within, I think 30 days. There are Group Policy or Registry settings that can be applied to disable the machine account password (I will post these details at a later date)

You may find yourself in a scenario where you are unable to login to your master image.  This could be because you have restored to a VM snapshot, at a point in time when the computer account password was different.  Your Citrix Master image is now showing this error when you login:

"The trust relationship between this workstation and the 

primary domain failed"

You attempt to rejoin this computer to the domain but find that you can't login as a local Administrator either, so what can be done here?  I patched together this solution from several online sources, referenced at the end of this posting.

1)   Boot the  VM with your Microsoft Windows Server 2008/2012 DVD
2)  From the Windows Setup menu, click “Next”.
3)  Select “Repair your computer”
4)  Under Choose and option, click on “Troubleshoot”.
5)  Under Advanced options, click “Command Prompt”.
6)  At the command prompt, run the following commands:
            

             D:

             cd windows\system32            
             ren Utilman.exe Utilman.exe.old             
             copy cmd.exe Utilman.exe

7)  Close the command prompt and then click “Continue”.

8)  The server should now boot and present the logon screen. Here click Windows Key + U. Or Click on 

9)  At the prompt you can now change the password, by typing the following command:

              Powershell

              Reset-ComputerMachinePassword -Server "yourdc" -Credential "yourdomain\yourusername"

This will reset the machine account name on the domain and workstation.  Allowing you to login once more

10)  Restart your server and once again, boot from the Microsoft Windows Server 2008/2012 DVD

11)  From the Windows Setup menu, click “Next”.
12)  Select “Repair your computer”
13)  Under Choose and option, click on “Troubleshoot”.
14)  Under Advanced options, click “Command Prompt”.
15)  At the command prompt, run the following commands:
           

             d:
             cd windows\system32
             ren utilman.exe utilman.exe.new
             copy utilman.exe.old utilman.exe

16)  Close the command prompt and then click “Continue”.

17) Reboot, and login.  

18) Makes changed to your master image, to disable the local machine password changes

SOURCES:

http://www.kieranlane.com/2013/09/18/resetting-administrator-password-windows-2012/

http://blog.blksthl.com/2013/03/18/fix-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/

It appeared that user logons were initially taking too long when logging in from Citrix Storefront. I checked the DC that the Xendesktop were using to authenticate using this powershell command from the servers: $type=[System.DirectoryServices.ActiveDirectory.DirectoryContextType]"Domain" $context = New-Object System.DirectoryServices.ActiveDirectory.DirectoryContext($type, "insert you domain name") $domain = [System.DirectoryServices.ActiveDirectory.Domain]::GetDomain($context) $domain.FindDomainController().Name Then I checked the Citrix Policy to make sure that Session Reliability was on (As default) and also checked the Firewall was enabled on the session hosts and Master Image (It Wasn't) I then downloaded the following hotfix by Citrix, to resolve this issue on the VDA.  This was installed on the master image, an the MCS Catalog then updated http://support.citrix.com/article/CTX139901 The patch can be downloaded from: CITRIX XENDESKTOP 7.1/7.5 VDA PATCH Also, there have been numerous issues with the new Graphic Codec in Xendesktop 7.  I found that changing the Citrix Graphics to Legacy mode to increase the logon times significantly.  Be sure to check whether your client side redirection policies are tuned also, as client redirection will also slow logons.  You may also be able to redirect the Desktop and Documents folder at logon.