How to present home drive and set Quota for Citrix provisioned desktop

When we use roaming profile we follow best practice suggested by Microsoft for roaming profile which is listed here. This redirected folder is presented as home drive to the end users. So say suppose company has a guideline to limit users home drive , then in that case we must limit this using quota.

We recommend to use different shares for home drive and profiles so that it would be easy to redirect everything and set quota. I usually present redirect folder as users home drive. This is achieve via GPO

 

So when user login he will see his home drive like this

To achieve this we decided to use windows 2012 and take benefits of SMB3 . I am not going to explain how to setup DFS here. There are tons of article on the net. What I am going to explain here is how we can setup desire quota for each users.

Windows 2012 have two console for quota setting

And other via FSRM

For quota setting we need to use FSRM . So lets start using FSRM and define hard quota for 5GB. We need to create custom template with Hard quota. Soft quota does trigger alert and all but hard quota does not.

Once template is ready go to the quota section and select create quota

Path to quota will be root where I will be storing all the users data . In my case share path name is data which is mention above. Make sure you select “Auto apply template and create quotas on existing and new subfolders”. Here under drop down you will see custom quota created earlier. After applying create , don’t forget to exist and report FSRM. I had challenge  because I was trying to refresh using FSRM. Once quota is set this is how it will looks like

Here you can modify quota for individual users

So what permission do I need?

Make sure share has following permission set on the shares

And this permission is in place

Make sure you enable access based enumeration to prevent users from seeing or accessing others folder

This will allow user to see home drive with quota along with  respective permission.

Tata Bye bye till next time

XD 7.1 : MCS error “Provisioning scheme not recognized” with VMWare

I was trying to create MCS catalog using virtual center 5.0 U1 and it was throwing error 

While looking at catalog provisioning scheme name was empty

While looking at active task it was erroring out after 29%.

We looked deeper into error message and it was “Error Id: XDDS:4E970E49”

This was the case where virtual and ESX were connected via WAN link with 200ms + of latency . Finally we increase timeout value for VMWare connection  from default to 8 hours and that worked. I am not going to explain details here but if you want to know more trying using wireshark.

Configure HP T410 for Citrix AGEE via using Native client

First we need to ensure that all the require certificate which is configured on AGEE SSL is copied over HP T410. To do that we need to enter admin mode

Once admin mode is enabled ( It will ask for password and default is root) you can find the option called certificates

 

Insert the pen drive with require certificate and then import using certificate manager

 

Once done then create connection using connection manager

This connection uses legacy client setting on store front.  So check store front setting for this

Once this setting is supplied it will prompt for user name password. This user name can be in form of domainname\user and then just the password

Once user name is accepted , then you will get desktop with all the icon

XenApp session throwing error "To log on to this remote computer, you must be granted"

When XenApp hosted shared desktop is launch or XenApp published applications are launch it throw following error " To log on to this remote computer , you must be granted the allow log on through Terminal Services right"

Users were member of local desktop groups but for some reason local policies for "Allow log on through Remote Desktop Services" were not configured for "Remote Desktop users" Once added , HSD were successfully launched.

How to integrate App -V with XenApp 6.5 -About Roy Approach

Though there are tons CTX and KB published but I would like to have my own reference based on my own experience.  All I need is XenApp and application will be streamed to the XA server rather to the client.So how do we start with. First we should download App -V integration kit from Citrix site. This site is listed under

Once downloaded extract it and you can find following files under it.

Copy this folder under App V hub. Now this App V hub is noting but where captured applications are kept and location is following

  

Next thing we need to do is install App-V client on the machine where application is intended to be streamed. In my case application will be streamed to the XenApp box. Remember App -V client for XenApp is different and you need to download App-V client for  remote desktops services 

After installing App-V client on XenApp box which will be used to published this app, we must insure some settings are populated. During installation we can install with default settings like locations for app hub. Rest all settings can be populated latter

 

Specifying publishing server is a must.

And yes do not forget to update the following registry setting on all the XenApp box which will be used for App-V streaming

So this all settings are on App -V client which is installed on XenApp box. Same XenApp box will be used for streaming App -V applications.

Now we need to provide permissions on Applications as well. Make sure application which we are intended to be publish have XenApp users mapped.

Now we will be publishing this applications via XenApp. I am not going to cover each steps.While publishing apps I am choosing stream to server because I will be using my XA box to stream App -V OSD (Application streaming)

Now I will be selecting locations for applications. So profile address will be pointing  App -V conduit which is from App -V integration kit. This will populate profile field. Then we need to type UNC path for application OSD. This is post application has been sequenced via App -V . To sequence App -V follow CTX126082

While selecting servers choose the server where we have installed App -V client which is mention in the beginning. Add the users and then we can see the application via SF portal

  

You can observe that here it launch from Q drive

Also on if you notice client status on XenApp server it will be 100% stream

Rest all will leave to you guys to figure out as I am no expert with App -V . And yes feedback as always welcome.