16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1106 Part XI: Upgrading <strong>and</strong> Migrating to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

Caution If you are using the SharePoint Migration Tool to migrate <strong>and</strong><br />

upgrade a site from SharePoint Team Services or FrontPage 2002 Server<br />

Extensions from <strong>Microsoft</strong> to Windows SharePoint Services, be aware that<br />

several features or types of customizations supported in these environments<br />

will not migrate properly or will not work in a migrated site. For a list<br />

of items that you must re-create or work around, see “Upgrade Considerations”<br />

in the Windows SharePoint Services Administrator’s Guide. These<br />

are also available in Appendix B, “Upgrading SharePoint Team Services to<br />

Windows SharePoint Services” on the Companion CD-ROM. It is very important<br />

that you review this list. Of special note is that some characters are not<br />

supported in Windows SharePoint Services, such as /, \, :, *, ?, “, , |,<br />

#, {, }, %, &, <strong>and</strong> ~, as well as tab characters <strong>and</strong> multiple periods.<br />

If a file, a folder, or a URL name in your original site contains one of<br />

these characters, it is replaced with an underscore (_). Multiple periods are<br />

replaced with a single period. Additional digits might be appended to the file<br />

or folder name if there are conflicting renaming changes. If you have other<br />

applications that make reference to these objects, they could fail or display<br />

broken links. Also, remember that lists within Windows SharePoint Services<br />

have column restrictions. You will receive errors when you try to add too<br />

many columns to a list, <strong>and</strong> migrated content might be truncated or might<br />

fail to restore if the original list has more columns than the second version<br />

supports. In addition you should be aware that lists <strong>and</strong> document libraries<br />

will have a new creation date; that is, the creation modification dates for<br />

lists <strong>and</strong> document libraries within SharePoint Team Services are not preserved.<br />

Creation <strong>and</strong> modification dates for list items <strong>and</strong> documents<br />

should be preserved.<br />

If you do not want to migrate user information to the new site, you would use the<br />

-x parameter with this tool. The new user accounts are created based on the users’ email<br />

addresses, so each user must have a unique e-mail address for the account creation<br />

to work correctly. If a user does not have an e-mail address in the old site, no<br />

account can be created for that user. Also, because only one account is created for each<br />

e-mail address, a shared e-mail address results in a merged user account that is given all<br />

of the rights that each original user had, <strong>and</strong> it is also listed as the user name for any<br />

items added to the site by any of the original users. If Windows SharePoint Services is<br />

installed using the Active Directory account creation mode, be sure that each existing<br />

user account has a unique e-mail address before migrating a site, <strong>and</strong> that you enter the<br />

full e-mail address (for example: someone@example.com).<br />

If the site you are backing up or restoring is large, it can take quite a while to<br />

process. For example, a site with about 4.5 gigabytes (GB) of data can take up to

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!