We've added a new check, "backup agent" to the "windows-hosted" servers.

This check tests to see if either the NetBackup OR Avamar agents is loaded.  If one is, then it return green, if neither are found or on any errors, a yellow alert is generated.

We'll be deploying this on other Windows machines shortly.

So, things are pretty wierd with 2/3 different DNS servers (NCSU,NCSU_LEGACY, and the Windows DCs) all offering "authoritative" results for the acsad.ncsu.edu DNS zone.

We had a couple of Windows hosts give the error "Could not get value" when checking uptime, and the extra mysterous "ERROR: Could not get data for 1 perhaps we don't collect data this far back?" while checking load.

Turns out the Windows performance counters had gotten sidewise, and need to be rebuilt.  With some help from the event log and http://eventid.net, we discovered

We've run into several machines that can't upgrade to the latest NSClient++ plugin (the software that implements NRPE, the Nagios Remote Plugin Executor "protocol") because the installed version doesn't appear in Add/Remove programs.

Bizzare!

To uninstall it manually, assuming it's located in "C:\Program Files\NC State University\NSClientPP" issue the folllowing commands from a cmd prompt:

"C:\Program Files\NC State University\NSClientPP\nsclient++.exe" /uninstall
rd /q "C:\Program Files\NC State University\NSClientPP"

I'm excited about the chance to use SAR for our account creation and other management, but I've got a nagging fear that all of ISO may not be on the same page about what strategies we're using these days.

The CAB has requested  more information about the impact of turing off dynamic DNS.  I'm making a blog entry, so we can all chime in to flush out details.

The proposal is that we turn off dynamic DNS in the acsad.ncsu.edu DNS zone, which currently allows a Windows comptuer to publish it's name (as typed in by the person installing Windows) into DNS. After turning it off, DNS names would have to be entered into the QIP system.

Several of us met individually with Richard over the last couple of days to talk about using SAR (aka Sun One identify manager) for account provisioning.

SAR is used as a replacement for an earlier home made applicaiton called ASAP, and is used to provision and deprovision access to things.  There are currently 36 systems in SAR, some of which don't actually do the provisioning, but handle the process flow by presenting forms for approval and sending e-mail to each party in the workflow to encourage them to fill out said forms.

So, in order to move forward on the DNS in .acsad.ncsu.edu, I think we need to do the following

The work isn't complete, but I've got a start of the Windows plugins for Nagios packaged in the WolfTech domain.

Debbie talked to me and asked me to create a container for Campus Messaging Services in WolfTech.  I've made some OUs, but I'm not convinced it's going to work properly with the Wolftech magic.

I think that Billy/Dan/Derek have to add the containters that get auto-populated with applications, allowed rights to link gpos, and so forth. 

I've made a skeleton of ou=CMS,ou=CT,ou=OIT and assigned all rights to the group "CMS-OU Admins" right now Debbie is the only member of that group, as she's co-ordinating the DESAD migration and can add others as she needs.