Not seeing Thumbnails with new 4.6.0 install on Windows
-
I installed the 4.6.0 release one Master and one client. I set them up to use ldap and I can log into the master, I can even do the remote view and remote control into my test client. I do not have any thumbnails on the Monitoring tab. If I click on Locations and computers I see all of our computers in our AD, selecting my test client computer here doesn't do anything either.
I have poured over the documentation, I did netstat -a to verify the systems are listening on 11100 and I also looked at the firewall configurations on both computers to verify the veyon exceptions are there.
Both computers are Windows 10 Pro.
Both computers are on the same network subnet.
When I telnet to the client or master computer on 11100 I get RFB 003.008I am trying to get this working so that I can set it up for my Computer Teacher to monitor her lab computers. Any help or pointers are appreciated.
-
I have been working on this some more from the computer I setup as the master. On the LDAP Basic configuration, Integration Tests tab everything works except for List all entries of a location.
The error I'm getting is:
Could not query any location entries. Please check the parameter(s) "Filter for computer groups" and "Computer locations identification" and enter the name of an existing object.
I am testing with my computer group HSLabComputers, when I do the do the list all groups of a computer for hslab-01.sps.local it is one of the computer groups listed. It also shows up with I do the List all Locations.
I currently have the Filter for Computer groups set to (cn=*) which returns my 25 computer groups. I have my groups located in a folder so the Computer group tree setting is OU=Computer Groups,OU=SPSComputers,OU=sps.
My LDAP is working for everything else except this one test, which I believe is why I'm not seeing any thumbnails when I go to select the computers.
-
@shelbytech Did you configure Computer locations identification to Computer groups in the Advanced settings tab and checked the Group member identification setting is correct? The Group member attribute in the Object attributes area seems to be set up correctly since Veyon can resolve the group/location name of a computer. Does the List all locations test return the desired groups? I'm sure there's just a small missing piece which prevents Veyon from retrieving the computers for a certain location. That's why you don't see any entries in the Locations & computers panel which you could check to add them to the monitoring area.
-
I have Computer locations identification set to Computer groups. I have the Group member attribute set to member right now because that is what I am seeing with my ldap software. I even moved all of my groups to their own OU to make it easier to find them all. I agree that it's probably something minor, just a matter of finding it.
The list all locations returns 25 locations, which is the number of computer groups I have setup. I tried to get it to list a couple of different locations out and they all return that error. I'm going to play with the filters some more and see if that isn't it.
By adding the filters I have gone from listing all 380 computers in the district to the groups, when I click on the group that the test computer is in nothing is showing up. Before the filters I would try to click on the entry for hslab-01 and nothing would come up.
-
I went back into the different settings tab and I think I found something related. In the Environment tab, the Group member attribute is set to member, when I click on the check mark and type in a group name that exists in my AD it gives me the error "Could not query any group members. Please check the parameter(s) "Group member attribute" and enter the name of an existing object.
Using my ldap browser I opened up the staffmember group and it lists all of the users in it with member as the attribute. I am afraid I might be tying problems together, right now I turned on debugging for the logs and trying some of these tests to see if I can make sense of it.
This is the log output for the query on the Environment settings page for Group member attribute.
2021-10-01T13:32:28.033: [DEBUG] LdapClient::queryDistinguishedNames(): results ("CN=LocalAdmins,OU=Groups,OU=sps,DC=sps,DC=local")
2021-10-01T13:32:28.033: [DEBUG] LdapClient::queryAttributeValues(): called with "CN=LocalAdmins,OU=Groups,OU=sps,DC=sps,DC=local" "member:1.2.840.113556.1.4.1941:" "(objectclass=)" LdapClient::Scope::Base
2021-10-01T13:32:28.033: [DEBUG] [KLDAP] asyncSearch() base=" "CN=LocalAdmins,OU=Groups,OU=sps,DC=sps,DC=local" " scope= 0 filter=" "(objectclass=)" " attrs= ("member:1.2.840.113556.1.4.1941:")
2021-10-01T13:32:28.033: [DEBUG] [KLDAP] ( 3 , 3000 ) : Waiting 3000 msecs for result. Attempt # 1
2021-10-01T13:32:28.034: [DEBUG] [KLDAP] rescode: 100
2021-10-01T13:32:28.034: [DEBUG] [KLDAP] ( 3 , 3000 ) : Waiting 3000 msecs for result. Attempt # 1
2021-10-01T13:32:28.034: [DEBUG] [KLDAP] rescode: 101
2021-10-01T13:32:28.034: [DEBUG] [KLDAP] rescode 101 retval: 0 matcheddn: errcode: 0 errmsg:
2021-10-01T13:32:28.034: [DEBUG] LdapClient::queryAttributeValues(): results: ()
2021-10-01T13:32:30.924: [DEBUG] [KLDAP] connection closed! -
Today I built a Centos vm and installed on it, I am seeing the same thing on it. I can list all of the computer groups in the ldap integration test, I cannot list the computers in these locations. In the master program I can select the location that my test computer is in and nothing shows up in the monitoring. I can remote into the computer by entering it's name.
-
I got the thumbnails to work by changing Identify computer location to Location attribute on the Advanced settings tab and setting Computer location attribute on the Environment settings page. We are small enough that I am going to roll it out this way and add the Group Name to the AD configuration for the computers. Not ideal, however it will work for us.
-
Thank you for sharing your solution! The troubles you had might be related to https://github.com/veyon/veyon/issues/761 so until 4.6.1 is released you could try again with computer groups and make sure the nested groups option is not enabled.