<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>AG&#039;s Latest! &#187; Relationship</title>
	<atom:link href="http://web2.tigs.com.au/blogs/agit/tag/relationship/feed/" rel="self" type="application/rss+xml" />
	<link>http://web2.tigs.com.au/blogs/agit</link>
	<description>Total randomness...</description>
	<lastBuildDate>Wed, 30 Mar 2011 11:29:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>The WinMac Relationship (part 2)</title>
		<link>http://web2.tigs.com.au/blogs/agit/2008/06/18/the-winmac-relationship-part-2/</link>
		<comments>http://web2.tigs.com.au/blogs/agit/2008/06/18/the-winmac-relationship-part-2/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 12:28:50 +0000</pubDate>
		<dc:creator>agreenlees</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[OS]]></category>
		<category><![CDATA[OS X (Mac)]]></category>
		<category><![CDATA[AD]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[OD]]></category>
		<category><![CDATA[Relationship]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://web2.tigs.com.au/blogs/agit/?p=82</guid>
		<description><![CDATA[Part 2…
With all Mac access completely offline and LDAP authentication for some odd (and at this point unknown) reason not able to hold a constant connection, I decided to use and configure the Directory Services Active Directory (AD) plugin. I could see the advantages and disadvantages of using the AD authentication method. However, my main  <a href='http://web2.tigs.com.au/blogs/agit/2008/06/18/the-winmac-relationship-part-2/'>[...]</a>]]></description>
			<content:encoded><![CDATA[<p>Part 2…</p>
<p>With all Mac access completely offline and LDAP authentication for some odd (and at this point unknown) reason not able to hold a constant connection, I decided to use and configure the Directory Services Active Directory (AD) plugin. I could see the advantages and disadvantages of using the AD authentication method. However, my main concern at this point was to relieve the pressure on me from the powers to be with a quick-fix solution.</p>
<p>The main advantages would be a single set of user credentials for all computers (Mac &amp; PC) in the school and easy (mapped) access to the users Windows hosted home folder. The disadvantage was that with the time constraints I was unable to find a way to map the users Windows home folder, Mac home folder and possible other AFP mappings at login. The workaround I used was to create a shortcut to the servers AFP path on all the Mac computers, which allowed users to list the directories that they had access too. During the coming holiday break I will be investigating further to find a solution.</p>
<p>So, I bound the XServer to AD without any hassle, opened Workgroup Manager, selected AD as the search path, authenticated and the users populated from AD. My colleagues and I then went to each Mac one by one and bound them to AD using a unique name. The only problem we ran into was that AD requires that the time on the client computer be the same (or close to the same) as the Domain Controller. With the occasional hassle, we synchronized the time settings on all Mac clients to our Domain Controller, which then enabled us to successfully bind.</p>
<p>With that all done I am now waiting for a full class login to occur to test the server reliability and authentication method. We will be purchasing a copy of Leopard server in the not too distant future and with the installation of this server upgrade, I am contemplating rolling back to the LDAP authentication as it allows for more flexibility and customisation considering the somewhat unique options our Mac network requires.</p>
<p>This is definately not the last I have seen of this issue…</p>
]]></content:encoded>
			<wfw:commentRss>http://web2.tigs.com.au/blogs/agit/2008/06/18/the-winmac-relationship-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

