|
Case Study - 'Nimble Designs' vs 'Donkey Studios'
|
Scenario 3 - Addition of SSH access
An existing customer, 'Elite Skills Agency', has taken on a new IT manager. He requests that he be given SSH (secure shell) access to the website so that he can conduct 'necessary modifications via the commandline'.
|
Bob Nimble (Reseller Hosting)
|
- Bob loads the WHM web-based interface.
- He clicks 'Modify an Account'
- He selects the 'eliteskills.co.uk' account.
- He ticks the 'Shell Access' box.
- He clicks 'Save'.
- SSH access is now active.
Bob passes the login details along to the IT manager (who upon receiving them, strokes his beard thoughtfully, cracks his knuckles and quotes 'A keyboard! How quaint!' before getting down to work).
|
|
Time spent: 2 minutes. | Additional cost: Nothing
|
|
|
Dave Donkey (Conventional Third Party Hosting) |
|
Dave sends a support request to 'Company A' requesting that SSH access be made active for the account 'eliteskills.co.uk'. 24 hours later, they e-mail him telling him that they cannot comply with his request - not even for a £20 one-off fee - due to security concerns.
Dave makes the mistake of passing this information along to the IT Manager who requested the change. Furious that he will be unable to exercise his keyboard fingers, the IT Manager declares that he will have to review Dave's hosting contract as part of his inaugral systems audit.
Dave must now either attempt moving the account to another hosting company that supports SSH access, with all of the associated re-configuration work and risks of Scenario 2 or lose the busines of his customer.
|
|
|
Either:
|
|
Time spent: 4+ days |
Additional cost: 0
|
|
Or:
|
|
Time spent: 24 hours |
Additional cost: The value of one client lost.
|
[ Prev | 1 | 2 | 3 | Conclusion | Next... ]
