Skip to main content


Showing posts from May, 2012

two upcoming events i wanted to mention

hi and good morning. i wanted to mention a couple of upcoming events that may interest you.   JUNE 1ST: the first is the atlanta techstravaganza event which has turned into an annual thing. not sure if you know this or not but atlanta systems management user group is a part of it and has been since the inception. the event has a great line-up of folks -- both mvp and other talent. it's a full day event with food, prizes, etc so plan accordingly. the schedule, registration, and everything else can be found at . hope you can make it!   MULTIPLE EVENTS: the second event is windows server 2012 community roadshow which is brought to you by fellow mvps. it's a four hour event at various locations both stateside and internationally. you can get all the information at the following location: sorry atlanta peepz -- it doesn't appear there's going to be an atlanta event. the closest you'll

"get computer/ip status" activity throws raw socket error

recently ran across this quirk trying to test a runbook in orchestrator... PROBLEM SUMMARY while in the runbook designer, whenever the "get computer/ip status" activity is called, it fails with the following error:     the error summary text in its entirety: Raw socket error. Error: 10013 An attempt was made to access a socket in a way forbidden by its access permissions.   according to this microsoft article (thanks richard catley), the error translates to this: WSAEACCES (10013) Translation: Permission denied. Description: An attempt was made to access a socket in a way that is forbidden by its access permissions. For example, this error occurs when a broadcast address is used for sendto but the broadcast permission is not set by using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind (Wsapiref_6vzm.asp) function is called ( in Microsoft Windows NT 4 .0 Service Pack 4 [SP4] or later), another program, service, or

managing client remediation in configmgr 2012

picked up this article from steve rachui. been extremely negligent on writing blogs and reading blogs this last year because of some other commitments. anyway, kent agerlund lays out a process for using settings management (aka dcm) to turn off client remediation for scenarios where a targeted selection of machines (e.g. servers, domain controllers, etc) may exist under stricter change control processes that do not allow the client to reinstall itself. anyway, check out the article here:

ntlm authentication is not dead nor are its problems

hanging out at tec this week, a recurring theme came up more than once. it's this thing called maxconcurrentapi. here's some relevant links:;EN-US;928576