Search results for query: *

I am having a similar problems with a lot of our users. They are running a publish app and everytime they click on it, it goes up to the citrix log on script then dissapear. The icon on the taskbar is there for a few seconds then disappear as well. I have done to many this to fix this and even...

Thanks again Jpoandi. You seem like the only person to help. Anyway I have done that and it did not work. I did some research and found out that sometimes when you re-install a site the account that it use to connect to the CAP get messed up. Mainly the smsclient_xxx. The password for it is...

Thanks Jpoandi I apreciate your response. Unfortunately that did not help. I have also tried it with new and old packages and it only work on some machines. It might be a bug with the service pack. I don't know. Its very annoying. Any other suggestion?

Try this also http://support.microsoft.com/support/kb/articles/Q223/3/72.ASP?LN=EN-US&SD=gn&FR=0

well then delete the collection and re-create it. that should take care of it I believe

Try thishttp://www.swynk.com/trent/Articles/DupLogin.asp

Try this http://www.swynk.com/trent/Articles/forcesoftware.asp

When you remove SMS server from any box it does not remove the client. A SMS Server is also a Client to itself. Did you try the Clicln?. I know it works well with 2.0. You also have to remove some registry settings..

Go into SMS service manager and try stop and starting the SMS_SOFTWARE_INVENTORY_PROCESS or any other service that related to software inventory.

Clicln.bat from the sms suportablily tools might do the trick. I should be in a folder called cleancli. How did get sms 1.2 client to be no a server with sms 2.0 sp3?

Sounds like you are having a rights issue. Make sure if you manually run the execuatable you are do so with admin rights. otherwise make sure when you advetise it, Its set to run with admin rights.

I am hoping someone can help me with this other problem. I recently change one of our servers from bdc to a dc. This machine use to be a secondary site server. I re-install sms on it and now I am having problems with client installing. When I check the logs they are getting the error message...

I was running SMS 2.0 sp2 and recently upgraded to sp3. Since then whenever I send out a package to clients I get this error message "SMS Offer status summarizer cannot process a status message because it has an invalid message ID 699. The message ID must be within the range 10000 to 10099...

If you are upgrading the clients will be fine, but replacing no. Your best bet is to back up the database of the site to be replaced. Configure the replacement server with the same name, address, drive configuration, domain etc. You can do a clean install of SMS and SQL. Then you can retrive...

Upgrade the current SMS Server with SP2 along with the secondary sites. It will take a few hours to upgrade the clients but will do so automatically. Then if you wish to add a new SMS Primary Site you can do so and attach the current primary site to it. If you do not upgrade your current Primary...