Finding a Way To Fill The Web
I had written this back in 2010 to a magazine, Virtual Intelligence Briefing.
I haven’t been able to find it, and people keep asking me for, “…how to start with VDI?”
I have not changed a word in this post from years gone by.
While versions have changed, as well as vendors that no longer exist, I believe that the logic applied herein is still valid.
Enjoy the Read!
Continue reading “VDI – How To Get Started”VMworld 2018
Las Vegas, Mandalay Bay, August 26-29Its coming quickly. If you know of anyone going, PLEASE…let me know. Want to make sure that we include our customers in anything WEI does in Las Vegas.
VMware vSphere 5.5 End of General Support
September 19, 2018 is coming, and many of our customers are engaged in projects getting their infrastructures up to date.It was a good five (5) year run on this version of vSphere, but all good things must come to an end.VMware has been repeatedly stating this over the past 7 months, and here is another reference back to a February post, with links and FAQs around the topic.
VMworld 2018
Las Vegas, Mandalay Bay, August 26-29
Its coming quickly. If you are going, PLEASE…let me know. Want to make sure that we include ALL our customers in anything WEI does in Las Vegas.
VMware vSphere 5.5 End of General Support
September 19, 2018 is coming, and many of our customers are engaged in projects getting their infrastructures up to date.
It was a good five (5) year run on this version of vSphere, but all good things must come to an end.
Mistake No. 1: Projects lack the right resources with the right skills.
Mistake No. 2: Projects lack experienced project managers.
Mistake No. 3: IT doesn’t follow a standard, repeatable project management process.
Mistake No. 4: IT gets hamstrung by too much process.
Mistake No. 5: They don’t track changes to the scope of the project.
Mistake No. 6: They lack up-to-date data about the status of projects.
Mistake No. 7: They ignore problems.
Mistake No. 8: They don’t take the time to define the scope of a project.
Mistake No. 9: They fail to see the dependencies between projects.
Mistake No. 10: They don’t consider Murphy’s Law.
Mistake No. 11: They give short shrift to change management.
Mistake No. 12: Project schedules are incomplete.
Mistake No. 13: IT doesn’t push back on unreasonable deadlines.
Mistake No. 14: They don’t communicate well with project sponsors and stakeholders.
– Meridith Levinson, CIO
July 23, 2008
Continue reading “The 14 Most Common Mistakes IT Departments Make”
