Remote tools don't start

[Guest_imported]

Hi, I've installed SMS 2.0 on a dedicated server in a Windows NT 4.0 domain.
I've activated all agents, I have discovered all machines/users/user groups using discovery services, and I've also manually installed client on some machines (in order to do some preliminary tests).

When I go in my collection, I try to start remote tools on one machine, then I get an error message 'remote control agent not found'

I tried to go to the microsoft support page, to search the web for information about that, but I didn't find anything helpful...

Just some additional information :

- First of all, modification of logon scripts doesn't work. It created a script called smsls.bat, which is called nowhere in the usual script.
- Note that I tried to launch smsls.bat manually on workstations, but it requires a variable called SESSIONNAME or WINSTATIONNAME, and no environnement key has been created.
- Also when I installed the client on the computers, it installed me the Systems Management applet in the control panel, but I can't do anything with it (no update, no configuration, etc)
- Finally I wonder about one thing : after installing smsman.exe on some workstations, is it normal that no additional service is created ?

If someone has got information about what I must have done wrong, thanks for his help.

 

[Jpoandl]

It sounds like your jumping the gun a bit. Did you set up your site boundaries? Site boundaries define what computers are going to part of your site. You can discover machines outside of your site boundaries...but they will not install if they do not belong to subnets listed in your site boundaries.

There is a ton of information on Tek-tips on setting up site boundaries. If you think this is your problem, do a search on tek-tips for site boundaries.


Hope this helps.
Joseph L. Poandl
MCSE 2000

 

[Guest_imported]

Well, I've resolved part of the problem, it was mainly a matter of boundaries. I thought that with a B-class subnet it would be OK, but it wasn't.

Now it has detected some machines (and remotely installed clients on it), and some other are still invisible in my site. I hope it'll be OK during the night (I'm in Europe

I've got another problem : I've got no user to take remote control of a machine. My own user is domain admin, SMS admin, I've set full access for the admins in the security part of the site, and even as local administrator, I can't remotely log on a machine. I think SMS should have created a local group for the remote control, but it just has created 2 local users (SMSCliSvcAcct& and SMSCliToknAcct&) and some global groups & users, whose passwords I don't have got...

I believe I'm near the solution, but we have been blocking on that since last wednesday.

Thanks for your help !

 

[Jpoandl]

Sounds like your SMS Site Server security needs to be modified to provide access for other domain users.

First check out this Technet document on how to set up security:

http://support.microsoft.com/support/kb/articles/Q201/1/26.ASP

Post if you have specific questions...

_I hope this helps... Joseph L. Poandl
MCSE 2000

 

[Guest_imported]

OK, never mind the security for now, I've configured full access for all domain admins :

In the remote tools client agents settings, I've set administrators, SMS admins, domain admins groups, and I've manually added all domain admin accounts to be sure.
In the security rights, I've done the same, with full access on all classes and all instances for each domain admin and each SMS admin.
In order to be completely sure, I finally added the SMSClient_xxx and SMSServer_xxx in both security lists.

And I still can't take remote control of any computer in my domain (all are assigned, with client installed and configured), the message says 'The currently logged-in user doesn't have rights to access the client machine'

Please note that I manually created a 'RConsole Users' local group on the machine I'm doing tests with, and I've assigned any domain or SMS admin to it.

Is there a windows component needed, such as a CAP ability, or something like it that I would have missed ?
By the way, can anyone tell me what is the WMI or WBEM configuration ? I think it's used for distant login on machines, but I'm not sure to have done right operations.

Thanks