philipnet

I received this error message when trying to start a remote tools session.

I couldn't understand this, one minute it was working - the next it wasn't?

I googled on the error message and came across various postings which all said to check the permissions of the users trying to start a remote tools session.

It didn't take too long for it to dawn on me that, as I had just changed my password, the system was being a bit upity on me.

As I'm loathed to reboot my workstation, and I was in the middle of troubleshooting a remote PC with a VPN connection, I just made use of the Run As facility within Windows 2000 to run the SMS MMC as myself, but with my new password  .

Problem: The SMS client isn't being sent out to our new/re-setup machines and I don't know why!

I eventually got round to having a look at
  C:\WINNT\System32\ccmsetup\ccmsetup.log
on the client machines SMS was trying to install on. Every 10 minutes SMS was trying to install the client on the machine, this failed everytime with the same error message.

Googling produced this result which lead me to have a look at the accounts SMS was using to install the client with.

I first found and altered Systems Management Server -> Site Database -> Site Hierarchy -> -> Site Settings -> Connection Accounts -> Client , with no luck.

I then found and altered ... -> Client Installation Methods -> Client Push Installation -> Properties -> Accounts , again with no luck

Finally, after looking through the SMS help guide I found and altered ... -> Component Configuration -> Software Distribution which stores two account and password settings (one for the different types of clients).

Lo and behold it worked. The SMS client started being installed on the machines!

It's a pain if you get that message when trying to install SMS on a server. (As an aside, I'm currently building a test domain with Windows 2000 Server, SQL Server and SMS on one machine with a couple of other machines in the domain as well. It's great being able to set create things from the ground up as you get to find all the idiosyncraies that have already been ironed out in a production system).

So, I checked out Google Groups and found an article which stated that the logged in user needed to be a member of the Schema Admins group and that the schema needed to be configured to allow the schema to be extended. As I was logged in as “administrator” I new that the former was the case - so how do I go about extending the Schema?

Some searching on Microsoft's website revealed that I needed to install the Active Directory Schema snap-in and then allow this computer to extend the schema.

I've had this one a couple of times - most recently when rolling out another set of software updates.

Microsoft detail what these codes mean on their website at: http://www.microsoft.com/downloads/details.aspx?familyid=9F009942-B4D8-4A70-8F74-E81CCC7B2309.

Simply put, SMS needs you to run the Security Update scanner before it will install the software update. I haven't had a problem with the expedited variant and I think that makes most sense in the circumstance.

And a quick plea for help: has anyone got any experience with EdTools Steadfast or similar and SMS?