O R G A N I C / F E R T I L I Z E R: 05.09

May 28, 2009

workstation fails to join the domain during configmgr task sequence

during an operating system deployment, if you find that your workstations are failing to join the domain, check your netsetup.log.  if you find a line like this…

01/01/2009 12:00:00:000 NetpGetComputerObjectDn: Specified path 'CN=Computers,DC=myDomain,DC=com' is not an OU

… it’s generating because the path specified is, in actuality, not an ou (organizationalUnit).  instead, the default computers location is a container.  feels like i’m splitting hairs when it comes to this, but if you point the “Apply Network Settings” to either a domain ou or blank, it works.


May 22, 2009

introducing the long awaited operations manager 2007 r2!

i’m not sure if i’m bringing you any “news” since i’m usually the slowest blogger when it comes to release dates and such.  however, this is pretty monumental so it’s worth repeating.  for those of you who wish to espouse the market fluff to your boss, you can read that here.  it’s not worth repeating here as i could not compete with the geniuses that write that material for a living.

i started off with every intent of doing a full article on all the goodness of opsmgr 2007 r2.  however, when i started searching for material with actual figures, i noticed that apparently this is such big news that even “fire pants” mckenna wrote a blog post about it!  believe it or not, it’s pretty good.  quite entertaining.  i won’t do an injustice by trying to complete with it.

a lot has changed since 2007 when opsmgr first launched.  (good grief, i just realized how much time had passed.)  where i work, we were very slow to begin our rollout.  i mean we started when r2 beta came out.  still, it was fun to ask some of the other mvps how things were going for them.  i think one of my favorite conversations went something like …

“you haven’t upgraded yet?”

“nope, still waiting for funding.”

“consider yourself lucky.  don’t do it!”

(did i say upgrade?  -snicker-  there still is no upgrade from mom 2005.)  it’s gone through a service pack since then and now is on r2.  if you haven’t started, there’s a steep learning curve.  once you get beyond the concepts, though, the potential starts to open up.

i should warn you that when you open the console for the first time after upgrading to r2, you’re going to be presented with what appears to be the “black” theme in outlook.  :)  i guess black is the new black.  details are here at this link if you want to know more.

preloadpkgonsite generates failed to get specified package in database errors

ran into this today while trying to bring back a new site server with all the current packages.

C:\SMSPKG>preloadpkgonsite.exe pkg00001
****** Preload Package On Site ******
Failed to get the specified package pkg00001 in the database. Please check if you have instance rights to that package.


smells conspicuously like a permission problem even though i’m getting my rights through a global group assigned to this server.  i tried it again, this time with local system permissions.  much better.

D:\SMSPKG>PreloadPkgOnSite.exe pkg00001
****** Preload Package On Site ******
Forward package status for pkg pkg00001 to site PKG
****** Successfully set the Compressed Package Path on this site ******
****** Successfully forwarded the information up the hierarchy ******


if you’re looking for how to execute preloadpkgonsite.exe, you can refer to this earlier post.

May 14, 2009

dns2003discovery.vbs script or executable failed to run

if you’re seeing an error similar to this --

The process started at 2:58:15 AM failed to create System.Discovery.Data. Errors found in output:
C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 2\4484\DNS2003Discovery.vbs(478, 9) Microsoft VBScript runtime error: Type mismatch
Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "DNS2003Discovery.vbs" {C8655A28-E27E-C6ED-B158-8569219A71A6} {641B9BD1-C4B4-E747-235B-362A0629EC54} <YOUR-DC-FQDN> false
it may be environmental as is the case for me.  at some point in the past, we had dns running on all of our domain controllers.  once we went to 2003, we started removing it from the nodes where it wasn’t needed.  we turned it off on the ones where it wasn’t required.  unfortunately, it leaves the remnant namespace in wmi.

on a system where this occurs, the following query will return an empty response:
select * from microsoftdns_server
with a response like this:

consequentially, this is the query that’s called in the dns discovery script.  and of course, on a working system, it returns the FQDN of the dns server in question.  fortunately for me, i can override the discovery fairly safely without concern that i’ll miss anything else.

examining the failure line (478, 9) puts us inside the DoDiscovery function.  since objServer is empty, it’s going to fail.  i think an “if isnull” would correct the problem here.

Function DoDiscovery(ByVal TargetComputer, ByVal oDiscoveryData)
' If IsNull  <--- maybe here would help... 
    For Each objServer In colServers
        Set objInstance = oDiscoveryData.CreateClassInstance("{83556DC0-78A0-1B5E-8947-509A5115EAB4}")
        Call objInstance.AddProperty("{E4F02B95-59EC-CA14-1A36-107F6ADB84D0}", objServer.EventLogLevel)
        Call objInstance.AddProperty("{B95C9A9B-1C3D-A19A-F6D1-7CAF6A98CE67}", TargetComputer)

May 6, 2009

listing all the views or tables of a database

navigating the sql management studio gui can be a bit of a pain when you don’t know the name of the table or view specifically that you’re looking for.  i was poking around looking for anything with the name “state” in it.

i finally decided to look into it, after procrastinating about it for months and months and months.  here it is:

for tables matching the word “state”:

select * from sys.tables where name like '%state%'


for views matching the word “state”:

select * from sys.views where name like '%state%'