Deployment Unit Schedule Config - Scenario B

Modified on Tue, 18 Jan 2022 at 12:49 PM

TABLE OF CONTENTS

Scenario B


As a Project Administrator, you have been tasked with migrating all the users currently based in the Birmingham 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
  • Saturdays should have 5 one-hour slots @ 10:00
  • The second Monday is a non-working day 


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 (Birmingham) on the grid to open the details panel
  • Define the deployment unit’s 'Start date and End date' (1). This should be over a 3-week period. The screenshot below shows it starts at 9:00 hrs on the 14/09/20 and finishes on Friday 02/10/2020 at 18:00 hrs
  • 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
  • Within the Switch Global/Local Schedule, ensure the checkbox ‘Yes, I’m sure’ (3) is ticked
  • Click on ‘Switch’ (4) to confirm the 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
    • Saturdays should have 5 one-hour slots @ 10:00
    • The second Monday is a non-working day 
  • Click on ‘Click here to add new item’ (1)
  • Define the Start time, End time, Migration Slots and the days of the week (2)
  • During the 3 weeks deployment, we have 5 one hour slots on Saturday 19th and 26th. This has been defined by entering the valid from/to dates and also selecting just Saturday (3)
  • Click ‘Save Changes’ (4) to commit the changes


  • We also understand that during the 3-week period, the second Monday is a non-working day, which according to the calendar is the 28/09/2020. This needs to be defined within the Suspended days section.
  • Click on ‘Click here to add new item’ (1)
  • Populate the date and the corresponding note (2)
  • Click ‘Save Changes’ (3) to commit the changes


  •  Once done, you should be able to see the number of Slots available, Blocked slots, Slots used and Free slots at the bottom of the Slot Utilisation grid.
  • 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.