Deployment Unit Schedule Config - Scenario B

Modified on Mon, 2 Feb at 5:24 PM

TABLE OF CONTENTS




Scenario B: Scheduling a Birmingham Office User Migration

This guide outlines how to model the following constraints for migrating users in the Birmingham office using the Deployment Unit schedule configuration:

  • 3-week deployment (Monday to Friday; occasional hours on Saturday)
  • 10 migrations from 09:00–10:00
  • 10 migrations from 10:00–11:00
  • 5 migrations from 11:00–12:00
  • 10 migrations from 14:00–15:00
  • 5 migrations from 16:00–17:00
  • Saturdays to have 5 one-hour slots at 10:00
  • Second Monday is a non-working day

Create a Deployment Unit

  • Select Deployment Units from the vertical menu.

  • Choose All Deployment Units.

  • Click New.

    Deployment Units menu

  • In the new deployment unit window:

    • Select User Migrations from the target module dropdown (1).
    • Enter the Deployment Unit Name and set the Location (2).
    • Click New to create the deployment unit (3).



  • Verify that the new deployment unit appears in the list.




Configure the Deployment Unit

  • Double-click the newly created deployment unit (e.g., Birmingham) to open its details.

  • Set the Start Date and End Date for a 3-week period (1). For example, start at 09:00 on 02/02/2026 and finish on 28/02/2026 at 18:00.

  • Click Save Deployment Unit (2).


  • Go to the Schedule Config tab (1).

    • By default, the schedule is inherited from the global configuration. To override:
  • Click the Toggle switch to change from Global Slots to Local Slots (2).

  • In the confirmation dialog:

    • Ensure the checkbox Yes, I’m sure is selected (3).
    • Click Switch to confirm (4).



Define Slot Schedule

  • Click Click here to add new item to create a new schedule entry.

  • For each schedule slot, define:

    • Start Time
    • End Time
    • Migration Slots (number of migrations per slot)
    • Applicable Days of the Week
  • Example slot setup:

    • Monday–Friday:
      • 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
    • Saturdays (e.g., 7th and 21st):
      • 10:00–11:00: 5 slots (set valid dates and select only Saturday)
  • Click Save Changes to commit the schedule.




Add a Suspended (Non-Working) Day

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

  • Enter the date for the non-working day (2) (e.g., 16/02/2026) and add a note if required.

  • Click Save Changes (3) to record the suspension.



Review Slot Utilisation

  • After saving, review the Slot Utilisation grid at the bottom to see:

    • Available Slots
    • Blocked Slots
    • Slots Used
    • Free Slots

This completes the process for modelling the Birmingham migration deployment constraints.




Further Support

For additional assistance, visit the ManagementStudio Service Desk to search the knowledge base or create a new 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