SharePoint-content-migration
Home > Support > FAQ

 FAQ
expand Q:   Are Tzunami Deployer’s operations run from the command line?
   A:
There is a command line option to simulate a "commit" operation.
expand Q:   Can URL redirection be placed so that those with links to documents on Livelink be redirected to the new location for the migrated documents on SharePoint?
   A:
The link redirection is a service which l notes all requests on a specific server (your old LL server). It then redirects any requests for an item already transferred to its new location in MOSS. This function is based on Tzunami Deployer’s Commit Reports option which contains the information regarding the source item as well as its new location.
expand Q:   Does Tzunami Deployer allow migration operations to be performed remotely?
   A:
Yes. Tzunami Deployer requires a Windows Service component to be installed on the SharePoint server. All Tzunami Deployer ‘s clients after this component are installed and can communicate and function remotely.
expand Q:   Does Tzunami Deployer fix broken links?
   A:
Tzunami Deployer itself does not handle the repairing of absolute links referring to the source system. Tzunami Deployer’s Family of Products includes a redirection tool to solve such instances. For more information, please contact the Tzunami Support Team at: support@tzunami.com.
expand Q:   Does Tzunami Deployer log migration operation results on to a file?
   A:
Yes. All actions are logged in various ways.
expand Q:   Does Tzunami Deployer migrate ‘publishing sites’ and layouts?
   A:
Yes, although this may require a certain amount of customization.  For more details, please contact sales@tzunami.com. 
expand Q:   Does Tzunami Deployer migrate documents and lists?
   A:
Yes. Tzunami Deployer supports the migration of all kinds of containers and contained items from the source-system.
expand Q:   Does Tzunami Deployer migrate metadata from the documents and lists?
   A:
Yes. Tzunami Deployer extracts and migrates metadata for sites/lists/items, including the create/modified dates and user fields.
expand Q:   Does Tzunami Deployer migrate personal sites?
   A:
Yes. Personal sites are treated as any normal sites in Tzunami Deployer and can be migrated along with its data.
expand Q:   Does Tzunami Deployer migrate regional settings?
   A:
No. Tzunami Deployer is a content migration tool and therefore does not support migrating non-data related definitions.
expand Q:   Does Tzunami Deployer migrate site definitions?
   A:
The main site-definitions of SharePoint reside on the SharePoint server and are not part of the SharePoint data itself. For this reason, Tzunami Deployer does not support the migration of site definitions. Custom site/list templates, on the other hand, reside in the SharePoint libraries: “site/list template gallery”. These lists are read by Tzunami Deployer. The contained item can be migrated to the target SharePoint. Note that any dependency or inconsistency that may occur after the migration takes place, is as a result of the creator of the site/list template. Tzunami Deployer is only responsible for moving the files.
expand Q:   Does Tzunami Deployer migrate the alerts feature?
   A:
No. Tzunami Deployer is a content migration tool and as such it does not support the migration of alerts or views.
expand Q:   Does Tzunami Deployer migrate the file-system security?
   A:
Tzunami Deployer extracts the file-system security definitions and enables the mapping of these to SharePoint security definitions. Security modeling is a complex topic. If you have any further questions about how Tzunami Deployer supports security extraction and modeling, please contact the Tzunami Support Team at support@tzunami.com.
expand Q:   Does Tzunami Deployer migrate the folder structures?
   A:
Tzunami Deployer extracts and enables the deployment of any hierarchy structure existing in the source system.
expand Q:   Does Tzunami Deployer migrate the version history of the documents?
   A:
Yes. Tzunami Deployer retains the version history for items and documents with all the relevant meta-data.
expand Q:   Does Tzunami Deployer migrate themes, titles and headers of sites?
   A:
Titles are retained but not their designs.
expand Q:   Does Tzunami Deployer migrate workflows?
   A:
No. Tzunami Deployer is a content migration tool and as such does not support the migration of non data related configurations.
expand Q:   Does Tzunami Deployer preserve ‘views’ when migrating lists?
   A:
No. Tzunami Deployer is a data migration tool and therefore does not migrate views.
   A:
No. The current version of Tzunami Deployer requires a Windows Service component to be installed on the SharePoint server
expand Q:   Does Tzunami Deployer support creating a batch of migration operations which can run a ‘scheduled time’ feature?
   A:
Yes. Tzunami Deployer works offline from SharePoint and commits all performed operations in a batch-style manner. Tzunami Deployer can be scheduled as a command-line tool, to run with the Windows Task Scheduler.
expand Q:   Does Tzunami Deployer support item level migration?
   A:
Tzunami Deployer allows migration of sites and items and their metadata to
SharePoint.
expand Q:   Does Tzunami Deployer support migrating permissions at the list level?
   A:
Tzunami Deployer enables the management of list-level permissions during migration. Security modeling is a complex operation. It is advisable to consult with the Tzunami Support Team regarding all aspects of your security migration requirements.
expand Q:   Does Tzunami Deployer support migrating the modified time field for libraries?
   A:
Tzunami Deployer does not migrate the specific time in which the library itself was created and neither does SharePoint support such an option . However, Tzunami Deployer does migrate the properties of the documents themselves including the modified by/date fields along with the rest of the system properties. They are updated by Tzunami Deployer according to the source data.
expand Q:   Does Tzunami Deployer support multilingual migration?
   A:
Tzunami Deployer is not language specific. Regardless of what language the data is written in, Tzunami Deployer can migrate it - including the creation of sites and lists, using installed language-specific templates.
expand Q:   Does Tzunami Deployer support site level migration?
   A:
Tzunami Deployer allows migration of sites, items and their metadata to SharePoint
expand Q:   Does Tzunami Deployer support the migration of all list types including:document libraries, issues, tasks, contacts, announcements, discussions ?
   A:
Yes
expand Q:   How does Tzunami Deployer control the basic differences between the way that eRoom and SharePoint manage their “versions comments”?
   A:
(I.e. eRoom retains all the comments at the items level, without a real connection between the comments and the versions themselves. SharePoint, on the other hand, retains the comments at the version level with each version possessing its own comments. )
In order to overcome this difference, Tzunami Deployer includes all the comments in every version.

expand Q:   I wish to install Tzunami Deployer on the production server , I have read about Documentum Foundation Classes (DFC) – how can this help me to export the content from Documentum?
   A:
In order to export content from the Documentum server, the DFC needs to be installed on the machine that operates Tzunami Deployer for Documentum (which is the same machine that runs Tzunami Deployer). The DFC should be part of your Documentum server installation.
expand Q:   Is .NET Framework required for the operation of Tzunami Deployer and / or Tzunami Deployer for eRoom ?
   A:
Yes it is required.  The installation of .NET framework 1.1 on the eRoom server can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&displaylang=en.  Once this is installed, download and run the Tzunami Deployer for eRoom from http://download2.tzunami.com/setups/exporters/eRoom/eRoom6exporterSAE.zip
Extract the zip file and save to any folder and then run ‘Tzunami eRoom exporter.exe’.
expand Q:   Is it a Windows or web- based application?
   A:
Deployer is a Windows-based application with a Windows service component running on the SharePoint server.
expand Q:   Some source items have “Publishing Date” as well as “End Date” properties as metadata.Using Tzunami Deployer, how can we migrate these properties to the “Publishing Schedule Start Date” and “Publishing Schedule End Date” column types?
   A:
Tzunami Deployer needs additional instruction to migrate “Publishing Date” values as “Publishing Schedule Start Date”. This is performed in the Property Mapping step located in the Deploy wizard.  Once this is accomplished but prior to committing the files to SharePoint, the correct values need to be checked. They should apply to the migrated items in the target SharePoint 2007panel.
expand Q:   We have a fixed list of domains that we would like to read, how can we achieve this?
   A:
The complete list can be specified in Tzunami Deployer’s configuration file. Ensure that only
the domains required for the migration are obtained. This may even save reading-time if some unnecessary domains exist.
expand Q:   What access rights does Tzunami Deployer require on the source environment?
   A:
This varies from system to system. Generally it requires a user with full read permissions on the source system. More details can be found in Tzunami Deployer’s installation guide.
expand Q:   Where can I download the Tzunami Deployer’s Remote Service?
   A:
The Tzunami Deployer’s Remote Service is a component required in order to run the Tzunami Deployer on ex-SharePoint farm machines. This component is not available as part of the Tzunami Deployer evaluation phase (in which the Tzunami Deployer installation must be installed on the SharePoint server). Upon purchasing the product, all relevant links for downloading will be supplied. If you have any further question in this regard, please contact the Tzunami Support Team at: support@tzunami.com.
expand Q:   Which “stored procedures” are required to “execute”?
   A:
The easiest is to grant execute permissions to all stored procedures. Regardless of the situation, no changes are needed to the source database. Nevertheless, the following stored procedures are required:
a. proc_getPortalSites
b. proc_getSites
c. proc_GetSiteFlags
d. proc_getSitesInVirtualServer
e. proc_getSiteByToken
f. proc_getServers
g. proc_EnumTemplates
h. proc_GetTemplate
i. proc_getDatabaseWithServer
expand Q:   While exporting the data, the filter required by the export wizard was set by the default "created equals now" function. However this exported almost no data?
   A:
When exporting the entire LiveLink, the filtering step should be ignored and skipped (click the “Next” button). Select properties and set the values only if filtering the exported data is preferred.
expand Q:   Why is “execute permission” required?
   A:
Some of the queries on SharePoint 2003 are performed by running stored procedures (i.e. stored  procedures for reading data). Therefore, permissions are necessary to execute stored procedures  when reading the source SharePoint 2003
Download evalutaion
Live Demo
Copyright 2008 Tzunami Inc. All Rights ReservedDesigned by PROPOZA

Tzunami logo Home | About Us | Careers | Partners | Contact | Site map | xml sitemap | Tzunami News Feed
Tzunami.com - Leading provider for SharePoint Migration solutions, offering Content Migration Such as:
Documentum to SharePoint, MOSS to MOSS, Fileshare migration, MOSS 2007 migration, Windows server 2003 migration, SharePoint Import and others.