Alteryx Server Ideas

Password is required to execute any command on LLS. Last time we forgot the password, only way to retrieve it was to reinstall the LLS ! 

A command to reset password in LLS should do.

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

We have the Local License Server installed.  Right now, if a Designer user changes roles, or leaves the company, they have to release their license from their client-side machine.  If they don't release it properly, and IT can't get us into their machines, then we have to wait 7 days for that license to roll off the server.  There should be a way for a system admin to forcefully revoke someone's license.

 Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted. 

Product should be capable of using the newly installed configuration and not require manual Config change and service restart. 

so every time there is a java version upgrade,  users have to be notified of the downtime  (even though they could move into 7 day grace period) and then the flexnetls.settings file should be updated with Java home path.  

@Kosi @SeanAdams 

Password entered during installation is changed to LLS default password after the following sequence of events.

LLS Service start -> Settings update -> Service restart (to let the settings change take effect). 

Avoiding this behavior will save server admin's time in changing password every time setting is changed. 

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

 Java Version upgrade requires LLS settings to be changed manually and LLS service to be restarted. 

so every time there is a java version upgrade,  users have to be notified of the downtime  (even though they could move into 7 day grace period) and then the flexnetls.settings file has to be updated with Java home path.  

Local License Server settings has to pick up the latest Java installation and not require manual Config change and service restart. 

@Kosi @SeanAdams 

Installation/upgrade of java in all servers are usually firmwide Tech team activity - which are outside of Server admins control. 

Java support by Alteryx - is version 8.0.212 - while the latest version available in our premise is 8.0.241. support for latest version of java - which is required for functioning of Local License Server should be prioritized. 

@Kosi @SeanAdams @ydmuley @RajK @LizaNemchynova @Arianna_Fuller @MPistone 

Right now, with LSS, the only thing you can query who has taken seats on licenses (you get user's email and host name).  This is OK, but it would be great if we could get more information than that.  Primarily

• What was the date/time that the user first grabbed that license
• When was the last date/time the user connected to the license

As you know, there is no way to forcefully remove a license from the LLS (you either have to have user deactivate from Designer, or wait 7 days).  Knowing this information would help admin's know who is actually using the licenses and if someone leaves the company, you can get a countdown until that license is released.

For historical tracking and auditing, I would also like to setup an Alteryx Workflow that puts licensed user information into a table or DB so we have a log of who is using the licenses.

I know the Alteryx server supports auto-scaling up and out as of now. Alteryx Servers should also support auto-scaling down and in.