SeventeenorBust

[VirtualLarry]

I just had something disturbing happen with SoB.

I had previously only had a single account on this XP PC, an admin account. I installed SoB, and ran it as a program (single-instance), not as a service.

Well, I implemented Software Restriction Policies today, and as part of that, I created an additional Admin account, and demoted my account to a Limited account.

Well, when I logged in to the Admin account, guess what? SoB started. So I had two instances of SoB running on the same single-CPU machine. Not good. What was even worse is, they were both running the SAME K and N values. Definately not good.

So I stopped the instance that was running in the Admin account, and left the one in my user account running, since it seemed that it was farther along. I hope I didn't screw up the WU by having two SoB instances at once running on it.

So my suggestion is, if you currently, or plan on, having multiple accounts on the PC, then always, always, install SoB as a service.

PS. What is the default host name for SoB for the client to get WUs? Is it sb.pns.net ? I changed mine to an IP address last time we had an outage, and I want to change it back.

 

[Silverthorne]

sb.pns.net is correct.

 

[VirtualLarry]

New problem. I let SoB (installed as an app) finish it's block and exit. Then I logged into my Admin account, and installed it as a service with sobsvc -i. I then started the service, and SB appeared, on my limited-user account's taskbar. However, the icon was red, and the error message was "block denied".

Has anyone been denied a WU before? Any ideas why this is happening?

Hmm. I changed the location to sb.pns.net, stopped and re-started the client, and now it's running normally.