7.12 Example of a Migration Plan

7.12.1 The Organization

Acme is an organization with a total of 30,000 users. 16,000 are allocated a fixed workstation, 3,000 are laptop users, and 11,000 access applications in kiosk mode. The network environment is Microsoft Active Directory and SecureLogin version 3.5 is currently implemented. All users are managed from one administration workstation. ZenWorks is used for application distribution and deployment generally occurs overnight.

Sales OU users have laptops for mobile access to the network. The Central Administration OUs contain a combination of static workstations and laptop users.

Manufacturing and Purchasing OU users are mobile; workstations are accessed in kiosk mode. Users in the remaining OUs are each allocated a workstation for their sole use.

The Java functionality provided by the new version of SecureLogin is eagerly awaited by users in the Sales group, so they have volunteered to trial the upgrade. Once the upgrade is successfully deployed to the Sales group, SecureLogin Single is deployed in stages to the rest of Acme.

7.12.2 Summary Order of Upgrade

  1. Directory and test user

  2. Sales

  3. Central Administration and Human Resources

  4. Accounting and Marketing

  5. Manufacturing and Purchasing

  6. Administration Workstation

Week 1, Day 1

Upgrade the server directory; extend the schema and assign rights to the organizational units. Ensure that all containers and organizational units have the:

  • Directory Database Version value 3.0.

  • Stop tree walking here preference option value set to Yes.

Create a test user in the Sales OU and change the setting for the user object to Directory Database Version value 3.5 Test single sign-on enabling of required applications.

Week 1, Day 2

On successful deployment of the upgrade on the test user, manually set the Directory Database Version value to 3.5 on the Sales OU to enable full upgrade functionality.

Deploy the SecureLogin upgrade on all Sales OU workstations/laptops. Assist Sales users with single sign-on enabling Java applications.

Ensure all laptop users have the SecureLogin Cache setting enabled to ensure the cache is stored locally.

Week 1, Day 3

Monitor any upgrade issues for the upgraded Sales OU users. If all issues have been resolved successfully install the SecureLogin upgrade on all laptops and workstations associated with the Central Administration and Human Resources OUs.

Set the Directory Database Version value 3.5 on the Central Administration and Human Resources OUs to enable full upgrade functionality.

Week 1, Day 4

Install the SecureLogin upgrade on workstations associated with the following OUs:

  • Accounting

  • Marketing

Week 1, Day 5

Review and resolve any issues.

Week 1, Day 6

Install the SecureLogin upgrade on workstations associated with the following OUs:

  • Manufacturing

  • Purchasing

Review any upgrade issues encountered by Central Administration OU users. If all OK, change the Directory Database Version value to 3.5 setting for the following OUs:

  • Accounting

  • Marketing

Week 2, Day 7

All users now have the SecureLogin upgrade application installed.

Review and resolve any issues.

Upgrade the administration workstation.

Week 2, Day 8

If all issues resolved successfully, change the Directory Database Version value to 3.5 setting for all remaining OUs.

Ensure the following OUs are enabled simultaneously to cater for mobile/kiosk users:

  • Manufacturing

  • Purchasing

The changeover is planned to occur at midnight and all users have been requested to logout prior to or at this time and wait until 12.10 AM before logging back in.

Week 2, Day 8

Migration completed.