I often find in a number of organisations people are unclear about the differences between the different roles (EA, SA, TA) so I thought I would put together a very simple poster to demonstrate the differences. I’ve put together the image and PDF version. I hope people find this useful, I’m thinking I might do a whole series on IT architecture from conception to implementation.
So I read a lot of analyst blogs and CIO top priority lists/predictions etc.
Sometimes what I struggle with is the idea that we as humans progress at anywhere near the rate of technological change. To give an example, I was at MS TVP for a partner Server 2012 launch event where we discussing cloud private/hybrid/public and the features, benefits and impacts this could have on our customers. I raised a question “considering how advanced technology used to be and how it is even greater these days, what do we do about the fact that organization IT maturity seems to be lagging so far behind the technology curve?”
Well there was some humming and pondering and a response of “well that’s a good point!” and then we continued to talk about technology features etc. etc.
My point here is that if we look ahead to the 2014 predictions we will see “mobility”, “BYOD”, “security”, “digital”, “SDDC” and all manner of other lovely acronyms and buzzwords. What I’d like to see is some thought about how we get there.
Let’s take this PDF:
On page 3 you will see a diagram that outlines something similar to that of a Maturity model. Here we can see that Gartner say that we are between “IT Industrialization” and “digitalization”. I would argue that we are not quite there yet, true in isolated areas in companies I’m sure we could find pockets where we are there, but as a whole I’ve yet to find a large number of customers who I would place at the “we are here” line. Sure from a high level viewpoint and from an Industry perspective I agree with the concept. What I’m failing to see is how we drag ourselves (and yes I believe it will require some heavy lifting) from today’s buzzwords into a reality whereby we are at a “rationalized” maturity which is capable of moving into this “Digitalization” phase.
I thought I’d jot down a few notes around the good use cases for VDI. I often hear people sell the idea with a reduction in cost as a key driver. It’s true you can use the VDI initiative to reduce the direct total cost of ownership, but in reality the VDI element is not what causes the reduction in TCO. (I am also assuming we are reducing TCO based on a BASIC level maturity orginisation).
So without using reduced TCO as a driver, when would I recommend VDI?
So I’ve been conducting a number of studies recently and a client asked me why in a recent study I hadn’t considered tablet’s as a PC replacement (primary device) when looking at VDI DaaS solution. When the question was posed it was something that I had actually not given a lot of thought, luckily with a brain full of VDI knowledge I worked in in nanoseconds that replacing my thin client with a tablet (non Full windows device)essentially had the same effect (just with now a mobile management effort required as well). Now having had some more time to ponder this in detail I thought I would give some further insight (any tablet donation’s are welcome!)
VDI = Reduced TCO??? Continue reading
“I started to write this a while ago… but never got round to publishing….” – Dan
A shared folder will do surely?
Back when I started in IT a network share was KING of the hill when it came to sharing documents and spreadsheets. Moving onwards from FAT based systems we could start giving access to groups (hopefully the correct type for those who have shared the pain when people haven’t used local groups) and having granular permissions both at the share and file system level.
Alas this shared pool of file storage still had many limitations, some can be augmented with search and shadow copy but mainly it’s a large pool, generally only separated by two dimensional folder structures (I’m ignoring access based control and metadata search but again this is an augmentation)