Archive
#Citrix #StoreFront 2.5.2 is released – #DaaS, #XenDesktop, #XenApp
Citrix has released Citrix StoreFront 2.5.2 with some good fixes…
Issues fixed in StoreFront 2.5.x
Updated: 2014-06-18
Issues fixed in StoreFront 2.5.2
Fail to launch a XenApp session from the second delivery site.
The StoreFront server had problems with load balancing between two XenApp farms. When the first farm was completely loaded, StoreFront did not use the second farm and the application launch failed. [#432279]
Enhanced enumeration fails with socket pooling enabled.
Enumeration failed for two or more farms when socket pooling was enabled in the store configuration file. [#470666 and #458139]
Issues with finding the domain controller for a domain.
Slow logon times occurred when geographically distant domain controllers were chosen. [#479210]
Submitting the logon form after the authentication service session timed out results in an HTTP 400 Bad Request.
When the logon form was submitted after the authentication service session timed out, an HTTP 400 Bad Request response was generated preventing the user’s credentials from being resubmitted. [#479200]
Directory queries are not thread-safe.
Citrix default Domain Services crashed because the Directory services account look-up was not thread-safe. [#479188]
Issues fixed from StoreFront 2.1 to 2.5
Changing an expired password on next logon fails.
When prompted to change a password, client domain users using Windows would not be able to successfully change their passwords because of Windows Server 2003 domain controllers failing to handle the operation correctly. Microsoft has issued an update that resolves this problem. The update is available via Windows Update or may be downloaded from Microsoft support directly at http://support.microsoft.com/kb/2927811. [#438725]
A user with a large number of subscriptions loses the ability to manage subscriptions.
When logging on, users with 353 or more automatic app subscriptions would receive the following error: “Citrix Receiver cannot currently add, remove, or reposition apps.” [#432086]
The wrong user name is sometimes shown.
Clients would erroneously display a different username. [#430823]
PNA resource IDs do not match requirements of local launch logic.
PNA resources from XenApp were in a format different than StoreFront’s usage. This inconsistency led to slower performance due to excessive ICA connections.[#429055]
Partial wildcard certificates cause issues in the admin console.
The admin console would improperly display configured host names from the IIS bound certificates. [#424708]
Change password option is not available for some users.
Some users were not given the option to reset their password even though they were enabled to do so. [#416373]
Subscription export/import loses subscription properties.
StoreFront was not properly maintaining multiple subscription properties. [#408668]
DAC smart card authentication updated to use domain account services rather than IIS certificate mapping.
Desktop Appliance Connector certificate authentication with smart cards required manual configuration with IIS certificate mappings rather than using the default domain account services. [#406945]
A SAN web server certificate with no CN causes issues for the admin console.
StoreFront admin console was improperly handling common name entries in certificates which would cause console crashes.[#401815]
StoreFront home farms support gives a user access to all farms when they should have access to none.
When a user was configured without access to any farms, all farms were enumerated for that user.[#400869]
The admin console being closed would overwrite some manually applied changes made to the configuration file.
Some manual configuration changes were being lost when the admin console was closed. [#440946, #424460, #439887, #395155]
How to: #Citrix #XenMobile 8.5 MAM upgrade! Part 2 – #StoreFront, #AppController, #NetScaler
Hi again!
If you haven’t read Part 1 then I highly recommend doing so prior to going directly to the upgrade that we’re covering in this post!
Prepare for a journey in this post about Citrix StoreFront upgrade, uninstallation, console and how messy it could be! NOT all the time, sometimes it “just works”! 😉
My little NetScaler is already upgraded to 10.1 so unfortunately I couldn’t take you on that journey as well, so we’ll start with the StoreFront upgrade from 1.2 to 2.0 in this post. These are the steps that we need to cover as highlighted in the migration guide that seems very short and straight forward:
Upgrade StoreFront 1.2 to 2.0.
- Logon to the StoreFront server console.
- Upgrade StoreFront by running the StoreFront 2.0 installer as an administrator.
- When the upgrade is completed, open StoreFront administration snap-in, remove CloudGateway controller from each store as this will be moved in the migration solution.
- Open NetScaler Gateway Properties and for each gateway defined and change the version field in settings from 9.x to 10.0.x or later.
- Test the configuration by logging on through web browser or Citrix Receiver.
- Verify if the users are able to login and authenticate to StoreFront defined stores configured.
Is it this easy?
Ok, I’ve downloaded the 2.0 installer, and I’m logged on to the server.
Before we even start the upgrade there are things that could go wrong in removal or upgrades of StoreFront. And one that I’ve seen cause a lot of headache for a lot of people out there is that they have the Windows Firewall service disabled. Though the installation and removal wants to delete or add these rules the installation will fail unless this service is running. As you can see in this picture below you see the FW rule added in StoreFront 1.2:
So let’s verify that the Windows FW service is started, and it is!
I’ll now start the installation by double-clicking the StoreFront 2.0 installer!
What is this popup that came directly after starting the installer?
Wait, ok so you guys at Citrix couldn’t ask me whether you could do this for me? My plan is to upgrade, so please just add a little step in your upgrade program that does this for me… change request #1 for the next SF release and it’s upgrade process! Verify pre-requisites or deal with them!
#Citrix #XenMobile 8.5 MAM upgrade! Part 1 – #StoreFront, #AppController, #NetScaler
In this little blog series series you’ll follow a little upgrade process to XenMobile 8.5 for Mobile Application Management (previously known as CloudGateway).
Ok, I don’t exactly know where to begin. I must first say that Citrix is THE master when it comes to renaming products, updating/changing the architecture, changing consoles (claiming to reducing the number of them like every year but at the same time introduce new ones).
How hard can it be to make crystal clear documentation and upgrade processes that works and are easy? I feel already that my tone in this blog post is “a bit” negative… but I think that Citrix actually deserves it this time.
I must now take a step back and calm down and point out that Citrix is delivering some MAJOR changes and good news/features in the new XenMobile 8.5 release though! It’s great (when you’ve got it up and running) and I must say that I don’t see anyone that is near them in delivering all these capabilities in a nice end-to-end delivery!! 🙂
Have a look at everything that is new, deployment scenarios etc. here before you even start thinking to upgrade or change your current NetScaler, StoreFront and AppController environment!
Once you’ve started to read the different design scenarios you’ll see that App Controller can be placed in front of StoreFront, in the back of StoreFront or totally without StoreFront… all the options just make your head spin! Because Citrix doesn’t really make it clear on how all of this should work with a Receiver and Worx Home depending if the device is on the internal network, external through NetScaler or what the capabilities that you need are supported in the different scenarios in a simple way, just text that explains it. And I find the pictures and text a bit misleading:
As you see above the App Controller is added as a “Farm” just as in 2.6, but is that the truth now in version 2.8 of App Controller?
If you have a look at the text from this page it’s getting even more confusing: Read more…
Upgrading to #Citrix #Receiver for #Windows – why and how?
This is something that all Citrix admins should read! How many questions don’t U get about which version of the client to use and why etc?
This document describes the various versions of Receivers for Windows, lists the reasons for upgrading, and recommends best practices for upgrading to the latest version of Receiver based on specific circumstances.
Note: The Online Plug-in 12.x will reach end of its maintenance in March 2013. Customers using Online Plug-in with XenApp 5, XenApp 6.x, XenDesktop 4.x, or XenDesktop 5.x must upgrade to the latest version of Receiver for Windows 3.X prior to that date where practical.
Citrix Receiver is the latest Citrix software you install on Windows end points to gain access to virtualized apps and desktops. It is also regularly installed on virtual desktops to enable access to virtualized apps.
The name of Citrix client software and the built-in functions are changed over the years. The clients in common use today are the Online Plug-in for Windows 12.X and the Receiver for Windows 3.X.
Where the Online Plug-in for Windows 12.X provided Web and PNAgent support, Receiver for Windows 3.X provides additional support. It can be configured for self-service access to applications, VPN-less remote access, single sign-on the Windows, Web, and SaaS applications, and has a built-in method to check for updates.
Both the Online Plug-in and Receiver have two versions.
- The Online Plug-in Web is used solely for Web access to applications and the Online Plug-in (Full) supports Web access as well as PNA Services. The Full version supported SSO, Smart Cards, and access to apps through the Start menu
The standard Receiver for Windows, CitrixReceiver.exe, can be considered is a complete replacement for the Online Plug-in Web and largely a replacement for the Online Plug-in (Full). It can be used for web access. It can be configured to access PNA Services. And it can also be used with the latest versions of StoreFront, CloudGateway (App Controller), and Access Gateway to provide a rich set of services. It contains the latest, multithread, multi-stream HDX engine.
#Citrix #XenDesktop 7 released – #RTW, #BYOD, #HSD, #VDI
Ok, it’s here! The official release is now available for everyone!
There are tons of blog posts and materials already out there and some great features as well that comes with this new release from Citrix. If you haven’t already played with the Excalibur release and know about them I suggest that you start evaluating and testing now!
Here are some good links to have a look at:
- XenDesktop 7 Overview
- XenDesktop 7 Feature matrix
- Excalibur is XenDesktop 7: what does this mean for XenApp and XenDesktop customers?
- XenDesktop 7: Upgrade & migration paths for XenDesktop and XenApp customers
- XenDesktop 7: AppDNA and Platinum Activation
- Reference Architecture: Director and EdgeSight
- XenDesktop 7 edocs – Documentation
- XenDesktop 7 Admin Guide
- XenDesktop 7 Upgrade Guide
- XenDesktop 7 Install Guide
Enjoy! 🙂
//Richard
Heads Up – issues with Access Gateway Plug-in for Mac OS X Version 2.1.4 – #Citrix, #NetScaler
Well, I guess that you’ve already read all the good things about the new capabilities of the newer Access Gateway plug-in, Receiver and Access Gateway Enterprise that together with StoreFront will add additional features and functions that haven’t existed before. It’s now built to work together with the Receiver on the Windows and Mac OS X platforms and promises a lot by various blog posts from Citrix and others (incl. myself).
Here is an example of what it can (should) do: What’s new with Access Gateway MAC Plug-in release 2.1.4
But is the Access Gateway Plug-in that great? Well, before you plan to implement version 2.1.4 on OS X and especially if you want to leverage the SSL VPN functionality and host checks (EPA) then read the Important notes and Known issues for this release:
Important Notes About This Release:
- The Access Gateway Plug-in for Mac OS X Version 2.1.4 supports Citrix Receiver Version 11.7
- Import the secure certificate for Access Gateway into the Keychain on the Mac OS X computer.
- The Access Gateway Plug-in for Mac OS X Version 2.1.2 and earlier versions are not supported on Mac OS X Version 10.8.
- Endpoint analysis scans for antivirus, personal firewalls, antispam, Internet security, and EPAFactory scans are not supported for Mac OS X.
- Client certificate authentication is not supported for Mac OS X.
First of all I’d say that these notes are not that great if you ask me! Why do I have to add the cert into the Mac Keychain? Why doesn’t the plug-in support the more “advanced” host checks like personal firewalls, certificates etc.?
Wait, it get even worse!! And before you go to the whole list I’d highlight these top ones that I’m kind of surprised about:
- It doesn’t support LAN access
- Upgrading doesn’t work
- Doesn’t apply proxy settings configured in session profile
- It doesn’t support SAN certificates
- Users cannot start the Access Gateway plug-in if the Receiver is already started, you first have to shut down the Receiver
Here you see the full Known Issues list for this release:
- When users disable wireless on a Mac OS X computer and connect by using a 3G card, the Access Gateway Plug-in does not upgrade automatically through Citrix Receiver. If users select Check for Updates to upgrade the plug-in, the upgrade fails and users receive the error message “Updates are currently not available.” [#45881]
- If you run stress traffic for HTTP, HTTPS, and DNS simultaneously, the Access Gateway Plug-in fails. [#46348]
- When users disable wireless on a Mac OS X computer and connect by using a Vodafone Mobile Broadband Model K3570-Z HSDPA USB 3G stick, the Access Gateway plug-in does not tunnel traffic. [#256441]
- If you configure an endpoint analysis policy and also enable the client choices page and proxy servers in a session profile, occasionally a blank choices page appears after users log on. When you disable the choices page in the session profile, the choices page appears correctly. [#316331]
- If users connect to Access Gateway with the Access Gateway Plug-in for Mac OS X and then run ping with a payload of 1450 bytes, the plug-in fails to receive the ICMP reply. [#321486] Read more…
Correct – SCCM 2012 doesn’t support SQL Mirroring! via @agerlund – #SCCM
Beware before upgrading to SP1. SCCM does not support database mirroring and if you’ve configured it don’t just try to upgrade! Thx @agerlund!
As stated here SQL mirroring is not supported for the ConfigMgr database. However a technet article do not stop all database administrors’s from enabling the setting anyway believing that it will not cause any issues – but boy it does. SQL mirroring will break the SCCM SP1 upgrade process and leave the primary site server in a non-functional mode where a site restore is the only way back.
The issue can be found in the ConfigMgrSetup.log file.
Continue reading here!
//Richard