125 Results Found
If you create presentations using the notes feature in PowerPoint, you probably have found yourself wanting to print multiple slides on one page (handouts) with the notes associated with those slides displayed on the same page. This layout can often help you better p...
As long as I've been involved in service management, one of the perennial debates that's really never been resolved focuses around how many discrete processes ITIL describes. No such single list exists in the ITIL core books. However, section 4.1 of each of the ITIL 2011 core books shows the processes described within that specific book. When we deliver accredited ITIL training, if it is describe in section 4.1 of any of the ITIL core books, then it is considered a "process".
What's the correct sequence of activities for handling an incident? Find out why categorization occurs before initial diagnosis in the ITIL incident management process flow so you can answer this common ITIL Foundation exam question.
Here are seven tips for working with vSphere, including: Logging in via Command Line, dealing with connection problems using ssh to an ESXi host; network performance issues; possible storage problems; Log Files to View in vSphere ESXi 5; network performance troubleshooting; migrating to a virtual machine using VMotion.
Previously I discussed service providers and their risks in the example of my involvement with a landscaping company. ITIL clearly states that services, “…deliver value to customers by facilitating outcomes customers want to achieve…” However, sometimes organizations and people focus on outputs as opposed to outcomes, which sacrifices some of the value of the service. This leads to a question, what is the difference between an outcome and an output?
Lessons learned is a theory, or conclusion, based on evidence at a given time and describes what went wrong (as well as what went right) throughout the lifecycle of a project. Although it’s completed during the project closeout process, it should occur during the entire project lifecycle to ensure all information is captured and documented. Consequences of not having a project review of lessons learned are the increased likelihood of repeating actions that might have caused:
This vSphere Essentials white paper will give you a basic understanding of some of the concerns or planning points to consider as you get ready to deploy vSphere in your organization. This is a glimpse into some of the essential things to consider for implementing vSphere. This will focus on some of the basics that vSphere administrators run into when installing the latest features and not realizing they still have some older versions implemented.
Organizations that plan for and conduct supplier management according to defined processes and boundaries are more likely to receive predictable, high-quality goods and services from their suppliers in a timely manner.
This white paper has three main goals. The first is to generate a better understanding of the cloud in both the business and IT communities. The second is to describe the major components of vCloud and the virtual datacenters they provide. The third is help businesses visualize and understand how vClouds could be beneficial in addressing their specific IT needs.
Once an organization has categorized suppliers, one of the benefits that is quickly realized is an understanding of how supplier changes affect the buying organization and vice-versa. Changes are the modification, addition, or removal of something from the environment. The scope and scale of each change can be different. Change management covers everything from regular, low-risk, operational modifications all the way to significant organizational strategic shifts.