[THIN] Re: XenApp 7.6 Policies

  • From: Jeremy Saunders <jeremy@xxxxxxxxxxxxxxxxxxxx>
  • To: "thin@xxxxxxxxxxxxx" <thin@xxxxxxxxxxxxx>
  • Date: Wed, 2 Sep 2015 15:23:56 +0000

So why not build a side-by-side 2008R2 image to give them a chance to address
the issue? It doesn’t need to become an issue. As Joe mentioned, you can also
address this via a logon script.


From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of
Jason CitrixADmin
Sent: Wednesday, 2 September 2015 11:10 PM
To: thin
Subject: [THIN] Re: XenApp 7.6 Policies

Then I will definitely need to test it. Fortunately we are going to
provisioning and every image will be identical, so if it works, it will work
across the board. If it doesn't then I get ot have an ... interesting meeting.

On Wed, Sep 2, 2015 at 11:07 AM, Joe Shonk
<joe.shonk@xxxxxxxxx<mailto:joe.shonk@xxxxxxxxx>> wrote:
From what I understand, they put the option back in but it only work for
certain OSes.


On Wed, Sep 2, 2015 at 10:14 AM, Jason CitrixADmin
<jasoncitrix@xxxxxxxxx<mailto:jasoncitrix@xxxxxxxxx>> wrote:
I found the following Hotfix
Is this going to help, or will it still be unsupported in Win2012? I am not
sure from reading the documentation.

On Wed, Sep 2, 2015 at 9:47 AM, Jason CitrixADmin
<jasoncitrix@xxxxxxxxx<mailto:jasoncitrix@xxxxxxxxx>> wrote:
It is our In house Application.
I can't go into all the details of the exact setup but we had a solid reason
behind it when the application was setup with this restriction in place.
I am going to see if I can find any documentation because without a solid
backing I KNOW there will be pushback against this.
Thank you for the reply.

On Wed, Sep 2, 2015 at 9:41 AM, Joe Shonk
<joe.shonk@xxxxxxxxx<mailto:joe.shonk@xxxxxxxxx>> wrote:
I don't have any off hand but I do know its a Microsoft issue and the work
around is to run a logon script to rename the printers after then have been

Time to call the software vendor and say WTF.


On Wed, Sep 2, 2015 at 9:35 AM, Jason CitrixADmin
<jasoncitrix@xxxxxxxxx<mailto:jasoncitrix@xxxxxxxxx>> wrote:
That is going to cause a major issue with our software.
Do you have a link to the documentation on that? I need to bring that up to
our development team as soon as possible.

On Wed, Sep 2, 2015 at 9:34 AM, Joe Shonk
<joe.shonk@xxxxxxxxx<mailto:joe.shonk@xxxxxxxxx>> wrote:
Nope. It's not going to work. Legacy printer names are not supported in
Windows 2012 or Windows 2012 R2. Yes, I know, the console is wrong and a fix
(removed from the console) should have been added a while back.


On Wed, Sep 2, 2015 at 9:02 AM, Jason CitrixADmin
<jasoncitrix@xxxxxxxxx<mailto:jasoncitrix@xxxxxxxxx>> wrote:
We are preparing to upgrade the infrastructure to deploy XenApp 7.6 on WIndows
2012 R2
and am setting up the Citrix policies but having an issue getting them to
apply. In particular we have to enforce the legacy client names for printers.
I have enabled the legacy client name and applied to all objects in use.

I am at a loss to understand at the moment what the cause is. To ensure there
are no conflicts I have disabled all other policies and left Only the one
policy active.

Other related posts: