SetupBuilder and RDP Font install problem

[NewsArchive]

Hi,
Installing fonts with SB 10.0.5204 in a Cloud Sql server 2008R2 VM.
The app is up and running ok usesing a bar code font in some reports
that were intalled ok with the same SB installer.
The app is used via Terminal Services.
If I installed a new version with the same installer using the
administrator login, the reports are still using the bar code font ok in
the administrator user but its not in the other users. Other users gets
letters instead of bar code in the reports.
Any "use it for all users" or something else to solve this?
Regards

--
*Alberto Michelis*
ARMi software solutions www.armisoftware.com <http://www.armisoftware.com>

[NewsArchive]

Alberto,

not sure if this helps. But there is a #pragma TERMINAL_SERVER_AWARE in
SetupBuilder.

This will set a flag in the IMAGE_OPTIONAL_HEADER DllCharacteristics field
in the setup image's optional header. When this flag is set, Terminal
Server will *not* make certain changes to the application.

Background: when an application is *not* Terminal Server aware (aka a legacy
application), Terminal Server makes certain modifications to the legacy
application to make it work properly in a multi-user environment. For
example, Terminal Server will create a virtual Windows folder, such that
each user gets a Windows folder instead of getting the system's Windows
directory.

Friedrich

--
Friedrich Linder
Lindersoft | SetupBuilder | www.lindersoft.com
Voice: +1.954.537.3701 | Fax: +1.954.537.3702

--SetupBuilder "point. click. ship"
--Helping You Build Better Installations
--Create Windows 10 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner

[NewsArchive]

Thanks Friedrich, I will test it and let you know.
How and where do I set this #pragma ?

*Alberto Michelis*
ARMi software solutions www.armisoftware.com <http://www.armisoftware.com>

[NewsArchive]

Hi Alberto,

> Thanks Friedrich, I will test it and let you know.
> How and where do I set this #pragma ?

I'd suggest at the beginning of the script (scroll down in the "Script
Functions" list to the "Compiler Directives" section and double-click
"#pragma...").

Friedrich

[NewsArchive]

Ive done this but I dont understand it very well.
Does it modify mi exe/dll files that are installing?
How does TS knows how to behave with my exe?


*Alberto Michelis*
ARMi software solutions www.armisoftware.com <http://www.armisoftware.com>

[NewsArchive]

Hi Alberto,

> Ive done this but I dont understand it very well.
> Does it modify mi exe/dll files that are installing?
> How does TS knows how to behave with my exe?

No, it does *not* change anything in *your* application. What this flag
does is, it compiles a Terminal Server aware setup.exe. As a result,
Terminal Server will not make certain changes to the (setup) application.
For example, if an application is *not* Terminal Server aware, Terminal
Server will create a virtual Windows folder, such that each user gets a
Windows folder instead of getting the system's Windows directory (but fonts
should be installed to the system's Windows folder, not to the virtual
Windows folder).

If the TERMINAL_SERVER_AWARE flag is *not* set, the installer might copy the
font to virtual Windows folder. If it is set (makes the setup.exe Terminal
Server aware), the fonts are installed into the system's Windows folder.

For your own .exe, (as far as I know) you should also make it Terminal
Server aware. Otherwise, it's handled as a "legacy application".

Friedrich

[NewsArchive]

Hi,
FWIW, not sure on the relationship between ts<-->uac regarding this
behavior but this may provide additional background

https://www.symantec.com/connect/articles/folder-virtualization-concepts-windows-vista

Cheers,
Federico