vanith

The standalone tool worked like a champ. I will flag the workstations in question and see what I can do with those after our deadline has be met. We are upgrading all of our old workstations to Windows XP and most likely these machines will be replaced if they do not meet our requirements for upgrade, so it will give me the chance to sideline them and figure out more information about them in a couple of months.

I did all of my workstation scanning on a simple HP 5100 desktop then shared out the database storage on a server because we don't have those kinds of resources at our disposal. I have read other posts that if it freezes up on you like that, try scanning a smaller section to see if that works.

Actually, out of 700 workstations/servers/external Jet direct devices, we have had only 60 computers that have come back with various problems. Most of those problems are either a Firewall, DNS (on our side), spyware, or this prolong scanning. Out of the 60 workstations, there are probably less than a hand-full that are giving us this prolong scanning problem. All of them are Windows 2000 machines, so I'm troubleshooting further why it's doing this. This product has saved us a lot of time since we do not have the human resources to scour all of these devices to find out the information as we are close to meeting our deadline for full inventory of our network. We only have a single AD/Novell Domain here and it's work wonders for us. Less than 10% of our network has been identified as having problems and non-compliant to our inventory, for us, this is a lot easier to do.

It is stuck on Win32_LogicalDisk on Windows 2000 machines.

Has anyone run into a problem with the TNI taking forever to scan a workstation. I have about 700 workstations in my environment either running Windows 2000 / XP in a single Active Directory domain in a LAN. I have three workstations that are doing this, 2 of them are Windows 2000 and the last one is Windows XP. I will gather more information from it tomorrow, but I have left it on a pecticular scan of 1 Windows 2000 workstation for over 4 hours and it still was not done scanning. The rest of the workstations would take no longer than 3 minutes to finish compared to these three. I will keep everyone posted because it's strange indeed. Vanith

Yes, this was our problem as well. I tried using the name or scanning through the Active Directory, but that error would pop up. I used the IP address and it did resolve our issue as well. Thanks! Is there a way to get the FAQ updated with this information as well?