WEM 1811 Application Icon File Path Bug (?)

[Julian Jakob]

Hey guys,

 

If you try to add some Icons to your WEM 1811 Applications, it would not work. A friend of mine tested it at another server OS and confirmed my discovery:

 

WEM 1811 Application:

 

 

 

As you can see, per design I have to "Select Icon" browse to the C$ share of my VDA where the application is installed and if I select the .exe, WEM should change the UNC Path to C:\...

 

-> As you can see, there is still a UNC Path and so the Icon File in the prod Desktop would be white.

 

 

WEM 4.6 Application: (I think in 1808 it should also be OK)

 

 

As you can see, I browsed to the UNC Path of my VDA where the application is installed and after I selected the .exe to the App, WEM is changing the Icon File Path correctly to C:\...

 

-> Icon File in the prod Desktop is created correctly.

 

 

If anybode has an idea how I can bypass this - I would say - bug, you're welcome to share.

 

Sure I know I could save all icon files to my WEM Infrastructure Server - local - and so I am able to browse to a local Path C:\... and so the icon file settings is written to the WEM Database, but I don't want to go through this workaround.

 

Thanks in advance and best regards

Julian

[Julian Jakob]

On 21.3.2019 at 11:57 AM, Marco Hofmann said:

I went from 4.7 -> 1808 -> 1811 without ever noticing this error. This is because is use the console differently.

You don't have to install the console locally, the WEM Administration console works happily by launching it from an administrative UNC path, for example if oyu have the Console installed on your Delivery Controller:

"\\delivery-controller-01\c$\Program Files (x86)\Norskale\Norskale Administration Console\Norskale Administration Console.exe"

This way you circumvent, that you have to search for the apps, that are installed on your VDA, as you can access them directly from the console itself. Makes my life sou much easier.

 

Thanks Marco, will give that „use console via UNC Path from the VDA directly“ a try. 

[dpalchu521]

 

On 3/21/2019 at 5:57 AM, Marco Hofmann said:

I went from 4.7 -> 1808 -> 1811 without ever noticing this error. This is because is use the console differently.

You don't have to install the console locally, the WEM Administration console works happily by launching it from an administrative UNC path, for example if oyu have the Console installed on your Delivery Controller:

"\\delivery-controller-01\c$\Program Files (x86)\Norskale\Norskale Administration Console\Norskale Administration Console.exe"

This way you circumvent, that you have to search for the apps, that are installed on your VDA, as you can access them directly from the console itself. Makes my life sou much easier.

 

This helped me. Just copied the console to the UNC share and do the configs from the machine that has software installed.

[James Kindon]

Same behavior in 1808....UNC is never converted back to local path - application executable path is (never noticed this before)

 

Install the console locally on a machine with access to the .exe / icon path, and you should be OK - I'd log with Citrix 

[Julian Jakob]

Thanks James, same behavior here. 

 

„Downgraded“ (Export, fresh install, Import) to 1808, too. UNC Path at the Icon file Path, too. BUT Icon file is created, correctly. 

 

I think main problem within 1811 is the Path, how the Agent is creating the Icon file at the Desktop:

\\%COMPUTERNAME%\c$\example\test.exe

 

Would gladly know from which Version this problem is getting started. In my other environment (WEM 4.6) it’s converted correctly to the local path of the exe. 

 

Thanks for your input, will work with installation of console at the worker, too. Simple copy paste of the local paths. 

 

Regards

Julian

[Daniel Weszligling]

In 4.7 it's converted correctly, too. It Comes with 1808.

[Christian Pressler 2]

Hi all

There is a private fix about the issue. Refere to case number 78695850.

 

Regards
Christian

[Detlev Koch]

Hi all,

Same here, with 1808 and other customers with 1811.

Get the private fix and replace the .dll - now works as expected

Refer to case number: 78776540 

 

Regards

Detlev

[Nick Panaccio]

I take it the private fix is for the console? I've been getting around this by creating the folder structure on my machine and copying the executable when creating the shortcut. Hopefully the fix is included in future builds.

[Marco Hofmann]

I went from 4.7 -> 1808 -> 1811 without ever noticing this error. This is because is use the console differently.

On 27.1.2019 at 0:55 AM, James Kindon said:

Install the console locally on a machine with access to the .exe / icon path, and you should be OK - I'd log with Citrix 

You don't have to install the console locally, the WEM Administration console works happily by launching it from an administrative UNC path, for example if oyu have the Console installed on your Delivery Controller:

"\\delivery-controller-01\c$\Program Files (x86)\Norskale\Norskale Administration Console\Norskale Administration Console.exe"

This way you circumvent, that you have to search for the apps, that are installed on your VDA, as you can access them directly from the console itself. Makes my life sou much easier.

[Richard Lapierre]

The bug has still not been fixed with WEM 1903, but a private fix is available for this version which works a expected (new Norskale.Common.Forms.Administration.Actions.dll). Citrix will fix the issue with WEM 1905.