<?xml version="1.0" encoding="iso-8859-1"?>

<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:admin="http://webns.net/mvcb/"
>

<channel rdf:about="http://microsys.unity.ncsu.edu/documentation/">
<title>Microsys Documentation</title>
<link>http://microsys.unity.ncsu.edu/documentation/</link>
<description>Recently updated documentation from NCSU ITD's Micro Systems group</description>
<items>
 <rdf:Seq>
  <rdf:li rdf:resource="http://microsys.unity.ncsu.edu/documentation/Windows-Update-Services/Use-of-ITDs-Windows-Update-Service-WSUS.php" />
  <rdf:li rdf:resource="http://microsys.unity.ncsu.edu/documentation/Windows-Update-Services/Whats-In-a-Name-Defining-that-Microsoft-Software-Update-Term.php" />
  <rdf:li rdf:resource="http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Account_Options.html" />
  <rdf:li rdf:resource="http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Security/Role-groups-for-access-control.html" />
  <rdf:li rdf:resource="http://microsys.unity.ncsu.edu/documentation/ITD-Active-Directory-Environment/Kerberos-Authentication.html" />
  <rdf:li rdf:resource="http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Security/Kerberos.html" />
 </rdf:Seq>
</items>
</channel>

<item rdf:about="http://microsys.unity.ncsu.edu/documentation/Windows-Update-Services/Use-of-ITDs-Windows-Update-Service-WSUS.php">
<title>Use of ITD's Windows Update Service (WSUS)</title>
<link>http://microsys.unity.ncsu.edu/documentation/Windows-Update-Services/Use-of-ITDs-Windows-Update-Service-WSUS.php</link>
<description>Installation for Unity Active Directory Clients</description>
<dc:date>2008-01-25T19:58Z</dc:date>
</item>

<item rdf:about="http://microsys.unity.ncsu.edu/documentation/Windows-Update-Services/Whats-In-a-Name-Defining-that-Microsoft-Software-Update-Term.php">
<title>What's In a Name - Defining that Microsoft Software Update Term</title>
<link>http://microsys.unity.ncsu.edu/documentation/Windows-Update-Services/Whats-In-a-Name-Defining-that-Microsoft-Software-Update-Term.php</link>
<description>Microsoft WSUS can be configured to deliver drivers, critical updates, security updates, hotfixes, tool updates and the like.  The infomation at the link "Description of the standard terminology that is used to describe Microsoft software updates" helps clarify what the impact of the settings within WSUS Update services.  These are set, in WSUS 3.0, using the WSUS.msc. Select:  Options, Products and Classifications, Classifications {tab}. </description>
<dc:date>2007-10-26T16:52Z</dc:date>
</item>

<item rdf:about="http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Account_Options.html">
<title>UNITY.AD account Options</title>
<link>http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Account_Options.html</link>
<description>ITD provides "Unity" user accounts with allow access to a wide variety of campus IT resources to all faculty, staff, and students at NC State University. </description>
<dc:date>2007-10-17T18:10Z</dc:date>
</item>

<item rdf:about="http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Security/Role-groups-for-access-control.html">
<title>Using Groups for Access Control</title>
<link>http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Security/Role-groups-for-access-control.html</link>
<description>What auditors and system administrators all need is to be able to easily assign rights to the accounts that need them, to easily know what rights have been assigned, and to quickly be able to satisfy the "ad hoc" requirements for access that inevitably crop up.</description>
<dc:date>2007-09-25T19:48Z</dc:date>
</item>

<item rdf:about="http://microsys.unity.ncsu.edu/documentation/ITD-Active-Directory-Environment/Kerberos-Authentication.html">
<title>Kerberos</title>
<link>http://microsys.unity.ncsu.edu/documentation/ITD-Active-Directory-Environment/Kerberos-Authentication.html</link>
<description>This page has moved. </description>
<dc:date>2007-09-25T18:58Z</dc:date>
</item>

<item rdf:about="http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Security/Kerberos.html">
<title>Kerberos Authentication</title>
<link>http://microsys.unity.ncsu.edu/documentation/Unity-AD-Guide/Accounts-and-Identity-Management/Security/Kerberos.html</link>
<description>In the unity.ad.ncsu.edu Active Directory, we use Kerberos authentication based on NCSU's existing Kerberos servers. We also set the Windows NTLMv2 password, to allow people to easily add their workstations to the domain. The NTLMv2 password associate with your AD account is updated whenever you reset your password.</description>
<dc:date>2007-09-25T18:50Z</dc:date>
</item>

</rdf:RDF>