The new look of RES Software

Hot off the press: As previously announced, wonderful things are happening over at RES. Today 5pm CET, RES Software has changed the website, logo and messaging, but that’s not all. Product names and categorizations have changed too! More below. There are many other significant changes underway, which will be revealed over the course of this week. To help you make sense of it all, here is a quick breakdown on what’s going on so far:

  • New website. Have a look at the new, which is live now.
  • New logo. Gone is the old blue-white-black. You can view the new shaded logo in all it’s glory by clicking on the miniature in the upper left corner of this article.
  • New product suite: As of today, all the current products are considered part of ONE  suite, called the RES Dynamic Desktop Studio. See the illustration on the right.
  • The product now formerly known as RES PowerFuse will from today be known as the RES Workspace Manager, part of the Dynamic Desktop Stuido.
  • RES Wisdom will from today be known as the RES Automation Manager. also part of the suite
  • Orchestra aka Orchestraton Pack for Wisdom is now known as the Service Orchestration Module in the Automation Manager.
  • The Workspace Extender aka Subscriber will from today be known as the Virtual Desktop Extender, or VDX.
  • VDX will be available as a stand-alone product from January 2011.

All this information and more is available in the New RES FAQ, available here.

As mentioned there will be made more, important announcements during this week, so keep an eye out for them here at the ‘Guru. In the meantime, you can see what the  new names and logo’s for the components of the Dynamic Desktop Studio will look like. Click on the individual components to jump to the corresponding product page.

Source ;

There are a variety of ways to experience the power of RES Software solutions – check out the evaluation and free product downloads below.

RES Workspace Manager 2010 SR2 – Free 60 day trial version (formerly RES PowerFuse 2010 SR2)
Download a 60-day trial version of RES Workspace Manager 2010 and see how user workspace management software will work for your business. The trial version allows you to evaluate the Enterprise-, Standard- or MyWorkspace Edition of RES Workspace Manager 2010.

RES Workspace Manager 2010 SR2 Express Edition – Free Download (formerly RES PowerFuse 2010 SR2 Express Edition )
Download a copy of the free, production-ready Express Edition for delivering a personalized, secure and reliable user workspace to your end users. Supports up to 100 concurrent users.

RES Automation Manager 2011 RC – Free 60 day trial version (formerly RES Wisdom)
Download a free 60-day trial version of RES Automation Manager 2011 Release Candidate and see how run book automation for Windows will work for your business.

Posted in Uncategorized

Citrix Connector for System Center Configuration Manager 2007


Microsoft have recently jointly released the Citrix connector for ConfigMgr 2007.  Through this release, the ConfigMgr SDK has been used to extend and support the management of application services through XenApp.  Very cool indeed.

Here is the announcement. Links are below.

Citrix® XenApp™ 6 introduces integration with Microsoft System Center Configuration Manager 2007 R2 giving organizations a single, integrated view and management of all applications across the enterprise including on-demand apps by XenApp. The Citrix XenApp Connector leverages the Configuration Manager console to deploy and publish applications and updates to XenApp servers with zero disruption to users and extends the reach of Configuration Manager applications to a broader set of users, devices and access scenarios

Some resources for you:

  • Jointly authored whitepaper is available here
  • A Video Demo can be viewed here
Posted in Uncategorized

Three Steps to a PXE-Free XenDesktop on Hyper-V

I ran into an interesting situation last week while working with Tony Sanchez from our Global Microsoft Team. He was setting up XenDesktop 4 on Hyper-V 2008 R2. However, the lab he was at used a Windows Deployment Server (WDS) for image management and it relies extensively on PXE. Rather than modify the WDS to support the Provisioning Services PXE boot file, we decided the best solution was to make a boot ISO that will load the OS directly from the Provisioning Services host and then boot the guests from that ISO.


Since not all my readers are familiar with using the Boot Device Manager, I will set the stage. When configuring a virtual machine to boot off of a CD-ROM image for PVS, you need to do three things:

  1. Add a Legacy network card on the host since the Synthetic network adapter is not created until the Operating System loads.
  2. Configure the BIOS boot order so that CD-ROM is first in the list.
  3. Assign a bootable ISO image to the CD-ROM/DVD drive.
Take Note
The PXE boot option is required in order for the NIC Option ROM to stay resident in memory during the pre-boot process. This way, UNDI will be available to the boot device to properly initialize the NIC. Otherwise, the “API not found” message would be displayed by the boot device.

In deployments of XenDesktop where you have more than about 15 machines, the XenDesktop Setup Wizard (XDSW) is normally used to create and link the XenDesktops with Hyper-V. Unfortunately, the XDSW does not support all the possible VM configuration options when duplicating the source virtual machine. One of the properties that is not transferred to the new virtual machine is the ISO in the DVD drive. Normally, this behavior is the preferred because Hyper-V needs a special configuration to support sharing an ISO across multiple guests simultaneously (See this Technet article), which if not configured correctly can cause startup issues.

If you do not want to configure ISO sharing, you can use the VMM server and VMM library to copy the boot ISO to each virtual machine’s folder. If the ISO was large, I would say spend time setting up the sharing configuration; however, in this case the file itself is only 300K and copying it will eliminate the possibility of file sharing/locking issues.

Now you understand some of the challenges, I can tell you the three steps to a PXE-free Hyper-V deployment.:

  1. Create a PVS Boot ISO using the Boot Device Manager
  2. Import that PVS Boot ISO into the VMM Library
  3. Execute a PowerShell script

Step 1: Create a PVS Boot ISO

The Provisioning Services Boot Device Manager is a three-dialog wizard that lets you pre-configure the boot environment just like a PXE server would, except you can then write that to a drive or CD-ROM media. The Boot Device Manager is found on the Start menu of any provisioning server at All Programs >> Citrix >> Provisioning Services >> Provisioning Services Boot Device Manager.

I do not want to spend a lot of time discussing the various options or provide a tutorial on this utility; however, I will provide a few pointers. First, be sure to enable the “Citrix PVS Two-Stage Boot Service” and set it to start automatically on any servers you will use as the targets for the ISO image. Second, if you are using Windows 7, be sure to enable the PAE Mode on the second page of the wizard, like this:

Third, be sure to select Citrix ISO Recorder as the boot device (shown below) before burning the ISO image, lest you accidentally wipe out your local hard disk. For a complete guide on using the Boot Disk Manager, see this Citrix Support Article CTX121331.

Step 2: Import the ISO into the SCVMM Library

Take the ISO you created in Step 1 and save it to the folder where the SCVMM library stores are located. I created a new folder called ISOs at the same level as VHDs and placed the ISO in that folder. Next start the SCVMM Administrative Console and go to the Library tab. Select the MSSCVMMLibrary node and click Refresh on the context-menu to add the ISOs to the library as shown here:

Step 3: Execute the PowerShell Script

Next, you can copy the contents of the PowerShell script below and save it to a file called AttachISO.PS1. I realize that I am not yet a PowerShell guru, so I am aware that several optimizations and error checks could be made to this script. Feel free to modify it for your own use. My goal was provide a working example to help with this issue. The PowerShell script below does the following:

  1. Sets the boot order to CD, PXE (Legacy NIC), IDE, Floppy
  2. Copies the ISO image from the library to the VM’s folder
  3. Creates a DVD drive object at the IDE bus 1:0 if no DVD drive is found
  4. Removes any existing ISO and sets the ISO image to the one specified on the command-line
  5. For larger environments, it lets you know how many VMs it has left to process
AttachISO PowerShell Script
# Purpose:      Attach ISO image from VMM Server Library to Guest Virtual Machine
# Date Written: 12 April 2010
# Author:       Paul Wilson (no implied or expressed warranties)
# Usage:        AttachISO [UNC Path to ISO in Library] [VM Name to Match Criteria]

# Check for the two required arguments and offer command-line assistance if not found

if ($args -eq $null -or $args.Count -lt 2)
   write-output "Usage: AttachISO.ps1 UNC_fileName_ISO_File VMNameMatches"
   write-output "Example: .\AttachISO.ps1 ""\\SCVMM\MSSCVMMLibrary\ISOs\pvbt.iso"" ""Desktop"" "
   exit 1

# Grab the arguments and store them for later use

$ISOPath = $args[0]
$VMNameMatches = $args[1]

# Get the name of the SCVMM server we are running this on.
# The VMM server could be passed as a parameter as well.

$VMMServer = Get-VMMServer -Computername "localhost"

# Get the ISO image reference object using the ISO path provided earlier. 
# Using the full path guarantees the right object is found. 

$ISOImage = Get-ISO -VMMServer $VMMServer | where { $_.SharePath -eq "$ISOPath" }

if ($ISOImage -eq $null)
   write-output "Unable to find ISO: $ISOPath"
   exit 1

# Get the collection of VMs that match the name parameters supplied and output that information

$VMs = Get-VM | where { $_.Name -match "$VMNameMatches" }
if ($VMs -eq $null)
   write-output "No VMs match the pattern: $VMNameMatches"
   exit 1
   $LeftToGo = $VMs.Count
   if ($LeftToGo -eq $null)
      $matchString = "Only one VM matched the pattern: {0}" -f $VMNameMatches
      $LeftToGo = 1
      $matchString = "{0} VMs match the pattern: {1}" -f $VMs.Count, $VMNameMatches
    write-output $matchString

# This loop goes through each VM found and does the following:
#   1. Sets the boot order to CD, PXE Nic, IDE, Floppy.
#   2. Gets the DVD/CD drive object.
#   3. The script will copy the ISO image from the library to the VM's folder.
#      The copy is part of the Set-VirtualDVDDrive and New-VirtualDVDDrive cmdlets.
#   4. Creates the DVD drive object if none found and sets it to the ISO.
#   5. Removes any existing ISO and sets the ISO image to the one specified.
#   6. Outputs the number of VMs remaining to process. Added for large deployments. 

foreach ($VM in $VMS)
   $LeftToGo = $LeftToGo - 1
   Set-VM -VM $VM -BootOrder CD,PXEBoot,IDEHardDrive,Floppy
   $current_dvd = get-VirtualDVDDrive -VM $VM
   if ($current_dvd -eq $null -or $current_dvd.count -eq 0)
      $newDVD = New-VirtualDVDDrive -VM $VM -Bus 1 -LUN 0 -ISO $ISOImage
      $DVDResultMessage = "Created DVD Drive on {0}. {1} VMs left to go." -f $VM.Name, $LeftToGo 
      if ($current_dvd.Connection -ne "None")
         set-VirtualDVDDrive -VirtualDVDDrive $current_dvd -noMedia
         set-VirtualDVDDrive -VirtualDVDDrive $current_dvd -ISO $ISOImage 
         $DVDResultMessage = "Replaced existing media in DVD Drive on {0}. {1} VMs left to go." -f $VM.Name, $LeftToGo
         set-VirtualDVDDrive -VirtualDVDDrive $current_dvd -ISO $ISOImage 
         $DVDResultMessage = "Successfully attached ISO to the DVD Drive of {0}. {1} VMs left to go." -f $VM.Name, $LeftToGo
    write-output $DVDResultMessage
Posted in Uncategorized

Announcing App-V 4.6 RC and integration with Office 2010 Beta!


First of all, we are excited to announce the availability of App-V 4.6 RC! In August we announced the App-V 4.6 Beta. Since then we have taken in lots of customer feedback and continue to refine the App-V 4.6 release so that we can deliver a great product!  We invite you to check out the RC release by registering and downloading the App-V 4.6 RC release via Microsoft Connect, where you can also submit feedback directly to the team.

We’re not done though, in addition we’d like to share some great news and also announce our integration with Office 2010 Beta:

Microsoft Office 2010 Beta, Ready to be Sequenced With the Microsoft Office 2010 Beta Deployment Kit for App-V

As you know the Office team just completed a major milestone Microsoft Office 2010 Beta, congrats to the team!  Throughout the process of building Office 2010 the App-V and Office teams have been working very closely to make sequencing Office 2010 Beta possible with App-V 4.6 RC!  We have taken the feedback and requests from post-Office 2007 and App-V 4.5 releases, and have been hard at work implementing a solid integration experience for Office when App-V 4.6 releases in H1 2010.

So what’s Different when using Microsoft Office 2010 Beta and App-V 4.6 RC together?

Office 2010 has introduced a new piracy protection initiative, the Software Protection Platform (SPP) service.  This service uses a machine’s hardware characteristics and product key to activate the installation, which is performed during the first Office application launch.

Since the Office 2010 product activation is linked to the hardware on which Office is originally installed, customers who wish to deploy Office 2010 using App-V must physically install the SPP service on the sequencer machine before beginning the sequencing process – and on any client machines that will stream and run Office 2010.

Our engineering teams have collaborated to address the top customer issues that people were running into when virtualizing past versions of Office.   As a result, Office 2010 has a much more integrated user experience.  The Office 2010 integration delivers key productivity enhancements and a seamless user experience by enabling the following::

· Microsoft SharePoint Integration – You can open, edit, and save Microsoft Office documents using Microsoft SharePoint.

· Microsoft Outlook Fast Search – You can use Microsoft Windows Desktop Search to find specific messages in your inbox.

· MAPI Proxy – You can connect to your inbox using Microsoft Outlook Send To functionality.

· Microsoft Office Document Indexing – You can index your documents so that you can use Microsoft Windows Search to locate files.

· Virtual Mail Control Panel icon – You can use the Email icon in Control Panel to perform advance mail configuration.

· URL protocol handler – You can configure links in the browser and specify the appropriate associated Microsoft Office application.

· Send to Microsoft OneNote Printer driver – You can print documents to Microsoft OneNote.

To help customers facilitate this process, we have created the Microsoft Office 2010 Deployment Kit for App-V (Beta). The Deployment Kit contains both the required SPP licensing component and Office 2010 integration features.

And what’s even more exciting, you can get your hands on it now.

How Do I Sequence Microsoft Office 2010 Beta for App-V 4.6 RC?

1. Download Office 2010 Beta here

2. Download the Microsoft Office 2010 Deployment Kit for App-V (Beta)

3. Download App-V 4.6 RC on Microsoft Connect

4. Read the App-V recipe for sequencing Office 2010 Beta on Microsoft Connect.

For detailed information on whether your environment meets the requirements of Office 2010 and App-V 4.6 RC, please refer to the App-V recipe.

Please note: We are providing a recipe to support the sequencing and testing of these pre-release products on Microsoft Connect.  Please provide feedback via Microsoft Connect, by choosing FEEDBACK once logged into the App-V 4.6 Program.

We look forward to hearing about your App-V 4.6 RC and Office 2010 experience!

Posted in Uncategorized

Citrix Workflow Studio 2.0

I’m pleased to announce that Workflow Studio 2.0 is now available:

Download Workflow Studio 2.0 (MyCitrix login required)

This release has a number of great new features and is a seamless upgrade from version 1.x. Here are some of the key new features:

  • Native XenApp activity libraries (and many other additional activities)
  • Remote runtimes
  • Simplified management interface
  • Enhanced security features
  • Simplified installation and configuration
  • Improved SDK
  • Simplified workflow Designer
  • Globalization support

I will post some more blogs over the next few days with more details on the above features and will also be updating the CDN site with many new articles, so subscribe to the Workflow Studio blog and head over to the Workflow Studio CDN site and subscribe for updates on CDN as well.

Feel free to leave feedback in comments or email me directly.

Workflow Studio will be included with XenApp Feature Pack 2

Learn more about Citrix XenApp 5 Feature Pack 2

Posted in Uncategorized