Archive
#Citrix #StoreFront Slowness, Join and Replication issue – check list!
Ok, I guess that you may have seen issue with StoreFront before… and it you have not then good for U!
But in the case that you have experience it here are a couple of things that you can do and hopefully it solves your issue with slow StoreFront console startup, server join issues or replication issues. Sometimes I’ve seen that the join, replication and slowness is ok and the process goes through. But then all of a sudden you get an error and the propagation fails… and this can be because of a timeout in the StoreFront process that you’ve initiated.
I already assume that you’ve checked the basic stuff.. that the servers can reach each other (ping server name and FQDN etc. and that there are no FW issues)….
You may have an issue because you/your server cannot reach the Internet, and some of the components of the product is signed with SSL certificates and StoreFront will try to perform a check whether the publishers certificate is ok or not. So if your servers are behind a proxy serevr that you usually configure in your browser to be able to connect from your companies internal network to the Internet then you should do the following.
1. Log on to your first StoreFront server and create a copy of the original aspnet.config file under C:\Windows\Microsoft.NET\Framework\v2.0.50727 (verify which framework version that your app is using in IIS and modify that appropriate aspnet.config file, more info about this change can also be found here and is for Web Interface but is also applicable to StoreFront)
2. Open Notepad as an Admin (if you have UAC of course enabled) and open the asp net.config file
It will have the content as described by the picture above, add this line to it: <generatePublisherEvidence enabled=”false”/>
SSO to StoreFront not working in CVPN mode – #Citrix, #NetScaler, #StoreFront
Single Sign-On from Access Gateway to StoreFront not working in CVPN mode
There is yet another “thing” to have in mind when setting up Access Gateway and StoreFront in CVPN mode!
It’s been an interesting day (or days/weeks/months I must admit) with some “issues” with a NetScaler ADC, Access Gateway with CVPN profiles and StoreFront 1.2. And one thing that we have been struggling with was Single Sign-On to StoreFront when we had the AG configured for CVPN access. And it was just this environment where I’ve seen this issue!!
After a lot of troubleshooting the Citrix guys came up with an explanation on why SSO from AG doesn’t work in this specific environment! And it’s not an obvious one to find I must say… but I now understand why it doesn’t work!
So let’s explain the design reason for why it doesn’t work (so bear with me, solution at the end!!)…
The following picture tries to give a VERY rough picture of how it could look like, clients on the Internet on the left, then a NetScaler ADC with the Access Gateway feature enabled and a vServer configured. This AG vServer has session policies and profiles for ICA proxy (old traditional ICA proxy policy) and the little newer CVPN mode. And YES; I’ve left out a lot of stuff like AD etc. to simplify this picture A LOT…
The overall idea and config is that AG authenticates the user and then shall do SSO to StoreFront. The CVPN policy have been created according to all best practices etc. (Citrix CloudGateway Express 2.0 – Implementation Guide).
But SSO still doesn’t work!! If you login through a browser when having the CVPN policy linked to the vServer you’ll see that authentication works perfectly but then when it tries to passthrough the authentication to StoreFront it fails.
This picture just shows the login to the NetScaler ADC Access Gateway vServer:
PVS support in XenServer 6.1 – via @_POPPELGAARD – #XenServer, #Citrix, #PVS
Good blog post from Thomas Poppelgaard!
And this is something that many have waited for, either they upgraded and ran into the issues and had to revert back to 6.0.2… but now it’s fixed! 🙂
Citrix have released Hotfix XS61E009 & XS61E010 for XenServer 6.1 and now you are able to have Citrix Provisioning Services with XS 6.1 and use VVS.
I have been waiting for this for a while.
Issues Resolved In This Hotfix XS61E009
- Virtual Machines (VMs) with out of date XenServer Tools, may not be flagged as “out of date” in XenCenter. This hotfix resolves this issue and enables customers to be notified in XenCenter when new XenServer Tools are available.
- Booting a Citrix Provisioning Services (PVS) target device using a Boot Device Manager (BDM) image can take an extended time to complete. This hotfix resolves this issue.
Issues Resolved In This Hotfix XS61E010
- Customers using XenServer Platinum Edition to license Citrix Provisioning Services (PVS) may find that one PVS license per VM is checked out, rather than one PVS license per XenServer host. This may lead to a shortage of PVS licenses and an inability to provision VMs. Installing this hotfix along with CTX135672 – Hotfix CPVS61016 (Version 6.1.16) – For Citrix Provisioning Services 6.1 – English resolves this issue.
- Attempts to shut down Microsoft Windows Vista and later VMs can cause intermittent blue screen errors, with a "STOP: 0x0000009f..." error message.
- Adding more than eight NICs to Microsoft Windows Vista and later VMs, using the xe CLI can lead to a blue screen error on reboot.
- Copying data to a Microsoft Windows 2003 VM can cause the VMs to hang and lead to a grey screen error.
- When Dynamic Memory Control (DMC) is enabled, attempts to migrate Microsoft Windows XP and later VMs using XenMotion can cause the VMs to hang and lead to blue screen error.
- When the Citrix Xen Guest Agent service is running, Cut and Paste will not work between a XenDesktop virtual desktop and the endpoint device.
- Microsoft Windows XP and later VMs may hang during the boot process and may have to be forced to reboot.
- Attempting to install or upgrade the XenServer Tools on Microsoft Windows Vista and later VMs, which do not have access to a paravirtualized or an emulated network device can cause the installation process to hang.
- Manually installing the Legacy XenServer Tools without changing the device_id to 0001 can result in a "STOP: 0x0000007B..."error when rebooting a Windows VM. After installing this hotfix, customers will not be able to manually install the Legacy XenServer Tools by running xenlegacy.exe…
Continue reading here!
//Richard
HEADS UP – PVS and XenServer compatibility issues
UPDATE!!! SEE THIS POST FOR MORE INFORMATION AND PVS SUPPORT ON XENSERVER 6.1; http://richardegenas.com/2013/01/22/pvs-support-in-xenserver-6-1-via-_poppelgaard-xenserver-citrix-pvs/
Ok, this is something that many may be aware of but I’m sure not all of you out there! Thanks Per Liif for the inputs to this little blog post!!
So what’s the issue? Well you can summarize it by saying that XenServer 6.1 and PVS is not compliant out of the box!
The Citrix information about this issue can be found here and basically tells you that; The standard XenServer Tools do not include support for Volume Shadow Copy Service (VSS) or Citrix Provisioning Services (PVS). For customers who wish to use VSS or PVS, the legacy XenServer Tools must be used.
What does this then mean in real life if you go ahead and use the standard XenServer tools and what errors might you be struggling with if you have this issue? Answer; you’ll see blue screens like this (xenvif.sys);
So what shall you do to prevent this, well use the steps in the support article from Citrix PRIOR to installing the legacy tools (xenlegacy.exe), otherwise you’ll end up with this blue screen (xenvbd.sys);
And of course you could argue whether Citrix could have provided a bit more heads up for everyone out there in the release notes and blog posts of XenServer 6.1. I hope that not many of you ran into this and spent to much time on it prior to finding the Citrix workaround article!
//Richard
The IT Melting Pot! 