From 19dd70783d94c93cd0e1dc3bb69ba581fdfcc61f Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Sat, 14 May 2005 01:22:34 +0000 Subject: Work-in-progress commit. (This used to be commit 0a60cc737533a2ef00176328c8481e1d35b8fd83) --- .../TOSHARG-TheNetCommand.xml | 108 ++++++++++++++------- 1 file changed, 74 insertions(+), 34 deletions(-) (limited to 'docs') diff --git a/docs/Samba-HOWTO-Collection/TOSHARG-TheNetCommand.xml b/docs/Samba-HOWTO-Collection/TOSHARG-TheNetCommand.xml index 0f7fb307a4..fa308be406 100644 --- a/docs/Samba-HOWTO-Collection/TOSHARG-TheNetCommand.xml +++ b/docs/Samba-HOWTO-Collection/TOSHARG-TheNetCommand.xml @@ -511,7 +511,7 @@ kyocera - Migration of Shares and Files + Share, Directory and File Migration Shares and files can be migrated in the same manner as user, machine and group accounts. @@ -523,7 +523,7 @@ kyocera - The net rpc share command may be used to migratio share, directories + The net rpc share command may be used to migrate shares, directories files, printers, and all relevant data from a Windows server to a Samba server. @@ -541,10 +541,10 @@ kyocera of both SMB and MS DCE RPC services. The benefit of the manner in which the migration process has been implemented, the possibility now exists to use a Samba server as a man-in-middle migration service that affects a transfer of data from one server to another. For example, if the Samba - server is called MESSER, the source Windows NT4 server is called - PEPPY, and the target Samba server is called GONZALES - MESSER can be used to affect the migration of all data (files and shares) from PEPPY to - GONZALES. If the target machine is not specified, the local server is assumed by default. + server is called MESSER, the source Windows NT4 server is called PEPPY, and the target Samba + server is called GONZALES, the machien MESSER can be used to affect the migration of all data + (files and shares) from PEPPY to GONZALES. If the target machine is not specified, the local + server is assumed by default. @@ -552,39 +552,72 @@ kyocera server (or domain) as well as the processes on which the migration is critically dependant. + + Share Migration + - -"net" allows to migrate plain share-definitions. These consists of a -share-name, a directory-path in the file-system, an optional description and -security-settings that allow share-access. If your migration-destination is a -Samba-System (the most obvious case), you need to have a "add share command" -configured in smb.conf. Otherwise the share-add on the destination-system will -fail. There is an example script that is suitable for the "add share command" -available under $SAMBA_SOURCES/examples/misc/. In addition, the account that is -used during migration must have enough permissions to add shares on the -destination system. See the privileges-chapter elsewhere in this document for a -description of how to set up the required privileges. - -* Syntax: - - net rpc share MIGRATE SHARES <sharename> -S <source> - [--destination=localhost] [--exclude=share1,share2] [-v] + The net rpc share migrate command operation permits the migration of plain + share stanzas. A stanza contains the parameters within which a file or print share are defined. + The use of this migration method will create share stanzas that have as parameters the file + system directory path, an optional description, and simple security settings that permit write + access to files. One of the first steps necessary following migration is to review the share + stanzas to ensure that the settings are suitable for use. + -If <sharename> is ommited, all shares will be migrated. The (possibly huge) -list of offered shares on the remote system can be limited with the -"--exclude"-switch in that case. + + The shares are created on-the-fly as part of the migration process. The smbd + application does this by calling on the operating system to execute the script specified by the + &smb.conf; parameter add share command. + -* Example: + + There is a suitable example script for the add share command in the + $SAMBA_SOURCES/examples/scripts directory. It should be noted that + the account that is used to drive the migration must, of necessity, have appropriate file system + access privileges and have the right to create shares and to set ACLs on them. Such rights are + conferred by these rights: SeAddUsersPrivilege, SeDiskOperatorPrivilege. + For more information regarding rights and privileges please refer to . + - "net rpc share migrate shares myshare -S win2k -U administrator%secret" + + The syntax of the share migration command is shown here: + +net rpc share MIGRATE SHARES <sharename> -S <source> + [--destination=localhost] [--exclude=share1,share2] [-v] + + When the parameter <sharename> is ommited, all shares will be migrated. The potentially + large list of available shares on the system that is being migrated can be limited using the + --exclude switch. For example: + +&rootprompt; net rpc share migrate shares myshare\ + -S win2k -U administrator%secret" + + This will migrate the share myshare from the server win2k + to the Samba Server using the permissions that are tied to the account administrator + with the password secret. The account that is used must be the same on both the + migration source server, as well as on the target Samba server. The use of the net rpc + vampire, prior to attempting the migration of shares, will ensure that accounts will be + identical on both systems. One precaution worth taking before commencement of migration of shares is + to validate that the migrated accounts (on the Samba server) have the needed rights and privileges. + This can be done as shown here: + +&rootprompt; net rpc right list accounts -Uroot%not24get + + The steps taken so far performs only the migration of shares. Directories and directory contents + are not migrated by the steps covered up to this point. + + + - - will migrate the share "myshare" from the server "win2k" to your - local Samba Server using the account "administrator" and the password - "secret". Note that "administrator" must exist on "win2k" and on your local samba - server with the same password. All the files and directories that are shared inside - "myshare" are not migrated yet. + + File and Directory Migration + + Everything covered to this point has been done in preparation for the migration of file and directory + data. For many people preparation is potentially boring and the real excitement only happens when file + data can be used. + Migrate files and directories of file-shares ----------------------------------------------------------- @@ -654,11 +687,18 @@ share-definitions and then all shared files and directories afterwards. - will generate a full file-server clone of "w2k3server" using the "administrator"-account. + + + -Migrating a Print-Server -======================== + + + Printer Migration + + + Migrating printers ----------------------------------------------------------- -- cgit