Wednesday, November 14, 2012

Official Android 4.2 Jelly Bean update for Nexus 7

It is out. So hit that update button.




The first change you'll see is when you wake the display up. It shows a highlighted boxes, one with an add sign, just beside the clock, indicating that you can add another widget for the lock screen. The digital clock looks a little different too with the hours bold.



The analog clock looks prettier too. Minimalistic yet modern and pleasing.



It might just be me but the app menu is nicer too with the icons seems to stand out as the black looks darker.

And when the keyboard is activated, you can immediately try out the 'gesture' typing as shown. From my little time with it, I feel it is easier than Swype.


First impression so far is positive coupled with a much more responsive system

Monday, September 3, 2012

Motorola Atrix 2 ICS

Update for Asia Pacific is released today. All I can say is that it is awesome!

Hit the update button!


Sunday, June 3, 2012

Installing and Configuring Citrix XenApp 6.0 Fundamentals


Citrix XenApp 6.0 Fundamentals

System Requirements

  1. Citrix XenServer 6.0
  2. Citrix XenApp 6.0 Fundamentals (XAF6)
    1. With Hotfix Rollup Pack 1 for Citrix XenApp 6 for Microsoft Windows Server 2008 R2
  3. Windows Server 2008 R2 Standard Virtual Machine (for XenApp)
    1. without XenServer Tools installed
    2. without Service Pack 1
    3. with .Net Framework 3.5.1 Roles
    4. with Remote Desktop Services (Remote Desktop Session Host and Remote Desktop Licensing) Role
    5. with Internet Information Services (IIS)  Manager Role
  4. Windows Active Directory Domain Controller (DC)
    1. with Certificate Authority (CA)


Installation Procedure

Preparing host machine for virtual machines

  1. Install XenServer 6.0



Creating a Windows Server VM (for DC)

  1. Install a compatible Windows Server operating system that can act as an Active Directory Domain Controller with hostname DC

  1. Launch dcpromo and configure domain

  1. Install and configure DHCP
    1. Configure scope to issue DNS pointing to DC’s IP address

  1. Install and configure CA



Creating a XAF6 VM

  1. Install Windows Server 2008 R2 (without SP1) with hostname XAF6

  1. Join domain as a member.

  1. Request for Web Server certificate from DC CA using CA Web Services at https://CAServer/certsrv

  1. Enter Name with server FQDN
  2. Download and install server certificate into Local Computer > Personal folder
  3. Download and install CA certificate into Trusted Root Certification Authorities

  1. Install .Net Framework 3.5 Role

  1. Install Remote Desktop Services (Remote Desktop Session Host and Remote Desktop Licensing) Role
    1. Configure Remote Desktop Licensing

  1. Download and install Citrix XenApp 6.0 Fundamentals trial.
    1. Enter a valid email address during registration to receive the license code

Configuring XAF6

  1. Trial License Allocation
    1. Login to MyCitrix (or create a new account if you do not have one)
    2. After login, go to: My tools>Choose a Toolbox>Manage Licenses>Allocate.
    3. Select the Don't see your product? link located at the top right corner of the Allocate web key page.
    4. Enter the license code(s) displayed above in the Find your license dialog box and click Continue. When the Host Name warning page displays, select Continue.
    5. Enter the actual server hostname
    6. Download the license file
    7. Launch Citrix XenApp Quick Start > Licensing and install the license


  1. XenApp Agent to accept SSL
    1. Launch IIS Manager and edit Bindings for Default Web Site to add https port 443 with server certificate downloaded earlier selected



  1. Publishing Applications
    1. Install applications on XAF6
    2. Go to Publish Applications and choose the application to publish.
    3. Select the users to publish the application to


  1. Publishing Printers
    1. Install printer(s) on XAF6
    2. Go to Publish printers and choose the printers to publish
    3. Select the users to publish the printers to


Wednesday, April 18, 2012

GUI for SUSE Linux Enterprise Server guests in Citrix XenServer

To enable GUI on SLES VM in Citrix Xenserver, you need to edit /etc/xinit.d/vnc and change the Port from 5901 to 5900

service vnc1
{
        type            = UNLISTED
        port            = 5900
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = nobody
        server          = /usr/bin/Xvnc
        server_args     = -noreset -inetd -once -query localhost -geometry 1024x768 -securitytypes none
        disable         = yes

Increasing VDI size on a Virtualbox VM

Update: Since v4, there is a command line to perform the following. Please refer here

You cannot actually increase the size of a VirtualBox VM VDI. What you can do instead is to copy the VDI to a new VDI with a bigger size

The steps are as follows

1. Create and add new VDI to the VM
2. Copy content of existing VDI to new VDI
3. Set the new VDI boot partition as active

To create a new VDI

1. Power off the VM
2. Open the VM Storage settings 
3. Select the controller where the current VDI is attached to
4. Click on 'Add attachment' 
5. Choose 'Add hard disk' 
6. Choose 'Create new disk'
7. Follow the wizard and specify the size you desire

To copy content of existing VDI to the new VDI

1. Choose Ubuntu iso as the virtual CD/DVD disk file for the VM. (Download Ubuntu iso if you have not already done so)
2. Start the VM and boot to Ubuntu 
3. Select 'Try'
4. Once the live Ubuntu is up, run Gparted
5. Select the existing VDI, right click and choose copy.
6. Select the new VDI, right click and choose paste.
7. Apply the changes.
8. Once successfully applied, reboot the VM

To set the new VDI boot partition as active

1. Boot the VM using the existing VDI as per normal
2. Run command prompt and type the following

diskpart
list disk
select disk n  
list partition
select partition n
active

Note: 'n' is the new VDI disk and partition number

3. Power off the VM
4. Remove the old VDI from the VM
5. Start the VM

Note: If you still unable to boot the VM with the new VDI with MBR error, you can do the following

1. Choose Windows XP iso as the VM virtual CD/DVD disk file. 
2. Start the VM and boot to Windows XP installation disk
3. Select 'Recovery Console'
4. Select the correct Windows directory
5. Run command 'fixmbr'
6. Reboot the VM.

Monday, March 19, 2012

VLAN crash course

A switch is a device that connects different devices together to form a similar physical network.

If you have two switches with devices connected to each of them, that means you have two separate physical network. In order to make them into one physical network, you join the two switches together by using appropriate connecting cable(s).

VLAN (Virtual Local Area Network) however is the total opposite of that. It allows you to create two or more separated networks on the same physical device.

The reason why VLAN is useful is because it makes no dollar sense to spend more on additional hardware just to support another network especially if it is just a small one and can fit into the current available resources. It is like having a big room separated by partitions to house two occupants rather than having two big identical rooms to house one occupant each.

This guide is meant to help you understand VLAN in the shortest time possible and hopefully allows you to plan and implement them in your network on your own.

Lets go through the technical details first. Take note, this guide is in reference to switches which is the device you will most commonly need to configure more than anything else.

Technical Terms
1. VLAN IDs

All VLANs in a switch must be identified with a number. The number to be used is directly connected to the maximum of VLANs the switch can support. If the switch supports 8 VLANs, then the ID(s) to be used must fall within the range of 1 to 8 only.

The ID are not restricted to any running order, as long as it meets the above requirements. For eg you can have two VLANs with IDs 1 and 5 and not necessarily 1 and 2.

2. Untagged/Tagged Mode

Untagged mode is the default mode and will exist in any VLAN capable/enabled switch. Untagged mode means the packet is not modified in any way as if no VLAN is configured on the switch. Simply put, in a non VLAN capable/enabled switch, all the ports on the switch is considered Untagged.

Tagged mode means that packets will be modified to identify them to a VLAN.

Using an analogy, imagine a post office that requires parcels intended for overseas destination to be marked (Tagged). If a post master receives a Tagged parcel, he knows that it is meant for overseas delivery and will inspect the destination country (VLAN ID). This automatically means that any unmarked parcels (Untagged) are for local delivery without even having to inspect the destination country.

Basic Rules

1. 
A port on a switch can support one or more VLANs subject to a maximum number of VLANs the switch can support.

2. If there is only one device connected to switch

2. If a port is configured with multiple VLANs, only one of those VLAN can be Untagged while the rest must be Tagged.

The reason for this is simple. Untagged means default. You cannot have more than one default as it will cause confusion.

Using the post office analogy, when the postmaster receives two Untagged parcels, he will assume they belong to one VLAN as there is no way to identify otherwise.

So even if it is possible to assign a port to two Untagged VLANs, it will be pointless because there is no way to identify and separate them.

3. The ID and tagging on the other end of the cable must be the same.

This means that if you set a port to VLAN ID 6 Tagged, the device at the other end of the cable must also be configured VLAN ID 6 Tagged.

Friday, March 2, 2012

Federating Microsoft Office Communications Server with XMPP

If you are trying to federate your OCS or Lync service with an XMPP domain using Microsoft Office Communications Server 2007 R2 XMPP Gateway, you will need to do the following

1. Create an SRV record on your DNS server

_xmpp-server._tcp.your-xmpp-domain-name SRV 0 0 5269 xmpp-gateway-hostname

You can test if your service record is correct by using nslookup command. The following is an example of a lookup for Google’s XMPP service.

system:~ # nslookup
> set type=srv
> _xmpp-server._tcp.gmail.com
Server: 165.21.83.88
Address: 165.21.83.88#53

Non-authoritative answer:
_xmpp-server._tcp.gmail.com service = 5 0 5269 xmpp-server.l.google.com.

2.  Install the latest patch for the XMPP gateway

3. Configure the XMPP gateway security settings to TCP dialback.

4. Set your XMPP server security settings to accept TCP dialback. You may need to disable TLS as well to force it to use TCP dialback.