NCSU OIT Integration Services

Both UPS's in the old Microsys racks in Poe Hall have failed batteries.  Construction around Poe is causing frequent power fluctiations. 

 The unix machines co-hosted there, with only a single power supply, were bouncing up and down on a short cycle.  Tim and I moved them to a new UPS, reclaimed from the surplus pile in the third floor hallway.

The Dell hardware is surviving better, because both power supplies have to fail at the exact same moment for the machine to blip.

Folks,

The scripts that feed the microsys home page were having trouble getting to SQL data they needed.  Rather than keep the page alive and possibly confuse people, I've done a simple redirect to http://integrate.oit.ncsu.edu .

Long live our new organization!

All the other content from microsys (eg http://microsys.unity.ncsu.edu/documentation) is still in place and accessible.

So, we destroyed and re-created the trust between ACSAD and Unity.ad  and rebuilt it.  I guess this just shows that you can't ignore important relationships, you've got to check in once and a while or your trust will fail and you'll have to rebuild it.

There seems to be a trust problem with ACSAD anf UNITY.AD

When I try to troubleshoot, I get an "incorrect function" call on DC03 in Unity.

We may need to reset our trust shared secrets. In any event, it should be good practice for anyone who wants some real-world AD troubleshooting. I'm calling it quits until tomorrow.

My desire is to get some global identiry groups established in ACSAD to control access to the applications shared via DFS in unity.ad .

I wrote a script, and added all of the folks in the shs-general paging group to all of the ex-ITD Novell servers, including the virtual cluster servers.

Both the o=Unity accounts, and the ou=NCS,o=NCSU have been added, so it shouldn't matter which part of the NDS tree one logs in with.

I've started but have not yet completed, a groupsync module to syncronize with AD, under ou=Pager,ou=Groups

Ralph had assigned us homework to identify what needed to be monitored and wasn't, and to come up with a list of deficiences that needed to be corrected.

So a while ago, I setup a group named "OIT_SERVER_CONSOLE_ACCESS".

The plan was, if you were on-call and could get called for an ex-ITD Novell server, you'd be in this group, and this group would be listed under "Console Operators" on all of the ex-ITD Novell servers.

We have been receiving reports of current Lenovo ThinkPads, running MS Vista with SP1, were not compatible with Symantec Endpoint Protection. In 2008, the Lenovo systems were being shipped with a trialware version of Norton Internet Security staged to install, if the user indicates they would like the application. Additionally, the systems are installed with Lenovo Group's "Client Security Solution".

TSS hosted a LanTech Forum 6/2/2008 9-12

1) Susan Klein gave an overview of the new OIT organizational structure, including the new CIO.

2) Upcoming projects & rollouts - John Garcia

- Office 2007 (and XP vs Vista)

Hardware requirements are greater than previous versions. 1 GB RAM is minimal for it to work well. 512 MB testing may be "ok". Recommendation is to purchase new machines with at least 2 GB RAM.

I had been hand poking the forms page of this site to rediect the login form to https:// rather than http:// so passwords would not get sent in the clear.

I've found a module, "securelogin" which does this automagically, and makes things much easier to keep updated.

I have been seeing some odd certificate messages, about the name "integrate.oit.ncsu.edu" not matching itself.  If you get these at login, I apologize and will someday get it resolved.