Skip to main content
  • EN

Hi All,

 

One of our customers is running VID's with FME Desktop in an App-V.

It seems the App-V is checking out a Floating License on startup, even there's no FME (workbench) process opened and after all FL's are checked out other users can't start FME Workbench anymore.

Why is the FL checked out on startup of the App-V and how can this be disabled until a real FME process is started.

Can this be arranged by removing the fme_license.dat, or perhaps using Non-persistant VID's?

 

Kind regards,

Krien Guijt

 

Hi @krien​ 

I do not have experience with App-V but had worked with Microsoft Remote Apps.

Looking at the floating license logs will give us an insight on which server/clients are consuming licenses.

I would suggest to file a support ticket and send us the log file(safe.log) from the floating license server.

 

WORKAROUND

I think you can use a option files to restrict that certain users are allowed to access the license. https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Desktop_Admin_Guide/FMEInstallation/Restricting_Licenses_to_Users_or_Groups.htm

At this point, I am not aware how the AppV architecture is configure i.e. if the virtual apps are configured to be used by users or if they are tied to server itself.

 

 

Hi @rahulsharma​ 

 

Tnx for your advice to contact Safe Support, I did that, but posted the question here also to see if this happens to other users too.

You suggested to limit the Floating Licenses access to groups / users.

I already thought of that, but it won’t work because the App-v will checkout a FL for the FME users even if they don’t open a FME process.

I'll let you know what Support comes with.

 

Kind regards,

Krien Guijt

Reply


Community Stats

30,162
Posts
114,487
Replies
37,809
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.