Thanks for your reply, despite the problems it leaves me with !
I am hoping you can give me your input on my understanding of how the
LOCALSVR and SETSMSVR should actually work, as the BORK documentation is
adequate without being specific.
In theory, running LOCALSVR against the SMS database should give you a
listing of all site systems and their respective roles. Assuming this works,
you then advertise SETSMSVR along with the .ini from LOCALSVR. So far, so
good. When the client runs the advertised program, SETSMSVR compares the IP
address (or subnet) of the client with NAL entries in the .ini file and sets
any that match as preferred servers on that client. This implies that only
servers in the same subnet as the SMS client can be set as preferred.
Ther problem seems to occur when you want to set preferred servers in
another subnet to the client - if you can't edit the .ini without causing
the errors you described (I tried this and got the same error as you in a
client in one subnet, but got the error 'No matches found' from the same
advertised program in another subnet !) then you can't REALLY set preferred
servers at all.
I have an instance where a local LAN contains several subnets, the clients
being on different subnets than the servers. As SETSMSVR sees no matches
between client IP and server IP in the .ini, it doesn't set any preferred
servers - this means that my clients can now do interesting things like try
to install NT SP5 from ANY Distribution Point, including those at the end of
64k WAN links !!
I would be very interested to hear from you if you make a breakthrough.
> Hi Richard,
> I've been working through this problem for about 3 weeks now to no avail.
> What I've noticed is that when the file generated by localsvr.exe is
> modified manually, following the same syntax and being careful to increase
> the # of site systems at the top of the list, client calls to setsmsvr.exe
> fail with the error;
> "No site systems section found in specified ini file"
> I too have problems getting localsvr.exe to generate a complete list of
> subnets and site systems. It usually includes most of the site systems,
> seems to leave out various site components seemingly randomly (I have yet
> find rhyme or reason).
> At any rate, I have put this issue "aside" for now and moved on...if I
> discover anything more I will post my results to this newsgroup.
> Jody Tomlinson
> Merlin Consulting
> >I am using LOCALSVR.EXE to extract the NAL paths for an SMS 2.0 site, in
> >order to feed a modified version of this info to SETSMSSRV.EXE and get
> >clients on the far side of slow WAN links to use their local DC as a CAP
> >Logon Point, instead of randomly connecting to any in the NAL list.
> >I noticed, however, that when I run LOCALSVR.EXE against the site
> >it only returns the paths for the servers in the local subnet - a slight
> >problem when I have about 30 subnets to worry about. I'm assuming I can
> >modify and add entries quite happily by following the existing syntax of
> >outout .INI file, but would like to know if anyone else has experienced
> >Richard Davies