Want to give it a try?
Check out the live images!
Want to install it?
Choose your favorite installation media among Blu-ray Discs, DVDs, CDs and USB sticks.
Already on Debian and want to upgrade?
You are just an apt-get dist-upgrade away from Wheezy! Find how, reading the installation guide and the release notes.
At the office we recently built two white box, built it yourself servers (lego’s). I called them Lego’s due to the fact they are build your own types and not OEM. For each of these powerhouse systems we got 3ware 9650SE RAID controllers (3ware 9650SE-4LPML PCI Express Lanes: 4 SATA II Controller Card RAID Levels 0, 1, 5, 10, Single Disk, JBOD, KIT).
After getting ESXi 5.x installed to a USB Stick to boot from I encountered an issue where the 3ware controller was not recognized by the system. Well this could only be one thing. Drivers.
This is where installing of the controller driver fun begins.
I first navigated to the LSI website and their support page to download the drivers for these controllers. Where I was able to find drivers for VMware ESXi 5.0 update 1 driver for 9650SE/9690SA
After downloading the zip archive of the driver, I extracted and used WinSCP to upload the drivers to the /tmp directory of my ESXi 5.x hosts.
I then logged into the ESXi 5.x using SSH with Putty.
After changing my directory to /tmp I ran the following command:
esxcli software vib install -v /tmp/scsi-3w-9xxx-2.27.08.036-1OEM.500.0.0.472560.x86_64.vib
Soon after I got the following messages:
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: LSI_bootbank_scsi-3w-9xxx_2.27.08.036-1OEM.500.0.0.472560
VIBs Removed:
VIBs Skipped:
After the install I followed the instruction to reboot and after the systems were up and running again I was able to see the controller and create my new datastores.
After converting a Linux (Debian) machine using VMware vCenter Converter Standalone, to have a copy of my virtual machine running on ESXi 5.x in VMware Player. I encountered the following error on start-up: buslogic SCSI adapter is not supported for 64-bit guests
There isn’t an option in the VMware Player to change the scsi type, so I turned to editing the virtual machine’s .vmx file changing the following steps.
Long story short; I wanted to have VNC Console access to my VMware ESXi 5.x guest systems. Now knowing what I wanted I needed to find a way out. After trying many steps I narrowed down the steps that work perfectly in ESXi 5.
First thing to know is that you require a custom firewall rule in ESXi to allow network access to your guest machines that are enabled for VNC console access. This firewall setting does not exist by default.
The following steps should help you create the new rule:
Using vi or in my case WinSCP I navigated my way to the following location /etc/vmware/firewall and created a file named VNC.xml
Using the built in editor I added the following information:
<ConfigRoot>
<service>
<id>VNC</id>
<rule id=’0000′>
<direction>inbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>5901</begin>
<end>5910</end>
</port>
</rule>
<rule id=’0001′>
<direction>outbound</direction>
<protocol>tcp</protocol>
<porttype>dst</porttype>
<port>
<begin>0</begin>
<end>65535</end>
</port>
</rule>
<enabled>true</enabled>
<required>false</required>
</service>
</ConfigRoot>
After saving the VNC.xml file I logged into my ESXi Console (via SSH) and issued the following command to restart the firewall service and enable my new custom firewall rule: esxcli network firewall refresh
Next I powered off the guest virtual machine I wanted to enable VNC access for and added the following lines:
remoteDisplay.vnc.enabled = “TRUE”
remoteDisplay.vnc.password = “password”
remoteDisplay.vnc.port = “5901″
The above lines can also be added via the vCenter Interface by doing the following:
Go to ‘Edit Settings’ for the virtual machine
Then the ‘Options’ tab
Select ‘General’ under the Advanced section
Click the ‘Configuration Parameters’ button and add the lines from above 1 by 1
Notes:
The following steps are what I used to disable this warning on top of my VSphere Client to manage my ESXi 5.x servers.
Another way to resolve this is to use the esxcli command via the local console or over ssh.
Connect to the ESXi host using the root credentials and run the following command:
esxcli system settings advanced set -o /UserVars/SuppressShellWarning -i 1
For the source of this info and additional steps please check out the VMware KB 2003637
I have been testing several free SIP Apps to go along with my FreePBX Asterisk server and after using an excellent app CSipSimple for a while I wanted to test how one of the paid variants would compare.
This had me looking right at CounterPath Corp’s Bria VoIP Softphone for Android. An app suited for corporations needed and at this point my own. It simply works great right out of the box. I had this setup in under five minute’s time. The sound quality is crisp both on 3G (H+) and Wireless There are many advanced features that I haven’t even played with yet. I may not need to as there doesn’t seem to be a need to fix what isn’t broken at this point.
The phone device I am using is a Samsung Galaxy S2 (i777 AT&T model).
For those of you who are serious about the applications you use and want to use a reliable one this is the app for you. Best of all, there is customer support if I find myself needing them.
Highlights
Telephony Features
Advanced Features
Accessories
The following accessories are supported:
ITSP/Operator/Enterprise Features
Feature Info Source: CounterPath’s Website
I am in the process of moving VirtualBox vdi’s over the VMware ESXi host so what better chance is there to post the process I am taking to make this happen. To perform this “magic” trick you will be using the VBoxManger tool to clone the VirtualBox disk into VMware formatted disk types.
I am using the following steps to convert my disks.
Once completed you have your new VMDK disk image which you can then copy over to a VMware Player, or ESX host to run from there.
Please note: You can do similar to above with other disk formats, however in this post I am just covering VDI to VMDK.
More info on VBoxManage here
Did you like this post, please stop by my Facebook Page and give us a Like
This past weekend I installed a fresh new FreePBX (FreePBX 2.11.0) distribution with Asterisk 11.3. The install of FreePBX and Asterisk is made simple and once installed you have a fully functioning PBX waiting for your phones and trunks to connect.
I don’t have a trunk provider at this time so I decided to use Google Voice as my solution. The process of setting this up via the FreePBX WebUI was simplified and simply works. Best of all you have this all configured and running in under 10 min’s (5 min’s if you have done this more than once).
Here are the steps I took to get this up and running.
Requirements:
After you have installed FreePBX and are up and running you will need to enter the webUI (http:// pbx address). From here you do the following:
Under Connectivity
Under Applications
Under Connectivity
Lastly you want to edit your sip settings
Under Settings
At this point you should be all set to test with your SIP Client. Simple log in using the extension and secret (password). Once registered attempt to place a phone call. Open port 5060 on your firewall and you can use this to connect to your server remotely.
Did you like this post, please stop by my Facebook Page and give us a Like
I have been using the Windows 8 Enterprise for several months this way for testing rather than backup my data and reinstall the OS just to reinstall my applications, followed by configuration tweaks, which can be time consuming. I have started extending the trail to give me more time.
The process of extending a trial is called ‘rearming’.
Here is how I have done so:
If you just want the expiration date info type: slmgr /xpr
And finally what you have been waiting for: The rearm command.
Like the ones I mentioned above all you need to do is type: slmgr /rearm then reboot the computer.
This can be done no more than 3 times of the life of the install of the Windows 8 system. If you time it correctly you could have Windows 8 for free for 270 days. How cool is that.
Info on my test machines:
1 Physical Machine and 2 Virtual Machines (VMware)
Similar to my previous post SharePoint 2010 – Deploying Webpart Solution, the upgrade process of a Webpart Solution you have a few steps to take to make this all happen.
As I did in my previous post:
I copied the webpart to the local disk of my SharePoint 2010 server. Placing it in a folder c:\install this time around I am not going to be running the command Add-SPSolution c:\install\SharePointWebpart.wsp as it already exist. If you do you will get an error stating that the solution already exists.
What you will need to do is run the following command for example: Update-SPSolution –Identity SharePointWebpart.wsp –LiteralPath c:\install\SharePointWebpart.wsp –GACDeployment
For more info on features and solutions cmdlets: http://technet.microsoft.com/en-us/library/ff607724.aspx
Follow Me!