SMS 2003 can't find all systems

[Nick85]

I have tried to bring the server into our domain.
Now i see all users and user groups of the included subnets. But if want to see all systems of our domain the online system i can see is my server...

I have installed on test computers the advanced clients, most other computer have the old 2.0 client.

Can anybody tell my how i can see all systems in my administrator console?

 

[Jpoandl]

Not sure...your description leaves a lot to the imagination...can you explain your situation better?


"I have tried to bring the server into our domain." what server? and existing server into the domain?


"Now i see all users and user groups of the included subnets. But if want to see all systems of our domain the online system i can see is my server..." Where do you see this?

"I have installed on test computers the advanced clients, most other computer have the old 2.0 client." did you upgrade an SMS 2.0 site server to SMS 2003? or do you mean to say the legacy client?





Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

 

[Nick85]

I'm sorry for that bad description. Now I will try to explain this points better:

I have installed a new Server with Win 2003 server, SQL 2000 Server and SMS 2003 Server. Then I've tried to get this server in an existing domain. In this domain the SMS 2.0 Server is still running at the moment. I have there some workstations with the SMS 2003 Advanced-Clients there.
In the SMS Administrator console under my site i opened the Queries and I have tried to see there under the point "All Systems" all my machines in the network that have a NIC. But the only machines i can see there are the server and 3 routers of our network. But if i want to see (under Queries) "All Users" or "All User Groups" it shows me all the user /-groups of our network...

Now to the client. I told above that we have a SMS 2.0 system in our network and most clients in the network have installed the SMS 2.0 client on itself. Now i installed new workstations with the SMS 2003 Advanced Client on it.
So there are no updatet clients...

Sorry for my bad english and for the grammatical mistakes

 

[Jpoandl]

Ok...I think I understand your situation a bit better. It sounds like you have a pre-existing SMS 2.0 site and that you are migrating to SMS 2003. This is possible...

Are you running Active Directory?

Just like SMS 2.0, SMS 2003 requires that you define site boundaries. Because you are migrating SMS 2.0 clients to your new SMS 2003 site, you will have to overlap your boundaries for a period of time.

1) Define your site boundaries. You can use subnets (just like in SMS 2.0) or Active Directory sites.

2) After your define your site boundaries to include your clients, you then have to discover your clients. You can use Network discovery (easiest method) for this...or choose another discovery method.

3) after discovery happens, you may have to Update Collection Membership and/or REFRESH the collection (right click on your All Systems collection to see these options).

4) once you have discovered your clients, you can choose to install the new client and force them over to your new SMS 2003 site...right click the client and choose INSTALL.

-hope this helps...

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[Nick85]

Thank you at first... Yes, I'm migrating from a pre-existing SMS 2.0 site to SMS 2003.

No, I'm not running an Active Directory, I have defined site bounderies.

I did all the points you told me. I have defined site bounderies and I have chosen my discovery method (network discovery).

Now if I'm trying to execute your 3rd point, I can't find any System than my own SMS 2003 Server and 3 routers.

I think there's only a mistake in my options, but I have no idea where it could be.

 

[Jpoandl]

hmmmm...

maybe you should try to install a client manually. Then look at the client logs to see if it give you more information about what the problem is.

It sounds like you have a subnet boundary problem. Remember that when you define your subnet boundaries, you need to take the clients SUBNET MASK into consideration.

For example, if you clients IP setting are 10.10.2.x with a subnet mask of 255.255.255.0, you will have to enter 10.10.2.0 into your boundaries. entering 10.0.0.0 or 10.10.0.0 will not work. This is because SMS uses the clients subnet mask to determine whether the client is in the SMS site boundaries.

Also, there is a slight possibility that your router is blocking ports... Do you have a firewall between subnets?





Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[Nick85]

I found the reason of my problem:
I have no Active Directory, no Microsoft DHCP, no SNMP-service and no routers where the server could get the adresses from.

So I had to install the SNMP service on the clients to find them under all systems.

All of this, thanks a lot for your help.

 

[Jpoandl]

Glad to see that you got this sorted out....however,

You should still be able to do Network Discovery (doesn't require anything but having systems on the network.)

However, on important thing to do when setting up a Network Discovery is making sure that your program the Start Time several minutes in the future.

For example, if it is 10:00am and your are programming the Network Discovery, you should put the start time at 10:10am. (not 10:00am)

The reason is that the SMS mechanisms to evaluate the new setting will take some time to process. So, if you set the start time too soon, the Network Discovery will fail....so you need to allow lag time.



Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)