Can I install DomainScan Pro on my 64 bit edition of Windows?
Yes

Will DomainScan Pro work with Windows Vista or newer?
Yes (except for Home and Starter editions).
However, due to the enhanced security defaults that is introduced with Windows Vista / Windows Server 2008, one must open up Windows in order for DomainScan to function correctly.

See Technote 8 for more information.


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


Can I use Windows 2000 Professional or Windows XP as a DomainScan Pro host-server?
Yes.
DomainScan Pro 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 Pro as of v2.7, and DomainScan Light became DomainScan as of v6.5

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 Settings to set the locations individually.

Is DomainScan Pro 2 backward compatible with version 1.x?
No.
Due to the fact that the database backend is a complete rewrite, with a lot of new functionality and a new database structure, a DomainScan v1 upgrade is not trivial.
However, all versions of DomainScan v2.x, DomainScan Light and NetScanG v5.x can be upgraded automatically or by the GDB Database Analyzer

I bought DomainScan Pro, and I don't like it - I want my money back.
DomainScan Pro is offered as shareware, with a fully functional trial period. Due to this fact, one has a chance to test DomainScan Pro prior to purchasing. Therefore GH Software does not offer refunds in a case like this, and we’re not legally bound to.


I bought DomainScan Pro but it doesn't work even though it is installed in a supported environment - can I get my money back then?
If it doesn't work, and the problem can't be corrected in a timely manner, a refund will be issued.


How can I trust that I get a license key if I buy DomainScan Pro?
Ordering is handled by Share*it! - A well-known company that has specialized in selling shareware. It is secure and used by a large number of companies.
Once the payment is validated by Share*it! , you'll receive an email with payment information as well as the license key.

Important Note: GH Software is not responsible or even involved in the order, so any problems regarding the order must be addressed to Share*it!

What is a license unit?
A license unit is the new name for a license key in DomainScan Pro 2. A 75 computer license key from DomainScan Pro 1.x will simply be seen as a 75 license unit key in DomainScan Pro 2. The change is due to the fact that the license model in DomainScan Pro 2 is rewritten to a dynamic per-usage license model.


Can I use my existing DomainScan Pro v1.x license key in DomainScan Pro 2.0?
Yes.
DomainScan Pro 2 uses the same keys as DomainScan Pro v1.x. Furthermore v2 supports multiple license keys to support an easier license upgrade path.

Why run DomainScan Pro with Domain Admin privileges?
DomainScan Pro 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 Pro engine runs with 'domain admin' privileges, DomainScan Pro is automatically granted full access to all computers in the domain.

Will DomainScan Pro 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 Pro to run with full access to the entire network, because of security concerns (I don't trust that DomainScan Pro doesn't collect data behind my back and sends them back to GH Software).
DomainScan Pro 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 Pro is setup to send to.

If you choose to let DomainScan Pro run with limited access privileges, all that happens is that DomainScan Pro 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 Pro makes).


I've set the DomainScan Pro engine service to run with domain admin privileges, but I cannot search the domain for files/services/processes/codec's or use the WMI browser!
Network searches are performed by the client application, and are not performed by the DomainScan Pro engines. Therefore, also the client must run with domain admin privileges in order for searches or WMI queries to run successfully.

Why doesn’t DomainScan Pro detect that PAE is enabled in Windows XP, when Windows says that it’s enabled?
The WMI interface in Windows XP does not expose whether or not PAE is enabled, which means that DomainScan Pro cannot detect PAE support directly.
However, PAE is enabled, if you’re running Windows XP on a CPU where DEP (Data Execution Protection) is enabled.
In reality, information about PAE is not useful in Windows XP, due to the fact that PAE is used by 32 bit server-editions of Windows to be able to use more than 4GB memory, and Windows XP is limited to 4GB memory. 64 bit editions of Windows do not use the PAE, due to the fact that they can address more than 4GB memory directly, which means that only Windows XP SP2, 32bit edition is affected by this problem.


Why does DomainScan Pro make my device offline, when it can be pinged?
An online device in DomainScan Pro terminology is a device that has completed the scan cycle successfully.
That means that a device may be shown as offline even though it responds to a ping request.
This will happen it the device fails to respond properly once queried for information – which may lead to the assumption that the device may not be fully functional, and thus is in need of attention from the system administrator.


I have installed DomainScan Pro on a domain controller and after a restart; all computers suddenly appear as being offline!
When DomainScan Pro 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 Pro work in domain forests (or with a domain with child domains)?
Yes and no
DomainScan Pro receives the list of online computers from the server where DomainScan Pro Service is installed. This 'device list' contains a list of known devices that are known by the server. Not all devices are discovered by this method, and if leaps in the forest are unknown to the server, then the leap will also be unknown to DomainScan.
Additional devices that are unknown to the server can be added to DomainScan Pro via the device list discovery method.

How many devices can DomainScan Pro monitor?
In theory, DomainScan Pro is capable of monitoring a little more than 2 billion devices.
Monitoring a large number of devices will naturally make DomainScan Pro run slower, because a scan cycle will last longer. Even though DomainScan Pro is scalable, and the number of concurrent worker threads can be increased, it is not recommended to use more than 16 threads per physical processor.

Active Directory names aren't resolved!
DomainScan Pro 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 Pro 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 Pro will fail to receive john doe's full name ('John Doe')