FAQShop.com: Managed Computer Scan Works for Windows 2000 Machines but not NT 4.0

Managed Computer Scan Works for Windows 2000 Machines but not NT 4.0

I am in the process of trying to install 60 agents at a remote location, the majority of which are NT 4.0. The rest are Windows 2000 boxes. My dilemma is this:

I have added one Windows 2000 and one NT 4.0 machine to the managed computer rules, and ran a managed computer scan. The agent manager promptly picked up the Windows 2000 box and processed the agent install with no problems. The same did not occur for the NT 4.0 box. The agent manager does not seem to pick up the box or install the agent, although the box is pingable by name. The environment is an NT 4.0 domain.

Contributed By: Baelson Duque [MSFT]
First the obligatory question: Are you running MOM SP1?

If you do a "net view /domain:<DomainNameHere>" do you see the server name here? I've found a few times that even if I could ping it (might be a cached NetBIOS entry) that the MOM Server may not find it.

But any servers that I don't see it in the "net view" list, MOM never picked up. This usually got resolved by doing something like "nbtstat -RR" on the server you can't reach.

Lastly, you can also try using the "AMScanSingle.vbs" script in the "<MOMInstallDir>\OnePoint" directory on the DCAM. The commandline options are pretty obvious.