i'm evaluating winflector using the free version. in winflector authentication mode, i can create users, and vary the applications a user can access per user (for example: User 1 can access AppA only, User 2 can access Apps A and B).

In Windows authentication, I'm not using Active Directory, so can only have computer name as domain and local windows accounts.  In such scenario, I don't know how to configure the set of applications a user can access and vary them per user (per example above). Is this possible? If so, how?

Thanks for any help!

thanks! i have a windows 10 home edition which lacks the lusrmgr snap in. but "net localgroup ... /add" worked for me

Hi John,

It looks like wrong domain or computer name information are entered in "Domain name" input.

You have to enter:

• Computer name where the Winflector server running (computer is not a domain member), or
• Domain name where that computer is the member of.

Hello,

(1) Using the Windows 10 HOME Edition (NOT the PRO Edition)  mentioned in my earlier posts in which I was able to resolve the problem using version 3.9.3.4b of the Winflector Server , I uninstalled the older Winflector Server version and installed version 3.9.4.0a instead (the version that I was using unsuccessfully .with Windows 10 PRO was 3.9.4.0, however, without the 'a' suffix)

I get the same msgs even though I completed your  (rafal's) instructions above successfully.

[TSV3940a] 0680 25.05.2017 18:49:22 INF:000010, NUM:000000 DSCR:"Winflector server turned ON"

[TSV3940a] 0682 25.05.2017 18:49:22 INF:000001, NUM:000001 DSCR:"Windows 10 10.0 build:15063, SP:no SP, CPUs:4"

[TSV3940a] 0684 25.05.2017 18:49:22 INF:000001, NUM:000002 DSCR:"CPU arch:Intel/AMD x64, CPU type:x8664, rev:36361, lev:6"

[TSV3940a] 0699 25.05.2017 18:49:22 INF:000001, NUM:000003 DSCR:"License number:F3940/1/F/17, License type:F, Users:2"

[TSV3940a] 0664 25.05.2017 18:50:13 ERR:004501, NUM:001355 DSCR:"NETAPI: DS domain get error"

[TSV3940a] 0668 25.05.2017 18:50:13 ERR:004501, NUM:001722 DSCR:"NETAPI: ANY domain get error"

Which leads me to think the Winflector code may be first trying the entry as a domain get, and then a different kind of domain get, and finally trying out the entry as a computer name?  so the appearance of those messages in the log may not really be indicative of an error in the entry i inputted into the "domain" text field???  (i dont use active directory or domain, only computer name, and yes, i may have inputted the computer name incorrectly when i was working with the Windows 10 PRO machine but i cannot check right now because it's now in a different location)

what can i do that may yield better diagnostic info??

what really happens when the "winflector users database (?)" fail to synchronize correctly with new localgroup members info? anything i can do more systematically around this potential synchronization problem? maybe if i know where this info is kept so i can read it, and verify or check for corruptions maybe?

 

Windows 10 HOME does not support domain functions used by Winflector, so using Winflector authentication is not possible. We do not recommend using Windows 10 HOME as a server due to lack of many features important for Winflector server.

 

(2) In Windows Authentication setup, if i try to change the authorized localgroups, it seems I could get into trouble easily which would then result in my inability to populate the User Profile List correctly. When this happens, what's the best way for me to recover? I know that one drastic way is to start fresh by uninstalling then re-installing  Winflector Server. any other less drastic way?

I do not understand situation described above, but if you want to backup synchronized Windows users, you can copy TGUICFG/WINUSER.* and TGUICFG/APPWUSER.* files and recover them if you need.

 

(3) Also, I'm wondering why is it that in Winflector Authentication setup, I can add one user at a time and also vary the applications accessible by THAT user vs other users, but in Windows Authentication setup, it seems I need to setup a local group first to get users added, BEFORE i can configure the applications each user will be allowed to access.  I only have a handful of local user accounts that I want to be able to access their specifically allowed applications, so I'm wondering if there's a way I can setup Windows authentication very much like Winflector Authentication setup (one user at a time, no need to create a local group first, but still be able to vary the set of allowed applications per user)?

Unfortunately not. The local group is necessary for limit users to synchronize. There is not possible to add Windows users manually. You have to create a local group (or use existing) add users and synchronize. Then you can add applications for each user separately.

 

(4) is the ability to export list of user info for import to a new Winflector Server instance limited to Winflector Authentication setup only? 

thanks for any help or tips!

You can copy database files: user.dat and appuser.dat (*.idx files should be rebuilt automatically). You need also locapp.dat and locapp.fpt because application ids must remain the same.

user.dat - list of usersappuser.dat - applications->users assignmentlocapp.dat & fpt - list of applications

You can also use export options in Winflector/Preferences/Users accounts/Export accounts to file.

Regards,

Mirek

We do our best to make Winflector server working on Windows HOME editions, but some problems still persist. In most cases Winflector works properly, but Win HOME limitations are much stronger than we have expected. Unfortunately domain/windows authentication still cannot be used on HOME editions.

Windows 10 PRO has domain/AD features, so it is suitable for Winflector server. You should have no problems with local group creating and domain/local users.

After small investigation we made a workaround in Winflector server. In the next release you will be able to use local Windows accounts to authenticate clients in Windows 10 HOME. It will use the system local group called 'Users' to synchronize accounts.