So a friend and I were discussing various things, and it came round to how we all give labels to various things.  My point was that we give labels to groups of people, and as soon as we encounter a person of the demographic we have ascribed to the label, we automatically reduce that person to that lable, rather than treating them as a human being..  Think about it.  Cyclist, activist, Audi driver, emo, gay, straight, parent.  Each of those is a descriptive term that we ascribe to people all the time.  ANd as soon as they are associated, Jassen is a cyclist, Steve is a runner, Lisa is emo.  We become the lables, which makes discrimination more palatable.

I’m as guilty of this as anyone.  As a cyclist I have a conviction that Taxi drivers think they own the road and Bus drivers are on a mission to crush me against trams / kerbs.  Also that drivers of expensive German cars seem to neglect the indicators option when they purchase the vehicle.

The problem is that we are too quick to apply labels, and we need to stop doing so and recognise that human beings are responsible for these actions, including our own.

There is more to say, but the ideas are bouncing around too much.

The point here is ignore the lables.   Black, White, rocker, emo, trumpist, tory, nat, we’re all still people.  Be excellent to each other


How many times have you looked at an Audi and classified the driver as an ‘Audi Driver’  Where Audi driver extols a certain wankerish badge, and implies that the car indicators will not work.


How many times have the car drivers complained about bloody cyclists?  How many times have they got in your way, moving out into the middle of the road, how many times have you ‘buzzed’ them.  How many times have you swore at the cyclists who jump a red light?


I’m a cyclist.  Actually I’m not, saying I’m a cyclist is perpetuating a problem on the UK roads.  Car drivers seem to feel that cyclists are foxes and deserved to be hunted down.


Actually that’s not fair, here I’m perpetuating the issue I’m trying to identify and stop.  Car drivers are still human beings, as are cyclists.  We are all living beings sharing a small piece of (in Edinburgh rutted) tarmac and we should all treat each other with a certain respect.  We are all humans in different forms of metal / carbon cages.  Please look out for each other, cos we’re all fucked if we don’t



Well here l sit once more bereft of inspiration trying to write something. And started thinking, how can I overcome this roadblock to creativity, this annoying wall placed between my mind and This tablet PC?

After the normal procrastination, Making tear coffee & walking the dog or the kids, what’s left to distract the budding writers psyche into writing rather than the avoidance of writing? A newly discovered handwriting recognition function on the tablet, a word press windows 8 application and an I.D& Password combination remembered.


So welcome readers all & thanks for sticking with this nonsense exercise which will allow me to write something a bit more meaningful now that the muse has had her starter motor primed.

And so the world loses a hero.

The new depiction of Lance Armstrong as a serial drug pusher and no longer great of sport is a real shame for those mere mortals who are seeking some form of inspiration.  Who could not have been inspired by the story of the man who fought one of the most insidious conditions of our time, and not only beat it, but was able to then conquer one of the worlds most gruelling and toughest sporting events and win another Tour De France?

Who could not be inspired by the man who since beating cancer has managed to raise $400 Million US to help in the fight against cancer?  I really hope that no matter what happens to the man, the Livestrong brand does not get collateral damage.

Lance Armstrong was one person I used as inspiration when I was recovering from my operation, if he can recover from something far worse, in such a positive way, then surely I can do it as well.  I would rather remember that Lance rather than the one the US Anti doping agency has uncovered.  Unfortunately, the genie is out of the bottle, and that is such a shame for the world, as now we have lost one of the greatest stories of overcoming adversity to performance enhancing drugs.

Well the pools nice and clean and the kids have started going in, bloody mad things.  It’s getting near time that I start trying to lose the weight that stopping smoking has put on.  Now to get the mind into gear and start the excercise program once more.  The spiders that have made their homes in the multigym and rowing machine won’t be happy but they’ll just have to deal with it

Why is it that people still confuse what role a Problem Manager should perform within an ITIL based service provision?

Problem management has it’s fingers in lots of pies when it comes to IT service provision, but most organisations I’ve seen seem to think that it’s either Enhanced incident management, or major incident management.

Problem management is neither.  Firstly Incident management is all about restoring service to the client in the shortest time possible.  BSOD – Restart.  Service restored, incident closed.  Problem management should only come into this scenario when there is a pattern to these incidents.  The service desk still resolves the incidents via the reboot workaround, while in the background the PM team is working away with whatever tech resources to identify the cause, and implement the fix to stop the incidents.  As my TL used to say, Service Desk fight the battles, we fight the wars.

Major incidents is another area where, in my view Service Desk managers mistakenly see value from Problem Management.  PM absolutley has a role in the MI process, but it should not be the first port of call for co-ordination of the incident.  To do so removes the effectiveness of the PM function, by pulling them away from managing problems, possibly including the ones which lie at the cause of the current MI.  This is counter productive, but most organisations will not have budgeted to have the capacity to have a dedicated Major Incident team / Manager, and removing staff from the front line service desk to perform the co-ordination and communication work is often not feasable.  This is why in most cases, Major incidents end up in the remit of the problem management function.  1 long running MI can in effect take 1 team member out for the entire lifecycle of the incident, meaning that all that Problem management work has now exceeded timelines / SLA.  And all the while the MI is going on and the comms have gone out to manage the flow of inbound calls regarding it, the Service desk are still dealing with incidents which probably would have had a resolution had the PM team not been diverted.

I have no idea where I was going with this post, really was a stream of conciousness thing.  I’ve probably failed to make any point successfully, and if you’ve read this far, well done.

Well sat down and watched Source code last night, expecting a fairly mindless Hollywood flick, and to that end it didn’t disappoint. However there are a couple of things about that film that are really bugging me

1. What happened to the teachers personality? If the captain is in his body where did he disappear to?

2. Why on earth didn’t they end the film at the freeze frame. I think that would have made for a much better and thought provoking ending than the vomit inducing saccharine that the director served up to us

All I can say is thank god I don’t have to watch that again

Well we had an issue where the Package share was fine, but the pkgsrg folder was on a drive that was trying to be all things to all men, and started filling up when we started sending packages down to the secondary sites.  Even though there had been the NO_SMS_ON_DRIVE.SMS file placed on the drives, and the actual package share was correctly configured, SCCM was still sending the compressed packages to this drive.  Unfortunately these Secondary site servers also provided print, domain controller, SQL, and Backups as well as having the Windows page file on this exact drive, so as can be expected, people were less than happy, and it was one of the few times where there was a system issue that was caused by SCCM.

The fix was very straightforward.

Firstly In each site, open Computer Configuration, and change the software deployment settings to point at the drive you want to. (Note the drive has to be specified complete with colon and slash e.g. C:\, D:\)

Check the site messages – you should see one for SMS_SITE_CONTROL_Manager submitted a copy nnnn of the actual site control file .

Test with a small deployment package.

Doing this not only means that new packages will use the specified drive, when older packages have their DP’s  updated they will now have their compressed files moved to the new drive, so be careful when updating large older packages across slow links.

Depending on the number of secondaries / packages you could update the DP’s on all the packages, and let SCCM move them, then delete the contents of the old PKGSRC folder.  That all depends on how practical it is in the particular environment.

Note this is from my own experience, and is in no way guaranteed.

Got this from one of the mailing lists I subscribe to.  Geeky, yes, nerdy, oh hell yes.  But I like it

Make your computer speak using Powershell

Add-Type -AssemblyName System.Speech

$synthesizer = New-Object -TypeName System.Speech.Synthesis.SpeechSynthesizer
$synthesizer.Speak(‘Hey dingus, What the hell did you press that key for!’)