A couple of months ago, I first heard about the SharePoint Saturday UK event – not sure if it was through a tweet or an email. There have been a number of similar events around the world before, but this was the first in the UK.
http://www.sharepointsaturday.org/uk/default.aspx
I’m always interested in these types of events as they offer you the chance to learn new things, brush up on existing skills, and reinforce knowledge. It also offers the chance to network with other people in the industry, which I consider is always a useful exercise. On top of that, you often get the opportunity to speak with people that have highly specific knowledge of their topic.
SharePoint is a product that I have experimented with but purely for evaluation purposes. I believe that collaboration between staff is going to become a major initiative, and SharePoint is a tool that can really help bring people together and allow them to work more sensibly. I hoped that the event would enable to learn more about the latest iteration of the product and understand more about what it can do and what limitations it has.
The event was held at the Birmingham Hilton Metropole hotel at the NEC. This is a very nice location, quite central for most people (although a bit of a journey for me). The hotel had a lot of suitable resources and I think that it was a great location for the event. I should also add that the event was free to attend!
There were a really good mix of topics – some were quite technical, some were a bit more of a high level overview, so there was plenty for most people to get involved in. A couple even involved some demos of various issues which were really helpful. I particularly enjoyed the PowerShell administration demo by Penny Coventry; as I have been recently doing some work in this area, I was able to relate it to the stuff that I had been looking at, and had the chance to clarify a couple of small issues.
What was quite amazing was that the individuals organising and speaking at the event were doing so on their own time, and travelling to the event at their own expense. When you consider that a couple of them had travelled from the States, South Africa and further afield, this shows a particular level of dedication to the concept of passing on knowledge. Many other people have expressed their gratitude, and I think that I have to add my thanks as well; they certainly deserve high praise.
I also have to say that the buffet lunch provided was really excellent. I have to get the recipe for the Blue cheese, mascarpone and red onion quiche tartlets - they were really delicious and I must admit that I ate more than a few of them! Not good for the waistline, but for a one day event, very enjoyable indeed. My compliments to the chef!
Another big thank you has to go to the event sponsors; apart from paying for the whole day, they provided a large number of valuable prizes which were awarded at the end of the day. Among these were a Kindle, an iPad, an Xbox, about 70-80 books, t-shirts as well as some really valuable licences and training offers. There was almost enough on offer for most people to walk away with at least one bit of swag.
The day finished with SharePoint Saturday 2010 UK turning into SharePint; the chance for everyone to head for the bar. I carried out a completely unscientific study amongst a number of those present, and it was clear that everyone had had a great day; learned a lot, had the opportunity to see some really valuable demos and network with other like minded people.
If you missed the event and want the chance to see another, I would bookmark their web page and watch out for next year. I get the feeling that they hope that this can become an annual event. Certainly I wish them well; the work that was put in to organising it deserves the recognition, and I think that it could become a very valuable resource for anyone interested in learning more about an under rated piece of software.
Monday, 4 October 2010
Wednesday, 29 September 2010
The birth of a Third Platform
The BCS South West region hosts a number of events; I like to go along to these as they usually include some very interesting topics, but it’s also quite useful to network with other IT pros from different backgrounds.
At a recent event, there was a guest speaker from Apple; Lawrence Stephenson talking about “The Birth of a Third Platform”. He was discussing the rise in use of iPhones and iPads, particularly by students at schools or in University / Colleges and proposed that this is a new form of computing. Although primarily about higher education, much of what he discussed was also relevant to business.
The basic argument was that the mainframe systems were the first generation of computing, and the standard client / server technology that we have become used to, is the second generation. The third generation is therefore the use of mobile computing devices as access points to process or make use of data; hence the “third platform”.
He illustrated his talk with some interesting facts about the growth in the numbers of smartphones and tablet devices particularly among students. He also compared how these are used; to access email, social networking sites, general web browsing etc. He also identified that there were some were using their devices to access relevant items related to the student courses, but this was still a relatively small amount and that there was potential for growth in this area.
He demonstrated by showing some apps that had been developed for a university in the States; and these were clearly items that a student would find tremendously helpful, particularly for those new to university life, such as campus maps etc. All in all, a really good demonstration of just what can be done.
There was one very interesting comment though; he showed some statistics that could be used to suggest that most people actually use their device more for accessing data than they do for making phone calls. As such, there could be an argument for saying that it is quite possible than some future device might not actually have a phone capability as such; you would be more likely to contact people using IM or calls would be routed through an IP based utility such as Skype.
Of course, these types of devices are not new; tablets have been around for some 10 years. However, the advent of the smartphone has encouraged the development of small apps that allow people to do specific tasks really quickly and easily, and that has made a huge difference in the take up of people using mobile computing. As people have found new uses, it encourages more people to make use of them, and more developers to consider writing apps for specific requirements.
Most companies have “road maps” that give a structure to their research and development process and show the customer what they are working on for future products. Apple are a bit tight lipped about their vision for the future, so it is difficult to be certain about what they have in the pipeline. However, I would suggest that they (and many others) are working on the basis that there will be more people wanting to make use of mobile devices.
Who knows; maybe in the not too distant future, we won’t be using PCs any more, but will just do all of the work using a mobile device.
At a recent event, there was a guest speaker from Apple; Lawrence Stephenson talking about “The Birth of a Third Platform”. He was discussing the rise in use of iPhones and iPads, particularly by students at schools or in University / Colleges and proposed that this is a new form of computing. Although primarily about higher education, much of what he discussed was also relevant to business.
The basic argument was that the mainframe systems were the first generation of computing, and the standard client / server technology that we have become used to, is the second generation. The third generation is therefore the use of mobile computing devices as access points to process or make use of data; hence the “third platform”.
He illustrated his talk with some interesting facts about the growth in the numbers of smartphones and tablet devices particularly among students. He also compared how these are used; to access email, social networking sites, general web browsing etc. He also identified that there were some were using their devices to access relevant items related to the student courses, but this was still a relatively small amount and that there was potential for growth in this area.
He demonstrated by showing some apps that had been developed for a university in the States; and these were clearly items that a student would find tremendously helpful, particularly for those new to university life, such as campus maps etc. All in all, a really good demonstration of just what can be done.
There was one very interesting comment though; he showed some statistics that could be used to suggest that most people actually use their device more for accessing data than they do for making phone calls. As such, there could be an argument for saying that it is quite possible than some future device might not actually have a phone capability as such; you would be more likely to contact people using IM or calls would be routed through an IP based utility such as Skype.
Of course, these types of devices are not new; tablets have been around for some 10 years. However, the advent of the smartphone has encouraged the development of small apps that allow people to do specific tasks really quickly and easily, and that has made a huge difference in the take up of people using mobile computing. As people have found new uses, it encourages more people to make use of them, and more developers to consider writing apps for specific requirements.
Most companies have “road maps” that give a structure to their research and development process and show the customer what they are working on for future products. Apple are a bit tight lipped about their vision for the future, so it is difficult to be certain about what they have in the pipeline. However, I would suggest that they (and many others) are working on the basis that there will be more people wanting to make use of mobile devices.
Who knows; maybe in the not too distant future, we won’t be using PCs any more, but will just do all of the work using a mobile device.
Monday, 13 September 2010
Watch the pennies
..and the pounds look after themselves. So the old saying goes.
Yes it’s that time of year again; time to think about next year’s budget. Our company financial year runs from 1st Jan to 31st Dec. The FD needs to check it over and approve it and he needs some time to cook the books (sorry, prepare the COA), so we need to get budget plans drawn up a few months before December.
I tend to start by writing a list of the specific jobs that we intend to do, plans to replace major hardware such as UPS or servers, major software upgrades like the move to Windows XP a few years ago. It can also include work that we think we will be required to do; currently we are waiting for the go ahead on new offices and they will have to be cabled up. I try to get a quote so that we have a fair estimate of the cost.
We have a lot of specialist software for CAD drawings etc. and these have quite expensive support costs. Added to that is the support costs for CRM, ERP and so on. In some cases, I think that it would be useful if these were in a separate budget, but they are not so I just have to get on and deal with it. I also add in an amount for other software upgrades.
The next step is to think about smaller hardware purchases; monitors, disks, cables, replacement printers etc. I also consider consumables; toner cartridges, disks and batteries. I try to work out what we have bought / used in these areas, then use that as a benchmark for the next year.
We also need to plan for Business Continuity / Disaster Recovery. This requires that we keep some spare equipment, pay towards a BC / DR partner and take appropriate actions to make sure that we can be flexible enough (and secure enough) to put things into place at short notice to allow the company to deal with sudden problems.
Once all of these items have been assessed, I put them into a spreadsheet. I tend to leave details on the form so that the FD can verify it; the more detail the better as it saves him pestering me. It also means that he sees part of the justification for the spending which gives him confidence that I have thought things through.
In our case, I also try work out roughly what we are likely to spend on travelling to work at our other sites; hotel, mileage allowance, flights as appropriate. In addition, I also added an allowance for some training costs as we have had to learn a lot of new skills around our ERP system and the training is absolutely essential. As it happens, the FD generally accepts my figures (although he does occasionally make some changes to match his numbers).
After all that however, the big thing is to try to stick to the budget. Sometimes this is easier said than done. Generally, the smaller amounts are easier to offset within a budget. For example, someone managed to destroy a laptop a few years (he ran over it; he forgot to put it in the boot of his car!) and we needed to replace this at short notice. We could just put that down as a replacement and not worry about it.
However, it is also possible to get a requirement for much larger items – we had to buy an add on disk unit for a server which had not been budgeted for – not the end of the world, but it meant we had to be a bit careful about some other spending.
But all in all, it seems to work for us. The FD is happy, the MD is happy, the staff are generally supplied with what they need, when they need it. We get to manage things ourselves, which is a lot better than having to justify every single item of expenditure. I’ve seen places where this happens, and I would not like to have to be working under those conditions.
Yes it’s that time of year again; time to think about next year’s budget. Our company financial year runs from 1st Jan to 31st Dec. The FD needs to check it over and approve it and he needs some time to cook the books (sorry, prepare the COA), so we need to get budget plans drawn up a few months before December.
I tend to start by writing a list of the specific jobs that we intend to do, plans to replace major hardware such as UPS or servers, major software upgrades like the move to Windows XP a few years ago. It can also include work that we think we will be required to do; currently we are waiting for the go ahead on new offices and they will have to be cabled up. I try to get a quote so that we have a fair estimate of the cost.
We have a lot of specialist software for CAD drawings etc. and these have quite expensive support costs. Added to that is the support costs for CRM, ERP and so on. In some cases, I think that it would be useful if these were in a separate budget, but they are not so I just have to get on and deal with it. I also add in an amount for other software upgrades.
The next step is to think about smaller hardware purchases; monitors, disks, cables, replacement printers etc. I also consider consumables; toner cartridges, disks and batteries. I try to work out what we have bought / used in these areas, then use that as a benchmark for the next year.
We also need to plan for Business Continuity / Disaster Recovery. This requires that we keep some spare equipment, pay towards a BC / DR partner and take appropriate actions to make sure that we can be flexible enough (and secure enough) to put things into place at short notice to allow the company to deal with sudden problems.
Once all of these items have been assessed, I put them into a spreadsheet. I tend to leave details on the form so that the FD can verify it; the more detail the better as it saves him pestering me. It also means that he sees part of the justification for the spending which gives him confidence that I have thought things through.
In our case, I also try work out roughly what we are likely to spend on travelling to work at our other sites; hotel, mileage allowance, flights as appropriate. In addition, I also added an allowance for some training costs as we have had to learn a lot of new skills around our ERP system and the training is absolutely essential. As it happens, the FD generally accepts my figures (although he does occasionally make some changes to match his numbers).
After all that however, the big thing is to try to stick to the budget. Sometimes this is easier said than done. Generally, the smaller amounts are easier to offset within a budget. For example, someone managed to destroy a laptop a few years (he ran over it; he forgot to put it in the boot of his car!) and we needed to replace this at short notice. We could just put that down as a replacement and not worry about it.
However, it is also possible to get a requirement for much larger items – we had to buy an add on disk unit for a server which had not been budgeted for – not the end of the world, but it meant we had to be a bit careful about some other spending.
But all in all, it seems to work for us. The FD is happy, the MD is happy, the staff are generally supplied with what they need, when they need it. We get to manage things ourselves, which is a lot better than having to justify every single item of expenditure. I’ve seen places where this happens, and I would not like to have to be working under those conditions.
Friday, 3 September 2010
New Skillz
Occasionally, I think back to when I first started working with PCs in the late 80s.
At that stage, there were relatively few companies made use of these and it was very much a hobby, although one that I enjoyed. I managed to get hold of some second hand equipment and by trial and error, worked out what everything was and how it worked.
In the mid 90s, I had the chance to work with computers as a job; primarily in a customer support capacity, but I also looked after the company hardware, network and server (yes we only had the one). In those days, it was considered normal that someone working in IT would have a broad range of skills and be able to turn their hand to whatever task was needed.
But in the last 10 years, we have seen a major change in the way that things work. There has been a considerable need for people to become more focussed in a specific area, whether that be database administration, programming, networking, telecoms etc. In the very big companies, they even have teams of people within these disciplines.
For the smaller shops like ours, this makes life a bit harder. We only have a couple of staff, but we still need to provide the same level of support on the newer systems. There is still an expectation that each of the IT staff has all of the relevant knowledge to instantly know how a product works, what is causing a problem, and with a wave of the magic wand, can fix it.
In the real world of course, it is completely different. In most cases we have some good general knowledge of hardware and some good experience of using a couple of products. We’ve then developed particular skills in specific areas. For example, I have had to do a lot of work with SQL server over the last couple of years, and although I wouldn’t describe myself as a DBA, I have a pretty good understanding of it. I also have had advanced networking and routing training, as well as some extra work in security.
Among the staff, we have each developed key specific skills; and we can share the work out in a way that allows us to be most effective. As a small team, we work quite closely, so still get the opportunity to broaden our skills base, probably far more than those in larger teams would be able to do. But we still have to learn those new skills and there is no question that even within a team the size of ours, there is a definite division of labour based upon speciality.
There are of course many companies that suggest we should outsource some of the work: and I can see a certain value in that. But I have not yet seen any outsourcing operation that will provide the level of support at an acceptable price that meets what we currently provide. It’s also likely that if we did outsource part of the work we do all that would then happen is that the users / management would still insist that we try to fix things for them anyway, defeating the purpose of outsourcing.
So for the moment, we just have to try to learn as much as we can, as quickly as we can (and probably as cheaply as we can). I’m looking forward to the day when we can get the plug in brain nodes that allow us to download information directly into our brains, without the pain of going through the learning process!
At that stage, there were relatively few companies made use of these and it was very much a hobby, although one that I enjoyed. I managed to get hold of some second hand equipment and by trial and error, worked out what everything was and how it worked.
In the mid 90s, I had the chance to work with computers as a job; primarily in a customer support capacity, but I also looked after the company hardware, network and server (yes we only had the one). In those days, it was considered normal that someone working in IT would have a broad range of skills and be able to turn their hand to whatever task was needed.
But in the last 10 years, we have seen a major change in the way that things work. There has been a considerable need for people to become more focussed in a specific area, whether that be database administration, programming, networking, telecoms etc. In the very big companies, they even have teams of people within these disciplines.
For the smaller shops like ours, this makes life a bit harder. We only have a couple of staff, but we still need to provide the same level of support on the newer systems. There is still an expectation that each of the IT staff has all of the relevant knowledge to instantly know how a product works, what is causing a problem, and with a wave of the magic wand, can fix it.
In the real world of course, it is completely different. In most cases we have some good general knowledge of hardware and some good experience of using a couple of products. We’ve then developed particular skills in specific areas. For example, I have had to do a lot of work with SQL server over the last couple of years, and although I wouldn’t describe myself as a DBA, I have a pretty good understanding of it. I also have had advanced networking and routing training, as well as some extra work in security.
Among the staff, we have each developed key specific skills; and we can share the work out in a way that allows us to be most effective. As a small team, we work quite closely, so still get the opportunity to broaden our skills base, probably far more than those in larger teams would be able to do. But we still have to learn those new skills and there is no question that even within a team the size of ours, there is a definite division of labour based upon speciality.
There are of course many companies that suggest we should outsource some of the work: and I can see a certain value in that. But I have not yet seen any outsourcing operation that will provide the level of support at an acceptable price that meets what we currently provide. It’s also likely that if we did outsource part of the work we do all that would then happen is that the users / management would still insist that we try to fix things for them anyway, defeating the purpose of outsourcing.
So for the moment, we just have to try to learn as much as we can, as quickly as we can (and probably as cheaply as we can). I’m looking forward to the day when we can get the plug in brain nodes that allow us to download information directly into our brains, without the pain of going through the learning process!
Thursday, 26 August 2010
Cool!
Some years ago, we undertook a small experiment with our server room. We had heard that other people were reducing the amount of A/C cooling they used and we wanted to see if it was appropriate for us.
Like a lot of other places, our small server room was kept cool to keep the servers cool; if we were to spend any length of time in there, we would need to put on a jumper or even a fleece to stay warm, as the room was around 10 degrees centigrade. The A/C units were running non stop, and we wanted to see if we could reduce the electric we used.
Essentially, we made a load of measurements to get a base line. These included the core temperature of the UPS, some measurements of the servers and various places within the server room. We were fortunate that our engineering manager had a device that we could borrow for this as he was conducting a number of tests to help the company work towards ISO14001.
He also had a device that allowed us to measure the amount of power drawn by various devices – we seemed to get a couple of slightly odd readings, but when we discounted those, the average values appeared to match what would be expected. We therefore assumed that the errors we had were down to incorrect use.
Having got our base line values, we then started to increase the ambient temperature of the room, and examine what affect this had. Each time, we would leave the changed settings for a couple of weeks to see what would happen; in each case, there was no sign of distress on the servers, so we were able to increase the temperature again.
After some time, we found that the “sweet spot” was between 20 and 24 degrees centigrade. Above 24 degrees, we would see the fans in the servers starting to work much harder and draw more power. Below 20 degrees, the A/C was still running almost all the time. However, in that range, we found that we had the A/C unit running at its least power draw whilst the servers ran at a comfortable level.
We found that in the racks, we had a few “hot spots”; places where the temperature was quite a bit higher than the ambient temperature of the room. We were told that this is normal and generally considered a good thing; these create a thermal current that allows the cooling to happen naturally. The interesting thing was that although the ambient temperature increased by 12 degrees, the hot spots only increased by 3-4 degrees.
Part of the work meant that we had to make sure that the racks were properly positioned in the room to allow for adequate air flow, and the direction of air from the A/C also had to be optimised to prevent “air curtains” forming at various places. We also had to make sure that things such as blanking plates were used to ensure a properly controlled air current within the racks.
Although this all sounds very grand, the room is quite small and most of the work was done in between our normal activities. We were able to make use of some additional advice from the A/C supplier, but that was relatively minor. The total amount of work required was actually quite small, but the results have been very good. We have seen a reduction in power consumption of just under 50% for the server room as a whole – which translates into significant cost savings.
I’ve added a link to a resource that I would recommend to anyone wanting to do work on their server room facilities. It is primarily aimed at North America, but there are some bits that are specifically for the European market. It will take some time to go through all of it, but I consider that it would be time well spent.
http://www.schneider-electric.com/sites/corporate/en/products-services/training/energy-university/energy-university.page?tsk=77518T&pc=26947T&keycode=77518T&promocode=26947T&promo_key=26947T
The really good thing - we now have a server room that we can work in, in reasonable comfort all the time!
Like a lot of other places, our small server room was kept cool to keep the servers cool; if we were to spend any length of time in there, we would need to put on a jumper or even a fleece to stay warm, as the room was around 10 degrees centigrade. The A/C units were running non stop, and we wanted to see if we could reduce the electric we used.
Essentially, we made a load of measurements to get a base line. These included the core temperature of the UPS, some measurements of the servers and various places within the server room. We were fortunate that our engineering manager had a device that we could borrow for this as he was conducting a number of tests to help the company work towards ISO14001.
He also had a device that allowed us to measure the amount of power drawn by various devices – we seemed to get a couple of slightly odd readings, but when we discounted those, the average values appeared to match what would be expected. We therefore assumed that the errors we had were down to incorrect use.
Having got our base line values, we then started to increase the ambient temperature of the room, and examine what affect this had. Each time, we would leave the changed settings for a couple of weeks to see what would happen; in each case, there was no sign of distress on the servers, so we were able to increase the temperature again.
After some time, we found that the “sweet spot” was between 20 and 24 degrees centigrade. Above 24 degrees, we would see the fans in the servers starting to work much harder and draw more power. Below 20 degrees, the A/C was still running almost all the time. However, in that range, we found that we had the A/C unit running at its least power draw whilst the servers ran at a comfortable level.
We found that in the racks, we had a few “hot spots”; places where the temperature was quite a bit higher than the ambient temperature of the room. We were told that this is normal and generally considered a good thing; these create a thermal current that allows the cooling to happen naturally. The interesting thing was that although the ambient temperature increased by 12 degrees, the hot spots only increased by 3-4 degrees.
Part of the work meant that we had to make sure that the racks were properly positioned in the room to allow for adequate air flow, and the direction of air from the A/C also had to be optimised to prevent “air curtains” forming at various places. We also had to make sure that things such as blanking plates were used to ensure a properly controlled air current within the racks.
Although this all sounds very grand, the room is quite small and most of the work was done in between our normal activities. We were able to make use of some additional advice from the A/C supplier, but that was relatively minor. The total amount of work required was actually quite small, but the results have been very good. We have seen a reduction in power consumption of just under 50% for the server room as a whole – which translates into significant cost savings.
I’ve added a link to a resource that I would recommend to anyone wanting to do work on their server room facilities. It is primarily aimed at North America, but there are some bits that are specifically for the European market. It will take some time to go through all of it, but I consider that it would be time well spent.
http://www.schneider-electric.com/sites/corporate/en/products-services/training/energy-university/energy-university.page?tsk=77518T&pc=26947T&keycode=77518T&promocode=26947T&promo_key=26947T
The really good thing - we now have a server room that we can work in, in reasonable comfort all the time!
Tuesday, 24 August 2010
I'm back!
It's been a while since I posted anything; 6 months in fact. It's not a case of having nothing to write about, far from it. I've just been very busy, plus I've been a bit more active in other areas.
One thing that I thought would be appropriate to point out is a Microsoft resource at: http://www.microsoft.com/uk/business/peopleready/technology/ioassessment/osyci/survey.mspx
This allows you to take a "survey" that can give you an indication of the status of your IT provision. I first came across this a while back and I found it very useful as part of the planning process. In order for you to reach a particular destination, it helps to know where you are starting from, so you can use the right directions.
Essentially, Microsoft suggest that IT departments can be classified into one of 4 levels based upon standard practice. Five years ago, we would have definitely been classed as being at the lowest level, "reactive". The IT provision was based around fixing problems after they occurred and very little thought went into planning or preparation.
We've slowly moved through the various stages, going from "standardised" to "rationalised", and are now pretty much at the top level, "strategic". There are still a few areas that we could improve upon, but that will always be the case. However, the IT is now a solid platform that people can use. We don't get the network failures, system crashes, or data losses that used to occur. Resources are there and available 24 x 365 for people to use, and generally they can access them using whatever device is appropriate.
Now although this all sounds great, there is unfortunately a fly in the ointment. The biggest problem is still the unit that is positioned between the chair and keyboard! It has been identified that we need to get people better trained, but somehow that never seems to get translated into action. Once of the worst instances was of a person that had been with the company for some 8 years. Unable to logon, the person phoned the helpdesk to ask what her user name was! (She normally didn't have to type that in, as it just appeared in the login box.)
I would encourage everyone to take a look at the Microsoft Core Infrastructure Optimisation resource. I think that you'll find it of significant value and help.
One thing that I thought would be appropriate to point out is a Microsoft resource at: http://www.microsoft.com/uk/business/peopleready/technology/ioassessment/osyci/survey.mspx
This allows you to take a "survey" that can give you an indication of the status of your IT provision. I first came across this a while back and I found it very useful as part of the planning process. In order for you to reach a particular destination, it helps to know where you are starting from, so you can use the right directions.
Essentially, Microsoft suggest that IT departments can be classified into one of 4 levels based upon standard practice. Five years ago, we would have definitely been classed as being at the lowest level, "reactive". The IT provision was based around fixing problems after they occurred and very little thought went into planning or preparation.
We've slowly moved through the various stages, going from "standardised" to "rationalised", and are now pretty much at the top level, "strategic". There are still a few areas that we could improve upon, but that will always be the case. However, the IT is now a solid platform that people can use. We don't get the network failures, system crashes, or data losses that used to occur. Resources are there and available 24 x 365 for people to use, and generally they can access them using whatever device is appropriate.
Now although this all sounds great, there is unfortunately a fly in the ointment. The biggest problem is still the unit that is positioned between the chair and keyboard! It has been identified that we need to get people better trained, but somehow that never seems to get translated into action. Once of the worst instances was of a person that had been with the company for some 8 years. Unable to logon, the person phoned the helpdesk to ask what her user name was! (She normally didn't have to type that in, as it just appeared in the login box.)
I would encourage everyone to take a look at the Microsoft Core Infrastructure Optimisation resource. I think that you'll find it of significant value and help.
Friday, 12 February 2010
BCS - Computer Forensics
For some time, I've been working towards a post graduate degree through the Open University. It's hard work, particular after a long day when all you want to do is switch off and relax. However, I find the courses fascinating and of help to me in my daily work, so I keep on working on it.
The last course I did was particularly interesting - Computer Forensics and Digital Examinations. This is a very technical issue, but it also requires an understanding of legal procedures. It isn't enough to say "I found so and so", you have to demonstrate that the evidence is relevant, accurate, consistent and to present it in a way that non-technical people can understand it. I found it all really interesting, if not totally linked to my daily job.
So when the BCS South West indicated that they were holding an evening event and the topic was Computer Forensics, I jumped at the chance to attend. It was at the University of Plymouth, which is a really nice venue, if a little bit of a trek to get to from where I live. The speaker was a visiting professor, John Haggerty from Manchester and the presentation was lively and informative. The actual notes should be available at this link. http://www.bcssouthwest.org.uk/server.asp?page=pastevents
For me, the presentation covered most of the items that I has previously studied and it was really good to refresh my memory. It was also interesting to see that after such a short time since I did my course, there are a number of changes that have occured and the discussion after the talk highlighted some of the issues facing practitioners in that field.
One thing that is of interest - Digital Forensics is a field that is wide open for people to move into. However, there are a lot of people that think just because they have a small amount of experience in running a computer, they think they know what to do to examine it. Professor Haggerty referred to this as the "CSI" affect - people see the TV shows where someone drives an expensive car, goes to a pristine work space and in half an hour recovers all the require information to solve the case (and the impossibly attractive woman is suitably impressed by the display of brain power!).
In reality, Forensics is a long tedious job. Everything has to be documented, step by step and assumptions made have to be justified. There are a number of practioners that have had their reputations destroyed by a simple mistake, and once that happens, they are unlikely to be able to work in the field again.
As the technology moves on, the process of the examination gets harder - I can remember when I bought my first hard drive of 20 MB and I wondered how I would ever fill it up. I now regularly work with physical hard drives of 500 GB and logical partitions of over 1 TB. To properly analyse and document such a drive can take a very long time and new tools are being developed to try to make the analysis easier, but it still requires considerable patience.
But all in all, a great evening - a fascinating topic, well presented. An dfor those IT people that think the BCS is only for academics, I would strongly suggest that you go along to one of the (free) events - I'm sure that you'll change your mind.
The last course I did was particularly interesting - Computer Forensics and Digital Examinations. This is a very technical issue, but it also requires an understanding of legal procedures. It isn't enough to say "I found so and so", you have to demonstrate that the evidence is relevant, accurate, consistent and to present it in a way that non-technical people can understand it. I found it all really interesting, if not totally linked to my daily job.
So when the BCS South West indicated that they were holding an evening event and the topic was Computer Forensics, I jumped at the chance to attend. It was at the University of Plymouth, which is a really nice venue, if a little bit of a trek to get to from where I live. The speaker was a visiting professor, John Haggerty from Manchester and the presentation was lively and informative. The actual notes should be available at this link. http://www.bcssouthwest.org.uk/server.asp?page=pastevents
For me, the presentation covered most of the items that I has previously studied and it was really good to refresh my memory. It was also interesting to see that after such a short time since I did my course, there are a number of changes that have occured and the discussion after the talk highlighted some of the issues facing practitioners in that field.
One thing that is of interest - Digital Forensics is a field that is wide open for people to move into. However, there are a lot of people that think just because they have a small amount of experience in running a computer, they think they know what to do to examine it. Professor Haggerty referred to this as the "CSI" affect - people see the TV shows where someone drives an expensive car, goes to a pristine work space and in half an hour recovers all the require information to solve the case (and the impossibly attractive woman is suitably impressed by the display of brain power!).
In reality, Forensics is a long tedious job. Everything has to be documented, step by step and assumptions made have to be justified. There are a number of practioners that have had their reputations destroyed by a simple mistake, and once that happens, they are unlikely to be able to work in the field again.
As the technology moves on, the process of the examination gets harder - I can remember when I bought my first hard drive of 20 MB and I wondered how I would ever fill it up. I now regularly work with physical hard drives of 500 GB and logical partitions of over 1 TB. To properly analyse and document such a drive can take a very long time and new tools are being developed to try to make the analysis easier, but it still requires considerable patience.
But all in all, a great evening - a fascinating topic, well presented. An dfor those IT people that think the BCS is only for academics, I would strongly suggest that you go along to one of the (free) events - I'm sure that you'll change your mind.
Subscribe to:
Posts (Atom)
