Help, help, help! I have been posted a few sms 2.0 questions here over the last couple of weeks and I only seem to be making backward progress! I know that I shouldn't put Help in my Subject Line, so I am putting it here--Help, help, help!
I really only want SMS to do a couple of very simple things that it ought to be capable of. I want it only to perform software audits on clients so that I can see what version
of a program a client currently has and I want to be able to push software updates to those programs. But everytime I make any changes, or reinstall something in order that I
have a clean slate, I just keep running into new and different problems. I can't seem to get off the ground!
Initially, when I first installed SMS server, there was communication with clients. Not only did I see the clients in the All Systems Collection, but the client software actually installed with all of the agents that I had specified. At that time, I even was able to use the remote tools to take control of a client--I only did this as a test, not because I actually required it. I even managed to push a program down to a client--that's not quite what I wanted because the program simply ran itself on the client. I really only wanted the program to get copied onto the hard drive of the client so I tried a copy command on the command line options for the program as part of a package. That did not work, and that was the last I saw of anything working at all.
In fairly quick order, my workstations began having problems with the client software. In the SMS control panel applet (on the client), the software inventory agent registered that it had problems and that a repair was pending. I tried uninstalling the client, and reinstalling but had the same problem. I never saw any clients in the All Systems Collection again either.
For the moment I have put aside any aspirations for pushing updates and auditing software. At this point, I would be quite happy if I could just see that workstations are being discovered by the server and installing the client software. I have reinstalled SMS and reinstalled one test client and now I have a brand new problem. I
have not even enabled network or windows logon discovery yet, but when a test user logs into the workstation, the smsls.bat file is still running and I receive these two error dialogues:
Slownet.exe has generated errors and will be closed by windows. You need to restart the program. An error log is being created.
Boot32WN.exe has generated errors and will be closed by windows. You need to restart the program. An error log is being created.
I don't actually mind that the login script is still running--it must still be there from my previous installation--and besides I should be able to get rid of it if I really want. But why am I getting these errors? I can't seem to even get the client installed anymore.
I am at my wits end and am being asked to produce this ability in SMS. From reading these SMS forums, I gather that SMS is not the most reliable of programs, but I sure
think it ought to work somewhat.
I really appreciate any help that anyone can provide.
I really only want SMS to do a couple of very simple things that it ought to be capable of. I want it only to perform software audits on clients so that I can see what version
of a program a client currently has and I want to be able to push software updates to those programs. But everytime I make any changes, or reinstall something in order that I
have a clean slate, I just keep running into new and different problems. I can't seem to get off the ground!
Initially, when I first installed SMS server, there was communication with clients. Not only did I see the clients in the All Systems Collection, but the client software actually installed with all of the agents that I had specified. At that time, I even was able to use the remote tools to take control of a client--I only did this as a test, not because I actually required it. I even managed to push a program down to a client--that's not quite what I wanted because the program simply ran itself on the client. I really only wanted the program to get copied onto the hard drive of the client so I tried a copy command on the command line options for the program as part of a package. That did not work, and that was the last I saw of anything working at all.
In fairly quick order, my workstations began having problems with the client software. In the SMS control panel applet (on the client), the software inventory agent registered that it had problems and that a repair was pending. I tried uninstalling the client, and reinstalling but had the same problem. I never saw any clients in the All Systems Collection again either.
For the moment I have put aside any aspirations for pushing updates and auditing software. At this point, I would be quite happy if I could just see that workstations are being discovered by the server and installing the client software. I have reinstalled SMS and reinstalled one test client and now I have a brand new problem. I
have not even enabled network or windows logon discovery yet, but when a test user logs into the workstation, the smsls.bat file is still running and I receive these two error dialogues:
Slownet.exe has generated errors and will be closed by windows. You need to restart the program. An error log is being created.
Boot32WN.exe has generated errors and will be closed by windows. You need to restart the program. An error log is being created.
I don't actually mind that the login script is still running--it must still be there from my previous installation--and besides I should be able to get rid of it if I really want. But why am I getting these errors? I can't seem to even get the client installed anymore.
I am at my wits end and am being asked to produce this ability in SMS. From reading these SMS forums, I gather that SMS is not the most reliable of programs, but I sure
think it ought to work somewhat.
I really appreciate any help that anyone can provide.
