Saiweb

So you have domain admin rights, but that server just wont play with remote desktop … you suspect a hung process what do you do?

Have someone log into the console (if they can) ?

Or surely there is another way …

Windows XP (Surprisingly) has a command line tool set for just such an event, in this case the two commands. (Via command line Start > Run CMD)

“TASKLIST”

and

“TASKKILL”

Just run off the list of processes using TASKLIST and kill the “offending” process with TASKKILL, if you can not figure out how to do that by reading the documentation via the links above, then I really do not recommend you use this method.

Oh dear oh dear, MS at it again.

Accoding to this story: here

SP3 has caused a huge rollout headache including screwing MS’s Point Of Sale application …

See now this is what happens when you FORCE users to have to install SP3 before they can get any more updates ><

Admitedly the users experiancing the problems all using Automatic Update …

So my advise is to grab the complete Network distribution (about 319mb).

Update if you are having problems and are using an AMD machine read this: here

Well it’s finally here!

And I get the fun task of testing this service pack and then rolling it out over a few hundered laptops located all over the place!

Oh well, I’m using my laptop as the test subject at the moment (poor thing), I’ll post updates with any problems I run into along the way.

UPDATE:

Well I realy do suggest you set aside a good hour per machine for this update (bare in mind I am using the Netoork rollout pack 316mb), especially if the client machine has windows live messenger installed, which seemed to need some sort of update entailing 30 minutes of wasted time.

If you have an antivirus running during the install it will take even longer.

Other than that _thusfar_ I have had no problems with SP3. Post a comment if you get stuck though.