|
Bravo Policies & Protocols
on Remote Access April 2, 2003
Background Info:
- Standard corporate policy: Workstations are
left on, or implement Wake-on-LAN (WOL). IT admins have
standing authorization and access during
after-hours.
- Some smaller firms have a policy of shutting
down workstations at end-of-day, and don't have WOL. Ad hoc
scheduling for admin access is required.
- By default, IT has implicit access to
dedicated servers. Access to workstations might require explicit
requests/authorizations, depending on management preferences.
Remote Access Policies & Protocols:
- Remotely administered tasks are billed
according to remote rates & policies―typically,
a hybrid of flat fee tasks (where applicable) and
reduced hourly rates, as they're done on a flexible scheduling,
resources-permitting and low-priority basis.
- The 1-time authorized block of access time
represents best-efforts appointment, subject to postponement, unless client specifically request
high priority, and incur the extra costs at standard rates.
- To commence access outside of pre-authorized
time frame, a new request for authorization will be made. For continuing
beyond authorized time, there's generally no additional notification (to
minimize disturbance). I
will be reachable by phone/IM during that period.
- If I access during authorized time, and
collide with you, I'll assume you either forgot about our appointment,
or something urgent just came up and you needed your system. I will immediately
yield the system to you. I expect you to recognize that and call me
back as soon as you're finished so that I may proceed as planned. If I
don't hear from you within a reasonable time, I'll contact you to make
arrangement. (see checklist below for
details)
|
Workstation Access Collision
Checklist:
- in the event of collision, I will
- recognize it (as
I'm always on the look out for that)
- immediately yield to
your usage, in case you have some urgent tasks
- as a courtesy, defer calling, to
avoid stress while you tend to urgent tasks
- unless I deem it critical, due to the nature
of my task-in-progress
- you should recognize the collision
- as indicated by obvious signs of me
in the midst of something, or
- interrupted by
our inadvertent "fight" for the session (once/twice)
- see mouse/key activities (if
administered via PCA, VNC, Bravo RMx)
- you should finish your quick tasks and
- call me to resume,
or
- to reschedule,
should you intend to work at length
- I'll call you if I don't hear from you
within a reasonable period
Keep in mind: I might not immediately
notice your "grab" as I could be in an unattended phase,
where I initiated the process and walked away, had yet to
check back on its progress/outcomes.
|
See also:
|
