Citrix have released a new Receiver for BlackBerry 2.1

Citrix Receiver is downloadable from BlackBerry App World for supported BlackBerry devices.  Automatic updates will occur when new versions are available.

For administrators, the download package can be downloaded and deployed to employee devices via the BlackBerry Enterprise Server.

Download Receiver for BlackBerry 2.1 here

Citrix is have released a technical preview of the next version of Citrix Reciever 3.0 for Windows.

Citrix Synergy is helding these days and on Wednesday all the great new technologies from Citrix will be announced.

Receiver 3.0 will dramatic improve the user experience, look out for features like Session Pre Launch, Multi-stream ICA, Multiple audio device redirection and New Single Sign-On Plug-in

Symptoms

When using Provisioning Services 5.6 and a distributed High Availability (HA) model for the virtual disk stores, the environment level view of virtual disk locks can become out of synchronization with the actual current status of the devices connected to specific virtual disks. In certain circumstances, this can lead to virtual disk corruption.

Note: This behavior relates to the virtual disk locking mechanism. HA failover ability is not affected by this behavior.

Scenario 1:

A target machine boots normally, however, a virtual disk lock is only created on the Provisioning Services server serving the virtual disk and not on the second Provisioning Services server.

Result:

The properties of the virtual disk can now be edited on the second Provisioning Services server because it is not aware of the lock on the first server. This could potentially lead to virtual disk corruption.

Scenario 2:

A target machine boots from one Provisioning Services server but a HA failover event occurs which causes the target to failover to the second Provisioning Services server. In this case, the only lock shown in the Provisioning Services console is the lock on the second Provisioning Services server, which is currently serving the virtual disk.

Result:

The properties of the virtual disk can be edited on the first Provisioning Services server, because it is not aware that the second Provisioning Services server is now streaming the virtual disk.

Scenario 3:

Following on from Scenario 2, if the target device fails over from the second Provisioning Services server back to the first, the lock is removed from the second server but never recreated on the first Provisioning Services server.

Result:

Neither server now shows a lock on the virtual disk. This means either server can be used to modify the virtual disk, leading to data corruption of the virtual disk itself.

Cause

Because Provisioning services does not centrally store the virtual disk locks, in a situation when HA functionality is executed in a distributed HA environment, the Provisioning Services servers view of the locks becomes inconsistent.

Workaround

Because the problem only occurs when using a distributed HA model for Provisioning Services virtual disk stores, this issue does not occur if a shared storage solution is used.

More Information

CTX127549 – Provisioning Services 5.6 Best Practices

Symptoms

Target devices hang and the Stream.log on the Provisioning Server contains the following entries:

ERROR   CSSProtocolModule::DoTraceEvent Detected one or more hung threads.
ERROR   CSSProtocolModule::LogReport 2 thread(s) last known to be active at .\SSProtocol.cpp:591 have been inactive from 215 to 215 seconds.
ERROR   CSSProtocolModule::DoTraceEvent Terminating StreamProcess.

Cause

This issue occurs either when the database server which hosts the Provisioning Services database goes offline or when the database server is not able to service the Provisioning Services requests in a timely fashion, without actually fully going offline.

Workaround

If the database server goes offline, enable DB Offline support to allow your targets to remain running until the database server can be brought back online.

If the database server is not able to respond in a timely fashion, investigate the loads on your database server and consider using a dedicated instance to service the Provisioning Services infrastructure.

More Information

CTX129173 - How to Enable DB Offline in Provisioning Services

Citrix have released this great secure deployment guide for NetScaler MPX and VPX appliance.

I have made a summary in bullets so you can get a quick overview what the guide covers. I recommend that you download the guide to read the entire content.

Overview

NetScaler® Security Best Practices for MPX and VPX

Citrix® NetScaler® MPX appliance is an application delivery controller that accelerates Web sites, provides L4-7 traffic management, offers an integrated application firewall, and offloads servers. Citrix® NetScaler® VPX is a virtual appliance that has all the features of NetScaler MPX appliance, runs on standard servers, and provides higher availability for Web applications including Citrix XenDesktop and XenApp. Utilizing both NetScaler MPX and VPX appliances, an organization can deploy the flex-tenancy solution that further optimizes Web application delivery infrastructure by separating high-volume shared network services from processor-intensive, application-specific services. Furthermore, a NetScaler appliance enables the seamless integration with Citrix OpenCloud Access that can extend a datacenter with the power of the Cloud.

To maintain security through the deployment lifecycle, Citrix recommends the following security considerations:

• PhysicalSecurity
• ApplianceSecurity
• NetworkSecurity
• AdministrationandManagement

Deployment Guidelines

The following are the organizational security considerations and recommendations for the deployment of a NetScaler appliance:

Physical Security

• Deploy the Appliance in the Secure Server Room
• Protect the Front Panel and Console Port from Unauthorized Access
• Protect Power Supply

Appliance Security

• Secure the Server operating system that Hosts a NetScaler VPX Appliance
• PerformRemoteSoftwareUpdates
• FollowSecureLifecycleManagementPractices

Network Security

• Consider using an X.509 Certificate from a Reputed Certificate Authority for the Internet Facing Web Application
• Use Transport Layer Security when Accessing an Administrator Interface
• Use a Non-routable Management IPAddress
• Configure a High Availability Setup
• Configure Network Security Domains
• Use Stateful Firewall Protection

Administration and Management

• Create an Alternate Super User Account
• Change Password for the nsroot Super User Account.
• Follow Best Practices for the Implementation of a NetScaler Appliance
• Use Access Control
• Set up Secure Communication Between Peer Appliances
• Configure Other Accounts Remotely
• Configure Logging to External NetScaler Log Host
• Add SNMP Managers
• Use SNMP v3 Security Features
• Configure NTP
• DisableSSLv2Redirect
• DropinvalidHTTPrequests
• DisableSSLRenegotiation
• Whitelist HTTP headers
• Disable Layer 3 Mode
• Consider Using Application Firewall in a NetScaler Platinum Edition Appliance

NetScaler-FIPS Recommendations

• Change FIPS Crypto Card Passwords
• Store the HSM Password in a Secure Location

Access Gateway Enterprise Edition Security Recommendations

• Use Default Deny
• Use SSLv3/TLS Communication Between Servers
• Use the Intranet applications feature

Application Firewall Security Recommendations

• Deploy the Appliance in the Two-arm Mode
• Use Default Deny

Download the - Secure Deployment Guide for NetScaler MPX and VPX Appliances here