Archivo de la categoría: Featured

Collaborating Through Crisis and Change for Successful Outcomes

By Brian Shaw, Program Manager, Managed Services Solutions

 

Crisis management and change management begins long before an incident occurs with the creation of a collaboration and decision making framework prior to project implementation.

A collaboration strategy needs to address the types of change to be communicated (perhaps based on thresholds for schedule and cost impact), who change needs to be communicated to, and what actions may result from that change. Actions resulting from change collaboration may be as simple as accepting the impact to the project schedule or as complex as allocating additional budgets and personnel. Follow the below steps prior to project implementation and your project team will be ready for change when it occurs. [Note: the method of applying these concepts should scale to the complexity and duration of the project.]

Preparation

Could it be coincidental that “preparation” and “Project Manager” both begin with a “p?” I think not. It is the responsibility of the Project Manager and the project team to create an environment for project success. A communication plan is a key component of project preparation. The plan should take into consideration the multiple audiences for project related information. All too often a single communication method is selected (such as emailing weekly status updates); however, this strategy doesn’t take into consideration that each audience has its’ own needs. A project engineer will require information regarding architecture and device level access that would be extraneous noise to an executive audience.

Additionally, most projects have a threshold for which change can be quickly accepted versus change or crisis that requires escalation. Define these thresholds as early as possible. If the duration of the work effort changes by less that x% or the cost changes by less than $x, can the project team quickly move forward without engaging an executive for approval? Prior to project initiation determine what types of change need to be escalated and who those changes need to be escalated to.

Control Sheet/Project Dashboard

Believe it or not, some audiences of project information don’t like reading MS Project plans and Ghantt charts…go figure. Both executive and client audiences often prefer a succinct format which quickly identifies task families that are on track, those at risk and those that have failed. This type of shorthand project metrics update is often referred to as a project dashboard or control sheet.

A project dashboard should quickly communicate project budget to actuals, project timeline and the status of milestones and/or important tasks. A popular method of sharing the status is the red, yellow, green light methodology. The critical benefit of this communication strategy is that audiences of this information can move quickly to problem areas and work towards resolution actions. If you are using a risk register then the yellow and red lights may kick out to the risk management work stream.

Collaboration Tools

Knowing what you are going to communicate and when you are going to communicate is only part of the collaboration strategy. It is critical that the project team determine how to collaborate and share types of information. Collaboration tools such as SharePoint, Drop Box and Huddle are commonplace, and I highly recommend your project team adopt a collaboration tool if you haven’t already done so.

The collaboration tool you use should allow the storage of multiple types of information along with selective access to information. The best tools allow access control at both the folder and file level. This level of information control allows sensitive information such as access credentials to be locked down to those that need access only.

The control sheet should be maintained within your collaboration tool so appropriate consumers can pull up a live project status at any time. Additionally, the collaboration tool should not replace individual action. If an important change or crisis occurs an update to the control sheet should not suffice as engaging decision makers. Those changes should be escalated in an active way to decision makers.

Execution:

Creating a communications plan around change is only the beginning. Once you’ve determined how you are going to communicate change, what changes will be communicated and how crises will be handled, it is then the responsibility of the Project Manager to ensure that consumers of this plan are informed and clearly understand the expectations. The plan is actionable and when change occurs the project team should be familiar enough with the plan to easily put it in motion.

 

Project Management Form

Looking for more information around Project Management? Please fill out this form and we will get in touch with you shortly.

Moving Email to the Cloud Part 2

By Chris Chesley, Solutions Architect

My last blog post was part 1 of moving your Email to the Cloud with Office 365.  Here’s the next installment in the series in which I will be covering the 3 methods of authenticating your users for Office 365.  This is a very important consideration and will have a large impact on your end users and their day to day activities.

The first method of authenticating your users into Office 365 is to do so directly.  This has no ties to your Active Directory.  The benefits here are that your users get mail, messages and SharePoint access regardless of your site’s online status.  The downside is that your users may have a different password than they use to get into their desktop/laptops and this can get very messy if you have a large number of users.

The second way of authenticating your users is full Active Directory integration.  I will refer to this as the “Single Sign On” method.  In this method, your Active Directory is the authoritative source of authentication for your users.  Users log into their desktop/laptop and can access all of the Office 365 applications without typing their password again, which is convenient. You DO need a few servers running locally to make this happen.  You need an Active Directory Federation Server (ADFS) and an Azure Active Directory Sync Sever. Both of these services are needed to sync your AD and user information to Office 365. The con of this method is that you need a redundant AD setup because if it’s down your users are not going to be able to access mail or anything else in the cloud.  You can do this by hosting a Domain Controller, and the other 2 systems I mentioned, in a cloud or at one of your other locations, if you have one.

The third option is what I will refer to as “Single Password.”  In this setup, you install an Azure Active Directory Sync server in your environment but do not need an ADFS server.  The Sync tool will hash your user’s passwords and send them to Office 365.  When a user tries to access any of the Office 365 services, they are asked to type in their password.  The password is then hashed and compared to the stored hash and they are let in if they match.  This does require the users to type their password again, but it allows them to use their existing Active Directory password and anytime this password changes, it is synced to the cloud.

The choice of which method you use has a big impact on your users as well as how you manage them.  Knowing these choices and choosing one that meets your business goals will set you on the path of successfully moving your services to the cloud.

 

Download this free ebook on the evolution of the corporate IT department

 

My VMworld Breakout Session: Key Lessons Learned from Deploying a Private Cloud Service Catalog

By John Dixon, Consulting Architect, LogicsOne

 

Last month, I had the special privilege of co-presenting a breakout session at VMworld with our CTO Chris Ward. The session’s title was “Key Lessons Learned from Deploying a Private Cloud Service Catalog,” and we had a full house for it. Overall, the session went great and we had a lot of good questions. In fact, due to demand, we ended up giving the presentation twice.

In the session, Chris and I discussed a recent project we did for a financial services firm where we built a private cloud, front-ended by a service catalogue. A service catalog really enables self-service – it is one component of corporate IT’s opportunity to partner with the business. In a service catalog, the IT department can publish the menu of services that it is willing to provide and (sometimes) the price that it charges for those services. For example, we published a “deploy VM” service in the catalog, and the base offering was priced at $8.00 per day. Additional storage or memory from the basic spec was available at an additional charge. When the customer requests “deploy VM,” the following happens:

  1. The system checks to see if there is capacity available on the system to accommodate the request
  2. The request is forwarded to the individual’s manager for approval
  3. The manager approves or denies the request
  4. The requestor is notified of the approval status
  5. The system fulfills the request – a new VM is deployed
  6. A change record and a new configuration item is created to document the new VM
  7. The system emails the requestor with the hostname, IP address, and login credentials for the new VM

This sounds fairly straightforward, and it is. Implementation is another matter however. It turns out that we had to integrate with vCenter, Active Directory, the client’s ticketing system, and client’s CMDB, an approval system, and the provisioned OS in order to automate the fulfillment of this simple request. As you might guess, documenting this workflow upfront was incredibly important to the project’s success. We documented the workflow and assessed it against the request-approval-fulfillment theoretical paradigm to identify the systems we needed to integrate. One of the main points that Chris and I made at VMworld was to build this automation incrementally instead of tackling it all at once. That is, just get automation suite to talk to vCenter before tying in AD, the ticketing system, and all the rest.

Download this on-demand webinar to learn more about how you can securely enable BYOD with VMware’s Horizon Suite

Self-service, automation, and orchestration all drove real value during this deployment. We were able to eliminate or reduce at least three manual handoffs via this single workflow. Previously, these handoffs were made either by phone or through the client’s ticketing system.

During the presentation we also addressed which systems we integrated, which procedures we selected to automate, and what we plan to have the client automate next. You can check out the actual VMworld presentation here. (If you’re looking for more information around VMworld in general, Chris wrote a recap blog of Pat Gelsinger’s opening keynote as well as one on Carl Eschenbach’s General Session.)

Below are some of the questions we got from the audience:

Q: Did the organization have ITSM knowledge beforehand?

A:The group had very limited knowledge of ITSM but left our project with real-world perspective on ITIL and ITSM

Q: What did we do if we needed a certain system in place to automate something

A: We did encounter this and either labeled it as a risk or used “biomation” (self-service is available, fulfillment is manual, customer doesn’t know the difference) until the necessary systems were made available

Q: Were there any knowledge gaps at the client? If so, what were they?

A: Yes, the developer mentality and service management mentality are needed to complete a service catalog project effectively. Traditional IT engineering and operations do not typically have a developer mentality or experience with languages like Javascript.

Q: Who was the primary group at the client driving the project forward?

A: IT engineering and operations were involved with IT engineering driving most of the requirements.

Q: At which level was the project sponsored?

A: VP of IT Engineering with support from the CIO

All in all, it was a very cool experience to get the chance to present a breakout session at VMworld. If you have any other questions about key takeaways we got from this project, leave them in the comment section. As always, if you’d like more information you can contact us. I also just finished an ebook on “The Evolution of the Corporate IT Department” so be sure to check that out as well!

The Evolution of Your Corporate IT Department

By John Dixon, Consulting Architect, LogicsOne

 

Corporate IT departments have progressed from keepers of technology to providers of complex solutions that businesses truly rely on. Even a business with an especially strong core competency simply cannot compete without information systems to provide key pieces of technology such as communication and collaboration systems (e.g., email). Many corporate IT departments have become adept providers of technology solutions. We, at GreenPages, think that corporate IT departments should be recognized as providers of services. Also, we think that emerging technology and management techniques are creating an especially competitive market of IT service providers. Professional business managers will no doubt recognize that their internal IT department is perhaps another competitor in this market for IT services. Could the business choose to source their systems to a provider of services other than internal corporate IT?

IT departments large and small already have services deployed to the cloud. We think that organizations should prepare to deploy services to the cloud provider that meets their requirements most efficiently, and eventually, move services between providers to continually optimize the environment. As we’ll show, one of the first steps to enabling this Cloud Management is to use a tool that can manage resources in different environments as if they are running on the same platform. Corporate IT departments can prepare for cloud computing without taking the risk of moving infrastructure or changing any applications.

In this piece, I will describe the market for IT service providers, the progression of corporate IT departments from technology providers to brokers of IT services, and how organizations can take advantage of behavior emerging in the market for IT services. This is not a cookbook of how to build a private cloud for your company—this instead offers a perspective on how tools and management techniques, namely Cloud Management as a Service (CMaaS), can be adopted to take advantage of cloud computing, whatever it turns out to become. In the following pages, we’ll answer these questions:

  1. Why choose a single cloud provider? Why not position your IT department to take advantage of any of them?
  2. Why not manage your internal IT department as if it is already a cloud environment?
  3. Can your corporate IT department compete with a firm whose core competency is providing infrastructure?
  4. When should your company seriously evaluate an application for deployment to an external cloud service provider? Which applications are suitable to deploy to the cloud?

 

To finish reading, download John’s free ebook

 

 

 

 

 

 

Top Ten Considerations When Investing in BYOD

By Chris Reily, Director of Solutions Architecture

Every year has its own special IT acronym and 2013 has been no different. During client meetings, in the pages of IT trade publications and on the minds of vendor partners – the term BYOD pops up more frequently than Psy’s “Gangham Style” does on pop radio. For the record, Psy is the smartly dressed Korean pop music sensation sporting Risky Business-style Ray Bans as opposed to the (also trending) bearded Uncle Si of Duck Dynasty (reality-TV) fame. If this is all meaningless to you, you’ve been working too hard. Ask your family, they miss you.

Consumerization of IT is finding its way into the enterprise rapidly. Choice, personalization and mobility are no longer simply appreciated but are ultimately demanded. BYOD in theory sounds like a terrific plan and if executed properly can be an outstanding component of an end user computing (EUC) solution in many environments. Success however goes far beyond an employee stipend and flexibility in choice. BYOD is not for every organization and even in those organizations where it makes sense, it’s not for every employee. Here is a list of the top ten considerations when investigating a BYOD solution for your organization:

  1. What are the core applications you need to deliver to end users? Are these applications supported by recommended or allowed devices? What are the corporate use cases?
  2. Will your infrastructure support connectivity and desktop/application delivery to new devices on your network? Storage, compute and network – it all matters.
  3. Do you have the budget to support this initiative? Hint: it will be more than you expect. Hint #2: don’t expect to “save money” (at least in the first year). The ROI (return on investment) may come but expectations inside 36 months are unrealistic.
  4. Who needs what? Organizations are diverse and dynamic. Not every employee will need to be part of a BYOD initiative. Different categories of associates will have varying device needs. The road warrior sales guy, administrative assistant and mechanical engineer will all have different needs.
  5. A well-executed plan will drive employee job satisfaction. Figure out how your team will deal with happy IT-using employees; it may be a new experience for all involved.
  6. Are you ready to set policy and stick to it? There will be challenges that make you question what you were thinking in the first place. Get managerial support and be confident.
  7. Be flexible. Sure, this may seem somewhat contrary to comment #6. Of course you’ll encounter situations where the intelligent response is to modify and improve.
  8. Get “buy in” from the board room and the corner office(s). The support of senior management and investors is critical; don’t even go there without serious majority support.
  9. Seek advice and approval from legal, accounting and human resources. Ask the art department and maintenance team too if you think it can help.
  10. Talk to others. I know this is hard for many of us who have spent careers in IT, but give it a shot and see what happens. Speak to partners who have delivered BYOD solutions. Reach out to similar organizations who have implemented their strategy. Heck, speak with companies who tried it and failed. Arm yourself with information, do your research.

This is a lot to digest. A poorly executed implementation has the surety of employees abandoning the program. Small steps and a detailed approach work best – don’t be afraid of running test groups and proof of concept (POC) trials. The risk of not exploring your options may leave your IT environment seeming as outdated as last decade’s pop dance craze. Is your organization considering BYOD? Have you already implemented a policy? If so, how has your experience been?

 

Time is Running Out: Important Price Changes of Windows 2012 R2

By Rob O’Shaughnessy, Director of Software Licensing

 

There’s some good news, and there’s some bad news.  The good news is Windows 2012 R2 is being released…the bad news you have to pay for it.

Microsoft recently announced the release of Windows 2012 R2 which will be offering some new functionality described here Windows Server 2012 R2. However, along with the new release is some new pricing that will make you…well…read on.

Microsoft is releasing Windows 2012 R2 on November 1st and will be increasing the price of Windows Datacenter by 28%.  This is not a typo.  I’ll spell it out for you: Twenty-Eight Percent.  For you Twitter people that’s #twentyeightpercentholycow.

Now, only Datacenter is going up in price.  Windows Standard Server and Windows Cals will remain the same price.  Also, Windows 2012 Cals will be compliant with Windows 2012 R2 so if you own Windows 2012 User or Device Cals you don’t need to purchase new Cals.  So it’s just Datacenter right?  Yes…well almost.

Also going up in price is Windows Remote Desktop Services Cals (RDS) which will be increasing by 20% on November 1st.   Same deal here – if you own 2012 RDS Cals they will also be compliant with Windows 2012 R2. This means new Cals are NOT required for Windows 2012 R2 if you own Windows 2012 RDS Cals.

FAQ’s:

Q: Why is Microsoft doing this?

A: Because, they can.

OK, so here’s what you have to think about:

  • If you want to have access to Windows 2012 R2 and typically purchase it with SA, be sure to purchase the license before November 1st to avoid the price hike.
  • If you are looking at getting Windows 2012 and are not in position to purchase or don’t need SA, you can purchase the license before November 1st to avoid the price increase but you won’t have access to R2.
  • If you want R2 and don’t need to purchase SA, be sure to wait until November 1st to purchase it. Otherwise, if you purchase the license without SA prior to November 1st, you will not have access to R2.
  • Lastly if you need RDS Cals purchase them before November 1st

It’s coming up fast as the last day to purchase Windows 2012 Datacenter and RDS is Halloween night…scary huh?

These are important decisions for your company to make, so if you have any questions please don’t hesitate to reach out to me directly roshaughnessy@greenpages.com

 

 

 

How IT Operations is Like Auto Racing

By John Dixon, Consulting Architect, LogicsOne

 

If you’ve ever tried your hand at auto racing like I did recently at Road Atlanta, you’ll know that putting up a great lap time is all about technique. If you’ve ever been to a racing school, you’ll also remember that being proactive and planning your corners is absolutely critical in driving safely. Lets compare IT operations to auto racing now. Everyone knows how to, essentially, drive a car. Just as every company, essentially, knows how to run IT. What separates a good driver from a great driver? Technique, preparation, and knowing the capabilities of your driver and equipment.

 

The driver = your capabilities

The car = your technology

The track = your operations as the business changes

 

Preparation

Lets spend a little bit of time on “preparation.” As we all know, preparation time is often a luxury. From what I have seen consulting over the past few years, preparation is not just installed in the culture of IT. But we’d all agree that more preparation leads to better outcomes (for almost everything, really). So, how do we get more preparation time? This is where the outsourcing trend gained momentum – outsource the small stuff to get more time back to work on strategic projects. Well, this didn’t always work out very well, as typical outsourcing arrangements moved large chunks of IT to an outside provider. Why didn’t we move smaller chunks first? That’s what we do in auto racing – the reconnaissance lap! Now we have the technology and arrangements to do a reconnaissance lap of sorts. For example, our Cloud Management as a Service (CMaaS) has this philosophy built-in – we can manage certain parts of infrastructure that you select, and leave others alone. Maybe you’d like to have your Exchange environment fully managed but not your SAP environment. We’ve built CMaaS with the flexible technology and arrangements to do just that.

Technique

 

Auto Racing IT Operations
Safety   first! Check your equipment before heading out, let the car warm up before   increasing speed Make sure   your IT shop can perform as a partner with the business
Know where   to go slow! You can’t take every turn with full throttle. Even if you can,   its worth it to “throw away” some corners in preparation for straight   sections Know where   to allocate investment in IT – its all about producing results for the   business
First lap:   reconnaissance (stay on the track) Avoid   trying to tackle very complex problems with brand new technology (e.g., did   you virtualize Exchange on your very first P2V?)
Last lap:   cool down (stay on the track) An easy   one, manage the lifecycle of your applications and middleware to avoid be   caught by a surprise required upgrade
Know where   to go fast! You can be at full throttle without any brake or steering inputs   (as in straight sections), so dig in! Recognize   established techniques and technologies and use them to the max advantage
Smooth =   fast. Never stab the throttle or the brakes! Sliding all over the track with   abrupt steering and throttle inputs is not the fastest way (but it IS fun and   looks cool) Build   capabilities gradually and incrementally instead of looking to install a   single technology to solve all problems today.
Know the   capabilities of your car – brakes, tires, clutch, handling. Exceed the   capabilities of your equipment and see what happens. Take the   time to know your people, processes, and technology – which things work well   and which could be improved? This depends greatly on your business, but there   are some best practices to run a modern IT shop.
Improve   time with each lap This is   all about continuous improvement – many maneuvers in IT should be repeatable   (like handling a trouble ticket), so do it better every time.
Take a   deep breath, check your gauges, check your harnesses, check your helmet Monitoring   is important, but it is not an endgame for most of us. Be aware of things   that could go wrong, how you could mitigate risk, which workarounds you could   implement, etc.
Carry   momentum around the track. A high horsepower car with a novice driver will   always lose to a great driver in a sedan Technology   doesn’t solve everything. You need proper technique and preparation.
Learn from   your mistakes – they aren’t the end of the world With   well-instrumented monitoring, performance blips or mistakes are opportunities   to improve

 

Capabilities

A word on capabilities. Capabilities are not something you simply install with software or infrastructure. Just as an aspiring racecar driver can’t simply obtain the capability required to win a professional F1 race with a weekend class. You need assets (e.g., infrastructure, applications, data) and resources (e.g., dollars) to build capabilities. What exactly is a capability? In racing, it’s the ability to get around a track, any track, quickly and safely. In IT, this would be the ability to handle a helpdesk call and resolve the issue to completion, for a basic example. An advanced IT capability in a retail setting might be to produce a report on how frequently shoppers from a particular zip code purchase a certain product. Or, perhaps, it’s an IT governance capability to understand the costs of providing a particular IT service. One thing I’ve seen in consulting with various shops is that organizations could do a better job of understanding their capabilities.

Now picture yourself in the in the driver’s seat (of your IT shop). Know your capabilities, but really think about your technique and continuously improving your “lap times.”

  1. Where are your straight sections – where you can just “floor it” and hang on? These might be well-established processes, projects, or tasks that pay obvious benefits. Can you take some time to create more straight sections?
  2. How much time do you have for preparation? How much time do you spend “studying the track” and “knowing your equipment?” Do you know your capabilities? Can you create time that you can use for preparation?
  3. Where are your slow sections? The processes that require careful attention to detail. This is probably budget planning time for many of us. Hiring time is probably another slow section.
  4. Do you understand your capabilities? Defining the IT services that you provide your customer is a great place to start. If you haven’t done this yet, you should — especially if you’re looking at cloud computing. GreenPages and our partners have some well-established techniques to help you do this successfully.

 

As always, feel free to reach out if you’d like to have a conversation just to toss around some ideas on this topic.

 

Now for the fun part, a video that a classmate of mine recorded of a hot lap around Road Atlanta. The video begins in turn 11 (under the bridge in this video).

  1. Turn 11 is important because it is a setup to the front straight section. BUT, it is pretty dangerous too as it leads downhill to turn 12 (the entrance to the straight). Position the car under the RED box on the bridge and give a small amount of right steering input. Build speed down the hill.
  2. Clip the apex of turn 11 and pull the car into turn 12. Be gentle with turn 12 – upset the car over the gators and you could easily lose control.
  3. Under the second bridge and onto the front straight section. Grab 5th gear if you can. Up to ~110mph. Position the car out to the extreme left side of the track for turn 1.
  4. Show no mercy to the brakes for turn 1! Engage ABS, downshift, then trail brake into the right hander, pull the car in to the apex of the turn in 4th gear, carrying 70-80mph.
  5. Uphill for turn 2. Aim the nose of the car at the telephone pole in the distance, as turn 2 is blind. Easy on the throttle!
  6. Collect the apex at turn 2 and downhill for turn 3. Use a dab of brakes to adjust speed as you turn slight right for turn 3.
  7. Turn slight left for turn 4, hug the inside
  8. Track out and downhill for “the esses” – roll on the throttle easily, you’ve got to keep momentum for the uphill section at turn 5.
  9. The esses are a fast part of the track but be careful not to upset the car
  10. Brake slightly uphill for turn 5. It is the entrance to a short straight section where you can gain some speed
  11. Stay in 4th gear for turn 6 and bring the car to the inside of the turn
  12. Track way out to the left for the crucial turn 7 – a slow part of the track. Brake hard and downshift to third gear. Get this one right as it is the entrance to the back straight section.
  13. Build speed on the straight – now is the time to floor it!
  14. Grab 5th gear midway down the straight for 110+ mph. Take a deep breath! Check your gauges and harnesses.
  15. No mercy for the brakes at turn 10a! Downshift to 4th gear, downshift to 3rd gear and trail brake as you turn left
  16. Slight right turn for turn 10b and head back uphill to the bridge – position the car under the RED box and take another lap!

 

Moving Email to the Cloud, Part 1

By Chris Chesley, Solutions Architect

Many of our clients are choosing to not manage Exchange day to day and not to upgrade it every 3-5 years.  They do this by choosing to have Microsoft host their mail in Office 365.  Is this right for your business?  How do you tie this into your existing infrastructure and still have access to email regardless of the status of your onsite services?

The different plans for Microsoft Office 365 can be confusing. Regardless of what plan you get, the Exchange Online choices boil down to two options.  Exchange Plan 1 offers you 50GB mailboxes per user, ActiveSync, Outlook Web Access, Calendar and all of the other features you are currently getting with an on premises Exchange implementation.  Additionally you also get antivirus and antispam protection.  All of this for 4 dollars a month per user.

Exchange Plan 2 offers the exact same features as plan 1, with the additions of unlimited archiving, legal hod capabilities, compliance support tools and advanced voice support.  This plan is 8 dollars a user per month.

All of the other Office 365 plans that include Exchange are either plan 1 or plan 2.  For example, the E3 plan (Enterprise plan 3) includes Exchange plan 2, SharePoint Plan 2, Lync Plan 2 and Office Professional Plus for 5 devices per user.  You can take any plan and break it down to the component part and fully understand what you’re getting.

If you are looking to move email to the cloud and are currently using Exchange, who better to host your Exchange than Microsoft?  Office 365 is an even better choice if you are using, or plan on using, SharePoint or Lync.  All of these technologies are available in the current plans or individually through Office 365.

I’ve helped many clients make this transition so if you have any questions or if there’s any confusion around the Office 365 plans feel free to reach out.

My next blog will be on the 3 different authentication methods in Office 365.

Cloud Corner Series – Making Sense of New Cisco Product Announcements

In this segment of Cloud Corner, Lou Rossi, VP, Technical Services, at GreenPages-LogicsOne provides some clarity around new product offerings from Cisco.

 

http://www.youtube.com/watch?v=p0qWff1IUT4

 

If you have questions around any of the products mentioned in the video send us an email at socialmedia@greenpages.com

 

Remember you can also follow us on…

Twitter @GreenPagesIT

LinkedIn: http://www.linkedin.com/company/greenpages-technology-solutions

Facebook: https://www.facebook.com/GreenPagesTechnologySolutions

YouTube: http://www.youtube.com/user/GreenPagesTechnology

Journey to the Cloud: An Insider’s Perspective

By Ben Stephenson, Journey to the Cloud

Our Journey to the Cloud blog has been live for a little over two years now, and I’ve had the privilege of running and managing it from the start. I wanted to touch base about the site, share my unique perspective from managing it, and hear from our readers about what we can do to make it even better.

Our goal from the very beginning was to establish ourselves as thought leaders in the industry by providing high quality content that was relevant and beneficial to IT decision makers. We wanted to make sure we let our authors keep their opinions and voice, while at the same time taking an unbiased, agnostic approach. The last thing we wanted to do was start blathering on about what a great company GreenPages is or bragging about the most recent award we won (it was being named to the Talkin’ Cloud 100 if you were wondering…).  Over the course of the two years, we’ve posted over 200 blogs and seen the number of page views and shares across various social media sites increase drastically. We’ve brought in some big time guest bloggers such as ConnectEDU CTO Rick Blaisdell, CA’s Andi Mann, the Director, Advanced Analytics and Sr. Research Scientist at Gravitant, and more. We’ve incorporated a lot of video as well – in fact for whatever strange reason someone thought it was a good idea to let me host our Cloud Corner Series. We’ve covered topics ranging from cloud, virtualization, end user computing, BYOD, network infrastructure, storage, disaster recovery, shadow IT, project management, and much more.

Have there been challenges along the way? Absolutely. Have I had to go after people and chase them down, scratching and clawing until I get a blog to post? Yes. Have tears been shed? Has blood been shed? We’ll keep that to ourselves as it’s generally frowned upon by HR. And, yes, I have had to give William Wallace-like speeches to attempt to rally the troops. While there have been some challenges, all in all there’s been a great amount of enthusiasm and support from our writers to produce a high quality publication. For me, being in the industry for two years now with no previous technological background, the amount I’ve learned is ridiculous. Before starting at GreenPages, I would have rather listened to a Ben Stein Lecture or Bill Lumbergh explaining TPS Reports than read an article on software defined networking and the impact it will have on businesses in the next 5-10 years. I can see why our customers get excited to work with our consultants because they truly love and believe in the technology they talk about. I completely buy into their enthusiasm and passion and it makes me genuinely interested in the topics we cover. I’m in my mid-twenties and have, sadly, found myself out drinking at a bar with my friends having a great time before somehow winding up in a heated debate over the pros and cons of moving to a hybrid cloud architecture.

 

So, in case, for whatever deranged reason, you haven’t read all 200 of our posts, I’m going to list out my top ten from the past two years (in no particular order). Take a look and let me know what you think:

 

 

To close this out…I want to hear from you. What can we do to make Journey to the Cloud better? Are there any specific topics you’d like to hear more about? Any specific authors you’d like to hear more from? How about any features or functionality of the site you’d like added, changed or improved? What have you seen on other sites that you like that we don’t have? Leave a comment here or tweet us at @GreenPagesIT or @benstephenson1