Legacy Client Installation

[mikehday]

I have what i think is a very simple quetion for anyone of you with experience. I've found the legacy client installation script here \\SiteSever\SMSClient\i386\smsman.exe. And i've had experience cleaning the old client if necessary. But when using the Wizard i have the option of Automaticly selecting the installation location or Specifying the installation location. Automatic does not work ... and i'm not sure what location other than the path to the legacy installtion script which i provided. Both fail and produce the error "The wizard was unable to locate a Systems Management Server. Re-enter the instalation location"

Thanks,
Mike Day

 

[Jerz]

Sorry Mike, no answer - but I'm having an awfully similar issue. Some specifics of my site. box1 primary site server & management point, box2 server (service?) locator point, box 3 SQL server. All 2003 SP1 boxes in a 2003 AD, some client install problems, but mostly advanced clients working OK. There are 4 NT 4.0 workstations in the AD, and they all took the pushed legacy client without issue and are working fine also. Now, the problem child. I have an NT 4.0 server that is in it's own domain, and is a domain controller (only machine in this domain). There is a trust between this domain and the AD. When I run the smsman.exe from any of the \\box1\shares, I get the same messages as Mike, automatic acts as if it wasn't started from a UNC, and Specify dosen't like anything I give it, and the install won't proceed without one, even using the /F parameter. I have seen a post from 2tired2care (reminds me of an old black flag song, but I digress...) that indicates I should have an entry in WINS for SMS_SLP, but I haven't got one. Our WINS is 2003. He/She mentions page numbers in the deployment guide, but I use the one online, and it has chapters & sections, not pages.

Deep breath. So, does anyone know:
Can I install a Legacy client on an NT 4 domain controller?
If it can be done, would an SMS_SLP entry in WINS help?
Where can I get instructions for adding such an entry if needed?

Thanks in advance,
David J.

 

[mikehday]

Lucky for you I just had to fix a problem with my NT DC. Here's the instructions on how I solved it.
------------------------------------------------------------

To create a static Server Locator Point entry in WinNT4.0 WINS:

1. Open Wins server
2. Click on Mappings
3. Click on Static Mappings
4. Click on Add Mappings
5. Enter SMS_SLP[1Ah] as a name and static IP for SLP Type:Unique

To create a static Management Point entry in WinNT4.0 WINS:

1. Open Wins server
2. Click on Mappings
3. Click on Static Mappings
4. Click on Add Mappings
5. Enter SMS_MP[1Ah] as a name and static IP for MP Type:Unique

To create a static Server Locator Point entry in Win2000 WINS:

1. Open a command prompt.
2. Type Netsh and press Enter.
3. Type Wins and press Enter.
4. Type server and press Enter.
5. Add name Name=SMS_SLP endchar=1A rectype=0 ip={static IP for SLP}

To create a static Management Point entry in Win2000 WINS:

1. Open a command prompt.
2. Type Netsh and press Enter.
3. Type Wins and press Enter.
4. Type server and press Enter.
5. Add name Name=SMS_MP endchar=1A rectype=0 ip={static IP for MP}

Mike Day
Inovis Systems Engineer

 

[Jerz]

Mike,

Thanks for the tip.

If anyone is interested, the syntax for adding the WINS entry for 2000 worked fine on 2003, and I now have an SMS_SLP.

Aditional note - My MP entry is MP_(site code), not SMS_MP.

However, my NT box is still getting the same message. I'll look more tomorrow, time to go home here.