XenDesktop 7.6, Windows 2012 R2, Office 365

 

When opening any Office 365 application before opening Internet Explorer 11 (IE11) Office will fail with file permissions error.

It turns out Office 365 uses the temporary internet folder location from IE11 as its path to open temp files into. IE 11 has now got a new path for these files:

%userprofile%\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5 – this Content.IE5 file does not exist until up have opened up IE11 first.

Even if you change the path in the user profile it ignores it and looks to use IE11 path regardless.

Solution:

Create group policy in IE11 (may have to load the IE11 admx files) which changes the path back to %userprofile%\AppData\Local\Microsoft\Windows\Temporary Internet Files

All works correctly once this applied.

 

Thanks to Andrew Hill – Senior Consultant, Experteq for the tip.

XenDesktop 7.6 Feature Pack 1 (Platinum Edition Below) Released

 

Features:

1. Session Recording - Session Recording enhances the ability for admins to actively monitor and record user sessions to simplify troubleshooting, accelerate issue resolution, evaluate personnel for training guidance, and monitor user behavior for compliance purposes.
   
2. Director 7.6.200 - This release includes controls to start and stop session recording (Session Recording is a feature in the Platinum Edition), as well as bug fixes.
   
3. HDX RealTime Optimization Pack 1.7 for Microsoft Lync - offers clear, crisp high-definition video calls in conjunction with Microsoft Lync®. This release adds support for Lync 2013 on Windows and Linux devices, plus new calling features.
   
4. License Server 11.12.1 for Windows - An optional component in Feature Pack 1. This release introduces the opportunity to participate in the Customer Experience Improvement Program.

• Note: that the components listed above are only the new items in Feature Pack 1. Even if you have already deployed 7.6, there are five components (beyond the items listed above) that have been updated or added since the initial 7.6 release.

Citrix PVS device BSOD 0x0000007B via SCCM build

 

After installing the Citrix PVS Target Device software via SCCM or some other command line tool the Provisioning Services Target Device software:

%drive%\%folder%\PVS_Device_X64.exe /s /v /qn /norestart

What can happen is via the command line installation (not via the GUI) the files are not copied to the correct place. The quick fix is after the install, via a new command line:

Copy “C:\Program Files\Citrix\Provisioning Services\drivers\*.*”  to “%windir%\System32\Driver”

Then copy the image to the PVS and good to go.

 

 

"Dave Colvin"

Copy a Citrix PVS Versioned Disk

 

If try and just cope the .VHD of a versioned vDisk you’ll get an error message about not disk found. What you need to do is copy more, rename, export and then import.

To simplify the process you can merge the VHD chain of the source vDisk or just copy more files now and do it after? Here is how:

• Copy all the versioned vDisk in the chain (*.vhd, *.ahvd, *.pvp NOT the *.lok)
• Rename the copied files as required

• Open the PVS console, right click the source vDisk, and choose ‘Export vDisk…’

• Choose the latest version in the ‘Export versions starting at’
• This creates a XML (manifest file) containing the entire information about the versions of that vDisk

• Rename the XML file
• Edit the XML file change all references of the source vDisk to the copied vDisk name
• You should have a set of VHD/AVHD/PVP/XML files with the same file name. And an XML which refers to the new VHD files
• Open the PVS console, right click the vDisk store, and choose ‘Add or Import Existing vDisk…’

• After a short delay a popup appears saying that the import was successful

Job Done.

 

Cheers Dave Colvin

http://dave.colv.in 

http://twitter.com/DaveColvin

Hat tip: http://www.out-web.net/?p=1177

Updated Citrix Receiver 4.2 PNA like experience

 

This is what the new PNA like experience looks like in the Start Menu of Windows 7. You can also get this on the desktop (but I have not shown this).

To get this you need to install the 4.2 receiver with the following command line. I cant stress enough how specific the CAPS, format and order this command line is.

Replace the section in yellow with your storefront server, ALSO note the /discover in the command line (see below where you can get this exact link from the Storefront server .CR file).

CitrixReceiver.exe /silent ADDLOCAL="ReceiverInside,ICA_Client,SSON,AM,SELFSERVICE,USB,DesktopViewer,Flash,Vd3d" ENABLE_DYNAMIC_CLIENT_NAME=Yes ALLOWADDSTORE=S ALLOWSAVEPWD=S STARTMENUDIR=\CitrixXenApps\ /INCLUDESSON /STORE0="Store1;https://storefront.COLV.IN/Citrix/Store1/discovery;On;Store1"

REBOOT, you need this as the SSOSVR.EXE needs to be running as seen below.

Additionally you need all the following:

1. TO BE USING HTTPS and a valid Cert.
2. You need the XML trust in both XenDesktop OR older XenApp
3. Your StoreFront server needs to be in ‘Local Intranet’ or ‘Trusted Sites’ in IE
4. Enable “Automatic Logon with current user name and password” is enabled in local Intranet if that is what you are in (see above).
5. Enable “Automatic Logon with current user name and password” is enabled in Trusted Sites if that is what you are in (see above).

 

Once it works, IE should auto logon as shown below.

 

If you don't know the URL above in yellow download the .CR file and it is highlighted below

 

This is the connection receiver once installed.

 

To get the Start Menu to populate this is the command line. It should do it automatically on reboot.

"C:\Program Files (x86)\Citrix\SelfServicePlugin\SelfService.exe" –showAppPicker

Once working correctly the Citrix Receiver in the notification area should logon automatically.

 

This is an update from the older article http://davestechnology.blogspot.com.au/2013/12/you-want-back-pna-program-neighbourhood.html

XenDesktop and XenApp VDA Exclusion

 

The default Citrix Virtual Delivery Agent installation includes several optional components that may not required, for example when upgrading the v7/v7.1 VDA software. They can be excluded using an installation command line.

The options are:

• Personal vDisk
• Machine Identity Service
• Citrix User Profile Manager
• Citrix Universal Print Client.

The command line is:

• XenDesktopVDASetup.exe /EXCLUDE “Personal vDisk”, “Machine Identity Service”
• etc

There is no help on the command line, thanks Citrix !

Links

Upgrading VDA: http://support.citrix.com/proddocs/topic/xenapp-xendesktop-75/cds-xd-upgrade-xd7-to-7-1.html#manual-phys-vda-upgrade

Article about the VDA: http://support.citrix.com/article/CTX140972

Citrix PVS 7.6 Wizard crashes “application was unable to start correctly”

 

After installing Provisioning Server 7.6 on Windows 2008 R2 SP1 (patched to current) you start the Configuration Wizard you receive the following error: “The application was unable to start correctly (0xc01500002)”

This error is caused by the program requiring Visual C++ 2008 Redistributable Package.

Download and install it to run the PVS Configuration Wizard.

Package: https://www.microsoft.com/en-us/download/details.aspx?id=2092

 

Hattip: http://www.vdnieuwenhof.eu/knowledge-base/the-application-was-unable-to-start-correctly-0xc01500002-configwizard-exe/

Change XenDesktop 7.6 SQL Server

If you setup the SQL Express edition and need to move it for production. This is how.

Open PowerShell as and Administrator:

Add-PSSnapin Citrix*
Get-LogDataStore
Get-MonitorDataStore

They BOTH output something like this:

ConnectionString : Server=XDC-PROD01\SQLEXPRESS;Initial Catalog=CTX-XD7-PROD;Integrated Security=True

DataStore        : Site


DatabaseType     : SqlServer


Provider         : MSSQL


SchemaName       : Monitor


Status           : OK

ConnectionString : Server=XDC-PROD01\SQLEXPRESS;Initial Catalog=CTX-XD7-PROD;Integrated Security=True

DataStore        : Monitor


DatabaseType     : SqlServer


Provider         : MSSQL


SchemaName       : MonitorData


Status           : OK

Copy the contents of the BOLD above to a string and change the server name and instance details with server= in the prefix.

$CS = “server=REMOTE-PROD01\SQL02;Initial Catalog=CTX-XD7-PROD;Integrated Security=True”

• Set-LogSite -State Disabled



• Set-LogDBConnection -DataStore Logging -DBConnection $null



• Set-MonitorDBConnection -DataStore Monitor -DBConnection $null



• Set-MonitorDBConnection -DBConnection $null



• Set-AcctDBConnection -DBConnection $null



• Set-ProvDBConnection -DBConnection $null



• Set-BrokerDBConnection -DBConnection $null



• Set-EnvTestDBConnection -DBConnection $null



• Set-SfDBConnection -DBConnection $null



• Set-HypDBConnection -DBConnection $null



• Set-ConfigDBConnection -DBConnection $null –force



• Set-LogDBConnection -DBConnection $null –force



• Set-AdminDBConnection -DBConnection $null –force

Move the database between the servers.

On the SQL server create the account(s)

sqlcmd -S env3-sql2\AON -q "create login [domainName\ddcName$] from windows"

set-ConfigDBconnection -dbconnection $cs

set-AdminDBconnection -dbconnection $cs


set-LogDBconnection -dbconnection $cs


set-AcctDBconnection -dbconnection $cs


set-BrokerDBconnection -dbconnection $cs


set-EnvTestDBconnection -dbconnection $cs


set-HypDBconnection -dbconnection $cs


set-MonitorDBconnection -dbconnection $cs


set-ProvDBconnection -dbconnection $cs


set-SfDBconnection -dbconnection $cs


set-LogDbConnection -DataStore logging -DbConnection $cs


set-MonitorDbConnection -DataStore monitor -DbConnection $cs


set-LogSite -State Enabled

 

Citrix StoreFront for dummies (v2x)

StoreFront key components

Authentication service: An integral part of StoreFront,  authenticates users to XenDesktop sites, XenApp farms. The authentication service ensures that users only need to log on to StoreFront/Receiver once.

Store: Retrieves user credentials from the authentication service to authenticate users to the components providing the resources. The store enumerates and aggregates the resources currently available from XenDesktop sites, XenApp farms. Users access the store through Citrix Receiver or a Receiver for Web site.

Application Subscription Store (Data Store):This store saves and indexes the application or desktop subscriptions of the users on a per - StoreFront Store basis. Tthe new Application Subscription Store uses the built-in Microsoft Windows Extensible Storage Engine to store details of users’ app subscriptions locally on StoreFront servers. When joining a StoreFront server to a Server Group the replication of data between all members is configured automatically.

Receiver for Web site:This site enables users to access stores through a webpage. If a version of Receiver installed locally it can be upgrade or if not detected it can be installed. Where Receiver cannot detected or installed the HTML5 client can start in compatible web browsers (IE over HTTP, Chrome/Firefox over HTTP/S).

Desktop Appliance site: Desktop Appliance sites provide users of non-domain desktops with an experience similar to that of user with domain-joined desktops. The web browsers is configured to start in full-screen mode displaying the logon screen for a Desktop Appliance site.

XenApp Services site: Used as a service to support PNAgent (Receiver for Enterprise), seamless desktop experience, Fast Connect, and Desktop Lock for repurposed PCs. or other devices like IPAD etc.

Authentication to StoreFront

1. User enters username and password on StoreFront server. The authentication service validates (the user credentials) with a domain controller.
2. StoreFront checks the data store for existing user subscriptions and stores them in memory
3. StoreFront forwards the user credentials as part of a XML query to the backend XenApp / XenDesktop
4. Delivery Controller validates (the user credentials) with a domain controller
5. Delivery Controller checks which resources have been published to this user within its database
6. Delivery Controller sends an XML response to StoreFront which contains all resources available for the user from the XenDesktop site
7. StoreFront sends the list of available resources including the existing subscriptions to the Citrix Receiver installed locally or displays them in Receiver for Web

A Non blank interface for new users

To avoid users from having a blank screen when they first logon, automatically subscribe users to a few core applications. Add KEYWORDS:Auto to the application or desktop description in XenApp or XenDesktop. Another option that can be used to organise applications is KEYWORDS:Featured. The Featured keyword only places apps in the Featured category

Local apps used via StoreFront

In addition the string KEYWORDS:prefer="application" can be used to specify that the locally installed version of an application should be used in preference to the equivalent delivered instance if both are available

Thanks to this white paper for the details, I have simplified it where I thought relevant : http://support.citrix.com/servlet/KbServlet/download/33432-102-697177/StoreFrontPlanningGuide.pdf 

Citrix HTML5 client on StoreFront Server

I put this together as official Citrix material is a bit ambiguous on what is needed, it is all there, but obtuse.

What is it? Receiver for HTML5 enables users to access desktops and applications directly within HTML5-compatible web browsers without needing to install Citrix Receiver.

StoreFront:

On the StoreFront use the Deploy Citrix Receiver task to configure the behaviour of a Receiver for Web site (HTML5 client) when a Windows or Mac OS X user without the Citrix Receiver installed accesses the site. By default, Receiver for Web sites automatically attempt to determine whether Citrix Receiver is installed when accessed from computers.

Specify the response of the Receiver for Web site if Citrix Receiver cannot be detected on a user's device.

• If you want the site to prompt the user to download and install Citrix Receiver but fall back to Receiver for HTML5 if Citrix Receiver cannot be installed, select Use Receiver for HTML5 if local install fails. Users without Citrix Receiver are prompted to download and install Citrix Receiver every time they log on to the site.
  
• If you want the site to enable access to resources through Receiver for HTML5 without download and install Citrix Receiver, select Always use Receiver for HTML5. With that option selected, users always access desktops and applications on the site through Receiver for HTML5, provided they use an HTML5-compatible browser. Users without an HTML5-compatible browser have to install the native Citrix Receiver.

XenApp and XenDesktop:

For local users on the internal network, access through Receiver for HTML5 to resources provided by XenDesktop and XenApp is disabled by default. To enable local access to desktops and applications using Receiver for HTML5, you must enable the ICA WebSockets connections policy on your XenDesktop and XenApp servers. XenDesktop and XenApp use port 8008 for Receiver for HTML5 connections.

Ensure your firewalls and other network devices permit access to this port.

Client browsers:

Receiver for HTML5 can only be used with Internet Explorer over HTTP connections. To use Receiver for HTML5 with Firefox over HTTPS connections, users must type about:config in the Firefox address bar and set the network.websocket.allowInsecureFromHTTPS preference to true.

Citrix Adaptive Display moving to GPUs

 

What is Citrix Adaptive Display and why should I care?

Before adaptive display there was Progressive Display which worked well back in the day, but if you wanted to tune it, it is was a manual dark art. It was often misconfigured resulting in a poor experience, so lets just move on.

Then came Adaptive Display, the first generation. It was based on progressive display but was auto tuning according to the available bandwidth and the capabilities of the client. Simply, it would use a different compression algorithm for moving images and still images and tune it on the fly.

Now there is Adaptive Display Second generation. It is now based on different codecs, the ‘SuperCodec’ from Citrix dynamically decide which compression is used for different parts of the screen. The most important codec is the H.264 deep compression codec known as HDX 3DPro. Add to this Desktop Composition Redirection.

If you want to offload you can also redirect Desktop Composition to the client if supported. This will work with the Microsoft applications like Internet Explorer, Office 2010+. You can also tune the quality of Desktop Composition Redirection can be configured in the following policy: Desktop_Composition_graphics_Quality

HDX 3DPro (H.264 Deep Compression codec) has now evolved and it can completely encode in host CPU. This new version, called the Deep Compression V2, uses even less bandwidth then before but hits the CPU harder. The load on the host side increases and can affect the scalability of the total solution, when CPU resources are limited or scalability is a concern in your environment you may need to tune this down or optimise it.

If you need to bring down the graphics performance you can turn on the legacy graphics mode policy to get the user density you are aiming for and scalability targets but this affects the user experience. And that kind of defeats the purpose of what we are aiming for.

So instead move to a Graphics Processing Units (GPU). The GPU can do the heavy graphics lifting.

In XenDesktop 7x you have the following options:

• Leverage the GPU directly (Either physically or through the Hypervisor GPU pass-through)
• Leverage the GPU indirectly through GPU virtualisation (Available by using Nvidia GRID and others)

Leveraging the GPU directly has been available for a while now but was one-to-one solution for Windows 7 VDI (Hosted shared desktops based on 2008 r2 etc. you could share a GPU with multiple sessions on the same server OS)

Graphics are first rendered and compressed in the GPU and then send down the client, so first the output of the GPU needs to be captured, compressed and tuned by the ICA client, this process is called screen scraping. Screen scraping, is not required when using a Nvidia GRID because it comes with an API which allows remote display protocols (ICA client) to access the frame buffer, (the encoding engine of the GRID card) directly. This means to you the job is rendered and sent remotely with almost no delay.

XenServer supports GRID GPU virtualisation and the remote display APIs. This is in early test for VMware and not on the map for HyperV.

So for the best graphics yet on VDI, get XenServer, XenDesktop and a bunch on NVidia GRID K1/2 Cards.

The newest Citrix Receivers supports the new codecs so stay current.

If you want to tune Adaptive Display you have the following settings, BUT ALWAYS leave it default until you have a test bed:

• Max frames per second
• Target Minimum Frame rate (up to 60 on newer receiver)
• Minimum Image Quality
• Moving Image Compression
• Extra Colour Compression (Chroma and Luma)
• Heavyweight Compression
• Lossy Compression level
• Legacy Graphics Mode
• Visual Quality
• Desktop Composition Redirection
• Desktop Composition Redirection Quality

16, 24 and 32-bit colour...

 

16-bit colour (High colour, from back in the day), can display 65,536 colours, which is fine for most uses.

24-bit colour (True colour), can display 16,777,215 different colours.

32-bit colour, also supports 16,777,215 colours but also has an alpha channel and using the alpha channel can create gradients, shadows, and transparencies.

To explain the alpha channel? In 32-bit graphics systems there are four 8-bit colour channels, three 8-bit channels for red, green, and blue (RGB) and one 8-bit alpha channel. The alpha channel is a mask not a colour. The alpha channel specifies how the pixels colours should be merged with the next pixel when the two are overlaid, one on top of the other.

Can my eyes tell a difference?

Most users can't. But custom programs that use gradients, shadows, transparency, etc. you may notice a difference with 32-bit colour.

XenApp Server that ‘thinks’ it is a farm member?

 

If you have an orphaned Xenapp 6.5 server, or three you can from the server registry tell it to leave home, move on, get a life and try and participate in society.

First try the nice way.

• Use XenApp Server Configuration Tool accessed through the Server Role Manager.
• In XenApp 6.5 the server manager is accessed through Administrative Tools > Citrix.
• Select Edit Configuration.
• Select Remove this server from the current farm.

If this didn't work, force it along.

Set this registry DWORD value to 0
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\IMA\Status]
"Joined"=dword:00000000

Then force the console to leave:
C:\Program Files (x86)\Citrix\XenApp\ServerConfig\XenAppConfigConsole.exe /ExecutionMode:Leave

Now it can re-join the farm or you can create a new one again.

 

• Thanks to “Christoph Sinabell” for the note.
• Support links: http://support.citrix.com/article/CTX125142
• Support links: http://support.citrix.com/article/CTX125130

Primer for HDX and 3D in XenApp and XenDesktop

HDX technologies built into Citrix XenApp and Citrix XenDesktop can and do deliver an excellent user experience on a many devices and over smaller network connections. HDX technologies are built on top of the ICA remoting protocol.

HDX has three technical principles:

1. Intelligent redirection; examining screen activity, application commands, and endpoint device, network and server capabilities to determine how and where to render on the server or redirect them on to the client.
2. Adaptive compression; defines codecs for specific network conditions, as manages CPU and/or GPU resources on hosts.
3. De-duplication of network traffic; using multicasting of multimedia streams, delivering of a single transmission  to many users at once. And the de-duplicates of bitmap graphics, files, print jobs and streamed media.

HDX is built on the core of ICA which also has these features to manage network traffic:

1. Adaptive TCP flow control accelerates the flow of all TCP-based traffic, by sensing and responding to high network latency and packet loss. The result is significantly higher network throughput and performance than with standard TCP implementations.
2. Adaptive compression to compress ICA traffic based on its characteristics, infrastructure capabilities and network conditions.
3. Adaptive protocol acceleration performs intelligent acceleration of ICA traffic while sensing and responding to network and traffic conditions.

Under the covers HDX is based on these seven components:

1. HDX Broadcast - Broadcast for providing desktops and applications over any network. It provides the underlying transport for many of the other HDX technologies. HDX Broadcast includes many of the older technologies such as instant mouse click feedback, keystroke latency reduction, multi level compression, session reliability, and queuing and tossing.
2. HDX Plug and Play - Plug and Play provide connectivity for local devices and applications in a virtualised environment, including USB, multi-monitor, printers, and peripherals. HDX Plug and Play includes technologies such as multi monitor support, smart card support, special folder redirection, universal printing, file type association, and USB support.
3. HDX 3D - 3D delivering high end graphics remotely such as image acceleration and progressive display for graphically intensive images.
4. HDX MediaStream - MediaStream for multimedia extends HDX Broadcast capabilities. With technologies for streaming media files to the client device for playing via local codecs with seamless embedding into the remote session.
5. HDX RealTime - RealTime for realtime communications such as voice and web cameras. RealTime extends HDX Broadcast capabilities. HDX RealTime support is in development today with third parties to support realtime communication via both voice and video on the remote client.
6. HDX IntelliCache - IntelliCache is to locally cache bandwidth intensive data and graphics and locally stage streamed applications. IntelliCache caches common application display data for multiple users locally to the branch office, eliminating redundant transfer of commonly used application objects.
7. HDX Adaptive Orchestration - Adaptive Orchestration enable seamless interaction between the HDX Technology categories. A central concept is that all these components work adaptively to tune the unified HDX offering for the best possible user experience.

Citrix XenApp 6.5 SDK and powershell tools

 

Get and install the SDK http://tinyurl.com/XenApp65PSSDK   

Or use the migration module if it has what you need

Run the right powershell, the one with the SDK not shown.

get-help *citrix*

Here is a script I used to dump out files for each area:

<#
Script Name     : XAInventory.ps1
Dependencies    : Powershell
Description     : Retrieves inventory from server
Purpose            : Inventory
OS Versions     : 2008R2
Date            : June 2014
Release            : v1.0
Usage : XAInvetory.ps1
#>

Write-Host "01. Get-XAFarm"
Get-XAFarm

write-host "02. Get-XAFolder"
Get-XAFolder

Write-Host "03. Get-XAZone"
Get-XAZone

#write-host "qfarm /load"
#qfarm /load

Write-Host "04. Get-XAZone | Get-XAServer | Get-XAServerLoad | format-table -wrap"
#Get-XAZone | Get-XAServer | Get-XAServerLoad | format-table -wrap
Get-XAServerLoad | sort 

Write-Host "05. Get-XAServer * | Select-Object ServerName, LogOnMode"
Get-XAServer * | Select-Object ServerName, LogOnMode

write-host "06. Get-XAServer * | Select-Object ServerName, OSVersion,CitrixVersion, CitrixServicePack"
Get-XAServer * | Select-Object ServerName, OSVersion,CitrixVersion, CitrixServicePack

Write-Host "07. Get-XAServer * | Select-Object ServerName, zonename, ElectionPreference"
Get-XAServer * | Select-Object ServerName, zonename, ElectionPreference | sort ElectionPreference

write-host "08. Get-XAZone | Get-XAServer | select ServerName, IPAddresses | Sort-Object IPAddresses"
Get-XAZone | Get-XAServer | select ServerName, IPAddresses | Sort-Object IPAddresses

write-host "09. Get-XAZone | Get-XAServer | select ServerName, IPAddresses | Sort-Object servername"
Get-XAZone | Get-XAServer | select ServerName, IPAddresses | Sort-Object servername

write-host "10. Get-XAServer | select ServerName | Get-XAPrinterDriver | Format-Table -Wrap"
#Get-XAServer | select ServerName | Get-XAPrinterDriver | Format-Table -Wrap
Get-XAServer | select ServerName | Get-XAPrinterDriver

write-host "11. Get-XASession | select ServerName, BrowserName, AccountName | sort servername | Format-Table -auto"
Get-XASession | select ServerName, BrowserName, AccountName | sort servername

write-host "12. Get-XASession | select clientname, AccountName, BrowserName | Sort-Object Accountname"
Get-XASession | select clientname, AccountName, BrowserName | Sort-Object Accountname

write-host "13. Get-XASession | select ServerName, BrowserName, AccountName, clientname | Sort-Object clientname"
Get-XASession | select ServerName, BrowserName, AccountName, clientname | Sort-Object Servername

write-host "14. Get-XAWorkerGroup | select WorkerGroupName, OUs"
Get-XAWorkerGroup | select WorkerGroupName, OUs

#write-host "Get-XAAdministrator"
#Get-XAAdministrator

write-host "15. Get-XAAdministratorPrivilege *"
Get-XAAdministratorPrivilege *

write-host "16. Get-XAAdministrator | select AdministratorName, FarmPrivileges"
Get-XAAdministrator | select AdministratorName, FarmPrivileges

write-host "17. Get-XAApplicationReport * | select WorkerGroupNames, DisplayName | Sort-Object workergroupname | ft -autosize -wrap"
#Get-XAApplicationReport * | select WorkerGroupNames, DisplayName | Sort-Object workergroupname | ft -autosize -wrap
Get-XAApplicationReport * | select WorkerGroupNames, DisplayName | Sort-Object workergroupname

write-host "18. Get-XAApplicationReport * | select DisplayName, Accounts | Sort-Object workergroupname | ft -autosize -wrap"
#Get-XAApplicationReport * | select DisplayName, Accounts | Sort-Object workergroupname | ft -autosize -wrap
Get-XAApplicationReport * | select DisplayName, Accounts | Sort-Object workergroupname

write-host "19. Get-XAApplicationReport * | select DisplayName,CommandLineExecutable | Sort-Object displayname | ft -autosize -wrap"
#Get-XAApplicationReport * | select DisplayName,CommandLineExecutable | Sort-Object displayname | ft -autosize -wrap
Get-XAApplicationReport * | select DisplayName,CommandLineExecutable | Sort-Object displayname

write-host "20. Get-XAApplicationReport * | select DisplayName,WindowType, ColorDepth | Sort-Object displayname | ft -autosize -wrap"
#Get-XAApplicationReport * | select DisplayName,WindowType, ColorDepth | Sort-Object displayname | ft -autosize -wrap
Get-XAApplicationReport * | select DisplayName,WindowType, ColorDepth | Sort-Object displayname

write-host "21. Get-XAApplicationReport * | select DisplayName,EncryptionLevel, EncryptionRequired, SslConnectionEnabled | Sort-Object displayname | ft -autosize -wrap"
#Get-XAApplicationReport * | select DisplayName,EncryptionLevel, EncryptionRequired, SslConnectionEnabled | Sort-Object displayname | ft -autosize -wrap
Get-XAApplicationReport * | select DisplayName,EncryptionLevel, EncryptionRequired, SslConnectionEnabled | Sort-Object displayname

write-host "22. Get-XAApplicationReport * | select DisplayName, PreLaunch | ft -autosize -wrap"
#Get-XAApplicationReport * | select DisplayName, PreLaunch | ft -autosize -wrap
Get-XAApplicationReport * | select DisplayName, PreLaunch

write-host "23. Get-XAApplicationReport * | select DisplayName, Enabled, AnonymousConnectionsAllowed | Sort-Object displayname | ft -autosize -wrap"
#Get-XAApplicationReport * | select DisplayName, Enabled, AnonymousConnectionsAllowed | Sort-Object displayname | Sort-Object ENABLED | ft -autosize -wrap
Get-XAApplicationReport * | select DisplayName, Enabled, AnonymousConnectionsAllowed | Sort-Object displayname | Sort-Object ENABLED

Write-Host "24. GET-XALoadEvaluator | select MachineName, LoadEvaluatorName"
GET-XALoadEvaluator | select MachineName, LoadEvaluatorName, IsBuiltIn

Write-Host "25. GET-XALoadEvaluator | select MachineName, LoadEvaluatorName  | Format-Table -wrap"
#GET-XALoadEvaluator | select LoadEvaluatorName, ApplicationUserLoadEnabled, ContextSwitchesEnabled, CpuUtilizationEnabled | Format-Table -wrap
GET-XALoadEvaluator | select LoadEvaluatorName, ApplicationUserLoadEnabled, ContextSwitchesEnabled, CpuUtilizationEnabled

Install MYOB on XenDesktop 7.5 in Azure on Server 2012 r2

 

Installing MYOB 19.10 in Azure Server Windows Server 2012 r2

Disable UAC via the registry, reboot

Install .NET 3.5

Just install the SERVER product for terminal services

Don’t just install it, do it via the old ‘add remove programs’

Install Application on Remote Desktop

Install

You may get stuck at this screen

If you do and hit cancel this is the error message

This is the workaround to this issue:

1. Log on to the system with Administrative Privileges
2. Open “Local Group Policy Editor” go to:
3. Computer Configuration
4. Administrative Templates
5. Windows Components
6. Remote Desktop Services
7. Remote Desktop Session Host
8. Application Compatibility
9. In the right pane, right click on ‘Turn off Windows Installer RDS Compatibility” and select Edit from the drop down menu
10. Select ‘Enable’
11. Hit OK

Hat tip for this http://community.myob.com/t5/Installing-and-upgrading/Upgrade-to-2014-2-hanging/td-p/263121

Rerun this install and it will work fine.

Few more next next nexts, Finish to complete

Then if you are using XenDesktop 7.5 allocate the application to users.

Good to go.

List to MYOB Supported platforms http://myob.com.au/business/customer-service-support/support/new-microsoft-environments-page/microsoft-windows-8-1257830102169

PVS Target install silently

 

There are lots of issues with installing the target software via SCCM to build gold images. The command line needed is documented, but here is the right command line switch!

PVS_Device_x64.exe /s /v” /qn /norestart

The installation help file says nothing of this funny quote (“) but it is the secret source. Good luck.

Getting to know Citrix XenApp 7.5

 

Here are the key differences between XenApp 7.5 and XenApp 6.5 and earlier.

Windows server 2008 R2 and higher – yes all 64 bit

All management is via Citrix Studio instead of Delivery Services Console, CMC etc

No IMA data store as XenApp 7.5 uses technology from XenDesktop, so Microsoft SQL Server database as the data store for both configuration and session information.

XenApp Farms are now known as Sites. Sites should (generally) be contained within one data centre.

Delivery Controllers connect you, the incoming user, to the correct application on the correct server.

Zone masters are automatic and distributed evenly across all Controllers in the site.

Replace folders and Worker Groups with a combination of machine catalogues, Delivery Groups. While this works it is not as flexible and will require some rethinking of large scale deployments.

To build Delegated Administration us the built-in administrative roles, such as help desk, applications, hosting, and catalogue.

Remote Desktop Services Client Access Licenses (RDS CALs / TS CALS) are not required on the Controllers server.

You still need RDS CALs on the servers that are hosting and delivering your applications ie the terminal servers.

Citrix Director monitors the environment — You can monitor the environment, shadow user , and troubleshoot issues

Shadowing uses Microsoft Remote Assistance to connect to user machines.

Virtual Delivery Agent (VDA) is the installed service that you put on the server BEFORE installing applications.

Machine Creation Services (MCS) or Provisioning Services (PVS) are used to manage the server OS for medium and large scale deployments.

There is no XenApp any version to XenDesktop 7.5 upgrade.

The process of publishing application has changed:

In XenApp 7.5 now, you use the Studio component to create and add applications to make them available to users who are included in a Delivery Group.

Using Studio, you

1. In your site,
2. create and specify machine catalogues,
3. create Delivery Groups within those machine catalogues. Delivery Groups are then used to determine which users have access to the applications you deliver.
4. then create an application to specify which Delivery Groups, they are detected or manually added

To balance application load on server Load Management assigns the user to the server best able to handle the request. This is based on:

1. Server maintenance mode
2. Server load index (based CPU, memory, disk)
3. The number of sessions (allowed number of concurrent requests to log on to the server).

Some of the technologies still to come:

1. Session pre-launch
2. Session linger

Brief video of Citrix XenDesktopApp 7.5 Video

Everything is subject to change once the final product is out.

Install Citrix Receiver the ‘easy’ way…

 

There is comprehensive documentation on installing the Receiver here: http://support.citrix.com/proddocs/topic/receiver-windows-40/receiver-windows-cfg-command-line-40.html 

There are THREE options, 1 manually via command line, 2 Via StoreFront server, 3 Email the configuration of the StoreFront (to then download it)

1. This is the command line to enable all the options.

c:\CitrixReceiver.exe /silent /includeSSON ADDLOCAL="ReceiverInside,ICA_Client,SSON,AM,SELFSERVICE,DesktopViewer,Flash,Vd3d,usb"

2. On the StoreFront server edit the client installation XML file to configure the installation options.

Contents of file:

<?xml version="1.0" encoding="utf-8"?><Services version="1.0" xmlns="http://www.citrix.com/ServiceRecord"><Service type="store"><SRID>3643525964</SRID><Name>sp</Name><Address>https://storefront.dave.colv.in/Citrix/sp/discovery</Address></Service></Services>

Save the file

3. Double click to test it and then you can email the config

Open it with IE

Bonus item (does not work on W8/W8.1):

If you want the receiver to look more like the PNA add the command line “/STARTMENUDIR=\Dave.Colv.in\” to the receiver install so the full line is:

CitrixReceiver.exe /includeSSON ADDLOCAL="ReceiverInside,ICA_Client,SSON,AM,SELFSERVICE,DesktopViewer,Flash,Vd3d,usb" “/STARTMENUDIR=\Daves.Colv.in\”  /Store0="sp;https://storefront.colv.in/Citrix/desktops/discovery"

You want back the PNA (Program Neighbourhood Agent) with Citrix Receiver 4.1, Citrix StoreFront 2.1 and Citrix XenDesktop 7.1

 

If you are longing for the 2000’s, you want back the PNA (Program Neighbourhood Agent) back but the man is making you move to receiver, never fear, with some time, configuration and tweeks you can be right back in the comfort zone.

This is the standard Citrix Receiver without sign sing on when it opens the StoreFront store.

First you need to install the agent with the single sign on support (/includeSSON and ,SSON,) in the command line below.

Just as a note when installing this and removing this the ,USB item had to be last to stop errors occurring in installing and the installation failing.

Command line to install Receiver 4.1:

CitrixReceiver.exe /includeSSON ADDLOCAL="ReceiverInside,ICA_Client,SSON,AM,SELFSERVICE,DesktopViewer,Flash,Vd3d,usb" /Store0="sp;https://storefront.colvi.in/Citrix/desktops/discovery"

YOU NEED TO REBOOT, you need the SSOSVR.EXE to be running as seen below.

You need to make the changes to the GPO for the client (the desktop computer) to allow internet explorer to pass the logon credentials.

You need to install and configure Authentication with Domain Pass-through on the StoreFront Server.

YOU NEED TO BE USING HTTPS and a valid Cert.

You can see I have the receiver web site disabled, you can use it, but it is not needed for this configuration (in fact it does not support pass-through and this confuses people).

You need to configure the XML Policy on the Delivery Controller, this is the GPO, but it can also be via PowerShell.

You need your StoreFront server to be in ‘Local Intranet’ or ‘Trusted Sites’.

If your IE policy is locked down, delete these Registry Settings and then you can check (until next reboot).

HKLM\SOFTWARE\Policies\Microsoft\Internet Explorer

HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings

Check that “Automatic Logon with current user name and password” is enabled in local Intranet if that is what you are in (see above).

Check that “Automatic Logon with current user name and password” is enabled in Trusted Sites if that is what you are in (see above).

At this point if you start the receiver you will see the client automatically logs on and gets the desktop(s) as shown below.

If you want to automate further (you needed the self service plug installed, it is if you used my command line above), then you can it force do a logon, a refresh and then see the newly created .EXE dummy files that you can use to create shortcuts in the Start Menu (or Metro interface), yes Windows 8.1 using these commands in the back ground.

Here are the commands to force this:

"C:\Program Files\Citrix\SelfServicePlugin\SelfService.exe" -logon

"C:\Program Files\Citrix\SelfServicePlugin\SelfService.exe" -poll

dir C:\Users\ColvinDave\AppData\Roaming\Citrix\SelfService

If you want to you can make shortcuts to the EXE files, anywhere in the start menu, you cant copy just the .EXE files or you will get the error below.

Good luck and tell them Dave Sent You.