SMS 2003 Discovery installation Problem on 2K

[Karactur]

I have recently installed SMS 2003. I like it! I was previously in an SMS 2.0 environment but have upgraded to 2003. I am working in an NT Domain with mixed clients. NT,98,2k,XP. All of my NT4 clients have connected to the new site, upgraded, become clients and produced an inventory. My 2K clients however, are discovered, assigned to the new site, but do not become clients, upgrade or inventory.
I have been able to manually install the client by pointing to the SMS site. It successfully installs the client components and inventories.

Any Ideas why they will not do this automatically?

 

[2tired2care]

Sorry, just need a little clarification...

The SMS 2003 client installed on all PCs with NT, 98 and XP operating system installed, but not on any PCs with 2K operating system installed.

Is this statement correct?

 

[Karactur]

The client ONLY installed and updated on the NT4 systems. The Win98, XP, 2K all need to be manually installed, or pushed from the SMS Management console.

I assume this has to do with the Advanced client for the XP, and 2K systems. Since I cannot seem to resolve the SLP for advanced installs, I assume it would continually fail.

The Win98 systems,..... I will install those puppies manually or through logon scripts if possible.

Thanks for anything you can offer.

 

[2tired2care]

First quick item to check on Windows XP clients...
To enable Client Push Installation for client computers running Windows XP SP 2, enable File and Print Sharing in the Windows Firewall (formerly known as Internet Connection Firewall, or ICF) configuration on the Windows XP client. For more information about deploying SMS clients, see Chapter 10, “Planning Your SMS Deployment and Configuration,” in the Microsoft Systems Management Server 2003 Concepts, Planning, and Deployment Guide. For information about how to configure Windows Firewall on Windows XP SP 2, search for "Windows Firewall" in Help and Support Center.

Next issue....Configuring for Client Push
I don't know if you are using the site wide Client Push or the Client Push Installation Wizard (which allows you to just push the SMS client to PCs within a specific collection).
If you are using the site wide Client Push, you need to configure the Client Push Installation and ENABLE it.
If you are using the Client Push Installation Wizard - the Client Push Installation configuration is automatically used by the Client Push Installation Wizard (and still needs to be configured) even if Client Push Installation is not enabled. For details see the Concepts, Planning and Deployment Guide, page 597.

Next issue....WINS
You need to make sure that the WINS database has two entries in it:
MP_xxx (where xxx is your 3 character SMS site code)
SMS_SLP
Use the WINS Manager utility to see if both of these entries are in the WINS database
Easiest way to locate - since you know the TCP/IP address of your SMS 2003 server - sort the WINS database by TCP/IP address.
Can't find the entries? ...Now the fun begins!
Assumption: Your WINS server is installed on a Windows NT Server 4.0
Download and install WINSCL from the NT Resource Kit SP4.
Since WINS is running on a Windows NT Server, you will need to use the WINSCL.EXE utility. WINSCL is CASE SENSITIVE for its commands. WINS is CASE SENSITIVE for the WINS entry names.
FYI - WINS entry names are generally in UPPER CASE.

WINSCL (to start the program)

If you need to add the SMS_SLP entry, then follow these steps:
\\xxxxxx (provide the Netbios name of the WINS server)
RN
SMS_SLP
1
1A
0
0
##.##.##.## (enter TCP/IP address of your SMS server)
1

If you need to add the MP_xxx entry, then follow these steps:
RN
MP_xxx (where xxx is your 3 character SMS site code)
1
1A
0
0
##.##.##.## (enter TCP/IP address of your SMS server)
1

To exit from WINSCL:
EX

Note: If you have WINS installed on a Windows 2000 server, multiple scopes in WINS, need more details or have other complexities at your facilities - then see the Concepts, Planning and Deployment Guide, page 558.

Next step...check the client PCs
Please don't feel insulted by this suggestion, but you need to verify that the SMS client was installed on the client, but NOT detected by the SMS server. Go to the CONTROL PANEL for the client PC and check for a control icon called SYSTEMS MANAGEMENT. If you don't see the control icon, then SMS client wasn't installed. If you do see the control icon, then SMS client was installed, but might not have been discovered by your SMS server. In which case... 1. Double-click the SYSTEMS MANAGEMENT icon. 2. Click on the ADVANCED TAB. 3. Click on the DISCOVER button - you should get a confirmation that the client PC found the SMS server site.
FYI - One good test of if the WINS entries are working correctly is to use the DISCOVER option under SYSTEMS MANAGEMENT. Not found/error message - WINS entries could be missing or incorrect. Found - WINS is OK.

 

[Karactur]

Thanks for the reply.

Assumption correct on the NT4 WINS server. NT4 DOMAIN.
Client Push is enabled on the server and configured for the site ID. I have enabled the SMSSITECODE=XXX to my site code and ensured it was set to push. I am using a Domain Admin account to push the installation.

WINS:
This was the first time I heard of the WINS entry for the MP. I have been inserting the SMS_SLP entry using the method described without success and became excited to see something new. However, after adding the entries, both SMS_SLP & MP_XXX, my clients still could not automatically discover the site code. I verified by testing on a system I had "Pushed" the client to previously. That client installed fine btw.

I am convinced it comes down to the discovery resolution of the SLP. I can install the adv client manually or even the Legacy client if I want to, however, the Legacy client cannot find the SMS Site server automatically unless I specifically enter the path to the CAP_xxx folder on the server. At which point, the legacy client installs. Those are not my problem, but the info may be useful in troubleshooting.

I always appreciate ANY suggestions, no matter how small or insulting they MAY sound, I want this site to PURRRR.. and until I get certified, I'm plugging away!

Thanks again!

 

[2tired2care]

Regarding the need for the to WINS entries - SMS_SLP and MP_xxx. See the Concepts, Planning and Deployment Guide, Page 559.

Management points (MP_xxx) are normally automatically registered in the WINS database. If this entry does not exist, then we need to talk for a moment about SMS roles...
The Advanced Client install require entries in the WINS, a Server Locator Point and a Management Point. See the Concepts, Planning and Deployment Guide, Page 563-564.

By default, the primary SMS site does ONLY the following roles:
Site Server
SQL Server
Component
Client Access Point (CAP)
Distribution Point

Notice that by default it does NOT include a Server Locator Point or Management Point. See the Concepts, Planning and Deployment Guide, Page 572 - step # 4. Suggest that you enable ALL the roles on the primary site - Server Locator Point, Management Point and Sever Locator Point.

FYI - At my location we have the primary SMS site serving all the roles.

 

[Karactur]

I have enabled all roles on my Primary site. That is why I'm so frustrated in this procedure. I definetly need to get the book on this issue to see if there might be something I'm missing. I do not see how these entries would be in WINS automatically, as all documentation I have found on 2003 in an NT domain state a manual WINS entry.

-Still puzzled.

FYI: I am currently working through numerous issues with the advanced clients that were pushed to the 2k servers and Wksts. Many Firing events that I have subsequently patched, as well as Citrix interoperablities causing connection and logoff problems.

I hope to find a way to remove the advanced client for now, and restore the legacy client until further patches are out for the advanced client.

Keep the advice coming, and any further suggestions you may have.

 

[Thermes]

Karactur,

Have you figured out what causes your citrix box to hang? I am having the same problem. Please let me know if you have found something.