Search results for query: *

Check which version your are running. You can do this trough the admin console. If you need more details let me know.

I not sure of the size of packets it uses. You might want to check out "myitforum.com". They also have a forum for SMS and numerous articles etc that might address your question.

I found this article on Microsoft technet that might address your issue: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q224197 If you are using smsman to install SMS on the clients, you might want to test using "smsboot1.exe".

Have you already resolved this problem? If so, let me know what you did to correct it. If not, I would rebuild the server from scratch. Were there any errors during the initial install of SMS? Have you tried rebooting the server and see if the service will start? We are currently using a NT...

I would run "newuid.exe" to remove the duplicate guids. Check out "myitforum.com" and search for "duplicate guids". There are numerous articles on this which are very helpful.

I would check the logs for any error messages on the sms server. Create a test package and target a few pc's to see if they can receive the package. Also, check the clients machines logs for any error messages. Are your SW and HW inventories working? The only time I have experienced packages...

What version of SMS are you running and what Service Pack? Are these machines Windows 2000 or NT? Is the "KEY" not working on all the pc's or a select few? I have encountered this problem on a few of my NT and Win2k boxes. Uninstalling and reinstalling the client (more than once)...

How many pc's do you have? Why are you having to send the advertisements to each pc individually? You can create a collection for a specific group of machines with various criteria if needed. I would check out "myitforum.com". It contains articles about collections, advertisements...

We run "smsboot1.exe" in the login script. It checks and makes sure the machine is a client and if not it will install SMS. How many 98 machines do you have? Did you check the logs on the clients machines for clues and make sure all the components were installed?

I would check the logs for any error messages on the sms server. Create a test package and target a few pc's to see if they can receive the package. Also, check the clients machines logs for any error messages. Are your SW and HW inventories working? The only time I have experienced packages...