SMS 2003? Meet The Princess
After successfully (ok, so mostly successful) getting SMS 2003 rolled out to our user base, it is now my new task to roll this pretty lil package out to the other five geographically separated entities in my Video Game Making Family.
Some may say, oh no Princess, this can?t be done. Some may even say oh Princess, your head must already be hurting from this mess. A ha I say to them! A ha indeed.
This is an awesome opportunity for me to really sink my pearly whites into SMS and get to know the nicks and crannies on a more personal level. I?m excited that such a task has been handed to me and I can only hope I?well, I can only hope I don?t fuck things up.
The main purpose for having SMS in our environment is to audit software, inventory hardware and push out critical security patches. Granted SMS is much beefier than that, but that?s our main goal. It didn?t hurt that the licenses were free either! The reason we are rolling out to the other company locales is SOX. Don?t like the latest in your IT department?s Policy Profile? Thank Enron, WorldCom and Global Crossing, dear reader. What a pain in the ass it can be to be a public company, but I must say, if anything, it will help us get more organized.
I ran across an interesting issue today with SMS. A handful of clients were not populating as installed clients, but were assigned our site code within a Network Discovery. The logs would continually read ?WNetAddConnection2 failed? errors on the affected machines. It turns out, when adding Site Boundaries, you should not only add the IP subnets, but the qualified domain name as well. This can be crucial if you?ve recently changed from a legacy domain to an advanced domain.
One last thing before I go this evening?.
The Fox baseball analysts are still complete fucktards.