Will DomainScan work with Windows Vista / Windows Server 2008?
Yes.
However, due to the enhanced security in Windows Vista and Windows Server 2008 one must make sure that Windows will accept remote connection.
See Technote 8 for more information.


Will DomainScan work with Windows XP Home Edition?
No.
XP Home Edition does not allow for remote WMI connections, which is the main protocol that DomainScan uses.


Can I use Windows 2000 Professional or Windows XP as a DomainScan server?
Yes.
DomainScan only uses software that is available on all editions of Windows. Therefore, a server edition is not required. However, it is recommended due to the fact that Windows 2000/XP only supports a limited number of concurrent network connections, which may cause problems.


What is the connection between DomainScan Pro, NetScanG, DomainScan and DomainScan Light?
Initially, it started with one product – NetScanG, which were initially a rather simple tool with the purpose of being able to present a list of computers in a domain plus who were logged in on these devices.

That program grew in scope, and with NetScanG v3 it was divided into two programs; a freeware edition, which used the NetScanG name, and a shareware version which were named DomainScan.

Then, in 2007, NetScanG was renamed to DomainScan Light in order to tighten the relation between the two programs.

And in 2008 the suffix changed so that DomainScan became DomainScan as of v2.7, and DomainScan Light became DomainScan as of v6.5

Why run DomainScan with Domain Admin privileges?
DomainScan collects a number of information though the WMI interface.
In order for Windows to secure that only authorized devices (or users) uses this interface, only users with administrative privileges on the local (client) computer is allowed to access the interface with no restrictions.
In a normal domain setup, 'Domain Admins' are automatically added to the local administrators group, which grants full access to the computer. If the DomainScan engine runs with 'domain admin' privileges, DomainScan is automatically granted full access to all computers in the domain.

The database files and the log files were located at different locations, but after I set a new database directory with the Setup Wizard, all files are located in the same directory?
The installation wizard is designed to make the initial setup easy – therefore, the Setup Wizard will modify both database and log file location.
Use Preferences to set the locations individually.

Is DomainScan backward compatible
Yes and no.
DomainScan is compatible with all NetScanG v5.x releases. However it is not compatible with earlier relases of NetScanG

What is 'Internal domain assignment error'?
This situation occurs with devices that are discovered with a different domain membership than the domain that DomainScan is a member of. And due to the fact that DomainScan only supports devices that are members of the same domain/workgroup as the server where DomainScan Service is installed, then the device is dropped, and this message is created. To resolve this situation, one must consider upgrading to DomainScan Pro which is multi-domain compatible.

How many computers can DomainScan monitor?
DomainScan can monitor what correlates to 1000 license units in DomainScan. With no monitors in action, that will leave licenses for up to 999 devices to be monitored.

For information about how many license units that are used, use the Database Analyzer.

Will DomainScan work with my Firewall software?
It general; yes, but only if the correct ports are open for DomainScan
For more information, please read this document.


I will not allow DomainScan to run with full access to the entire network, because of security concerns (I don't trust that DomainScan doesn't collect data behind my back and sends them back to GH Software).
DomainScan does not send data back go GH Software (or anywhere else for that matter). This can be proven by using a connection monitor, or a software firewall. Emails are only sent to the location that DomainScan is setup to send to.

If you choose to let DomainScan run with limited access privileges, all that happens is that DomainScan fails to collect some of the information its suppose to collect, and if the privileges are too low, the service will completely fail to run (Windows will deny every request that DomainScan makes).


I've set the DomainScan engine service to run with domain admin privileges, but I cannot search anything with the WMI browser!
The WMI data search is performed by the client application, and is not performed by DomainScan Service. Therefore, also DomainScan Client must run with domain admin privileges in order for WMI queries to run successfully.

I have installed DomainScan on a domain controller and after a restart; all computers suddenly appear as being offline!
When DomainScan starts a new scan, it queries Windows for the computer browse list for the domain (or workgroup) that the computer is a member of.
This list is maintained by the domain browse master, and therefore the list will be empty after a restart, until the browse master rediscovers all online computers, which may take a few minutes.


Will DomainScan work in domain forests (or with a domain with child domains)?
Yes.

Active Directory names aren't resolved!
DomainScan uses a simple lookup based on the logon name in order to resolve the corresponding full user name. If the logon name and the principal name are different (by default they're the same), DomainScan will not be able to identify the user in the Active Directory, and therefore interpret the user as being deleted.
Example: If the logon name is johndoe and the principal name is jd@example.com and not johndoe@example.com then DomainScan will fail to receive john doe's full name ('John Doe')