The best option here would be to split the networks. As you know, Windows really doesn't allow 2 nodes with the same name on the same network. So Network Inventory Advisor shouldn't do this either. Locating 2 nodes with the same name, our software will treat them as the same node which changed the IP address, and that's also correct. In your case, I would definitely do the import of one complete network, and then quit Network Inventory Advisor. Then rename the [information] folder to something like [information-Net1]. Then launch Network Inventory Advisor again, and complete the import of all nodes from the other network range. Then you can easily switch between networks without conflicts. The next major release of Network Inventory Advisor is going to feature full-blown multiple networks management.

Jeff,

How do I do that? when I renamed the information folder, it comes up a blank network. How do i switch between two separate networks? do i have to rename the information folder everytime?

andre said: do i have to rename the information folder everytime?

[information] folder has all the details about a specific network. So when you have everything in place in Network Inventory Advisor, quit and rename. So when you need to get back to that network, quit and rename backwards.

Jeff, any idea when the next major release will be out?

Only hopes :) email me, I might share some data from our roadmap. Can't post it publicly. Or we can finally talk via Skype, once we finally match timing...

Sorry for my bad english... As for me i did next thing (I also have to scan many subnets in many domains): as first, i scanned first subnet and has received couple computers with names (for example) comp1, comp2,... i has opened every [Information.xml] file in every [computername].[domainname] directory. Next i found tag CompName="COMPx" and rewrited it to CompName="COMPx.DOMAINx" and then i has scanned the next subnet and also rewrited all "CompName" tags in all [Information.xml] files. In the end of my experiment i turned full scan of all subnets and all of my computers were defined correctly. Taking into account that iadvisor.exe it is possible to launch in command line with parameters, I think, it is possible to write a script automating my actions (At most yet there was no time to be engaged in the decision). Maybe it will help you.

I'll comment on this shortly.

OK, seems like you are using a nice workaround. One update though: don't forget to rename those nodes in common.xml as well. This issue will be addressed in version 4.x.