hello there!
after a particularly shoddy morning in the office i'm curious to learn how your support organisation is structured.
do you have a skilled service desk who actually understand:
what a computing environment is,
the basics of what a client is, what a server is,
how to check whether a network point is patched in,
that a machine needs an ip address to communicate on a tcp/ip network,
how a client gets said address,
knows the basics of how email works,
understands that to be able to get to a website you need to be able to resolve a name to an ip address,
understands that if an application on a *single* users pc halts with a fatal exception error but they are still logged into ldap, can access email, the internet etc that it's likely to be an issue that a) a reboot will fix and b) that the specialised team of people who troubleshoot dynamic routing protocols for a living really dont care about,
etc...
i.e. are they capable of what i would probably term first/second line support? or rather:
asking the right questions to eliminate stupidity before escalating the call up the support chain.
and then do you then have further teams of more specialised people? such as:
server people who look after ldap, file/print, dns, dhcp...
network people who look after cabling, switches, routers, leased lines...
security people who look after firewalls, authentication servers, remote access... etc
do you have proper procedures and processes for troubleshooting common issues? a knowledge base? a list of who looks after what? a defined escalation procedure? system owners who are responsible and accountable for stuff?
answers on a postcard!
after a particularly shoddy morning in the office i'm curious to learn how your support organisation is structured.
do you have a skilled service desk who actually understand:
what a computing environment is,
the basics of what a client is, what a server is,
how to check whether a network point is patched in,
that a machine needs an ip address to communicate on a tcp/ip network,
how a client gets said address,
knows the basics of how email works,
understands that to be able to get to a website you need to be able to resolve a name to an ip address,
understands that if an application on a *single* users pc halts with a fatal exception error but they are still logged into ldap, can access email, the internet etc that it's likely to be an issue that a) a reboot will fix and b) that the specialised team of people who troubleshoot dynamic routing protocols for a living really dont care about,
etc...
i.e. are they capable of what i would probably term first/second line support? or rather:
asking the right questions to eliminate stupidity before escalating the call up the support chain.
and then do you then have further teams of more specialised people? such as:
server people who look after ldap, file/print, dns, dhcp...
network people who look after cabling, switches, routers, leased lines...
security people who look after firewalls, authentication servers, remote access... etc
do you have proper procedures and processes for troubleshooting common issues? a knowledge base? a list of who looks after what? a defined escalation procedure? system owners who are responsible and accountable for stuff?
answers on a postcard!