Deployment Unit Schedule Config - Scenario C

Modified on Fri, 6 Dec at 3:54 PM

TABLE OF CONTENTS

Scenario C

As a Project Administrator, you may have been tasked with migrating all the users currently based in the Manchester office and have been given the following constraints to complete the deployment.

  • 3-week deployment (Monday to Friday with occasional hours on Saturday) 
  • 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 should have 5 one hr slots @ 10:30 & 12:30
  • There is a need to remove 2 slots from the 9am 10am and 11am appointments on Tuesdays
  • The last two Fridays should be excluded and team is away on another site
  • Reduce available slots on the 1st Monday by 3 for each session

This article will describe how to model this within the deployment unit schedule config tab.


Create Deployment Unit

  • Click 'Deployment Units' (1) from the vertical menu on the left
  • Select 'All Deployment Units' (2)
  • Click 'New' (3)



  • Select 'User Migrations' (1) from the target module drop down menu
  • Populate the 'deployment unit name and location' (2) 
  • Click on 'New' (3) to create the new deployment unit

  • The new deployment unit should now be visible on the grid


Configure Deployment Unit

  • Double click on the new deployment unit (Manchester) on the grid to open the details panel
  • Define the deployment unit's 'Start date and End date' (1). The screenshot below shows the deployment will kick off at 09:00 hrs on 28/09/2020 and run through until 18:00 hrs on 16/10/2020
  • Click on 'Save Deployment Unit' (2)



  • Click on 'Schedule Config' (1) tab
By default a Deployment unit will inherit its available sessions from the globally defined schedule. It is possible to override this global schedule.


  • Click on the 'Toggle' (2) to switch from Global Slots to Local Slots
  • You will receive a prompt on the screen, ensure the checkbox 'Yes, I'm sure' (3) is ticked
  • Click on 'Switch' (4) to confirm changes



  • Next we need to configure the schedule based on the constraints from earlier:
    • 3-week deployment (Monday to Friday with occasional hours on Saturday) 
    • 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 should have 5 one hr slots @ 10:30 & 12:30
  • Click on 'Click here to add new item' (1)
  • Define the Start Time, End Time, Migration Slots and the days of the week (2)
  • There are five one hour slots to migrate users over the middle Saturdays during the 3-week period. According to the calendar, this is 03/10/20 & 10/10/20. This has been defined accordingly to reflect the number of migration slots available (3) on both Saturdays
  • Click 'Save Changes' (4) 



  • We also have the following constraints to define:
    • There is a need to remove 2 slots from the 9am 10am and 11am appointments on Tuesdays
    • The last two Fridays should be excluded and team is away on another site
    • Reduce available slots on the 1st Monday by 3 for each session
  • Scroll down to the slot Utilisation grid. Filter the grid to display all the 9am, 10am and 11am appointments on Tuesday (1)
  • Click on 'Select All' (2)
  • Right-click and select 'Block Slots' (3) from the context menu -> 'Block 2 Slots' (4). This will remove 2 slots from the 9am, 10am and 11am appointments on Tuesday



  • The last two Fridays, 09/10/2020 and 16/10/2020 are non working days. This is defined in the suspended days section
  • Click on 'Click here to add new item' (1) from within the Suspended Days section
  • Enter the 'Dates' (2) and the corresponding notes
  • Click on 'Save Changes' (3) to commit the changes



  • Reduce the available slots on the first Monday by 3 for each session
  • Scroll down to the slot utilisation grid
  • Select and highlight all the slots available for the first Monday (1) which is 28/09/2020
  • Right-click on the grid, click on 'Block Slots' (2)->'Block 3 Slots' (3)
  • This will reduce the available slots by 3 from each session on that particular day
  • Click on 'Save Changes' at the top of the screen




  • Once done, you should now have a deployment Unit that has been defined and you should be able to see the number of Slots available, Blocked slots, Slots used and Free slots
  • This completes the process of configuring the deployment unit based on the constraints given




Further Support

If you require further support, please visit ManagementStudio's Service Desk to search the knowledge base or create a new support ticket.