Using Smigrate.exe to Migrate Sites

The Smigrate.exe tool is available in the Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin folder on your server computer. To use Smigrate.exe, you must be a site administrator for both the Web site being backed up and the destination Web site. Smigrate.exe takes the following parameters:

To back up a site, you use Smigrate.exe with the following parameters:

smigrate.exe -w <Web site URL> -f <backup filename> [-e -y -u <username> -pw <password>]

For example, to create a backup of http://myserver/site1 to a file called backup.fwp at the root of the c:\ drive, without including any subwebs of the Web site, you would type the following:

smigrate.exe -w http://myserver/site1 -f c:\backup.fwp -e

Note  If you are migrating a large number of Web sites, it is recommended that you manually back up each Web site separately and restore each Web site after backup to prevent possible memory usage errors.

To restore a site, you use Smigrate.exe with the following parameters:

smigrate.exe -r -w <Web site URL> -f <backup filename> -u <username> -pw <password>]

For example, to restore the above site to http://yourserver/site2, you would use type the following:

smigrate.exe -r -w http://yourserver/site2 -f c:\backup.fwp

If you are logged on with an account that does not have specific permissions to the destination Web site, you can specify a site administrator user name and password that has the appropriate permissions. For example, to restore a site and specify the administrator user name and password, you would use the following syntax:

smigrate.exe -r -w <Web site URL> -f <backup filename> -u <site administrator user account> -pw <password>

When you migrate a site from SharePoint Team Services v1.0 to Windows SharePoint Services Beta 2, you can also use the -x parameter, which allows you to determine whether or not to preserve the security settings for the Web site (user accounts and site groups). You can run the smigrate.exe tool from any computer running Windows 2000 or later. The tool can be copied to another computer and used even if Windows SharePoint Services Beta 2 is not installed.

Note   The upgrade and migration from SharePoint Team Services v1.0 to Windows SharePoint Services Beta 2 is not full fidelity, and some data may be lost due to changes in the functionality between versions. You can view the smigrate.log file to see which items migrated successfully and which did not. The smigrate.log file is stored in the %temp% directory for your user account. If a log file already exists from a previous backup or restore, a log file will be created using the next available name (such as smigrate_1.log, smigrate_2.log, and so on).

To restore a site based onSharePoint Team Services v1.0 to a server running Windows SharePoint Services Beta 2, and exclude the security information, you use Smigrate.exe with the following parameters:

smigrate.exe -r -w <Web site URL> -f <backup filename> -x

Troubleshooting Migration Issues

If you site does not migrate as expected, refer to the following list to understand causes or find solutions:

• Alerts and Web discussions from unavailable users were not restored.

If a user account no longer exists at restore time, or if the account was a local account, the Alerts and Web Discussion items for that user account cannot be restored.

• File creation timestamps are incorrect

The file creation timestamp is set to the restore time when you restore a site.

• Survey creation times are incorrect.

Creation times for surveys are not preserved during migration.

• The site language is incorrect.

When you restore a site, the language of the restored site must match that of the backed up site. Be sure that the language you need is available on the server you are restoring to.

• There are too many views.

If your site was migrated from SharePoint Team Services v1.0 to Windows SharePoint Services Beta 2, the restored site contains both the views from the original site and the default views for Windows SharePoint Services Beta 2. The restored SharePoint Team Services v1.0 views are listed after the default Windows SharePoint Services Beta 2 views. You can remove any views that you do not want.

• I can't back up or restore a site through a proxy server.

If your firewall or proxy server requires authentication, you may not be able to back up or restore a site.

• I see error messages in the log file for files in folders in a document library.

The files have been restored even though you may see error messages.

• Web Discussions for a particular user were not migrated.

User accounts are case-sensitive during migration. If the original site had a user with the username "User1" and the restored site's database has an entry for "user1", the Web discussions for the user are not restored.

In addition, when you migrate a site from SharePoint Team Services v1.0 to Windows SharePoint Services Beta 2, there are some features or customizations that do not migrate. For a list of these items, see Upgrade Considerations.

Comme promis, ca fonctionne

Notre sécnario peut etre donc tester

il suffit de lancer la ligne de commande suivante

stsadme.exe -o addtemplate -filename <chemin du fichier> -title <template title> -description <description of the template>

exemple :

dans le chemin

C:\Program Files\Fichiers communs\Microsoft Shared\web server extensions\60\BIN

stsadm.exe -o addtemplate -filename c:\DemoCIDJ.stp -title "Modèle de DEMO1" -description "Modéle spécifique de DEMO"

une fois lancé, si tout ce passe bien , le systéme te demande de relancer IIS via la commande iisreset en dos

Apres c'est tout bon

J'ai même vérifié depuis le site directory (zone annuaire) du portail

voila

Renaud