VMware Horizon Mirage RES Automation Manager Integration

Leave a reply

So in my previous post “VMware Horizon Mirage RES Workspace Manager Integration” I covered the simplicity of integrating Workspace Manager with Mirage…

The good news is that RES Automation Manager and Service Orchestration integrate just as seamlessly.

Again if you have integrated Automation Manager and/or Service Orchestration with VMware View, Citrix XenDesktop or even a good old sysprep deployment before then this is really nothing new.

  • Install the Automation Manager agent on the Mirage reference machine
  • Locate the agent in the Automation Manager management console and open its properties
  • Click on Prepare for Image and following the instructions (you can choose to run automation tasks when agents are first invoked).

AMAgentPrepare

Note that if you set a runbook/project to run when the Mirage client is “layered”, this job will run on every subsequent Mirage re-layering or layer update. – We found this useful in a hotdesk and/or student environment as we run delprof2 to clear any local user profiles or any profiles that didn’t remove properly (be nice if Mirage had an option to clean/remove local profiles).

Service Orchestration… Simple… Just install the Service Orchestration client on the reference machine, configure it to point to your environment.

So there you have it… Some more validation of how to combine the most exciting next gen deployment and management technology with the best user environment and system/service automation technology available today!

Fingers crossed our VMware Horizon Mirage business case is successful because I wouldn’t want to do it any other way!

VMware Horizon Mirage RES Workspace Manager Integration

Leave a reply

Probably one of the best acquisitions in end point computing (in recent times) was VMware’s crafty swipe for Wanova.

In my opinion VMware Horizon Mirage (formally Wanova Mirage) is the best next generation Windows deployment and management platform in the market today.

To learn more see: https://www.vmware.com/products/desktop_virtualization/mirage/overview.html

And for some more in depth info of their layering coolness see:

RES Workspace Manager
So we’re currently at the end of our pilot phase with Mirage and are now in that “anxious” Business Case phase. Like with any project you must set out clear success criteria. For us one of the key check boxes was compatibility with the RES product suite.

So the good news is that if you have integrated Workspace Manager with VMware View or Citrix XenDesktop before, it’s pretty much the same process.

Configure Workspace Manager to ‘Identify Agents By’ ‘Computer domain name and NetBIOS name’.

AgentsByNetBIOS

Simply install Workspace Manager on your Mirage reference machine as you would with your parent/golden VDI image and that’s it. Publish the base layer to your Mirage end-points and off you go.

Hardly worth blogging about I know but sometimes with something “new” people like a little validation.

Next up, VMware Horizon Mirage RES Automation Manager Integration! – Not hard either…

Using RES Workspace and Automation Manager with App-V 5.0

Leave a reply

At the time of writing this RES Workspace Manager and Automation Manager do not currently support App-V 5.0 and PowerShell 3.

This article is the work around… We are using RES WM and AM to publish and manager App-V 5 packages. I’m guessing there are other/better ways of doing this ;)

First of all using Automation Manager I created a new module called “App-V 5 Publisher”.  Within this a “Command” task (note, PowerShell 3.0 is not supported at this time).The script field has the following,

“”c:\windows\system32\WindowsPowerShell\v1.0\powershell.exe” “add-appvclientpackage -Path ‘$[AppPath]‘| Publish-AppvClientPackage -global | Mount-AppvClientPackage””

The ‘file extension of Script’ is the default ‘cmd’.

Note: I use a parameter called AppPath to which we pass a variable from Workspace Manager.

Under the Settings tab, I execute the command using the windows command interpreter and I specify a domain based service account with local admin access.

Note:  You need to ‘Load user profile’.

That’s all that’s required in Automation Manager.

Before the Workspace manager configuration I recommend you publish the app to your “test” machine which also has the WM management console… Un publish/remove when after the following steps.

In Workspace Manager, under Composition and Applications, create a new package (using the wizard if you prefer) and for the application path, browse/type the location of the published application (%programdata%\appv\etc\etc…

Configure the application as you would any other managed app. Note you can still use Process Interception, Zero Profiles, etc…

Under the Configuration options add a new Automation Task.

Now select the module you created in Automation Manager (above). You will be prompted to enter a parameter value for the module. Enter the path to your app-v package (Package.appv) on your content/network share.

Select ‘Skip if application executable was found’, ‘wait for task to finish before continuing’ and ‘Run before other actions’.

Click OK and ta-da, test away…

This is far from perfect but it works (for me anyway). My only recommendation at the moment would be not to publish packages with start menu/desktop shortcuts and use Workspace Manager for this. As the package is being published globally, other users of that workstation will be able to access the package (unless you implement other lockdown, etc).

It’s a start anyway!

The Power of a Service Store

Leave a reply

At work we have traditionally opted for a push “everything” to everyone and everywhere model with the desktop. This in my view is a legacy concept and can pigeonhole users in to a single “class” of user type.

For us (IT) it’s becoming increasingly challenging to manage the diverse range of users we have. From the task worker to mobile power user we can no longer “dictate” what people use to work/study.

One of the most exciting projects I think I’ve led in my time here is the introduction of the KUSS (Kingston University Service Store). With the KUSS we will (have already started to) change users into service consumers and empower our staff and students to control their workspace. This is achieved by providing a personal service catalogue, where services can be subscribed to and where the service will follow the user.

To give an example of how a small and simple service can dramatically improve the user experience, as well as save time and not have IT involved with the process…

One of our service store workflows has reduced one support task from an average 1 to 3 days response time down to 30 seconds!

Our academics often require the ability to have local administrator access on their managed workstations. The traditional process for this has been to,

  • Log a call with the service desk
  • Wait for the call to be escalated to the local support team
  • Wait for local support team to either remotely add the user to the local administrators group or visit the machine in person.

Now with the KUSS we are providing users with a self-service facility to grant local administration access on their local workstation without the service desk or IT being involved. In addition to this a job is automatically opened and resolved for the user on our helpdesk system (for audit purposes).

This is one of many “small” services that can have a big impact.

Of course a service store is much more than simple administration tasks… Application access, app delivery, drive mappings, printer access, storage and VM provisioning – Anything that can be automated/scripted can be turned into a service for users to “consume” and make life easier for IT – or at least allow us to focus on innovation rather than spending our time being reactive.

For those that are interested… We’re using RES Service Orchestration for the KUSS. I can’t think of a better product that brings self-service delivery and workspace management together.

The best way to empower a user is to give them nothing…

Dan.

KU vWorkspace Multi Session Initiator – Beta

Leave a reply

I’m pleased to be able to announce the public beta of my new vWorkspace session initialization tool for the purpose of load/stress testing vWorkspace deployments.

I say “my new” but Adam Wilden (works with me) brought a lot to the table too.

I’ve dedicate a page (with details and screenshots) HERE

Enjoy!