D2 – The New Corporate Desktop

Business DesktopSo why “D2” you ask? It stands for “Desktop 2.0”, which is of course, a play on Web 2.0. While there have been many predictions and suggestions, I want to take this opportunity and posit my opinion of where the corporate or enterprise desktop solutions should be heading. My poor coworkers have got to be tired of hearing my pitches and ideas on this by now!

In a nutshell, I believe Window Vista to be the last large-scale revision and release of the operating system. As such, corporations need to figure out whether they want to continue the upgrade cycle of Microsoft’s high-maintenance operating system. Or, choose to go a different path to secure their data, lower management costs of their client systems, and bring more areas of the business under the business continuity (disaster recovery) umbrella.

To accomplish this, businesses need to look at the pros and cons of both options and take a hard look at their computing needs. The solution for a manufacturing company that merely needs to track production, finance and sales does not have the computing requirements of, say an engineering firm where most of the employees require high-powered CAD/CAM software solutions.

The problem with the traditional desktop is not the initial cost for the hardware, installation, software licensing and so on. Its obviously the ongoing support costs, hardware replacement, service calls, and much more depending on how skilled your technical staff is.

In another world with the proper use of terminal services or Citrix server farms, data replication, thin clients, system virtualization, and load balancing, a company could eliminate or significantly reduce the reliance in traditional desktops and laptops. The key thing to focus on is not reducing cost so much as realizing that you can take control and secure your data. You can create an environment where all data is backed up at your central hub and backup locations that you currently use. (Just think of all those unsecured hard drives that aren’t backed up storing, in some cases, critical business data!) You can also reduce or eliminate the complexity of supporting the Windows operating system.

Yes, Microsoft has made great strides in managing and deploying the operating system, but you do know that you will need to deploy yet another server system to manage the licensing of Windows Vista – right? Did you know that the methods for deploying Vista is different than deploying Windows 2000 & XP? Yep, start planning a big upgrade budget, even if you choose to slipstream the OS, you’ll need to plan the deployment infrastructure out properly. (*Shameless plug* Contact me if you want some consulting done on this – its what I do as an Infrastructure Architect and Analyst smile_wink ).

There is a better way, and it doesn’t need to be the standard Windows desktop – also think about what Apple has been doing with the Mac lately, or Linux – several distributions have really made huge usability strides in the last few years. Do I have a chip on my shoulder regarding Vista – not really, but I think there are more solutions today than when Windows XP was fresh and new and the focus of everyone’s attention. I just think that the proliferation of web-based applications, increased bandwidth, robustness of terminal services, and the flexibility of virtualization, that there can be a simpler corporate environment than we have today.

DR is Over… I Survived!

Ok, we’ve completed DR, and it was an overall success.  Though our provider had several hardware issues that delayed our start time, and impeded our early progress, we did complete our required tests.

One stretch objective was “bagged” at the end, though we did restore the systems involved.  This was due to the length of the test, we had added 8 hours to the test when the provider offered them for not being 100% ready at the beginning.  That change did make for a longer than anticipated work schedule for a number of the staff – several extra hours were spent on-site rather than getting much needed rest.

Once we completed yesterday, we all headed home for rest; I got home in the afternoon, ate a little, watched a movie and tried to waste a little time to get closer to a “real” bedtime.  Finaly crashed around 9pm and slept for a little over 12 hours.  Good thing we don’t do this too often, its hard to catch up on rest.

Now we’ll gather our notes, archive the contents of the DR Blog and bring all this information to our post-DR de-brief meeting sometime in the next week.  Lots of items will be discussed, from our performance, our providers performance, what went well, what we can improve on, and so on.

Until next time!

DR Doldrums

After a few hours it sure does get boring.  We’re on track to finish up tomorrow afternoon sometime, and I know everyone is looking forward to concluding the test.

There are not many ammenities at the test facility we are at, our remote team probably is at the nicer site.  However, they are carrying the “heavy load” so to speak.  They are putting in longer hours and doing most of the restore work.  Our team here in town is focused more on  supporting and coordinating the system testers that validate that the restore is completed successfully.

Well, I’m going to get a chance for some extra rest this evening, and will be surfing on my favorite news sites to see what is new out in IT land.  Soon, it’ll be back to normal and I can’t wait for that.

Day 2 of DR Test…

We got in around 9am this morning and found there were several issues from the night team.  It’ll make for a long day for the other side of the house, but they usually are able to get around hardware handicaps.

We’ll hopefully be testing several restored systems by late morning or early afternoon, but we have until tomorrow morning to finish up.  With only about 4 hrs of sleep for the team, they’re doing well.
Its unfortunate that there are so many hardware issues in this test, the vendor is working with us to figure out what is wrong.  The last two tests we’ve run have had flawless hardware execution, everything was configured correctly and ready to go.  This is the first test in a year that has had HW issues, and not small ones either.

Oh, well, 23hrs to go. 🙂

Pin It on Pinterest