I start the shell type Powershell.exe and POW! I have a fully working Powershell session, with all my modules. I jump over to the Bomgar command shell not expecting Powershell to actually work. This is where Bomgar saved me, I could connect to my machine just not log in. I jump onto my PC at work using Bomgar as I do, but this time for whatever reason I couldnt access it, for the life of me the pc wasnt accepting my password.
I’m using a Mac, therefore using Powershell was out the question. I know I can use the web console in O365 to perform the migration but I also had to bulk add permission to the migrated mailboxes. I usually do this by a series of scripts.
I had to access my PC at work to perform some Office 365 migrations (because I left my work laptop at work).
What I had never really paid attention to was the interactive command shell that Bomgar also has, why would I need to? The only time I use it I have full access to the PC/Mac anyway! This is all pretty standard for remote support clients. Namely, working remotely off my personal computer. These are clients and are constant in the support console, I use this to access my pc at work, should for whatever reason I need to. Once a support session has started I can then take full control and if I elevate Bomgar’s privilages I can interact with UAC prompts. For me its a great remote support tool, requires no installation on the part of the user I can just point them to our support site and they click my name.