Would like to get these wrapped up and to Jeff Truelsen by 2/24
Bomgar processes documentation progress and schedule
Process | Start | Target | Complete | Owner | Notes |
---|---|---|---|---|---|
Main Procedure | 2/8 | 2/22 |
| Dan/Tony | Attached updated version from Dan below. |
Jump | 2/8 | 2/17 | Dan/Tony |
| |
Provisioning | 1/31 | 2/23 |
| Chuck/Dan | |
FAQS | 2/9 | 2/22 | Chuck/Dan/Tony | ||
Script/Dialog | 2/15 | 2/21 | Chuck/Dan | Conversation to have with the user to walk them through getting Bomgar running. See "Bomgar sample dialog.docx" below. |
Reference Links
- http://www.it.cornell.edu/services/bomgar/ - Customer facing pages on IT@Cornell
- ITSM Process Confluence Page
- ITSM Process Confluence Page, final repository for completed Bomgar processes
- Chuck Boeheim's Provisioning Confluence Page
- Bomgar Training
- Bomgar Documentation Library
- Bomgar Overview of the Representative Console
- Bomgar, Introduction to the Representative Console
- Bomgar Session Start Options
- Bomgar Support Session Overview
- Bomgar Screen Sharing
- Bomgar File Transfer
- Bomgar System Information
- Bomgar Command Line
- Bomgar Presentation
- Bomgar Rep Invite
- Bomgar Customer Client Page - nice info on how to customize the Bomgar end user experience
Jump Clients
- Bomgar Jump Clients - general information
- Bomgar Using Jump Clients - Control Unattended Computers with Jump Clients video and transcript
- Bomgar The Jump Clients Page - mass deployment information
- Bomgar Manage and Deploy Jump Clients - more info on mass deployment from the administrative interface
- Bomgar Jump Technology Index Page - has links to most all things Jump Client
Meeting Notes
16 Comments
Tony Lombardo
Dan - feel free to add any comments you want as we iterate through these documents! Also, you can "watch this page to get any updates via email if you want.
Tony Lombardo
I just attached the latest versions of the main process Visio swim lane diagram. I added a tab for the jump client, pleases note the tabs at the bottom of the Visio diagram! The process steps in the diagram are the basic ones, but I think they are logically accurate and make sense. I broke the process out into 4 areas, start, initiating the remote session, incident resolution and the jump client. Each should be self contained so that any changes that might be needed affect only that section without affecting the others.
My next steps will be to flesh out the Bomgar Service Desk procedure document.
Dan, I know you have a lot going on but when you get a chance take a look at the swim lane document and give me your feedback.
Thanks!
Tony
Tony Lombardo
Dan, I took your change suggestions to the swim lane Visio diagram and incorporated them. I've up loaded it to the site. Whew! I believe it came out clearer, take a look - I was afraid my thinking was getting a little circular! There are now 5 tabs, Start, Session, Resolution, Transfer and Jump Client - but I think it makes sense!
Thanks Dan!
Tony
Dan Elswit
Tony - Swimlane is looking better all the time. A couple of clarifications... First, between 304 and 305 I think we need one more decision diamond for "will the user grant admin rights?". On the C - Transfer one, I think 400 should be "Click Transfer", leading straight to 401. Otherwise it doesn't seem like you'd ever get to that branch at all. Then 403 goes away entirely. I've been experiementing with transferring and at the present time anyway, there is no user assent required to transfer the session to someone else. I thought there was at one point. I'll verify with Chuck. Lastly, 406... normally you wouldn't hold the session. You work it until it's done. If you or the user need to go off and do something else (and in the case of the user, if there's no jump client) you would put it on hold.
Other than that, looks fantastic!
--Dan
Tony Lombardo
Hi Dan. OK, so I made the changes to the swim lane diagram you mention above. However, I left the initial 400 decision block. Mainly because in case someone got to that section by accident, they'd be directed back to the resolution section. I did the renumbering too, so let me know if it still makes sense!
Thanks Dan!
Tony
Tony Lombardo
During our check in the morning Dan mentioned that the security office would like to see a process around the transfer to another technician. This is covered in the swim lane diagram and we discussed putting additional detail in the main procedure document.
Dan Elswit
I'm realizing that we need a standard set of information for unit IT leadership in order that they understand the decisions they need to make, particularly regarding the Jump client. I'll draft something along those lines and send it along to you.
Tony Lombardo
Sounds good - I'm making progress on the main procedure draft as well.
Tony Lombardo
Sigh. I updated a bunch of the content on the main procedure, BomgarServiceDeskProcedure.dox - it's making my eyes blurry! I'm trying to cross reference what is in the "Bomgar sample dialog.docx" the "Remote Assistance Communication.docx" the "Information_Technology_Process_Swimlane_Bomgar.vsd" and information fro mthe Bomgar documentation into one coherent procedure document. I've made progress, but it's still not quite where I'd like it to be.
Tony Lombardo
PS - I added more stuff to the FAQs as I came across it too.
Joanne Button
Please correct "Bombar" to "Bomgar" in several instances in the Bomgar Service Desk procedure document.
Joanne Button,
Bomgar Infrastructure, 255-6622
Tony Lombardo
OK thanks.
Tony Lombardo
Joanne, did you mean the "BomgarServiceDeskProcedure.docx" document? I searched the entire document and didn't get any hits on Bombar. At least in the most current version.
Joanne Button
Hi Tony,
Yes, the instances of "Bombar" are in the BomgarServiceDeskProdedure.docx" file. It looks as if you would not find them in the text because they are text inside your images on pages 4, 5, 7, 8 and 9.
Joanne Button
255-6622
Tony Lombardo
OK, got it. I changed the swim lane diagram as well as the images in the "BomgarServiceDeskProdedure.docx" file. Thanks!
Joanne Button
If the ujumptechnology.pdf file is used, it should be with a note that the Jump Point technology is turned off in our instance. Only jump clients, the second half of the document are available.
Joanne Button