It ‘s not wrong not for my title the thing that I would like to share with you today is about change. In term of [[PMI]] project management change is a part of risk management but in [[ITIL]], change is the most important because Information Technology services manager alway got movement not just because of risk or internal or external factor.
To ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to controlled IT infrastructure, in order to minimize the number and impact of any related.
What’s I learn?
- Stakeholder don’t care what you need to do in order to archive their requirement then as your are [[PM]] or [[ITSM]] you have to plan your own change.
- Stakeholder don’t care as long as change is not effect them.
- 10 small change is easy to manage than 1 big change, what’s I always did is try to slim down my change but do it more organize often.
What’s the meaning of more organize often?
- Plan to put over all action together .
- Do every action in small size of effect to stakeholder.
- Act all action continuously but may not in the same time or same day, if same stakeholder will nice.
- Check every foot step of your action and update it all to your plan.
- Redo everything in cycle again, until your change has been done.
When I practices like this my change not really have any problem but every change is a problem that have its own characteristics for you to learn. It’s depend what you try to put it in which position.
When a user does something on his PC that makes the PC want to send data, acouple of things happen, in order, as described in the preceding section. First, for the refernce, here are the first three basic steps that you will examine now:
1. When the user type/implies a name of another computer (for example, by choosing to go to a website with the name embedded in the URL) the PC asks DNS to resolve the name into an IP address.
2. After it knows the IP Adrees, it the IP Address of the other computer is local, the PC directly send the packet to the other PC
3. After it knows the IP Addressm, if the IP Address of the other computer is on other subnet the computer sends the packet to its default gateway.
A reasonable methodology for troubleshooting is to somehow verify whether the PC can succeed at step 1, If succeeds, somehow verify if Step 2 is working, and so on. Most PC OSs include built-in tools that allow such testing, such as NSLOOKUP ping and tracert
You can use NSLOOKUP to displays information that you can use to diagnose Domain Name System (DNS) infrastructure. Before using this tool, you should be familiar with how DNS works. The Nslookup command-line tool is available only if you have installed the TCP/IP protocol. As you can see in the picture.
PING is command verifies IP-level connectivity to another TCP/IP computer by sending Internet Control Message Protocol (ICMP) Echo Request messages. The receipt of corresponding Echo Reply messages are displayed, along with round-trip times. Ping is the primary TCP/IP command used to troubleshoot connectivity, reachability, and name resolution
TRACERT or traceroute
Determines the path taken to a destination by sending Internet Control Message Protocol (ICMP) Echo Request messages to the destination with incrementally increasing Time to Live (TTL) field values. The path displayed is the list of near-side router interfaces of the routers in the path between a source host and a destination. The near-side interface is the interface of the router that is closest to the sending host in the path.