| Title: | POLYCENTER AssetWORKS + Microsoft Systems Management Server |
| Notice: | See note 937.1 for kit access information access |
| Moderator: | RDVAX::LEVY D |
| Created: | Wed Feb 23 1994 |
| Last Modified: | Fri May 30 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 977 |
| Total number of notes: | 3989 |
How do you get a Unix client to end up in the Sms hierarchy where you
want it to be and not in some default place. If you have a large
amount of sites you want the clients to show up at specified places in the
hierarchy.
Is this possible to set where you want the client to show up, which
site and which domain, under the installation or after?
Regards
//Pierre Schuster
NSIS
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 967.1 | No support in PAW$EXEC | SUBSYS::CARLETON | A paradigm shift without a clutch | Mon Apr 14 1997 12:05 | 15 |
There was a file, I think it was called smsls.ini that would allow you
to assign the PC clients to other than the default domain. I think it
would be unlikely that using this file would help with the UNIX clients
but you may have to try it to find out. It's a question of where SMS
refers to this file. If it is used durring inventory then it will not
help with UNIX clients.
The part of PAW that assigns the domain is called PAW$EXEC. There is no
support in PAW$EXEC to assign other than the site server's domain. You
could segragate UNIX clients by using more than one site server to
collect the inventory. This might fall out of a configuration for free
if you were going to set up one SMS site server per site anyway. If
you want to sort into more than one domain per site, you might be out
of luck. There may be a way to hack around it but I've been away from
the code too long to know if it would work.
| |||||
| 967.2 | BHAJEE::JAERVINEN | Ora, the Old Rural Amateur | Tue Apr 15 1997 11:50 | 6 | |
SMSLS.INI is the way to do it for PC clients. It is read by SMSLS32.EXE
(or SMSLS16.EXE) during logon. (Basically, you always have this problem
if you have more than one site server per NT domain).
As to PAW, no idea...
| |||||