NCSU OIT Integration Services

How to find a printer.

Do you need to be an admin?

When do you authenticate to print on a standalone machine?

We need to stop creating folders and doing other desktop setup that was in testing from the Microsys days.

After much frustration fighting with the Microsoft documentation, I have managed to get a script that will collect roughly all the date we need and pruning off the unnecessary chaff. Kevin, John and I determined we need to have Name, Group, Resource Type, Dependencies and Possible Owners. We came up with two scripts to get all this information. One script lists the possible owners of all the resources. One script lists all the resources for which cluster node is the possible owner.

These are just my raw notes from installing print00.

The lastest locally built samba is in /afs/bp.ncsu.edu/project/realmlinux/yum/MICROSYS/5Server/

You can point yum to this with a config file in /etc/yum.repos.d containing

[oit-iso-shs]
name=OIT ex-Microsystems Locker
baseurl=http://install.linux.ncsu.edu/pub/yum/MICROSYS/5Server/$basearch
enabled=1
gpgcheck=0

Install everything with

sudo yum install samba samba-client samba-doc

Debbie and I spent some time this afternoon trying to quantify what was broken between ACSAD and UNITY.AD.

What we tested was creating a domain local group, and then adding members to that group from the other domain.  In all cases, we could browse and add from either domain without difficulties, but when we tried to view the members of the group, we got a "the other domain may be down" error after a long delay.

We've extended the Unity.ad schema to support the older DRAC4 series out of band management cards, and will shortly do the same for ILO cards. Info about how they're used can be found in an earlier blog post.

Well, I'm finally getting some of my promises kept.  The live account management scripts, hot off scripts02 can be found at

https://svn.unity.ncsu.edu/svn/shs-general/acctmgmt/trunk

Both Wade and Joe have mentioned that subversion isn't working for them -- I'm still checking on that. :-) 

Folks,

 I've removed the trust between unity.ad.ncsu.edu and the test domain test3.unity.ad.ncsu.edu .

We still have a parent-child trust with test2.unity.ad.ncsu.edu that's proving troublesome to remove.  I think the issue is that we don't have all the proper SRV records in QIP and so dcpromo can't find something it thinks it needs.

We need a script to attach to all our servers and change the local administrators

We need to identify what "classes of approval" we're prepared to offer campus for MS updates via WSUS.  I figure we'll need at least

• All updates approved automatically
• All except for "Office" updates (for Citrix and PeopleSoft)
• No updates auto-approved

Once we identify what classes of approval we want to implement, we can go ahead and start providing them. :-D