Technically Speaking

One of the coolest things going on in business is mobility of data; from the user perspective at least.  As an administrator, this stuff makes me cringe.  Allowing users to access their data from anywhere is a key requirement, but letting the data travel on a flash drive or portable device is somewhat sketchy because the media can be lost, broken, stolen, etc.  This would allow in many cases, the data to get into the wrong hands.

The IEEE standards board is working on IEEE1667 which is an encryption/authentication method for USB devices to allow them to support enhanced storage capabilities.  Microsoft supports this standard in all SKUs of Windows 7.  Hopefully soon, the devices that make use of the standard will hit the shelves.

The idea is that the device supports a certificate (and many types of certificates) to allow authentication by the host system and the device to protect data.

An example of how this might be helpful

Suppose that Joe User is working in a company and carries his most used data on a 1667 supported flash drive.  This way he has it everywhere just in case he needs it.

The device has a certificate to ensure that it works with computers within the organization, but not on computers outside the organization because the certificate authentication cannot happen.

It works great for moving between the company computers.  Allowing Joe to be in the Washington office where he works every day, using the flash drive and data, but also to travel to the New York office and plug right in and continue working.

When Joe goes home and plugs into his desktop PC, the drive will not work because there is no certificate there for authentication with the device.

New, not perfect

This provides a bit of peace of mind to business for the majority of their users travelling with and possibly losing flash drives, however it is likely far from perfect at this point.  Going forward other applications and “smart” enhancements for USB drives will make this technology a great standard, keeping employees happy because they can use portable media without stepping on the toes of the IT department and risking data loss.

Windows 7 does recognize these devices and can make use of them when they arrive, which is definitely something I am looking forward to.  I hope the idea takes off simply to encourage companies to properly handle the portability of Information by employees.

There are other uses for this technology I am sure, but the data portability portion is something I have been working to correct for quite some time, maybe this is just the technology needed to do that job.

All people who use a computer have some contact with storage.  From the disk inside your PC to the flash drive that stores all of the photos of your kids, we all get to interact with storage.  Over the past two years I have been a Microsoft MVP in the File System Storage area and it has provided a great opportunity to see that there is more to storage than the disk(s) that hold the data.

Working with enterprise class storage, using SANs or direct attached storage in file servers, is an interesting role.  My organization uses a network attached storage box running Windows Storage Server 2003 with a very small amount of disk space.  Certainly not the piles of disks used by large companies, but still a good amount of storage to manage.

Finding out more

Last week I was in Redmond learning about storage and the ways it works within Windows Server (and client) as well as storage (or file system) related features in Windows Server 2008 and 2008 R2.  The opportunity to interact with other MVPs and the product groups based around storage was amazing and I am hoping to really begin digging into storage more.  My first goal is to rebuild my Windows Server 2008 R2 box to look more at iSCSI and Storage Server.

My goal isn’t to build Peta-bytes of storage, but to look at smaller storage possibilities for mid-sized businesses.  Companies similar in size to my employer who might not have the resources for huge amounts of storage, but might want to create a very efficient storage platform perhaps using Windows based iSCSI and a reasonable amount of physical disks.

Storage is all about disk isn’t it?

For a good portion of my career I thought that disk was the only component of storage, after all to store the data, there has to be some where to put it.  However, another factor is the method by which the data gets to the disk and its availability.  Other things that influence storage (or certainly could in the future) are items like Virtualization.  Being able to captialize on the mobility of virtualized servers and the reduced hardware overhead they provide seems to bring a better storage utilization.

Many opportunities but just getting going

With the MVP Summit 2010 behind me, I am very interested in what I learned and the relationships I have formed.  Getting the opportunity to work with those at Microsoft, like Suzanne Morgan, who works with the storage initiatives in and around Windows Server is amazing. In the next few months I am sure I will have a few questions, both of Microsoft and of other Storage MVPs as my learning about enterprise storage is just getting started.

Wow… Aerosmith must have been on a radio somewhere today.  But none the less, I am back in Seattle WA for the Microsoft MVP Global Summit and am quite looking forward to the forthcoming information overload.

Microsoft spends a great deal of resources to put this event together for MVPs around the world and having the opportunity to attend is really outstanding.  That and the weather here today was about 50 degrees compared to somewhere in the 20’s back in Wisconsin.  I’ll admit, I like being able to get outside in February without wearing all the Winter essentials.  Similarly, getting to Advaiya’s offices from somewhere middle Bellevue did take closer to 40 minutes than the 20 or so I had thought (or I’m a slow walker).

Bring it on.

Tomorrow starts the festivities that are Summit and surely there will be more than a little NDA and Non-NDA content provided.  My intent was not to go into detail about the content of the Summit, which is in many cases protected by the aforementioned NDA, but to look at two things, the experience itself and maybe why an organization might put together an NDA in the first place.

Summit – or geek week

My wife refers to the MVP Summit as Geek Week, the one week out of the year where I get to spend time learning about Microsoft stuff and what other ‘geeks’ are doing.  The experience of being an MVP is amazing but still likens much to a fire hydrant.  The amount of information one gets as part of the program is a ton.  There are so many ways to interact with other MVPs and Microsoft that it seems like overload at first, but as you get used to it, it really doesn’t seem so bad.

Side sessions and learning about things new (or just new to you) while getting the opportunity to interact with others and with Microsoft is the idea of the weeklong event.  Feedback and just overall face to face conversation with Microsoft is something not many technology professionals get the chance to experience.  I have found myself seeing Microsoft as the huge corporation they are more than once, but now that I have gotten a chance to know some of the people behind the company and the products, my outlook or consideration o things that might go into an application is a bit different.  Do I drink some of the Microsoft Kool Aid, absolutely, but at the same time there are things I am not sure I agree with.  The MVP program provides multiple feedback opportunities, both good and bad are allowed, as long as they are constructive and helpful.

Where do I take the exam for MVP?

That’s the thing… you don’t.  MVPs are picked by Microsoft for contributions to the technical community.  Things that they do to help others learn a technology or better service their customers.  You cannot buy the MVP Award, sure you might get an MVP to sell you their used MVP t-shirt, but the award must be earned.  I found out about the MVP program a few years back and could never really figure out how one became an MVP.

Then one day, I got an email from a former Microsoft employee about the idea of nomination for a few blog posts I had done. And the rest is history.  Putting together content and resources to help others in the technology field learn or better do their jobs is a great way to be considered for the program… and rest assured, someone from Microsoft is likely paying attention.

To NDA or Not to NDA

Many companies do not guard their intellectual property with a formal Non-Disclosure Agreement.  Many other companies do.  I guess the nature of the business and the information that an employee has access to determines the need for an NDA.  Basically the document outlines things that cannot be discussed and at what lengths they cannot be discussed outside the agreement. 

For MVPs this means talking about unreleased Microsoft items and other things they learn as part of the program.  For dealings with other organizations this might mean discussing trade secrets or even the future of an athlete as pertaining to a team.

Before the MVP program I wasn’t sure about NDAs in general.  Maybe because I blog and feel that there is a reason to share things with those who read or want to read it.  Since teh MVP program I am able to see the need for them and have learned to err on the side of quiet.  If it is something I’m not sure about, I keep it to myself and ask someone to clarify.  If their answer is grey and I’m still confused; it stays off the Internet.

Thankfully the existence of the MVP program is not something MS wants to keep quiet.  They value the MVPs more than I can explain (and even if I could, it would end up something like War and Peace; long and unwieldy for most).

The bottom line

I hope that you will make an effort to make more contributions to your technical communities, even if that is just helping your neighbor get his Wireless working.  Trust me the visibility is icing on the cake, but being able to help those who might need it, is worth its weight in gold.

Working primarily in a support role for the past few years has taught me a thing or two.  One of the things I learned was about helping others and this is the focus for this post.

When providing support it is essential that you deal with other people, it is also essential that you try to avoid the blame game as much as possible, however it is unreasonable to think that one will never fall into the “he said she said” blaming of others.

Another think I have noticed, perhaps recently (and maybe far too late), is that matching the level of politeness and patience can go along way, but being polite regardless of the other end of the conversation is a home run.  Working on this takes time, frustration, and possibly some conversations with yourself during the ride home from work.

Being helpful and able beats being right

There are times when it is fun to be right.  For example, when the colts beat the saints on Sunday it will be fun to have been right (although this isn’t guaranteed) and maybe even bring in a few bucks for me.

When doing technical support, being helpful is more important than being right, no matter the situation or the reason.  Imagine if you will a relative who asks you to look at their computer because the Internet doesn’t work.  Sometimes it is an inconvenience, sometimes it is happening again, but think about how much better it feels to help than to complain or refuse. 

I will admit that I have to eat my own dog food here and can surely improve this, but I am confident that I can.

Helping with purchasing decisions

There are many organizations where a purchasing department places the orders for the needs of the company and handles all of that, but from time to time they will ask another department for help.  Sure they could get help from the vendor, and maybe they’ll need to anyway, but when asked providing the information you can might save extra work for these individuals.

For other systems, like when Aunt Mary asks what computer to buy, probe a bit and discover the ultimate use of the system and provide your opinion.  Be honest when asked “what would you do?” but make sure you let them know that you are providing an opinion about a system.  This way if they shop around or ask others as well, they wont feel like they are stepping on your feet.

Remember it is OK to ask for help

Along these lines, when you are asked to help someone solve a problem, you may need to ask for help from a colleague or co-worker or even an outside party.  If this is the case, make sure you let the person who asked you for help know you need to get assistance so they do not feel you are blowing them off.

Thinking about these few items in relation to the support calls and requests you receive might make your day a bit less stressful because helping someone just for the sake of helping them, can be rewarding sometimes.