Deployment Unit Schedule Config - Scenario C

Modified on Fri, 20 Feb at 10:04 AM

TABLE OF CONTENTS



Scenario C: Scheduling a Manchester Office User Migration

This article provides step-by-step instructions for configuring a deployment unit in ManagementStudio to support a complex migration schedule. The example scenario is for migrating all users based in the Manchester office with the following constraints:

  • 3-week deployment (Monday to Friday, with occasional Saturday hours)
  • 10 migrations 09:00–10:00
  • 10 migrations 10:00–11:00
  • 5 migrations 11:00–12:00
  • 10 migrations 14:00–15:00
  • 5 migrations 16:00–17:00
  • Middle Saturdays: 5 one-hour slots at 10:30 and 12:30
  • On Tuesdays: Remove 2 slots each from the 09:00, 10:00, and 11:00 sessions
  • Exclude the last two Fridays (team away at another site)
  • On the first Monday: Reduce available slots by 3 for each session

Follow the steps below to implement these requirements in a deployment unit schedule.


Create a Deployment Unit

  • Navigate to Deployment Units in the vertical menu (1).

  • Select All Deployment Units (2).

  • Click New (3).


  • In the target module dropdown, select User Migrations (1).

  • Enter a name and location for the deployment unit (2).

  • Click New to create the deployment unit (3).

  • The new deployment unit will appear in the grid.


Configure the Deployment Unit

  • Double-click the new deployment unit (e.g. Manchester) in the grid to open its details.

  • Define the deployment unit's Start date and End date (1). For example, schedule the deployment to start at 09:00 on 28/09/2020 and finish at 18:00 on 16/10/2020.

  • Click Save Deployment Unit (2).


  • Go to the Schedule Config tab (1).

  • By default, the deployment unit inherits session slots from the global schedule. To override this:
  • Click the Toggle button (2) to switch from Global Slots to Local Slots.
  • In the confirmation prompt, tick Yes, I'm sure (3).
  • Click Switch to confirm (4).

Add Migration Slots and Constraints

  • Click Click here to add new item (1) to define migration slots.

  • For each session, specify (2):

    • Start Time
    • End Time
    • Migration Slots (number of available slots)
    • Days of the week (e.g. Monday–Friday)
  • Example session configuration:

    • 09:00–10:00: 10 slots
    • 10:00–11:00: 10 slots
    • 11:00–12:00: 5 slots
    • 14:00–15:00: 10 slots
    • 16:00–17:00: 5 slots
  • For the middle Saturdays during the 3-week period (03/10/2020 and 10/10/2020) (3):

    • Add entries for 10:30–11:30 and 12:30–13:30 with 5 slots each.
  • Click Save Changes (4) after configuring all slots.


Additional Constraints

Remove 2 Slots from Tuesday Morning Sessions

  • In the slot utilisation grid, filter for all 09:00, 10:00, and 11:00 sessions on Tuesdays (1).

  • Click Select All (2) to highlight these slots.

  • Right-click and select Block Slots (3)Block 2 Slots (4). This reduces each session by 2 slots.

Exclude the Last Two Fridays (09/10/2020 and 16/10/2020)

  • In the Suspended Days section, click Click here to add new item (1).

  • Enter the dates to be excluded and add a note (2).

  • Click Save Changes (3).

Reduce Slots by 3 on the First Monday

  • In the slot utilisation grid, filter and select all slots for the first Monday (28/09/2020) (1).

  • Right-click and select Block Slots (2)→ Block 3 Slots (3) to reduce each session by 3 slots.

  • Click Save Changes (4) at the top.


Review the Deployment Unit

Once configuration is complete, you can view the deployment unit schedule. The number of available, blocked, used, and free slots will be displayed.


Further Support

For additional assistance, visit the ManagementStudio Service Desk to search the knowledge base or submit a support ticket.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article