I looked everywhere to find Exchange 2007 VHD default password but no luck. If you had downloaded Exchange 2007 with Windows 2003 and you are trying to login, you will get a screen with following inputs, fill out the way I have givenbelow:

Username: Administrator
Password:  Evaluation1
Log on to: LITWAREINC

Package details for Exchange 2007 VHD:

Microsoft Exchange Server 2007 SP1 VHD
This download comes as a pre-configured VHD. It enables you evaluate Microsoft Exchange Server 2007 SP1.

Google Update software is used to keep Google based applications up-to-date on your system. Google Update keeps track of downloaded softwares (Google Toolbar, Google Earth etc.) and as soon as there is download available, it downloads the update by default. If you are also getting tired of seeing GoogleUpdate.exe running in Windows Task Manager, you have several options.

  1. Uninstall Google Updater

    You can follow regular steps of uninstalling software on your windows. Start -> Control Panel -> Add Remove Programs you will see “Google Updater” listed in Add Remove Programs window and click on Remove. Although this is the cleanest method,it is not the permanent solution. Next time you would like to download a Google Software, Google Updater will be installed automatically and you will end up dealing with same crap.
    google-updater.gif

    With this step, you will uninstall Google Update Software.

  2. Remove Google Updater from Scheduled Tasks

    Although Google claims to be “angle” and “not being any devil”, it really acts like one when it comes to Desktop Software. They are very persistent to keep running Google Update, Google Notifier and other Google software applications in the background of every Windows user. You will see one example of it with Google Update. As soon as you install Google Update software, it adds itself to Scheduled Tasks and unless you are a pro user of some kind, you will not realize this. You can check more details of this argument on “Why Google’s Software Update Tool is Evil“.

    Here are a few reasons why an always-active daemon (software speak for a tiny app that runs in the background) for handling software updates is a bad idea:

    1. It opens up an always-on tunnel to Google. While Google may be confident its update servers will never be compromised, how confident are you? If a third party gains control of that server, it can inject nearly any code it wants into your machine.
    2. It’s always on, always looking for update. On an expensive, pay-by-the-megabyte EVDO network? Google Updater doesn’t care and will suck down any available updates without asking, costing you money.
    3. Google updates Google Earth or Picasa or Gtalk, but the update ends up having a bug that wipes data from your drive. Sorry, too late — the auto-updater already grabbed the latest version without asking. Kiss your data goodbye.
    4. Administering a large network that needs to be locked down and tightly controlled? Cross Google software off your list. All the above problems apply, but they’re cascaded across your network for added headaches.

    In order to remove Google Update keep running in the background, you can go under Scheduled Tasks by; Start -> Programs -> Accessories -> Systems Tools -> Scheduled Tasks

    You should remove all Google Update tasks on this window.

    google-updater-scheduled-tasks.gif

When you are trying to get hardware details for Linux machines, it seems very challenging at first but you have variety options and it is quiet easy. Some includes using custom scripts and existing resource folders(ex: dmesg, /proc) or by some applications like hwinfo and lshw.

In this article we will mention about different methods to get the hardware details from your Linux OS. These tips are mainly for Redhat, Suse and Debian and different distros might include little or more details for the hardware depending on the kernel levels.

1- Hardware Details on Linux using custom script:

This script will get almost everything you would need using existing messages or applications and give you a brief output.

It uses dmesg to get Memory Information
lspci for displaying information about all PCI buses in the system and all devices connected to them. By default, it shows a brief list of devices.
/proc/cpuinfo for CPU information (including cpu model, modelname (AMD Opteron(tm) Processor), Mhz (1992 Mhz)
fdisk -l –> For Hard drive and partition information
rpm -qa for the release info (mainly for Redhat) so you can remove this line for other distros.
/etc/*-release to get the Linux distro
uname -a to get the Linux Kernel level


#!/usr/bin/sh
rm  /tmp/outputecho "/n PCI info /n" >  /tmp/output
lspci >> /tmp/output
echo "/n Memory info /n" >>  /tmp/output /tmp/output
dmesg | grep -i memory >>  /tmp/output
echo "/n CPU info /n" >> /tmp/output
cat /proc/cpuinfo  /n" >>  /tmp/output
echo " HDD info /n" >>  /tmp/output
fdisk -l >>  /tmp/output
echo "/n " >>  /tmp/output
fdisk -l /dev/sdb* >> /tmp/output
echo "/n" >>  /tmp/output
fdisk -l /dev/hda* >> /tmp/output
echo "/n  Package info /n" >>  /tmp/output
rpm -qa >> /tmp/output
echo "/n Relese info /n" >> /tmp/output
cat /etc/*-release >> /tmp/output
echo "/n platform info /n" >> /tmp/output
uname -a >> /tmp/output

2- Hardware Details on Linux using tools (hwinfo, lshw):

There are different tools for different distros that you can use to get the hardware details.

On Suse, you can use: # hwinfo

You could hwinfo for Debians (apt-get hwinfo) very quickly too. It is very handy.
# hwinfo –short will give you a brief summary of your hardware

# hwinfo --short
cpu:
AMD Opteron(tm) Processor 246, 1992 MHz
AMD Opteron(tm) Processor 246, 1992 MHz
monitor:
Generic Monitor
graphics card:
ATI Rage XL
storage:
Floppy disk controller
AMD-8111 IDE
Silicon Image SiI 3114 SATALink Controller
network:
eth2                 Intel EtherExpress PRO/100 S Server Adapter
eth0                 Broadcom NetXtreme BCM5704 Gigabit Ethernet
eth1                 Broadcom NetXtreme BCM5704 Gigabit Ethernet
network interface:
lo                   Loopback network interface
eth0                 Ethernet network interface
eth1                 Ethernet network interface
eth2                 Ethernet network interface

On Debian, you can use: # lshw

# lshw -short will generate a summary output of your hardware list in a organized fashion.

H/W path            Device      Class      Description
======================================================
system     PowerEdge 1950
/0                              bus        0TT740
/0/0                            memory     64KiB BIOS
/0/400                          processor  Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
/0/400/700                      memory     128KiB L1 cache
/0/400/701                      memory     12MiB L2 cache
/0/400/702                      memory     L3 cache
/0/401                          processor  Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
/0/401/703                      memory     128KiB L1 cache
/0/401/704                      memory     12MiB L2 cache
/0/401/705                      memory     L3 cache
/0/1000                         memory     8GiB System Memory

3- Hardware Details on Linux using /proc folder:
You can get as many details as you like by just going under /proc folder and showing the contents of files. (# more meminfo)

# more meminfo
MemTotal:      8186420 kB
MemFree:         56572 kB
Buffers:        166008 kB
Cached:        4887080 kB
SwapCached:         12 kB
Active:        2886576 kB
Inactive:      4722968 kB
SwapTotal:     7807580 kB
SwapFree:      7807548 kB
Dirty:             220 kB
Writeback:           0 kB
AnonPages:     2556436 kB
Mapped:          35064 kB
Slab:           453328 kB
SReclaimable:   422408 kB
SUnreclaim:      30920 kB
PageTables:      11848 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:  11900788 kB
Committed_AS:  4229312 kB
VmallocTotal: 34359738367 kB
VmallocUsed:     27880 kB
VmallocChunk: 34359710403 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
HugePages_Surp:      0
Hugepagesize:     2048 kB

4- Listing DMI Table with dmidecode and USB devices with lsusb:

Another very effective and powerful tool is # dmidecode. dmidecode is a tool for dumping a computers DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description of the systems hardware components, as well as other useful pieces of information such as serial numbers and BIOS revision.

# lsusb is the tool to show the devices attached to USB port even more.

if you use only # lsusb it will list the ports and what’s attached to it. If you use, lsusb with -v (verbose) you will get tons of info about USB ports.

# lsusb -v

Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               1.10
bDeviceClass            9 Hub
bDeviceSubClass         0 Unused
bDeviceProtocol         0 Full speed hub
bMaxPacketSize0        64
idVendor           0x0000
idProduct          0x0000
bcdDevice            2.06
iManufacturer           3 Linux 2.6.18.2-34-default ohci_hcd
iProduct                2 OHCI Host Controller
iSerial                 1 0000:03:00.1
bNumConfigurations      1
Configuration Descriptor:
bLength                 9
bDescriptorType         2
wTotalLength           25
bNumInterfaces          1
bConfigurationValue     1
iConfiguration          0
bmAttributes         0xe0
Self Powered
Remote Wakeup
MaxPower                0mA
Interface Descriptor:
bLength                 9
bDescriptorType         4
bInterfaceNumber        0
bAlternateSetting       0
bNumEndpoints           1
bInterfaceClass         9 Hub
bInterfaceSubClass      0 Unused
bInterfaceProtocol      0 Full speed hub
iInterface              0
Endpoint Descriptor:
bLength                 7
bDescriptorType         5
bEndpointAddress     0x81  EP 1 IN
bmAttributes            3
Transfer Type            Interrupt
Synch Type               None
Usage Type               Data
wMaxPacketSize     0x0002  1x 2 bytes
bInterval             255

Search engine giant Google is having very hard time with keeping up with Better Business Bureau. There are lots of complaints about Google Adsense payment practices which is affecting many web publisher. Google Adsense Support team is terribly lacking of replying to messages or solving the issues for webmasters. The forum opened for Google Adsense Support is left to users discretion and Google Adsense Support team is not even responding to one message in the forum.

There are tens of web publisher listed under:
Please respond here if you Google has not paid you in multiple months for no apparent reason and there hasn’t been any response to their quest. Many of those webmasters who couldn’t get an answer months of months waiting period, they started filing complaints to Better Business Bureau in Santa Clara, San Benito, Santa Cruz, and Monterey. We also filed a complaint recently to this department about our Google Adsense payments. Google had sent the payments to the wrong address and after tons of messages to Google Adsense Support Team, we are left without options.

If you are experiencing similar problems with Google Adsense Payments, you can simply follow this link to file a complaint on Better Business Bureau against Google.

Google’s Better Business Bureau rating is “D” which simply means “don’t do business with Google”:

Our opinion of what this rating means:
We have enough concerns about this company (for example, their offer, customer complaints, advertising, etc.) that we recommend caution in doing business with it.

One sample complaint to Better Business Bureau:

DESCRIPTION OF PROBLEM: “Google has had numerous problems with its automated AdSense payments to its “publishers” (people who create original content that attracts internet viewers). Many like many others, it seems my account is on an invisible hold for unknown reasons. I have followed ALL the account setup instructions and pretty much worthless Help advice, providing accurate contact and bank account information for Electronic Fund Transfer. This bank account is showing as verified and no “Holds” of any kind are indicated on the account. And yet I have yet to be paid. Worse, Google AdSense has NO contact phone number or even a useful email address to resolve this problem. Further, its instructions note that if funds are “not claimed” by six month point they will be returned to the advertisers! So they are holding my money and threatening return of my earnings with no recourse. No PIN (confusing as to when/why it would be required) was ever issued and no links show up that enable me to request a new one.”

Ubuntu installations come with 640 x 480 default config on console or TTY (Teleprinter/Teletype/Teletypewriter). To change that config to something readable:

- You need to edit /boot/grub/menu.lst
- To the end there are lines:
title Ubuntu 8.04.2, kernel 2.6.24-23 server
….
….
kernel /vmlinuz-2.6.24-23…

at the end of kernel /vmlinuz line we need to a new argument ‘vga’.

I mostly use vga=791

then update grub using:

# update-grub

and reboot.

Color Depth

640×480

800×600

1024×768

1280×1024

8 (256)

769

771

773

775

15 (32K)

784

787

790

793

16 (65K)

785

788

791

794

24 (16M)

786

789

792

795