[48] in Kakapo Windows Team
WIN policies
daemon@ATHENA.MIT.EDU (Thomas L. Thornton)
Mon Aug 4 11:03:28 2003
Date: Mon, 4 Aug 2003 11:02:23 -0400 (EDT)
Message-Id: <200308041502.h74F2NZv017322@the-rim.mit.edu>
From: "Thomas L. Thornton" <tomt@MIT.EDU>
To: kakapo@mit.edu
CC: pismere-team@mit.edu, contact-container-admins@mit.edu
A couple corrections on my last week's message regarding WIN policies.
First correction - our approach to licensing is an important addtional
policy missing from my previous post. Current web docs may not
currently explicitly name this as a policy, but in essence we should
establish that software compliance is the Department's responsibility.
I am sure it will take constant efforts to clarify this as a Container
Administrator's obligation.
Hints to this effect are on the WIN web site in places such as theRIS
FAQ:
It is important to remember that MIT does not have a site license
for all Windows Operating Systems and users. Container
Administrators must each keep track of our licenses, and make sure
we have a CALs per machine. For OS licensing, please see
_MIT/Windows 2000 Professional License_. For CALS (ordering info
from May, 2003), visit the _GovConnection Catalog_, either
departmental or personal, and find the Microsoft Select product
named "Acad. Select Windows Server 2003 per Device Client," Catalog
Item #440472.
Second correction - Joe reminds me I am inaccurate in writing "There
are no Domain-assigned WIN user policies. Actually, there are a very
few we apply through two group policies, GP-Moira-Users and
GP.Pismere. Container Admins cannot really affect these settings, but
any user from the Moira/Users container who logs into any machine in
the domain will get them, and local machine users or other domain
users not in the Moira/Users container will not. These policies are
enumerated in the User Configuration section of the Group Policiy
Management Console reports:
http://mit.edu/pismere/support/for-cont-admins/gpsnap.
-Tom
