Moving Repository How to guide

From Swivel Knowledgebase
Revision as of 17:34, 14 December 2012 by Gfield (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Overview

Users may be required to move repository, such as from one AD domain to another, this details the process to handle this within Swivel.


Prerequisites

Swivel 3.3 or higher


How to Guide

Swivel 3.9

Swivel version 3.9 allows users to optionally move repository, so they will not need a new PIN number to be sent out (Swivel 3.8 and earlier deletes and creates the user)


Swivel 3.3 to 3.8

Moving repository requires the account to be moved to the new repository and Swivel will delete the user from the existing repository and create the user in the new repository. This will result in a new PIN number being generated for the user.

Create the new repository on the Swivel Server see AD Repository Server Settings, and assign the path for the groups see AD Groups. If new groups are to be created, then new transports will need to be configured.

  • Move the user in AD to the new domain, removing them from the old AD group and adding them to the new AD group.
  • On the Swivel primary Synchronise the old AD by selecting User Administration, and the Old AD repository
  • On the Swivel primary select User Administration, and the Old AD repository then click on purge
  • Under User Administration select the new AD domain then click on user Sync and the user should appear. They should be sent a new PIN number. If the user does not appear, check the logs. If there is a duplicate user entry, then the user will still be in the old Ad and will need to be purged, see above


Testing

Ensure users are moved to the new repository


Known Issues

Troubleshooting