Difference between revisions of "Active Directory/Documentation"

From WolfTech
Jump to navigation Jump to search
m
m
 
(2 intermediate revisions by the same user not shown)
Line 60: Line 60:
  
 
==== Options for integrating Mac OS X clients with AD ====
 
==== Options for integrating Mac OS X clients with AD ====
 +
 +
*Billy's instructions on joining domain... [[/Joining Macs to WolfTech Domain|Joining Macs to WolfTech Domain]]
  
 
With the included Active Directory plug-in, OS X can be configured to authenticate to an AD domain, and use network home directories. More comprehensive management (MCX) requires one of the 3 options below:
 
With the included Active Directory plug-in, OS X can be configured to authenticate to an AD domain, and use network home directories. More comprehensive management (MCX) requires one of the 3 options below:
Line 170: Line 172:
 
*[[/Planning | Planning]]
 
*[[/Planning | Planning]]
  
=Windows 2003 Server R2=
+
=Windows Server 2003 R2=
 
*[[/Extend_Schema_R2| How to extend the schema?]]
 
*[[/Extend_Schema_R2| How to extend the schema?]]
  
Line 181: Line 183:
 
=Windows Deployment Services (WDS)=
 
=Windows Deployment Services (WDS)=
 
*[[/WDS | WDS]]
 
*[[/WDS | WDS]]
 +
 +
=Windows 7=

Latest revision as of 15:58, 23 April 2010

Active Directory Users and Computers

Automatic Logon

Administrative Users

Automatic Updates (WSUS)

Details on the WolfTech WSUS Service Group can be found here.

Disaster Recovery

DNS

File Servers

Folder Redirection

Distributed File System (DFS)

Group Policy

Group Policy Preferences

Internet Explorer 7

Laptops

Lights Out Management

  • HP ILO
  • Dell DRAC

Macintosh

Options for integrating Mac OS X clients with AD

With the included Active Directory plug-in, OS X can be configured to authenticate to an AD domain, and use network home directories. More comprehensive management (MCX) requires one of the 3 options below:

Additional resources:

Issues to address:

  1. Configuring your mac to use your UnityID/paswd (specifically, by authing against the DCs, but alternatively against the campus KDC). Plus how the laptop reacts when not on the network - should be caching.
  2. Adding your Mac to the domain.
  3. Restricting access to AD defined users.
  4. Printing from your domain'd mac to a Windows print server; and to a WolfCopy printer.
  5. Accessing Windows file shares from your domain mac
  6. Why DFS doesn't work, or if the new OS fixes this. And steps to get around this (3rd party apps - AdmitMac) or things to look out for).
  7. Options to apply policies to the mac client via GP? (likely to require 3rd party apps)
  8. Scripts to inventory hardware/applications on your mac clients (longterm we'd want a WolfTech Collector Agent for Macs)
  9. AFS client for Macs
  10. Software distribution to Mac via GP?

Migrating

Active Directory Migration Tool (ADMT)

MS-SQL

New OU Admins

Printing

Public Labs / Kiosks

Remote Assistance

Remote Installation Services (RIS)

Scripting

Services for UNIX

Software Packaging

Symantec Antivirus (SAV)

Teaching Labs

User Account Control (UAC)

Virtual Servers

Vista

Windows Server 2003 R2

Windows Server 2008

Windows Defender

Windows Deployment Services (WDS)

Windows 7