Microsoft Onboarding Crate: 2 Specific Issues [Check User Exists, Office Location]
C
Confident Opossum
My company is now experiencing CSAT issues due to the Crate:
1st: Due to how the conditions are handled for the "Check If User Exists" sub-workflow built into the form - if an AD server is unreachable by the powershell flow - a CTX.user_info.output == "Task Expired" (Timeout) resolves into a message "User Exists" message on the form - causing our techs to back out and do it manually because they are being told the user they are creating already exists. The form should not accept that as a false positive - as checking manually is still time savings.
2nd: It appears that there are no fields to populate the "Office" field in a user's AD attributes from the Crate Form. I can see that there is a variable assignment before running power shell, but that value cannot be added since there is no genesis for a value. It would be excellent if we can fill this out through the form instead of having one single field to update on a perfect run.
Log In
E
Eburnean Cardinal
I do remember having the same issue with the Does User Exist form field sub-workflow I ended up just cutting it from the form and replacing it with a static string saying it does exist every time and modifying the create new ad user template in Rewst to failover to next available username_format.
That being said, it stopped being an issue after I deployed Agent Smith to the hybrid/sync'd client Domain Controllers... as the timeout is a Datto RMM issue, due to the quick jobs in Datto RMM having a subjective definition of the word quick. So I resync'd the onboarding form as the subworkflow would be complete usually by the time the engineer had filled in the users first & lastname