Multiple AD with NETBIOS name "AD"

[ifm]

We have just moved our student computers to another AD that conflicts with "our" own AD used for employees. the dns names are different but the netbios names are both "AD".
This seem to confuse Lansweeper since the credential feature locks on the short name that is AD for both of them. The same way it is difficult to separate the computers since they all are listed in "AD". It would be much better if the full name where used in our case, AD.xxx.xxx.xx vs AD.xxx.xx.

It would also be great if I could "group" computers (in our case, student computer rooms) and run commands on all of them at once. Eg. wake on lan, shutdown, restart, full rescan, run custom command etc.

[Hemoco · Accepted solution]

You could make a custom report to replace the default asset list containing the FQDN or you could add all student computers to a separate IP location (since this is included in the asset list and you can sort/filter on it).

Using Active Scanning as the only scanning method a computer won't be scanned until it logs into the domain (controller). Lansweeper contacts your domain controllers every 15 minutes for a list of newly logged on computers. Only newly logged on computers that have not been scanned in the last 20 hours are then scanned by Active Scanning.

[ifm]

Using 5.0.0.18

The biggest problem is that under "Assets" there is only one "AD" where computer from both domains are mixed.
One of the computers I added this week still havent been added to lansweeper by using active scanning. (cant use lspush since the server is not accessible from this student domain network.)

[Hemoco]

Which Lansweeper version are you using? 4.2 or 5.0?

- Scanning shouldn't be an issue in 5.0, as you can map as many credentials as necessary to the "AD" NetBIOS name. These credentials will be tried for both domains. (In Lansweeper 4.2, you can only map one credential to each domain.)
- You can create a custom report that includes the "full" domain names and separate the machines that way.
- You can create custom asset groups, but custom actions can currently only be run on one machine at a time. The only exception is the Rescan option. To rescan multiple machines, click the Assets link at the top of the Lansweeper 5.0 web console, tick the checkboxes in front of the assets and hit the Rescan button on the left.