Tuesday, January 17, 2012

rename ESX host

To rename a VMware ESX host:
*If the ESX host is part of a Cluster, remove it from the cluster.
*If the ESX host is managed by VirtualCenter / vCenter, disconnect and remove the ESX host from the cluster.
*Make the modifications in your DNS environment to reflect the correct name and IP association for the new name.
*Log in as root to the console of ESX host.
*Using a text editor (I prefer nano ) change the name and domain name, if applicable, of the host in these files:


nano /etc/hosts
nano /etc/sysconfig/network


Execute this command where hostname is the new FQDN hostname for the ESX host:

esxcfg-advcfg -s hostname /Misc/HostName

Reboot the ESX host.
Note:
The iSCSI Qualified Name used for iSCSI storage configuration is based on the hostname of the ESX host. If you change the hostname of the ESX host, make sure to review your iSCSI software initiator configuration
Join the ESX host to VirtualCenter / vCenter and clusters

reference:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010821





Wednesday, January 4, 2012

Windows 2008 R2 Best Practice Analyzer (BPA)

How to install:
BPA is installed by default on all editions of Windows Server 2008 R2 except the Server Core installation option.

How to use BPA:
You can open BPA in the Server Manager console by opening the home page for a server role that supports BPA.
To open BPA in Server Manager
1.Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.

2.In the tree pane, open Roles, and then select the role for which you want to open BPA.

3.In the details pane, open the Summary section, and then open the Best Practices Analyzer area.

ow BPA works


BPA works by measuring a role’s compliance with best practice rules in eight different categories of a role’s effectiveness, trustworthiness, and reliability. Results of measurements can be any of the three severity levels described in the following table.


*Severity level

Description
Noncompliant
Noncompliant results are returned when a role does not satisfy the conditions of a rule.

Compliant
Compliant results are returned when a role satisfies the conditions of a rule.
Warning
Warning results are returned when a role is compliant as operating currently, but may not satisfy the conditions of a rule if changes are not made to its configuration or policy settings.
Reference:
http://technet.microsoft.com/en-us/library/dd759260.aspx

Ubuntu vmware image template

these are the steps to configure a newly deploy Ubuntu VM , in my case I use a std template
1.- Remove PCI using the following command:

Sudo nano /etc/udev/rules.d/70-persistent-net.rules


2.-Re-ip the VM
Sudo nano /etc/network/interfaces



Rename host

Sudo nano /etc/hostname


sudo /etc/init.d/networking restart


Restart computer
Sudo reboot

Shavlik 8026 Problem

I'm seeing the following error on my Windows Servers with Hsavlik Netprotect installed:

Event Type: Information
Event Source: ShavlikPatchMgmt
Event Category: (8)
Event ID: 8206
Date: 9/8/2009
Time: 3:47:54 PM
User: XX\XX
Computer: XXXX
Description:
The description for Event ID ( 8206 ) in Source ( ShavlikPatchMgmt ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \\XXX.XXX.XXX.X\C$\WINDOWS\ProPatches\Patches\, C:\WINDOWS\ProPatches\Patches\.

instructions:

1. Open a CMD prompt and navigate to C:\Windows\ProPatches\Scheduler
2. Run STSchedEx.exe /remove
3. Delete the \Propatches folder
4. Open regedit and delete: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Shavlik\Scheduler
try running the job again.

reference:
http://forum.shavlik.com/viewtopic.php?f=35&t=540&p=34323