Archives

Category Archive for: ‘Ask Dave’

Ask Dave! Tip #7: Finding items in Deployer

When working with a large amount of data, as usually happens in SharePoint migration projects, it is useful to quickly find items.
Tzunami Deployer provides a useful Find/Find All window, with many options, including:
  • Search in source/all sources/target
  • Search for items and/or containers
  • Search in specific properties or specific types of properties.
  • Search with wildcards or regular expressions
 

Select View –> Find –> Find (Ctrl+F) for the Find window, or View –> Find –> Find All (Ctrl+Shift+F) for the Find All window.

 

Ask Dave! Tip #6: Selective loading of content

When loading content into Tzunami Deployer, loading only the exact content that you wish to migrate will make your life much easier. With only the needed content loaded, you can focus your attention on the specific migration that you are currently performing.

Tzunami Deployer Reloading window

In order to facilitate selective loading of content, Tzunami Deployer provide you with several options, that are available both when just connecting to SharePoint, as well as when (re)loading content into the project. These options includes:

  • Turning on/off the reading of sub-sites
  • Selecting the type of lists you wish to load – None of the lists, only libraries or all lists
  • Controlling items versions reading – No items, the last version of each item, or all versions of the items.

With these options in place, performing a “drill-down” reading of your content is very easy:

  1. Connect to SharePoint, and select to load only the Site Collection that you are interested in. Set Tzunami Deployer not to load subsites, lists or versions.
  2. Once the connecting is finished, you can right click any one of the sub sites, and reload it. Again, select not to read any list nor items’ versions.
  3. Repeat the above step until you reach the sub site that contains the content for migration
  4. This time, you can either reload the sub site with all its content, or reload just some of the lists that contain the content you are migrating.

Ask Dave! Tip #5: Cross Domain users mapping

Ofter, SharePoint migration is only part of a more global IT effort, that includes SharePoint implementation (obviously), Active Directory migration and cleanup, multiple ECM unification, and so on.

The part of Active Directory migration has a deep impact on SharePoint migration, as it often includes changing of Domain names, or even login names. Users names may change from DOMAIN\first.last into a completely different form, such as COMPANY\last_name. This poses a challenge when migrating content from one SharePoint to another, or even when the same SharePoint is used, but with a new Domain Controller or just a different domain.
This case becomes even more interesting when performing a migration from other systems, such as LiveLink or eRoom, which might have their own users repository, and might not even be connected to any LDAP.

Tzunami Deployer User Mapping

Luckily, Tzunami Deployer is built just for those cases. As part of the content migration, you can easily define a mapping between source users (users that come from the the source system, either from Active Directory or another repository), and target users (users that are available from the Active Directory used in your destination SharePoint).

During the migration process, you will encounter user mapping steps, that will allow you to perform mappings, edit past mappings, or even export and import mapping files.

The Export/Import feature is extremely useful – it generates an XML file that you can edit using Excel (or any other editor) in order to map your users, based on any logic you which. Alternatively, you can generate your own mapping files, and import them into Tzunami Deployer.

Additionally, Tzunami Deployer will provide you with a smart suggestion for the default mapping. This suggestion is smart enough to identify the same username (in case the same Active Directory is used), or even the same login name under different domains.

Lastly, you can always contact Tzunami Support Team in order to get information about enhancing the default users mapping to meet your special needs.

Ask Dave! Tip #4: Rule Egine

Tzunami Deployer Rule Engine is a powerful Deployer component that enables you to automate large parts of the SharePoint migration process by creating flowcharts of If-Then statements in a rules editor. A Rule consists of a set of conditions (logical IFs) and Actions (logical THENs). If all conditions are fully met, then the Actions are executed. A Rule Set is a set of rules that define deployment options for a specific Enterprise Content Management (ECM) system.

The Deployer Rule Engine is intended for power users, System Integrators, and Tzunami Deployer specialists. It provides you with a high degree of freedom in regard to the business logic you can create.

The order of the Rules in a Rule Set is important. The Rule Engine processes each container item in the deployed item, evaluating the Rules one after the other against each item. If even one Condition is not met, the Rule is ignored, and the Rule Engine proceeds to the next Rule. If all Conditions are met, the Actions are performed, and the Rule Engine continues handling the next item. No other rule is evaluated for that item. As a result, even if two Rules are valid for a certain item, only the first Rule is evaluated and performed.

Rule Sets Editor contains several built-in default Rule Sets that define some common deployment logic. You can customize these default Rule Sets to suit your specific deployment needs.

Ask Dave! Tip #3: Filtering source items

Did you know? With Tzunami Deployer, you can filter items in the source panel, prior to the deployment and migration. This allows you to perform content clean-up before moving to the new system. The filtering can be done based on any property.

Load the desired source content into the Tzunami Deployer project, right-click a folder, and select “Filter”
The new window that appears allows you to select properties, and add filtering condition.

Select a property in the left list of properties, select a criteria and one or more values. Click the “Add Condition” button, and press “OK” to close the window.

You can now see that only files that match the conditions selected appear (and only those items will be deployed and migrated). Additionally, a new counter appears next to each folder (using the square brackets ‘[ ]’) that display the number of items that matched the conditions.

Ask Dave! Tip #2: Finding problematic items

Although Tzunami Deployer resolves many of the issues during the deployment process, some issues must be handled manually by the user. Examples of these issues might include folder names that are too long, files with blocked extensions and so on.

In order to easily locate items which are problematic, you can use the “Find problematic items” feature of Deployer. From the View menu, select Find, and then Find problematic items (clicking CTRL+P will also work). A window with a list of all problematic items will appear, with the reason the item was identified as problematic.

You can now double-click on any item, or select an item and press Go to, in order to jump directly to the selected item.

Bonus: Resolving an item’s issue will automatically update the list, and remove the problematic item.

Ask Dave! Tip #1: Editing metadata of multiple items

Did you know, that in Tzunami Deployer, you can select multiple items and modify their metadata in one action?

Load the desired list into the Tzunami Deployer project, select multiple items (you can use the CTRL  or SHIFT keys, just like in Windows Explorer). Once you have the items selected, right-click and select “Properties”.
You can now go and modify the values of the various properties. All the selected items will receive the assigned value.

Visit Our Partner