71 lines
4.5 KiB
HTML
71 lines
4.5 KiB
HTML
|
<?xml version="1.0" encoding="utf-8"?>
|
||
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow"/>
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<title>Logon server home directories</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="logon_homed"></a>
|
||
|
|
<h2 id="logon_homed">Logon server home directories</h2>
|
||
|
|
<p><span class="bold">Configuring home directories on the Logon Server</span></p>
|
||
|
|
<p> A PC user can be configured to have a home directory and can be collectively
|
||
|
|
backed up and maintained on the server. The Logon Server that authenticates
|
||
|
|
the user determines the location of their home directory. By default, an iSeries Logon
|
||
|
|
Server considers the Home directory path stored in the user profile (on the iSeries server)
|
||
|
|
as the PC client user's home directory too. For example, if user JOE has
|
||
|
|
a home directory configured in his user profile as /home/joe, then this path
|
||
|
|
is treated as a UNC name (Windows 98) for the client and the client's view
|
||
|
|
of this folder would be \\logonServer\home\joe. The /home directory would
|
||
|
|
need to be shared with a share name of HOME in order for a Windows 98 client
|
||
|
|
to map a drive to it.</p>
|
||
|
|
<p><span class="bold">Mapping a drive to your home directory</span></p>
|
||
|
|
<p>Windows 2000 and Windows XP clients using the IPLC will attempt
|
||
|
|
to map a drive to the user's home directory automatically when they log on.</p>
|
||
|
|
<p><span class="bold">Home Directories on other servers</span></p>
|
||
|
|
<p>Sometimes it is desirable to store user home directories on a server other
|
||
|
|
than the Logon Server. This may be the case if a lot of data is normally
|
||
|
|
transferred to and from the home directories (perhaps they are also being
|
||
|
|
used to serve roaming profiles) and the Logon Server is not equipped to handle
|
||
|
|
this extra load and provide responsive Logon support to many clients at the
|
||
|
|
same time. Remote home directories can be configured in the user profile
|
||
|
|
for the iSeries server. The remote home directory is actually a share on
|
||
|
|
a different server and it is specified by the QNTC path to the share. For
|
||
|
|
example, if home directories are to be stored in share HOME on iSeries server
|
||
|
|
DRACO2, then the home directory field for user JOE could be given as /qntc/draco2/home.
|
||
|
|
Alternatively, individual home directories could be shared from DRACO2, in
|
||
|
|
which case the home directory above would be given as /qntc/draco2/joe.</p>
|
||
|
|
<p>Specifying the QNTC path name here does not imply that the client is going
|
||
|
|
through the QNTC file system on the Logon Server to reach the remote share
|
||
|
|
on the home directory server. The client makes a separate direct connection
|
||
|
|
to the remote home directory share. The reason why the QNTC path format was
|
||
|
|
chosen is to be consistent across the system since this is stored in the user's
|
||
|
|
profile. This way, other applications running locally on the iSeries server
|
||
|
|
would, in theory, be able to access this same home directory. </p>
|
||
|
|
<a name="wq87"></a>
|
||
|
|
<div class="notetitle" id="wq87">Note:</div>
|
||
|
|
<div class="notebody">Since this configuration also changes the home directory for the local user
|
||
|
|
that signs on to the iSeries system through PC5250, for example, the ramifications
|
||
|
|
of this need to be considered if there is a possibility that the user will
|
||
|
|
sign on directly to the iSeries server configured as a Logon Server.</div>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|