So, there is in fact a valid PPD file for the BizHub Di3510

Download the Vista (32 bit) postscript drivers from

http://onyxftp.mykonicaminolta.com/download/SearchResults.aspx?productname=Di3510

Unpack the .exe on a windows box, and poof! Instant PPD (I've attached it here to save trouble re-re-re-unpacking it)

So I was working in ldap today, and saw the following structure for OIT described under ou=units

I noticed a few units I didn't expect, namely "First Year College", "Joint Enterprise Services" and "Major University Projects"

Anybody hear about a re-org?  Is the ldap data in error?

Working with Ralph on the DNS issues, the question of what DHCP servers were running in ACSAD was raised. Well, there are 9 "authorized" DHCP servers

It's taken a while, but we finally are monitoring the Sybase tables that manage the Unity account creation, renames, and password resets.  In the past, if our account management code in either Novell or AD land failed for some reason, the first indication we would get would be furious screaming from the dbas,

https://sysnews.ncsu.edu/tools-bin/server-status?info=ncsu-accounts-ad

I've added significant rights to the OIT role for this site, which is fed from the "OIT People" application.  Basically, I'm granting everyone in OIT the same rights that we used to have only for ISO staff, meaning personal blogs, forum creation, book editing, and overall content creation rights.

Here's a long description of how the rights are established for the software groups in OIT's portion of the WolfTech active directory.  It's long and in narrative style, in hopes it will illustrate the thought processes that yielded this configuration.

Two facts one should know

• Computers objects can be members of AD groups
• Group objects can be members of AD groups

In WolfTech, to assign an application to be installed on a machine, you just add that machine to a specially named group. 

A 2004 article from SearchWindowsServer.com but still applies. by James Michael Stewart, Contributor

One or more group policies (GPOs) can be defined for each domain, site, and organizational unit (OUs) in a forest (that is, an entire Active Directory domain network). All of the GPOs can be managed from a Windows 2000 or Server 2003 domain controller system through the Active Directory Users and Computers utility as well as several others.

Kevin and I met with TSS to finalize our plans to create a better OU structure for OIT.

Workstations and other computers will be gathered up under an OU=Computers directly under OU=OIT

Kevin

Clients that TSS supports will get sub-containers under "Clients"

The "Test" OU will be used for application/gpo testing

Some settings are not explained in the Microsoft spreadsheets. However, there is an explanation of many of them, includng the security settings, here: http://technet.microsoft.com/en-us/library/cc785710(WS.10).aspx

See particularly the entries under "local policy".

Wonder what all those GPO settings mean? Microsoft has provided some guidance. They have produced spreadsheets that identify all of the settings for the .adms included with Win2k3, plus addendums for Win2k8 and Win2k8R2. They include short text explaining what the settings do.

For convenience, I've attached them. They came from:

Group Policy Settings References for Windows and Windows Server
(also referred to as "Group Policy XLS")
http://go.microsoft.com/fwlink/?LinkId=54020