SMS 2003 SP2... installing legacy client on NT servers and Win 98 Machines

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello,

I've run into a strange little problem in getting SMS up and running.

SMS 2k3 SP2 is running on a single Win 2k3 SP1 server (it is the only
site). I started by having SMS use Active Directory discover, but
remembered that this would miss all of our Win 98 and NT Server
computers, so I added network discovery.

I set the boundaries up (based on subnet) so that all of our subnets
are accounted for. I have SMS set up to install whatever client is
needed based on platform.

So the discovery ran and found pretty much all of our 2000/XP/2003/NT
Server machines... but none of our Windows 98 machines. I've been
checking the 98 machines out and they have file & print sharing
enabled.

Ok, so the first question is: how can I get my Windows 98 machines
discovered? I noticed one interesting thing: when I am in the Windows
98 machine (via PCAnywhere) and I go to the command prompt and ping
"sterlingsms" I get responses with no problem. However, if I go
Start>Run and then "\\sterlingsms" I get an error box "The network came
cannot be found." I also tried "\\sterlingsms.sterling-usa.com" and
also "\\192.168.2.100"... both get the same error.

Ok, next question: my NT servers are getting discovered with no
problem, but the client won't install. When I am in a Windows NT
server machine (via PCAnywhere) and I go to the command prompt and ping
"sterlingsms" I get responses with no problem. However, if I go
Start>Run and then "\\sterlingsms" I get an error box "The network came
cannot be found." However, when I try either
"\\sterlingsms.sterling-usa.com" or "\\192.168.2.100" I can explore the
network shares on the sms server. I then run smsman.exe, but I have to
manually type in the installation location (automatic fails).

I tried setting the FQDN on the sms server, but that didn't seem to
work. Any advice?

Thanks in advance

.

Relevant Pages

  • Re: SAP client advertisment runs on wrong computers
    ... SMS doesn't directly go to DNS to discover any records. ... network discovery then SMS will go to DHCP to discovery machines. ... > and "Adv Client Spy" confirmed that advertisment was applied and actually ...
    (microsoft.public.sms.swdist)
  • Re: XP clients do not appear in Collections
    ... You may have to enable logging on your server through the Tools - Service ... XP machines were not discovered until I created a collection ... .ddr file on clients. ... >> What discovery method did you enable? ...
    (microsoft.public.sms.admin)
  • Re: Network discovery Search to Subnet
    ... QIP (another system DHCP - not compatoble with SMS). ... I want to use the network discovery search by subnets but it doesn't work. ... Windows Server System MVP - SMS ... 360 secondary site 2003 sp2 ...
    (microsoft.public.sms.admin)
  • Re: Backup and reinstall
    ... I played with this in my test lab, and the machines did not report in until ... You have laptops with SMS agents on them. ... > correctly provided site code & site server name. ...
    (microsoft.public.sms.setup)
  • Re: Help need desperately!
    ... > Have you given your SMS Server's machine account FULL CONTROL of the Systems ... > machines are already discovered or you wouldn't be able to push to them. ... > Check through the SMS Server logs, ... All clients are discovered, assigned and have successfully installed the ...
    (microsoft.public.sms.inventory)