Finally its now supported to build a Citrix Provisioning Server 5.6.x or 6.0 on a VMware vSphere 5 solution.
Provisioning Server 5.6 and 6.0 Target Devices hosted on VMware vSphere 5.0 becomes unresponsive after Windows operating system restart (at a black screen with PXE)
- Or -
“hang” after “Found “!PXE” @ xxxx:yyyy” (with BDM).
Provisioning Server 5.6.x and 6.0 are now supported with vSphere 5 with an updated Bootstrap configuration change.
The workaround for this issue is to select Interrupt safe mode in the Bootstrap.
This needs to be performed in one of two places:
If you are providing the Bootstrap through the Provisioning Server:
In the Provisioning Server Console, right click on Configure Bootstrap, click on Options, and select Interrupt safe mode, as shown in the following screen shot:
If you are using the BDM boot ISO to provide the bootstrap to your Target Devices, perform the following:
Click on Start > Citrix > Boot Device Manager, as displayed in the following screen shot.
In the Specify Login Server screen, enter the necessary information for your environment, click Next.
On the Set Options screen, select Interrupt Safe Mode and click Next, as displayed in the following screen shot:
On the Burn the Boot Device screen, enter any relevant details for your configuration, select: Citrix ISO Image Recorder from Boot Deviceand select Burn, as displayed in the following screen shot:
Save the Boot ISO and/or move it to the VMware data store that your Target Devices have access to, and configure your Virtual Machines to start from the new Boot ISO you just created.
RES Software have announced an upcoming new product called RES HyperDrive which is an on-premise virtual appliance-based “follow me data” solution that’s similar to DropBox, Box, Citrix ShareFile, or VMware Octopus.
RES Software announced an exciting new addition to the RES Software portfolio that answers one of the biggest challenges users and IT face today — securing and compliant access to user data. Without an enterprise-class solution, users have adopted their own “Follow Me Data” solutions, and brought personal, public and cloud-based services into the office, bypassing structured corporate services with personal, consumer services. This has created risk for the business, and unless IT can provide seamless solutions to the user, the trend will continue.
RES HyperDrive is a secure way to deliver Follow Me Data and file-sharing with the enterprise-class security of on-premises technology. Available on any device, anywhere, RES HyperDrive empowers IT organizations to better serve an increasingly mobile, next-generation workforce that demands convenient access to data from personal devices, applications, and cloud-based services. RES HyperDrive has been built with the CIO, IT Admin and end user in focus.
To the CIO, RES HyperDrive answers one of the biggest challenges they face— the need for business users to access their data at work, at home, or on the road, regardless of device. As the Consumerization of IT (and ByoD) grows, it has led to trends like alternative form factors, architectures, devices and connectivity to be used for productivity by employees. Today’s CIO understands cloud-based, consumer-driven, file-sharing solutions are being brought into the enterprise, bypassing IT. He may be using them himself. This has created compliance, regulatory and security vulnerabilities.
IT administrators are tasked with delivering a Follow Me Data solution to their users and lines of business. That’s not easy with today’s choices. With budgets already under a microscope, IT is trying to become a strategic partner to the business. But without a solution that answers the concerns of the CIO (compliance, security etc.), they are faced with users simply finding their own solution. Without a secure, managed solution, admins are simply not empowered to deliver an infrastructure that meets the needs of everyone. Their users want access anywhere on their chosen devices, and their management must ensure everything is secure and compliant. In the face of IT not providing them something seamless, they have provided their own.
RES HyperDrive solves all of these levels of challenges. RES HyperDrive can be summarized as:
Anywhere Access – Accessible through Outlook, Windows Explorer, Mac Finder or a browser, users are able to access their data the way they want to, on their personal or corporate hardware. Full cross-platform support for Android, iOS (iPhone, iPad), Windows and Blackberry phones, using a simple app interface, connects the user to their data. Centrally viewed with a web interface, the RES HyperDrive online dashboard provides easy access to data and devices, and the flexibility to share data with approved external contacts
Secure Data – RES HyperDrive is based on premises to assure enterprise-class security. With optional Active Directory integration, RES HyperDrive provides local data encryption, remote theft protection and integrated backup to ensure that users’ data is thoroughly protected across all of their devices.
Seamless Integration – RES HyperDrive provides organizations on-premises, private cloud, data management capabilities. RES HyperDrive is flexible, and supports an organization’s existing storage infrastructure. Integration with Outlook provides attachment options for large files, reducing impact on messaging infrastructure.
Applications with .Net or Java components take long time to start.
When the user accesses the published XenApp application with .NET or Java component, first time user logon to the published application takes long time to appear after first click over the application. The application appears after a time out that varies and after appearing, the applications behave as expected.
In other cases, the application is started correctly but during scenarios such as execution or accessing different module of the application, this access might take more time to process or fail in some cases.
This behavior occurs when the servers where the applications are published do not have Internet access and these applications have some.NET or Java component certificate that must be verified. If the server does not have Internet access, then the .NET framework or Java component cannot access the crl.microsoft.com website to verify that the digital signatures that are used to sign the binaries for managed applications are valid. Each certificate check has a 15 second timeout in the .NET runtime implementation. Depending on what features are installed, this can add up to a minute of startup time for the application.
To avoid this behavior and resolve the application delay, you must change several options in the Internet properties Advanced tab on the servers, applying a GPO or manually through registry modifications
Open User Configuration > Administrative Templates > Windows Components > Internet Explorer > Internet Control Panel > Advanced Page.
The options that must be set to disable value are:
Check for publisher’s certificate revocation
Check for server certificate revocation*
Setting the following options through GPO policy and applying to all the users ensures that these changes are updated in the next registry modifications in the servers:
For Check for publisher´s certificate revocation:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
Default setting: 0x00023c00 (166432)
After manually setting disabled: 0x23e00 (146944)
After applying the GP preference settings: 0x002c9 (713)
For Check for server certificate revocation*:
Certificate Revocation Dword Key == 0
Once this is done, the application does not attempt to verify the certificate and the time out is not reproduced.
Citrix Consulting have created this great whitepaper that describes how you create High Availability for TFTP with Citrix Provisioning Services and Netscaler
Citrix Provisioning Services is a software streaming technology that allows servers and desktops to be provisioned and re-provisioned in real time from a single shared-disk image
1. The service is commonly integrated with Citrix virtualization solutions to optimize Operating System delivery and management. Often these solutions are critical to the operation of organizations and require high availability. Providing high availability for Provisioning Services requires designing each component of the service without a single point of failure across the network. The „bootstrap file‟, named ardbp32.bin, is a key component that must be delivered to Provisioning Services target devices in order for them to communicate with Provisioning Services over the network.
The bootstrap file is typically delivered via Trivial File Transfer Protocol (TFTP) services hosted on Provisioning Servers. This document focuses specifically on comparing high availability options fordelivery of the bootstrap file to target devices via TFTP. The advantages and disadvantages of each option are outlined as well as the steps to implement the load balancing options with NetScaler. The document scope does not include details of the implementation or operation of other aspects of Provisioning Services.