When trying to upload files from a vCenter client to a datastore in ESX  /  vCenter Server you get the error “Failed to login into NFC server”.  To solve this problem you can do any of the following:

1. Ensure there is enough space in the datastore

2, Make sure Port 901/902 are open between the VI Client to the source of the file and/or the vCenter server.

3. Make sure the DNS configuration for the host servers is on both the machine youre trying to run the vCenter Client on and on the vCenter server on.  So the software knows where all the ESX servers are.

In this particular version of Linux there is something called “udev” that remembers the networking interfaces from the cloned machine when the new one is deployed.  See the output from my “/etc/udev/rules.d/70-persistent-net.rules" file:

$ more /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x15ad:0x07b0 (vmxnet3) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:92:00:07", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

As you can see in my /etc/udev/rules.d/70-persistent-net.rules file it specifies a mac address and interface name for both eth0 and eth1.  To fix the problem go back into vCenter server and check the settings of the NIC. Under the virtual machine properties you can see what the MAC address is of the virtual NIC.  In this particular case its "00:50:56:92:00:25".  After you verify the NIC in vCenter Server log back into the client and check the /etc/sysconfig/network-scripts/ to make sure the file “ifcfg-eth0″ is there with the correct MAC address as in your “/etc/udev/rules.d/70-persistent-net.rules" for eth0.
[root@localhost ~]# more /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=”eth0″
BOOTPROTO=”dhcp”
HWADDR=”00:50:56:92:00:07″
IPV6INIT=”yes”
IPV6_AUTOCONF=”yes”
NM_CONTROLLED=”yes”
ONBOOT=”yes”

Once you have the MAC address matching in all three locations (/etc/sysconfig/network-scripts/ifcfg-eth0 , /etc/udev/rules.d/70-persistent-net.rules, and the network settings for the virtual machine) reboot the system and networking should be restored on eth0.  Hope that helps!

When installing CentOS 6 you’ll have the option of what type of server/system you want to install. The default is a minimal install but you have many other optins as well.   By mounting http://mirror.centos.org/centos-6/6/os/x86_64/images/install.img and looking at /usr/lib/anaconda/installclasses/rhel.py you can see the choices are as follows:

Minimal Desktop: base, basic-desktop, core, debugging, desktop-debugging, desktop-platform, directory-client, fonts, input-methods, internet-browser, java-platform, legacy-x, network-file-system-client, print-client, remote-desktop-clients, server-platform, x11

Minimal: core

Basic Server: base, console-internet, core, debugging, directory-client, hardware-monitoring, java-platform, large-systems, network-file-system-client, performance, perl-runtime, server-platform

Database Server: base, console-internet, core, debugging, directory-client, hardware-monitoring, java-platform, large-systems, network-file-system-client, performance, perl-runtime, server-platform

Web Server: base, console-internet, core, debugging, directory-client, java-platform, mysql-client, network-file-system-client, performance, perl-runtime, php, postgresql-client, server-platform, turbogears, web-server, web-servlet

Virtual Host: base, console-internet, core, debugging, directory-client, hardware-monitoring, java-platform, large-systems, network-file-system-client, performance, perl-runtime, server-platform, virtualization, virtualization-client, virtualization-platform

Software Development Workstation: additional-devel, base, basic-desktop, core, debugging, desktop-debugging, desktop-platform, desktop-platform-devel, development, directory-client, eclipse, emacs, fonts, general-desktop, graphical-admin-tools, graphics, input-methods, internet-browser, java-platform, legacy-x, network-file-system-client, performance, perl-runtime, print-client, remote-desktop-clients, server-platform, server-platform-devel, technical-writing, tex, virtualization, virtualization-client, virtualization-platform, x11

This is how you return a G2 back to stock firmware. In order to do this you need to have radio S-OFF. Also make sure that gfree_verify returns secu_flag = 0 before following the steps outlined below.

1. First check to see if your main version is higher than 1.19.531.1

If the current main version is higher than what you want to install you have to change the main version number in the misc partition. To do this you can use misc_version..
download the file and extract it. In a command prompt type the following from the misc_directory:

c:\> adb push misc_version /data/local/tmp/misc_version
c:\> adb shell chmod 777 /data/local/tmp/misc_version
c:\> adb shell
# /data/local/tmp/misc_version -s 1.19.531.1
# exit

The above commands create a backup pf the misc partition 17 on the sd card with the name “part17xxxxx.bin”

2. Next install the stock G2 rom called

“PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip” you can Google this and download it from many different websites. Again go to the directory where you downloaded the file and type the following:

c:\> adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip

Shutdown the phone and remove it from the computer. Next, boot into hboot by holding “volume down” and “power”. The hboot should automatically load the PC10IMG.zip and ask you to update. Press “volume up” to start the update process. The screen goes dim for a little but will come back up and complete the process. This process will replace fake S-Off engineering hboot.

3. Radio S-ON and original CID

The 2 ways to get radio S-ON and the original CID are:

a. Restore the backup of your partition 7. This will set secu_flag = 1 and CID = T-MOB010 and will also bring back the SIM-lock data.
b. Use gfree to set secu_flag = 1 and CID = T-MOB010.

Both scenerios require you to use temporary root. To do this you can use psneuter

Gaining temporary root:

Since you loaded the stock ROM you must now re-enable debugging on the phone. Go to “Applications -> Development” and check “USB debugging”.

Next go to the directory of the psneuter command you downloaded and type:

c:\> adb push psneuter /data/local/tmp/psneuter
c:\> adb shell chmod 777 /data/local/tmp/psneuter
c:\> adb shell /data/local/tmp/psneuter
c:\> adb shell

you should now have temporary root denoted by the # prompt

3. Use gfree to get radio S-ON and the original CID

If you lost your partition 7 backup or you do not want to restore the simlock data you can use the -c and -s options of gfree to set the CID and the S-ON flag.

ON YOUR PC:

Get gfree_06.zip that is attached to this page [4].

Unzip gfree_06.zip to a place on your computer. Open a terminal or command window, navigate to where the files are on your computer, and type:

c:\> adb push gfree /data/local/tmp/gfree
c:\> adb shell chmod 777 /data/local/tmp/gfree

gfree should now be in your phone at /data/local/tmp

IN THE ROOT SHELL (in the first terminal/command) : Now run:

# /data/local/tmp/gfree -s on -c T-MOB010
# sync

Remove the PC10IMG.zip and the tools from the phone

# rm /sdcard/PC10IMG.zip
# rm /data/local/tmp/psneuter
# rm /data/local/tmp/gfree

Disconnect your phone from USB and power it down.

Boot into hboot by holdingwhile powering on.

The heading should now read: “VISION PVT SHIP S-ON”

Thanks to the XDA Developers and their tutorial for help on this.

1. Make sure your column of words are in column A.

2. In column B, cell b2 put =A1 & “,” & A2

3. In column B, cell b3 put =B2 & “,” & A3

4. All you have to do now is copy the formula down to the rest of the cells. The last cell in column B should have all your terms from column A in a comma delimited list.

Hope that helps!

If you initially created your VMWare disk into multiple 2gb files and would like to convert them back into a single file use the following command:

vmware-vdiskmanager.exe –r thefirstfile.vmdk –t 0 newlargefile.vmdk

While the headset is blinking red, press: Noise Assassin button, Talk button, Talk button, Noise Assassin, Talk, Talk.

vgscan # This will show you the name of the Volume Group
vgchange –available y VolGroup00 # Activates the Volume Group and the Logical Volumes in it
lvscan # Shows the Logical Volumes as active; the devices in /dev it mentions should now exist
exit # Exits you to the prompt

Step 5. Resize the filesystem with command:

e2fsck -f /dev/VolGoup00/LogVol00 # fsck on the filesystem
resize2fs /dev/VolGoup00/LogVol00 xxG # resize the file systems to xx GB; xx should be less than the current fs size
e2fsck -f /dev/VolGoup00/LogVol00 # Do another fsck on the filesystem; fix any errors which appear

Step 6. Run lvm again and type:

lvreduce -L xxG /dev/VolGoup00/LogVol00 # Resize the LV to xx GB; xx should be the same as above
exit # Quit, return to the prompt

Step 7. Do another filesystem check:

e2fsck -f /dev/VolGoup00/LogVol00 # Do another fsck on the filesystem; fix any errors which appear

Step 8. Remove the CD and reboot.

machinebios.bootDelay = “5000″

or

bios.bootdelay = 5000

For example, a setting of 5000 gives you 5 seconds to hit F2.