1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�34.�SWAT The Samba Web Administration Tool</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="NT4Migration.html" title="Chapter�33.�Migration from NT4 PDC to Samba-3 PDC"><link rel="next" href="troubleshooting.html" title="Part�V.�Troubleshooting"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter�34.�SWAT The Samba Web Administration Tool</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NT4Migration.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="troubleshooting.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="SWAT"></a>Chapter�34.�SWAT The Samba Web Administration Tool</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="SWAT.html#id2613258">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="SWAT.html#id2613340">Guidelines and Technical Tips</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2613352">Validate SWAT Installation</a></span></dt><dt><span class="sect2"><a href="SWAT.html#xinetd">Enabling SWAT for Use</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2613877">Securing SWAT through SSL</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2613986">Enabling SWAT Internationalization Support</a></span></dt></dl></dd><dt><span class="sect1"><a href="SWAT.html#id2614117">Overview and Quick Tour</a></span></dt><dd><dl><dt><span class="sect2"><a href="SWAT.html#id2614130">The SWAT Home Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614198">Global Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614301">Share Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614356">Printers Settings</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614412">The SWAT Wizard</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614476">The Status Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614520">The View Page</a></span></dt><dt><span class="sect2"><a href="SWAT.html#id2614539">The Password Change Page</a></span></dt></dl></dd></dl></div><p> 2There are many and varied opinions regarding the usefulness of SWAT. 3No matter how hard one tries to produce the perfect configuration tool, it remains 4an object of personal taste. SWAT is a tool that will allow Web-based configuration 5of Samba. It has a wizard that may help to get Samba configured 6quickly, it has context-sensitive help on each <tt class="filename">smb.conf</tt> parameter, it provides for monitoring of current state 7of connection information, and it allows network-wide MS Windows network password 8management. 9</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2613258"></a>Features and Benefits</h2></div></div></div><p> 10SWAT is a facility that is part of the Samba suite. The main executable is called 11<span><b class="command">swat</b></span> and is invoked by the inter-networking super daemon. 12See <a href="SWAT.html#xinetd" title="Enabling SWAT for Use">appropriate section</a> for details. 13</p><p> 14SWAT uses integral samba components to locate parameters supported by the particular 15version of Samba. Unlike tools and utilities that are external to Samba, SWAT is always 16up to date as known Samba parameters change. SWAT provides context-sensitive help for each 17configuration parameter, directly from <span><b class="command">man</b></span> page entries. 18</p><p> 19There are network administrators who believe that it is a good idea to write systems 20documentation inside configuration files, and for them SWAT will always be a nasty tool. SWAT 21does not store the configuration file in any intermediate form, rather, it stores only the 22parameter settings, so when SWAT writes the <tt class="filename">smb.conf</tt> file to disk, it will write only 23those parameters that are at other than the default settings. The result is that all comments, 24as well as parameters that are no longer supported, will be lost from the <tt class="filename">smb.conf</tt> file. 25Additionally, the parameters will be written back in internal ordering. 26</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 27Before using SWAT, please be warned SWAT will completely replace your <tt class="filename">smb.conf</tt> with 28a fully-optimized file that has been stripped of all comments you might have placed there 29and only non-default settings will be written to the file. 30</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2613340"></a>Guidelines and Technical Tips</h2></div></div></div><p> 31This section aims to unlock the dark secrets behind how SWAT may be made to work, 32may be made more secure, and how to solve Internationalization support problems. 33</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613352"></a>Validate SWAT Installation</h3></div></div></div><p> 34The very first step that should be taken before attempting to configure a host 35system for SWAT operation is to check that it is installed. This may seem a trivial 36point to some, however several Linux distributions do not install SWAT by default, 37even though they do ship an install-able binary support package containing SWAT 38on the distribution media. 39</p><p> 40When you have confirmed that SWAT is installed it is necessary to validate 41that the installation includes the binary <span><b class="command">swat</b></span> file as well 42as all the supporting text and Web files. A number of operating system distributions 43in the past have failed to include the necessary support files, even though the 44<span><b class="command">swat</b></span> binary executable file was installed. 45</p><p> 46Finally, when you are sure that SWAT has been fully installed, please check the SWAT 47has been enabled in the control file for the inter-networking super-daemon (inetd or xinetd) 48that is used on your operating system platform. 49</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613395"></a>Locating the <span><b class="command">swat</b></span> File</h4></div></div></div><p> 50To validate that SWAT is installed, first locate the <span><b class="command">swat</b></span> binary 51file on the system. It may be found under the following directories: 52</p><table class="simplelist" border="0" summary="Simple list"><tr><td><tt class="filename">/usr/local/samba/bin</tt> the default Samba location.</td></tr><tr><td><tt class="filename">/usr/sbin</tt> the default location on most Linux systems.</td></tr><tr><td><tt class="filename">/opt/samba/bin</tt></td></tr></table><p> 53</p><p> 54The actual location is much dependant on the choice of the operating system vendor, or as determined 55by the administrator who compiled and installed Samba. 56</p><p> 57There are a number methods that may be used to locate the <span><b class="command">swat</b></span> binary file. 58The following methods may be helpful: 59</p><p> 60If <span><b class="command">swat</b></span> is in your current operating system search path it will be easy to 61find it. You can ask what are the command-line options for <span><b class="command">swat</b></span> as shown here: 62</p><pre class="screen"> 63frodo:~ # swat -? 64Usage: swat [OPTION...] 65 -a, --disable-authentication Disable authentication (demo mode) 66 67Help options: 68 -?, --help Show this help message 69 --usage Display brief usage message 70 71Common samba options: 72 -d, --debuglevel=DEBUGLEVEL Set debug level 73 -s, --configfile=CONFIGFILE Use alternative configuration file 74 -l, --log-basename=LOGFILEBASE Basename for log/debug files 75 -V, --version Print version 76</pre><p> 77</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2613504"></a>Locating the SWAT Support Files</h4></div></div></div><p> 78Now that you have found that <span><b class="command">swat</b></span> is in the search path, it is easy 79to identify where the file is located. Here is another simple way this may be done: 80</p><pre class="screen"> 81frodo:~ # whereis swat 82swat: /usr/sbin/swat /usr/share/man/man8/swat.8.gz 83</pre><p> 84</p><p> 85If the above measures fail to locate the <span><b class="command">swat</b></span> binary, another approach 86is needed. The following may be used: 87</p><pre class="screen"> 88frodo:/ # find / -name swat -print 89/etc/xinetd.d/swat 90/usr/sbin/swat 91/usr/share/samba/swat 92frodo:/ # 93</pre><p> 94</p><p> 95This list shows that there is a control file for <span><b class="command">xinetd</b></span>, the internetwork 96super-daemon that is installed on this server. The location of the SWAT binary file is 97<tt class="filename">/usr/sbin/swat</tt>, and the support files for it are located under the 98directory <tt class="filename">/usr/share/samba/swat</tt>. 99</p><p> 100We must now check where <span><b class="command">swat</b></span> expects to find its support files. This can 101be done as follows: 102</p><pre class="screen"> 103frodo:/ # strings /usr/sbin/swat | grep "/swat" 104/swat/ 105... 106/usr/share/samba/swat 107frodo:/ # 108</pre><p> 109</p><p> 110The <tt class="filename">/usr/share/samba/swat/</tt> entry shown in this listing is the location of the 111support files. You should verify that the support files exist under this directory. A sample 112list is as shown: 113</p><pre class="screen"> 114jht@frodo:/> find /usr/share/samba/swat -print 115/usr/share/samba/swat 116/usr/share/samba/swat/help 117/usr/share/samba/swat/lang 118/usr/share/samba/swat/lang/ja 119/usr/share/samba/swat/lang/ja/help 120/usr/share/samba/swat/lang/ja/help/welcome.html 121/usr/share/samba/swat/lang/ja/images 122/usr/share/samba/swat/lang/ja/images/home.gif 123... 124/usr/share/samba/swat/lang/ja/include 125/usr/share/samba/swat/lang/ja/include/header.nocss.html 126... 127/usr/share/samba/swat/lang/tr 128/usr/share/samba/swat/lang/tr/help 129/usr/share/samba/swat/lang/tr/help/welcome.html 130/usr/share/samba/swat/lang/tr/images 131/usr/share/samba/swat/lang/tr/images/home.gif 132... 133/usr/share/samba/swat/lang/tr/include 134/usr/share/samba/swat/lang/tr/include/header.html 135/usr/share/samba/swat/using_samba 136... 137/usr/share/samba/swat/images 138/usr/share/samba/swat/images/home.gif 139... 140/usr/share/samba/swat/include 141/usr/share/samba/swat/include/footer.html 142/usr/share/samba/swat/include/header.html 143jht@frodo:/> 144</pre><p> 145</p><p> 146If the files needed are not available it will be necessary to obtain and install them 147before SWAT can be used. 148</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="xinetd"></a>Enabling SWAT for Use</h3></div></div></div><p> 149SWAT should be installed to run via the network super-daemon. Depending on which system 150your UNIX/Linux system has, you will have either an <span><b class="command">inetd</b></span>- or 151<span><b class="command">xinetd</b></span>-based system. 152</p><p> 153The nature and location of the network super-daemon varies with the operating system 154implementation. The control file (or files) can be located in the file 155<tt class="filename">/etc/inetd.conf</tt> or in the directory <tt class="filename">/etc/[x]inet[d].d</tt> 156or similar. 157</p><p> 158The control entry for the older style file might be: 159<a class="indexterm" name="id2613696"></a> 160</p><pre class="programlisting"> 161 # swat is the Samba Web Administration Tool 162 swat stream tcp nowait.400 root /usr/sbin/swat swat 163</pre><p> 164A control file for the newer style xinetd could be: 165</p><p> 166 167</p><pre class="programlisting"> 168# default: off 169# description: SWAT is the Samba Web Admin Tool. Use swat \ 170# to configure your Samba server. To use SWAT, \ 171# connect to port 901 with your favorite web browser. 172service swat 173{ 174 port = 901 175 socket_type = stream 176 wait = no 177 only_from = localhost 178 user = root 179 server = /usr/sbin/swat 180 log_on_failure += USERID 181 disable = no 182} 183</pre><p> 184 185In the above, the default setting for <i class="parameter"><tt>disable</tt></i> is <tt class="constant">yes</tt>. 186This means that SWAT is disabled. To enable use of SWAT, set this parameter to <tt class="constant">no</tt> 187as shown. 188</p><p> 189Both of the above examples assume that the <span><b class="command">swat</b></span> binary has been 190located in the <tt class="filename">/usr/sbin</tt> directory. In addition to the above, 191SWAT will use a directory access point from which it will load its Help files 192as well as other control information. The default location for this on most Linux 193systems is in the directory <tt class="filename">/usr/share/samba/swat</tt>. The default 194location using Samba defaults will be <tt class="filename">/usr/local/samba/swat</tt>. 195</p><p> 196Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user, 197the only permission allowed is to view certain aspects of configuration as well as 198access to the password change facility. The buttons that will be exposed to the non-root 199user are: <span class="guibutton">HOME</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, 200<span class="guibutton">PASSWORD</span>. The only page that allows 201change capability in this case is <span class="guibutton">PASSWORD</span>. 202</p><p> 203As long as you log onto SWAT as the user <span class="emphasis"><em>root</em></span>, you should obtain 204full change and commit ability. The buttons that will be exposed include: 205<span class="guibutton">HOME</span>, <span class="guibutton">GLOBALS</span>, <span class="guibutton">SHARES</span>, <span class="guibutton">PRINTERS</span>, 206<span class="guibutton">WIZARD</span>, <span class="guibutton">STATUS</span>, <span class="guibutton">VIEW</span>, <span class="guibutton">PASSWORD</span>. 207</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613877"></a>Securing SWAT through SSL</h3></div></div></div><p> 208<a class="indexterm" name="id2613885"></a> 209Many people have asked about how to setup SWAT with SSL to allow for secure remote 210administration of Samba. Here is a method that works, courtesy of Markus Krieger. 211</p><p> 212Modifications to the SWAT setup are as follows: 213</p><div class="procedure"><ol type="1"><li><p> 214 Install OpenSSL. 215 </p></li><li><p> 216 Generate certificate and private key. 217 218</p><pre class="screen"> 219<tt class="prompt">root# </tt><b class="userinput"><tt>/usr/bin/openssl req -new -x509 -days 365 -nodes -config \ 220 /usr/share/doc/packages/stunnel/stunnel.cnf \ 221 -out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem</tt></b> 222</pre></li><li><p> 223 Remove swat-entry from [x]inetd. 224 </p></li><li><p> 225 Start <span><b class="command">stunnel</b></span>. 226 227</p><pre class="screen"> 228<tt class="prompt">root# </tt><b class="userinput"><tt>stunnel -p /etc/stunnel/stunnel.pem -d 901 \ 229 -l /usr/local/samba/bin/swat swat </tt></b> 230</pre></li></ol></div><p> 231Afterward, simply connect to swat by using the URL <a href="https://myhost:901" target="_top">https://myhost:901</a>, accept the certificate 232and the SSL connection is up. 233</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2613986"></a>Enabling SWAT Internationalization Support</h3></div></div></div><p> 234SWAT can be configured to display its messages to match the settings of 235the language configurations of your Web browser. It will be passed to SWAT 236in the Accept-Language header of the HTTP request. 237</p><p> 238To enable this feature: 239</p><div class="itemizedlist"><ul type="disc"><li><p> 240 Install the proper <span><b class="command">msg</b></span> files from the Samba 241 <tt class="filename">source/po</tt> directory into $LIBDIR. 242 </p></li><li><p> 243 Set your browsers language setting. 244 </p></li></ul></div><p> 245The name of msg file is same as the language ID sent by the browser. For 246example en means "English", ja means "Japanese", fr means "French. 247</p><p> 248If you do not like some of messages, or there are no <span><b class="command">msg</b></span> files for 249your locale, you can create them simply by copying the <span><b class="command">en.msg</b></span> files 250to the directory for “<span class="quote"><span class="emphasis"><em>your language ID.msg</em></span></span>” and filling in proper strings 251to each “<span class="quote"><span class="emphasis"><em>msgstr</em></span></span>”. For example, in <tt class="filename">it.msg</tt>, the 252<span><b class="command">msg</b></span> file for the Italian locale, just set: 253</p><pre class="screen"> 254msgid "Set Default" 255msgstr "Imposta Default" 256</pre><p> 257and so on. If you find a mistake or create a new <span><b class="command">msg</b></span> file, please email it 258to us so we will include this in the next release of Samba. The <span><b class="command">msg</b></span> file should be encoded in UTF-8. 259</p><p> 260Note that if you enable this feature and the <a class="indexterm" name="id2614097"></a>display charset is not 261matched to your browsers setting, the SWAT display may be corrupted. In a future version of 262Samba, SWAT will always display messages with UTF-8 encoding. You will then not need to set 263this <tt class="filename">smb.conf</tt> file parameter. 264</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2614117"></a>Overview and Quick Tour</h2></div></div></div><p> 265SWAT is a tools that many be used to configure Samba, or just to obtain useful links 266to important reference materials such as the contents of this book, as well as other 267documents that have been found useful for solving Windows networking problems. 268</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614130"></a>The SWAT Home Page</h3></div></div></div><p> 269The SWAT title page provides access to the latest Samba documentation. The manual page for 270each Samba component is accessible from this page, as are the Samba HOWTO-Collection (this 271document) as well as the O'Reilly book “<span class="quote"><span class="emphasis"><em>Using Samba.</em></span></span>” 272</p><p> 273Administrators who wish to validate their Samba configuration may obtain useful information 274from the man pages for the diagnostic utilities. These are available from the SWAT home page 275also. One diagnostic tool that is not mentioned on this page, but that is particularly 276useful is <a href="http://www.ethereal.com/" target="_top"><span><b class="command">ethereal</b></span>.</a> 277</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 278SWAT can be configured to run in <span class="emphasis"><em>demo</em></span> mode. This is not recommended 279as it runs SWAT without authentication and with full administrative ability. Allows 280changes to <tt class="filename">smb.conf</tt> as well as general operation with root privileges. The option that 281creates this ability is the <tt class="option">-a</tt> flag to swat. <span class="emphasis"><em>Do not use this in a 282production environment.</em></span> 283</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614198"></a>Global Settings</h3></div></div></div><p> 284The <span class="guibutton">GLOBALS</span> button will expose a page that allows configuration of the global parameters 285in <tt class="filename">smb.conf</tt>. There are two levels of exposure of the parameters: 286</p><div class="itemizedlist"><ul type="disc"><li><p> 287 <span class="guibutton">Basic</span> exposes common configuration options. 288 </p></li><li><p> 289 <span class="guibutton">Advanced</span> exposes configuration options needed in more 290 complex environments. 291 </p></li></ul></div><p> 292To switch to other than <span class="guibutton">Basic</span> editing ability, click on <span class="guibutton">Advanced</span>. 293You may also do this by clicking on the radio button, then click on the <span class="guibutton">Commit Changes</span> button. 294</p><p> 295After making any changes to configuration parameters, make sure that 296you click on the 297<span class="guibutton">Commit Changes</span> button before moving to another area, otherwise 298your changes will be lost. 299</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 300SWAT has context-sensitive help. To find out what each parameter is 301for, simply click on the 302<span class="guibutton">Help</span> link to the left of the configuration parameter. 303</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614301"></a>Share Settings</h3></div></div></div><p> 304To effect a currently configured share, simply click on the pull down button between the 305<span class="guibutton">Choose Share</span> and the <span class="guibutton">Delete Share</span> buttons, 306select the share you wish to operate on, then to edit the settings 307click on the 308<span class="guibutton">Choose Share</span> button. To delete the share, simply press the 309<span class="guibutton">Delete Share</span> button. 310</p><p> 311To create a new share, next to the button labeled <span class="guibutton">Create Share</span> enter 312into the text field the name of the share to be created, then click on the 313<span class="guibutton">Create Share</span> button. 314</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614356"></a>Printers Settings</h3></div></div></div><p> 315To affect a currently configured printer, simply click on the pull down button between the 316<span class="guibutton">Choose Printer</span> and the <span class="guibutton">Delete Printer</span> buttons, 317select the printer you wish to operate on, then to edit the settings 318click on the 319<span class="guibutton">Choose Printer</span> button. To delete the share, simply press the 320<span class="guibutton">Delete Printer</span> button. 321</p><p> 322To create a new printer, next to the button labeled <span class="guibutton">Create Printer</span> enter 323into the text field the name of the share to be created, then click on the 324<span class="guibutton">Create Printer</span> button. 325</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614412"></a>The SWAT Wizard</h3></div></div></div><p> 326The purpose if the SWAT Wizard is to help the Microsoft-knowledgeable network administrator 327to configure Samba with a minimum of effort. 328</p><p> 329The Wizard page provides a tool for rewriting the <tt class="filename">smb.conf</tt> file in fully optimized format. 330This will also happen if you press the <span class="guibutton">Commit</span> button. The two differ 331since the <span class="guibutton">Rewrite</span> button ignores any changes that may have been made, 332while the <span class="guibutton">Commit</span> button causes all changes to be affected. 333</p><p> 334The <span class="guibutton">Edit</span> button permits the editing (setting) of the minimal set of 335options that may be necessary to create a working Samba server. 336</p><p> 337Finally, there are a limited set of options that will determine what type of server Samba 338will be configured for, whether it will be a WINS server, participate as a WINS client, or 339operate with no WINS support. By clicking one button, you can elect to expose (or not) user 340home directories. 341</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614476"></a>The Status Page</h3></div></div></div><p> 342The status page serves a limited purpose. First, it allows control of the Samba daemons. 343The key daemons that create the Samba server environment are: <span class="application">smbd</span>, <span class="application">nmbd</span>, <span class="application">winbindd</span>. 344</p><p> 345The daemons may be controlled individually or as a total group. Additionally, you may set 346an automatic screen refresh timing. As MS Windows clients interact with Samba, new smbd processes 347will be continually spawned. The auto-refresh facility will allow you to track the changing 348conditions with minimal effort. 349</p><p> 350Lastly, the Status page may be used to terminate specific smbd client connections in order to 351free files that may be locked. 352</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614520"></a>The View Page</h3></div></div></div><p> 353This page allows the administrator to view the optimized <tt class="filename">smb.conf</tt> file and, if you are 354particularly masochistic, will permit you also to see all possible global configuration 355parameters and their settings. 356</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2614539"></a>The Password Change Page</h3></div></div></div><p> 357The Password Change page is a popular tool that allows the creation, deletion, deactivation, 358and reactivation of MS Windows networking users on the local machine. Alternately, you can use 359this tool to change a local password for a user account. 360</p><p> 361When logged in as a non-root account, the user will have to provide the old password as well as 362the new password (twice). When logged in as <span class="emphasis"><em>root</em></span>, only the new password is 363required. 364</p><p> 365One popular use for this tool is to change user passwords across a range of remote MS Windows 366servers. 367</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NT4Migration.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="migration.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="troubleshooting.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�33.�Migration from NT4 PDC to Samba-3 PDC�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Part�V.�Troubleshooting</td></tr></table></div></body></html> 368
