Hi,
we are using corel in a windows domain (sbs2011, users have win7proX64) in which users have only restricted rights (aka normal user accounts, not admin).
With corel x7 and bitstream font navigator i was able to create a shim db that evokes the exe of bitstream to admin rights using the
microsoft application compatibility toolkit. You had to create an application fix and choose "run as invoker".
The new font manager x8 calls the "FontService.exe", which is also in the Programs64 Folder, when installing a font.
creating an application fix for "FontService.exe" doesn't seem to work. i tried many combinations of different levels of rights but it always asks for administrator permission when installing a new font. i can see that the font manager calls fontservice with an parameter that holds the information about the location of the font database. our users have access rights to this folder since its in AppData.
Does anyone have an idea what else i could do?
Please @Corel create a way to use the Font Manager in a professional setting like a domain. It was possible with the Bitstream Navigator.
Thanks for any Infos
Hi Johannes,
Can you PM me your email? I'll try to solve this with you over skype or chat.
Thanks,
Lawrence
I just wanted to provide an update on the investigation into the problem found by Johannes. Thanks to Johannes, we were able to track down an issue with Font Manager.
With the shim on Font Navigator, it seems like Font Navigator is installing the fonts temporarily because a reboot would undo the fonts installed as the user. In order to install a font, we need to make two changes:
1. The first of which is a call to AddFontResource (this makes it possible to use the font right after).
2. The second part of the change is to make a change to the registry so that the font stays permanently installed (even after a reboot).
The AddFontResource part of the change can be done by any user, it doesn’t require admin privileges. The registry change requires admin privileges and that fails for Font Navigator (as seen when you reboot).
Font Manager is different from Font Navigator in that it doesn’t attempt any part of the installation without admin privileges, so AddFontResource isn’t called at all (this is the cause of your bug). The good news is that we can change this behavior and this would address the limited user issue without requiring a shim applied for Font Manager or FontService. Unfortunately, this involves changes to FontManager source code and we don’t know when this fix will make it into the final release. It should be going into X8.1 (if a lot of users report this issue, we may put this in the next hot fix which would come out sooner than X8.1).
If anyone else runs into an issue similar to what Johannes described, please post here stating that you have a similar problem (but only if it is closely related). For anything else, please post a new thread.