Purpose: To train anyone who may need to use immyBot on how to perform this function
---
Scope:
Section titled “Scope:”Service Desk
---
Responsibility:
Section titled “Responsibility:”Provisioning owns ImmyBot and its documentation
---
Completion Criteria:
Section titled “Completion Criteria:”Successful Deployment setup within ImmyBot
---
Records:
Section titled “Records:”Halo and ImmyBot itself
---
Steps:
Section titled “Steps:”- Concept: ImmyBot presents the conceptual idea and layout below with a labeled and color-coated chart demonstrating each section’s meaning
- Navigate to the Library section of the sidebar within Immy.Bot
- Use the search bar in the expanded view to find a piece of software that you would like to deploy
- In this instance, we are selecting and deploying the Microsot 365 Apps for Business package. Most clients utilize this version of Office, however, I’m going to contain this deployment to a single tenant to avoid mistakes.
-
You will see configuration items for each application deployment, some more than others. Take great care in ensuring that these configuration items do not impact users or base program functionality unless specified by the work Instruction for that particular client, the VITM or a specific request.
-
We should build deployments to be as generic and broadly applicaccable as possible.
-
Ensure that your new deployment is targeting “All Computers”, “Workstations and portables”, and check the “Onboarding Only” box so that no current system has its software overwritten.
-
This should be your generic template for all new deployments. Custimize and tweak as needed. You can easily delete, duplicate, and test deployments.
-
An example of Adstra’s deployment profile
- Each item can be configured and specifically tailored to the neds of each client. Feel free to test things, just ensure that the final output is aligned wit the Client Work Instruction
--- ### Process References:
1. Create a relationship back to a related process.
KB00038353
CentrexIT CI: Immy.Bot