Archive for February, 2012

Citrix Receiver 5.5 for Apple iOS

Written by Thomas Poppelgaard. Posted in Receiver

Description

If your company uses Citrix to host applications, you can use Citrix Receiver to check your email, review documents, tune into project dashboards, and approve expenses from your iPad or any other device. Just ask your help desk for the URL to set up Receiver. If your company doesn’t use Citrix yet, you can still install Citrix Receiver and try a demo of virtual environments (http://citrixcloud.net/).

What you can do with Citrix Receiver:

• Access your applications and Windows desktop at your office, home, or on the road

• Keep your information stored on your provider’s secure servers, not on your device

• Move from desktop to tablet to smartphone

For more information on Citrix Receiver, go to http://citrix.com/receiver. If you’re looking for an app to connect to your Mac or PC, be sure to try GoToMyPC, the remote desktop app by Citrix Online. …More. Citrix Systems, Inc. Web SiteCitrix Receiver. Support.

What’s New in Version 5.5

✓ RSA SoftToken integration

✓ Client Certificate Support

✓ Enhanced Graphics/Video

✓ GPS and sensor remote into session

✓ CloudGateway Express (StoreFront Services)

✓ SaaS App support

Download Citrix Receiver 5.5 for iPhone here http://itunes.apple.com/dk/app/citrix-receiver./id363501921?mt=8

Templates in Citrix XenServer remember mr. SID and mrs. SYSPREP

Written by Thomas Poppelgaard. Posted in XenDesktop, XenServer

My experience using templates in XenServer together with XenDesktop

The other day i was doing a Proof of Concept where i help some ppl building a Citrix environment containing multiples Windows Server 2008R2 servers and some Windows 7 machines. I build 1 VM with Windows Server 2008R2 patched it up to latest hotfixes from MS and then  converted into a template, that i could use as a OS template for my new VM’s i attend to build for VM’s that was needed for a Domain Controller, Citrix Provisioning Server, XenApp Controller, XenDesktop Controller, File server, SQL server well you get the picture.

I build a new domain with some XenApp 6.5 servers, file servers, provisioning, sql, file servers and everything runs smooth and fast off course its new and clean build =O) then when i wanted to build a Citrix XenDesktop Controller the software installed fine and  smooth as it has done multiple times i have build this. When i then wanted to connect to a SQL i got some errors, i troubleshooted it and it seems so weird the SQL issues i had. Well and nice and easy turn was building the SQL express that you can choose within Citrix XenDesktop ISO. I placed the SQL express where i installed the Citrix XenDesktop Controller software. Then lets get things up and running and create and database … new bug.. started to troubleshoot again… hmm. I noticed that all the machines had the same SID that is used when I build them from the template. The solution was building a fresh VM with Windows Server 2008R2, patched it and then install Citrix XenDesktop and then i could connect to the external SQL or to its build-in SQL express if i had chosen that.

I got my lesson learned from Mr. SID.

The case where SID duplication would be an issue is if a distributed application used machine SIDs to uniquely identify computers. And using the machine SID in that way doesn’t work just for the fact that all DC’s have the same machine SID. Citrix XenDesktop relies on unique computer identities either uses computer names or computer Domain SIDs (the SID of the computer accounts in the Domain).

The right way of building a template in XenServer

So the SID really does matter. Prior to taking your clone or image, just remember to use Sysprep as follows:

1) Run Sysprep (on Windows Server 2008 this is located in c:\Windows\System32\Sysprep\Sysprep.exe)
2) Ensure ‘System Out-of-Box Experience (OOBE)’ is selected
3) Tick the ‘Generalize’ option (this resets the SID)
4) Select ‘Shutdown’ from the Shutdown Options.
5) Once the machine has shutdown, take your image and you are good to go!

Good stuff to read about mr. SID

Mark Russinovich explains The Machine SID Duplication Myth (and Why Sysprep Matters)
http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx

I used PSGetSID from Microsoft Mark Russinovich http://technet.microsoft.com/en-us/sysinternals/bb897417.aspx to see that all my VMs from the template had the same SID.

RES Automation Manager 2012

Written by Thomas Poppelgaard. Posted in Automation Manager, Citrix, Dell, HP, IBM, Microsoft, Provisioning, RES Software, SCCM, XenApp, XenDesktop, XenServer

RES Software have released RES Automation Manager 2012. RES Automation Manager now supports Linux and better integration with Microsoft System Center. In the following article i will describe whats new in RES Automation Manager 2012.

Whats new in RES Automation Manager 2012

RES Automation Manager 2012 introduces the RES Automation Manager Agent for Linux Operating Systems. With this Agent, you can execute the following new RES Automation Manager Tasks on machines running Linux Operating Systems:

  • Linux Command (Execute) (“Task “Linux Command (Execute)
  • Linux Computer (Reboot, Shutdown) (“Tasks “Linux Computer (Reboot, Shutdown)
  • Linux Resource (Download) (“Task “Linux Resource (Download)RES Automation Manager Agents for Linux need to be installed with a separate installation file. The RES Automation Manager Agents for Linux will run on the following Linux Operating Systems:
  • Red Hat Enterprise Linux release 4: 4.5 and higher
  • Red Hat Enterprise Linux release 5: 5.3 and higher
  • SUSE Linux Enterprise Server release 10: versions higher than 10.0
  • IBM AIX 5L: version 5.3

Licensing: Evaluation licenses valid for 45 days

When you install RES Automation Manager 2012, 75 evaluation licenses are provided automatically. These evaluation licenses are now valid for 45 days, instead of 60.

New RES Automation Manager Dispatcher: Dispatcher+

RES Automation Manager 2012 introduces a new Dispatcher that has been developed using the latest Microsoft tools. This has enhanced the Dispatcher with the following capabilities:

  • Improved scalability: The Dispatcher+ is no longer limited to 150 concurrent connections.
  • Native 64-bit installer.
  • Resource integrity check: When the Dispatcher+ starts, an integrity check is now performed on the available Resources in the Resource cache of the Dispatcher+. This ensures that Agents can always download valid Resources from the Dispatcher+.
  • The availability of a Web API provides full support for building and deploying RESTful and SOAP web services. This allows you to integrate Job scheduling in external systems.
  • The Dispatcher+ logs all events in the Event log, which can be viewed with e.g. the Event Viewer that is part of the Microsoft Windows Operating System.The new Dispatcher requires the installation of Microsoft .NET Framework 4 (full version) on all machines hosting a Dispatcher. Please make sure to update all Dispatcher hosts with this version before installing or upgrading to RES Automation Manager 2012

New RES Automation Manager Upgrade Pack

RES Automation Manager 2012 introduces a new Upgrade Pack: the Upgrade Pack now consists of a standalone executable file. This differs from Upgrade Packs of previous releases of RES Automation Manager, in which you could upgrade your RES Automation Manager environment by importing a .WUP file in the Console. The RES Automation Manager 2012 Upgrade Pack can also be used on machines on which no Console has been installed.

As a result of the new Upgrade Pack, the buttons Update Wizard and have been removed from the node Infrastructure > Datastore > Setup > Components in the Console.

If necessary, it is now possible to downgrade to a previous version of RES Automation Manager by right-clicking the node Infrastructure > Datastore > Setup > Components and choosing Downgrade (WUP).

The RES Automation Manager 2012 Upgrade Pack needs to be deployed manually and is not suitable for unattended installations.

RES Automation Manager 2012 upgrade requirements

  • RES Automation Manager 2011 SR3 or later
  • Microsoft Windows XP SP3 Professional or later (x64/x86)
  • Microsoft Windows Installer 3.1
  • Microsoft .NET Framework 4.0 or later: Client Profile is the minimum requirement for the machine on which the Upgrade Pack is run; Full Version (Client Profile and Extended) is required for all Dispatchers. Microsoft .NET Framework 4.0 Full Version can be installed on your Dispatchers from the Console.

RES Automation Manager samples for RES Automation Manager 2012

RES Automation Manager introduces a set of samples that make it easier to perform certain IT tasks. These samples are Building Blocks of predefined Modules and include hypervisor Modules, Linux Modules and Microsoft Windows Modules. After importing these Building Blocks into your RES Automation Manager environment, you can adapt the predefined Tasks to your situation if necessary.

The samples are included in the file RES-AM-2012-Samples-6.5.0.0.zip, which can be downloaded from the support portal.

The samples cover the following:

  • Linux Tasks:
    • Application Management
    • Disk Management
    • Network Management
    • Security Management
    • Service Management
    • System Management
    • User Management
  • Hypervisor Tasks: These Tasks allow you to manage snapshots and VMs on:
    • VMware vSphere Hypervisor
    • Microsoft Hyper-V Server
    • Citrix XenServer
  • Additional Tasks:
    • Citrix XenApp 6.5 Unattended Deployment
    • Write Event to Microsoft Windows Event Log

Support for Bare Metal OS deployment using WDS and RES Automation Manager

When deploying new workstations or servers, Bare Metal OS deployment usually is the first task that is performed. This task can now easily be carried out by combining Microsoft Windows Deployment Services (WDS) and RES Automation Manager.

For more information about Microsoft Windows Deployment Services, please refer to the Windows Deployment Services Getting Started Guide, available at http://technet.microsoft.com/en- us/library/cc771670(WS.10).aspx.

For more information about Bare Metal OS deployment using WDS and RES Automation Manager, please refer to the chapter Appendices\Best Practices\Bare Metal OS deployment using WDS and RES Automation Manager of the RES Automation Manager 2012 Administration Guide, available at http://support.ressoftware.com/automationmanageradminguide2012.

Variables

RES Automation Manager 2012 introduces Variables.

When configuring a Task, the values of many fields can now optionally be replaced with Variables. Similar to parameters, Variables function as placeholders for customer-specific values, such as, for example, server names, passwords or credentials. Different from parameters however, Variables are resolved at the moment of Job execution, rather than at the moment of Job scheduling.

The global values of Variables can be set up at Infrastructure > Datastore > Settings > Global Variables. These values are inherited by default by all Teams and Agents, but exceptions for individual Teams and Agents can be set up on the Team’s Team Variables tab and the Agent’s Agent Variables tab.

Team Variables and Agent Variables allow “owners” of a specific Team or Agent to override the Global Variables by specifying a custom-value. This makes Variables especially useful for use in multitenant RES Automation Manager sites, because it makes it easier to manage different settings for different customers and assigned projects, and to exchange Modules, Projects and Run Books with other branches of an organization.

Example

You can set up Global Variables to specify a Domain, Security Context and Domain controller for usage in a Task Manage Active Directory Computer. This creates a generic Task that can be used by all customers in your multitenant site. “Owners” of a specific Team or Agent at the customer site can override the global values of these Variables by specifying a custom-value that only applies to their site. When the Task is executed, the Task automatically gets the correct values that applies to the individual customer site. Depending on the hierarchy of these Variables, these can be the global values, Team-specific values or Agent-specific values.

Video tutorials

As of RES Automation Manager 2012, video tutorials are available that will help you quickly start using RES Automation Manager. These tutorials cover a broad range of subjects, from planning, installing and setting up an environment to using the functionality of RES Automation Manager.

Video tutorials can be accessed from the Help:page8image18472page8image18840

Custom Properties from previous versions of RES Automation Manager will automatically be migrated to Variables in RES Automation Manager 2012. Because names of categories in Variables must be unique, any categories in Custom Properties with the same name will be merged into one category in Variables and any existing Custom Properties objects in these categories will be categorized in this category.page8image25128

A complete list of all available video tutorials by category can be found in the Help, by clicking Help > Video Tutorials from the menu bar of the Console.

Depending on availability, individual tutorials can be accessed from the matching Help topic, by clicking “View tutorial”.

New Tasks in RES Automation Manager 2012

Task “Linux Command (Execute)”

At Repository > Modules, a new Task has been added to the library folder Linux: Execute Linux Commands. With this Task, you can run commands on Agents running on Linux Operating Systems.

Scripts that you run on the RES Automation Manager Agent for Linux using the Task Execute Linux Command cannot include reboot and shutdown commands. Use the Tasks Reboot Linux Computer or Shutdown Linux Computer instead. See Tasks “Linux Computer (Reboot, Shutdown)” (on page 6).

The library Linux and its Tasks will only be available in the Console if your RES Automation Manager environment contains at least one RES Automation Manager Agent for Linux.

Tasks “Linux Computer (Reboot, Shutdown)”

At Repository > Modules, the following Tasks have been added to the library folder Linux: Reboot Linux Computer and Shutdown Linux Computer. With these Tasks, you can reboot or shut down Agents running on Linux Operating Systems automatically. A restart is often required after the installation of new software. These Tasks can also be useful after the execution of a Task Execute Linux Command. See Task “Linux Command (Execute)” (on page 6).

The library Linux and its Tasks will only be available in the Console if your RES Automation Manager environment contains at least one RES Automation Manager Agent for Linux.

Task “Linux Resource (Download)”

At Repository > Modules, a new Task has been added to the library folder Linux: Execute Linux Commands. With this Task, you can download Resources to Agents running on Linux Operating Systems.

The library Linux and its Tasks will only be available in the Console if your RES Automation Manager environment contains at least one RES Automation Manager Agent for Linux.

Tasks “Microsoft System Center Configuration Manager (Distribute Software, Query Client)”

At Repository > Modules, the following Tasks have been added to the library folder Provisioning: Distribute Software with Microsoft System Center Configuration Manager and Query Microsoft System Center Configuration Manager Client. You can find these Tasks in the Task library Provisioning.

Microsoft System Center Configuration Manager allows you to distribute, configure and manage software across virtual, distributed and mobile environments. RES Automation Manager supports Configuration Manager 2007 and 2012.

  • With the Task Distribute Software with Microsoft System Center Configuration Manager, you can deploy software distribution packages on Agents on which a Configuration Manager Client is running.
  • With the Task Query Microsoft System Center Configuration Manager Client, you can:
    • Create status reports of Configuration Manager clients, including client version, cacheoptions, service states, etc.
    • Obtain an overview of all software distribution packages that were advertised to Configuration Manager clients, including local status of the advertisement, last run date and exit code.

Tasks “RES Automation Manager Job Results (Delete, Export)”

At Repository > Modules, the following Tasks have been added to the library folder RES Automation Manager: Delete RES Automation Manager Job Results and Export RES Automation Manager Job Results.

    • With Delete RES Automation Manager Job Results, you can clean up the Datastore from Job results that are no longer relevant, for example because they have become obsolete through Snapshot Intelligence or because they are the results of recurring Jobs.
    • With Export RES Automation Manager Job Results, you can export Job results to XML files. This allows you to back up Job results for review purposes. This Task is especially useful in combination with the Task Delete RES Automation Manager Job Results, in which you first back up certain Job results by exporting them to zipped XML files, and then clean up the Datastore by deleting them.In these Tasks, you can delete or export Job results from the Datastore, based on a combination of criteria:
    • The type of Job that was performed (recurring/non-recurring)
    • The relevance of the Job results (actual Job results/Job results that have become obsoletethrough Snapshot Intelligence)
    • The Agent(s)/Team(s) that executed the JobThe period in which the Jobs were executed

Task “RES Automation Manager Team Membership (Change)”

At Repository > Modules, a new Task has been added to the library folder RES Automation Manager: Change RES Automation Manager Team Membership. With this Task, you can add or remove Agents from a Team, and offers a more dynamic way of adding and removing Agents to and from Teams.

This Task is typically used in combination with a Task Query Installed Programs in which an evaluator determines whether the succeeding Task Change Team Membership should be executed.

For example, suppose you want to add an Agent to the Team Office if Microsoft Office is installed on the Agent. You can achieve this by setting up a Module that contains the following:

  • A Task Query Installed Programs with an evaluator for Microsoft Office that fails the Query if it does not return results.
  • A Task Change RES Automation Manager Team Membership with a condition that executes the Task if the status of the previous Task is Completed. This Task adds the Agent to the Team Office.When the Module is executed, the Agent(s) that execute the Module will be added to the Team Office if Microsoft Office is installed; if not, they will not be added to the Team.
page9image15768

Enhancements and Improvements

Agents: Agents no longer shown as offline when using IBM DB2

When using an IBM DB2 database, all Agents were shown as being offline in the Console. This did not have any consequences for the functioning of these Agents: in reality, they were online and all RES Automation Manager functionality was available. This has been fixed. All online Agents will now also be shown as being online.

Agents: Delete Job history of Agents

At Infrastructure > Agents, it is now possible to delete the entire Job history of individual Agents.

If many snapshots of an Agent are made, for example by using a provisioning server, the Job history of such Agents can become very large and may contain many obsolete entries. In such situations, it can be desirable to clean up the Job history of the Agent.

For this purpose, a button Delete Job History has been added to the History tab of the Agent Properties window, which is available when viewing the properties of an Agent.

It is also possible to delete the Job history of an Agent at Infrastructure > Agents (right-click the Agent, select Delete Job History).

Further informations about RES Automation Manager 2012

For the full release notes read the informations from RES Automation Manager 2012 release notes which can be downloaded from the client portal at www.ressoftware.compage9image16040
page9image16312

Published Desktops do not Recognize Dual Monitors in XenApp 6.x

Written by Thomas Poppelgaard. Posted in XenApp

Symptoms

The published Desktops in XenApp interpret two displays on a computer as one display, as shown in the following screen shot:

Cause

A published Desktop only identifies the second monitor when configured to launch in full screen mode, on the initial launch.

Resolution

To resolve this issue the published Desktop should be configured to launch in full screen mode.

To configure the published Desktop to launch in full screen mode, complete the following steps:

  • In the Citrix Delivery Services Console under the Applications node, locate the target published desktop.
  • Right-click on the target published desktop, and select Application Properties, as shown in the following screen shot:
  • Select the Appearance node in the Application Properties dialog box.
  • Select Full Screen for the Session Window Size.
  • Click OK, as shown in the following screen shot:
  • Create a new session.
  • After you log on to the published desktop, right-click on the desktop and select Screen Resolution. The server should display 2 monitors, as displayed in the following screen shot:

 

Missing ICA Latency Data in Desktop Director for Citrix XenDesktop / XenApp

Written by Thomas Poppelgaard. Posted in XenApp, XenDesktop

Symptoms

Windows Remote Management (WinRM) is correctly configured on the desktop machine; this is displayed by Activity and HDX information appearing. Desktop Director is showing dash (-) for ICA latency under the Session Details panel.

Cause

The ability to retrieve ICA latency information depends on DCOM security permissions. The Desktop Director user might not have the necessary permissions to retrieve this data.

Resolution

  • Log on as administrator, open command prompt on the desktop machine, and run comexp.msc, as displayed in the following screen shot:
  • Open Console Root > Computers > My Computer > DCOM Config > Citrix PortICA COM Server
  • Right-click and select Properties, as displayed in the following screen shot:
  • Select the Securities tab. For the Launch and Activation Permissions, select Customize and click Edit, as displayed in the following screen shot:
  • Click Add and add the Desktop Director user, ensuring that the Local Launch and Local activation permissions are set. Once these permissions have been applied, Desktop Director displays the ICA latency information.

More Information

Enabling WinRM for Desktop Director

This document applies to:

  • XenApp 6.5 and XenDesktop 5.5

Recent Comments

Server 2016 Migration

|

Hello I wish to to share a comment here concerning you to definitely be able to inform you just how much i personally Loved this particular study. I have to elope in order to aTurkey Day time Supper but desired to leave ya an easy comment. We preserved you Same goes with be returning subsequent function to read more of yer quality articles. Keep up the quality work.

Server 2016 Migration

MarilynToush

|

This message is posted here using XRumer + XEvil 3.0
XEvil 3.0 is a revolutionary application that can bypass almost any anti-botnet protection.
Captcha Recognition Google, Facebook, Yandex, VKontakte, Captcha Com and over 8.4 million other types!
You read this – it means it works! 😉
Details on the official website of XEvil.Net, there is a free demo version.

Server 2016 Support

|

Wonderful website. A lot of useful info here. I am sending it to a few friends ans also sharing in delicious. And obviously, thanks for your sweat!

Server 2016 Support

Thomas Poppelgaard

|

Thanks Jose, I have corrected the map plus updated the map so 29 datacenters are now alive.

Jose Brenes

|

Your map of Australia is wrong. You have put the state of Victoria inside the West Australian state.