Internet Blog

longtime kartolocyber wasnot update the article, some of us so busy in our study. okey, i'll write about virtual machine in Windows. Sometimes, there is a particular program that we want to run but is plagued with compatibility Operating System (OS). For example there are applications that we know first run on WinXP but now after a try again in Win7 not be opened (crash). Or even it could also have a special application we need to work, but teryata application can only run on Windows while Linux-based computer.

Of course, we can use the system to plant two Dual Booting OS in one computer. But sometimes this method is less practical because more needs to be prepared such as set partitioning, manage files, etc.. In addition, if one day we already do not need a second OS, then the uninstall process was not easy. All too often ended up reformatting, and that means set the partitions and file again.
Actually, there is one practical solution to this, that is by using VirtualBox. With VirtualBox, you can as if making a new computer ( virtual machine ) and install it with the OS you want (Guest OS). More great again, you can run both at the same time, moving from guest to host and vice versa with ease. If it does not need anymore, you just delete it (remove) the virtual machine without a complex process.

Well, in this article I will explain about how to create a virtual machine using VirtualBox. Because many things to be explained, for convenience, so I split them up into several sections, namely: Download & installl Virtual Box, Virtual Machine http://www.blogger.com/img/blank.gifSetup & Guest OS, and the last is the setting. In this example, I will install WinXP in a virtual machine that will be created. As for his own VirtualBox I run across operating systems Win7. So, the Guest OS and Host OS = WinXP = Win7. Here are the steps:
DOWNLOAD & INSTALL VirtualBox

First download the installer once its in here . Select according to the type of OS you use.



1. After that run its installer file. Click Next> when VirtualBox Setup Wizard appears.

2. Then you can choose the installation location. Click Next> to continue.

3.Choose anywhere you want a shortcut is created, then click Next>

4. Usually will appear warning that the connection to the network is disconnected while on during the installation process. Just click Next>.

5. Click Install to begin the installation process.

6. If UAC appears, click Yes.

7. Up here you've managed to install VirtualBox. Click Finish to run the VirtualBox program

VIRTUAL MACHINE SETUP

Next you need to do is make her a virtual machine. Click New on VirtualBox Manager to get started. You will be greeted by the New Virtual Machine Wizard. Click Next to continue. Here you will choose what type of OS you want to install as guest OS. In this example we will install WinXP. Click Next when done select the type of OS. You can determine how much memory (RAM) for the virtual machine later. Move the slider to the desired number, then click Next.For the first time, make sure you men-centang/contreng Boot Hard Disk and also select Create new hard disk, If so, click Next. Next you will go to the Create New Virtual Disk Wizard. Click Next to continue. You can choose whether the size of virtual hard disk later this magnitude can change or always remain. For savings should you choose a dynamically expanding storage. Click Next if you have selected. Here you can choose the location where the virtual hard disk will be created, it also determines the maximum size hard disk (hard disk maximum size). VirtualBox by default suggested size is 10 G. But you also can set smaller as long as you believe that size is sufficient for your needs later. Click Next. This is a Summary of the Create New Virtual Disk Wizard. Click Finish. It appears that you already have a virtual machine called WinXP, although it is still empty. Now the next task is to fill this virtual machine with the Guest OS. Double-click on the entry to start WinXP.
You will be greeted by First Run Wizard. Just click Next.Here you will select the media you will use as a source installation. In this example I use WinXP CD (bootable of course), which I enter into Drive E (DVD ROM). If so, click Next. This is a Summary of the First Run Wizard. It's good here you have prepared her to drive installer that you selected earlier. Click Finish to begin the installation process. Display WinXP installation will start out. Press Enter to continue. Select Format the partition using the NTFS file system, then press Enter. Please wait until the WinXP installation process is complete.
Congratulations, you now have a WinXP Guest OS on your virtual machine! Before you start "playing around" with this new virtual machine it's good to do some changes to the settings used to make you more comfortable in using it later. Some settings require the virtual machine in a non-active, some can only be done in the Guest OS Safe Mode. Thus, to present first shutdown the Guest OS you.

SETTING UP PROCCESS

This time will discuss about some important settings of your order the more comfortable in using your virtual machine. Make sure your virtual machine is turned off (powered off), then double-click to turn on and be prepared to press F8 as we will go into Safe Mode.

Choose Safe Mode, then Enter twice.
After entering Safe Mode, click Yes to close the window notification.
In the VirtualBox menu, select Devices -> Install Guest Additions.
It would appear the Windows Explorer . Double-click VBoxWindowsAdditions.
You will be greeted by the VirtualBox Guest Additions Setup Wizard. Click Next> to continue.
Select the installation location and click Next>.
If you plan to run an application in the Guest OS that require Direct3D (games for example), then make sure the Direct3D Support selected. If you already click Install.
Guest Additions installation process was completed. Click OK.
Click Finish to restart and get into WinXP as normal.
Next we'll create a Shared Folders. Usefulness is as a place to exchange (transfer) files between Guest and Host. The trick is to select Devices -> Shared Folders.
Click the Add button on the right side of the window.
In the Folder Path, select Other.
Specify the folder where you want shared.
Then select Auto-mount that folder directly at-shared automatically at startup.
Rekapnya be seen here. You also can create more than one Shared Folders if you wish. Click OK to finish.
Shared Folders will only begin to be used if you have to restart. But for now the Guest OS shutdown before you because we will make changes in the last settings via VirtualBox Manager.
Click Settings on the menu VirtualBox Manager.
Select the System tab on the left. Well here you can make settings memory (RAM) and also the Boot Order. In order for fast booting, select Hard Disk as the Boot Order first priority.
Select the Display tab and you can change the amount of Video Memory (VGA Card) and also activate the Enable 3D Acceleration feature. Click OK if it is.
Next run the virtual machine again. After entering Windows, try running Explorer. It appears that the Shared Folders now can be accessed.
Applications that can not be opened in Win7 are now able to run.

an explanation of the technical steps to create a virtual machine and its installation with the Guest OS using VirtualBox. In this way, we seemed to have a "new computer" is ready to run. In the world of IT, many benefits to be gained by using this VirtualBox. A Java programmer who want to create a multi-platform applications, can use VirtualBox to test programs in various OS (Windows, Mac, Linux, FreeBSD, etc.).

Or someone who is studying to be a hacker, usually also will create a virtual machine to test the efficacy of scripts or artificial virus, without having to worry about major OS that is being used also infected. You can also experiment with VirtualBox it suits your needs.

Voice over IP (VoIP) systems today are gaining in popularity today for several reasons, most notable are the availability of so many open source and commercial options, the high degree of available interface devices that allow you to connect to existing circuit based networks and hardware, and the ability to create full end to end IP based solutions using available high-speed links or gateways with commercial trunk providers. However, it is still easy to make a poor purchasing decision unless you take a good look at the basic requirements of what a communication system needs to provide to be effective in your business and help you achieve your cost savings while still maintaining your ability to be connected to your clients and vendors in an effective manner. My intent here is to help outline the 5 standard features that your VoIP system should have for it to be considered the proper solution for your enterprise.

Examination

Standardization and Flexibility

Just like Henry Ford grew the automobile business based upon the obvious concept of standardization, the VoIP industry gained its recent focus and popularity based upon the same ideals. Gone are the days of having to select and architect a solution based upon the supported protocols of one vendor and become locked in. The two major signaling protocols you will see today, H.323 and SIP are the largest players, with H.323 starting to lag behind as SIP gains in popularity and support, more compliant vendors, and continued enhanced to support more media streams and tighter device integration that up until recently has been what was keeping H.323 ahead in the game. Keeping in mind that H.323 is still the more mature technology, currently it is holding its ground in the carrier space and is used quite extensively as a trunk side protocol. This has allowed SIP to comfortably gain foothold in the enterprise space as a local carrier style protocol that is simpler to implement, troubleshoot, and extend with new features as needed. It is clear that for a system to be considered future proof it has to support the currently prevalent standards but also allow ‘plug ability’ and offer support for emerging standards, or alterations to the existing standards as well.

Integration Options

Unless you are starting from scratch you are most likely attempting to integrate a VoIP option into your existing infrastructure as part of a phased deployment strategy. The current list of options to accomplish this is growing longer and longer every day, and that has many benefits for the consumer with regards to architecture, cost, interoperability options, and the quicker movement to tighter standards compliance between vendors. There is no longer a need to consider the move to VoIP to be an all or nothing deal with the introduction of gateway devices that allow you to leverage your current investment in older TDM based equipment and enhance it with the newer IP based messaging solutions. Doing this allows you to add new devices to the newer IP network while maintaining a rich level of integration with the legacy TDM equipment until it lives out its natural (and still depreciable) life span.

Security

As with everything today, security is a huge consideration when you start to think about moving to VoIP. If it is not something that you have already though about, or your vendor has not discussed it deeply with you then I urge you to stop reading this right now, go to your vendor and ASK how secure your current VoIP implementation (or the one you are planning to install) is.

Security is so critical in today’s business market, but because people have felt so safe in the past using TDM voice infrastructures where ‘tapping’ meant actually making a physical connection to the ‘wires’, the thought of security quite often eludes people when you starting the talk about VoIP. It is so easy to fire up a copy of Wireshark on your network, collect some packets, and use the tools built right into the GUI to listen to VoIP conversations. So, what do you do? The answer is simple. You turn on encryption and ensure that every device you use within in your IP infrastructure involved in the call supports the encryption scheme that you pick. Keep in mind that while encryption is good, it does add CPU load to your devices, can cause higher network utilization because the packets can get larger, and can add complexity to any troubleshooting efforts, but you should NOT implement any VoIP system without taking security into consideration. One fine option that I have used is to consider your internal network to be secure and just encrypt the calls that pass via IP between external parties (over your IP based trunks if you use them) or between all your company locations using the public IP network. It’s my feeling that as long as you keep your internal IP infrastructure secure (IE: tight controls on who can enter your IT area, and you are using switches rather than hubs), bothering to encrypt internal IP connections is not always needed because in a properly configured environment you will not be able to capture VoIP data other than what is directed to you. If you are using hubs then all bets are off of course. That is a subject for another article.

Support

As with most other technologies, part of your purchasing and deployment planning MUST be to take the support model into consideration. Don’t just assume that your existing vendor that supports your current internet connection to the external world is going to be there if you have IP trunk problems, understand what terminology like QoS, jitter, and other VoIP lingo means, or even how to correct them if problems occur. As when introducing any new technology you need to have a sit-down with everyone involved in the proposed value chain and establish an understanding of expectations, possible support needs, costs, and schedules. You may find out that your provider is by default blocking the native ports that the typical VoIP protocols require simply because they are not used to requiring them to be open for other clients. If you are ready to move to IP for your voice communications just understand that while you may have been willing to put up with slowness in the afternoons when you tried to use the web to order your dinner so you could pick it up on the way home, a slow data connection can wreak havoc with voice quality and the ability to establish a call. You may need to consider a separate IP connection just dedicated to voice, and in fact you may need to start considering redundant connections using two different providers for your voice if you have not already done so for your data. Additionally, ensure that your vendor has the proper debugging tools in place, knows how to use them, and is willing to offer training to your staff, or that you are willing to use third parties to get them trained, so that they can be used to keep the system running in top condition. Remember that voice communication is still considered a top priority in today’s business world and loosing that, even for a few hours, can make a customer start looking for someone to replace you as a vendor.

Extension Points

Many people today are used to just using the phone to talk, or maybe send faxes, but once the move to IP is made the benefits will start to bring on questions about other methods of application integration, and additional ways to leverage the new communications system. One thing that you should always consider on any new system, not just VoIP, are ways that you can utilize it going forward for things other than just your current needs. A car would not be much use if you could only drive it back and forth to work would it? The same goes for your telephony solution. Right from the start you should consider investigating the extension areas of all the solutions you look at and at least gain an understanding of the features and benefits that each system may or may not offer. For example, it could be very disappointing to get a system all in place and six months latter determine that you still need to add a bank of analog trunk lines to and receive faxes because your solution did not include the ability for Fax over IP (FoIP) codecs. Making blanket assumptions like ‘just because traditional faxes use our existing voice lines the VoIP system should also do fax’ can lead to some very tense moments across a boardroom table. Also consider integration with other areas like Instant Messaging (IM) and application integration such as the ability to build basic Interactive Voice Response (IVR) menus (IE: ‘To talk to support, please press 1, to talk to sales, please press 2,…) into the system and create simple auto attendant applications. These simple features can help add some great value that may not have been considered previously, and allow you to recoup the costs of a VoIP implementation over a shorter timeline than previously anticipated. Areas like this can allow you to bring systems together under one area and thus cut down the size of your external vendor list.
Conclusion

As you can see, the move to VoIP is fraught with decisions, technical considerations, and even some simple human capital management opportunities, but the gains in productivity, efficiency, and the ability to leverage existing infrastructure and gain some valuable benefits in the areas of long term manageability, application integration, multi-modal communications options and simpler to manage infrastructure far outweigh the potential problems as long as the map forward is well thought out and planned. As with most IT based business decisions it is always good to ensure that everyone understands the possible features and benefits as well as the potential risks and how they can be mitigated to derive the value that is expected.

Disclosures and References

As part of my previous experience in VoIP technology I spent 10 years as a product and training specialist working for both Intel Corporation and Dialogic Corporation in the area of Digital PBX TDM to IP interfacing with regards to the Netstructure PBX/IP Media gateway product line. In addition, my secondary focus was working closely with vendors offering tightly integrated VoIP solutions such as Microsoft Exchnage Unified Messaging and IBM Lotus Sametime using these devices as well as the design and development of product training classes, certification programs for user and administrative positions, and product documentation collateral.