Seven Tips for Troubleshooting VMware vSphere5

Here are seven tips for working with vSphere, including: Logging in via Command Line, dealing with connection problems using ssh to an ESXi host; network performance issues; possible storage problems; Log Files to View in vSphere ESXi 5; network performance troubleshooting; migrating to a virtual machine using VMotion.

By default, the ESXi host does not have ssh enabled, and the method to enable ssh can change based on whether or not the host is ESX or ESXi, and the version of the ESX/ESXi host. There are occasions when you need to login via command line using ssh to troubleshoot problems. In addition, there are alternative methods to get to a command line prompt such as DCUI and TSM, depending on the version and type of host. The ability to manage the host at a command line prompt will allow you to use many different Unix based commands as well as commands introduced by VMware called esxcli commands. The ability to make changes to network, storage and other critical parts of the host, depending on the state of the host, might only be possible at a command line prompt.

In vSphere 5, an administrator can manage the ESXi host from the command line using esxcli commands, such as esxcli network vswitch standard. The esxcli command set was first introduced in vSphere 4.0 and allows an administrator to manage many aspects of the ESXi host from the command line. The commands are available using the Direct Console User Interface (DCUI) to access the ESXi shell, using a remote application like putty to ssh into the host, or through the vSphere Command-Line Interface (vCLI).

The DCUI is similar to the BIOS of a computer and allows you to interact with the host through the console of the ESXi server to perform initial basic configuration and can also be used for troubleshooting using text-based menus. You can use the DCUI to enable local and remote access to the ESXi Shell.

A second method to access the command line is by utilizing an application such as putty to ssh into the ESXi host. In order for ssh to work you must enable the sshd service on the ESXi host.

A third method to run command line commands is thru vCLI. The vCLI provides a command-line interface for ESXi hosts. Multiple ESXi hosts can be managed from a central system with vCLI installed on it. The central system that VMware uses is a downloadable appliance called vMA. vMA enables administrators to run scripts that interact with ESXi hosts and VMware vCenter Server systems without having to authenticate each time. vMA is easy to download, install, and configure through the vSphere Client.

Direct Console User Interface (DCUI)

When the DCUI screen appears, press F2 Customize the System and login as root.Scroll to Troubleshooting Options and press Enter.Choose Enable ESXi shell and press Enter.Press Esc until you return to the main DCUI screen.

To enable ssh from the vsphere Client

Select the host and click the Configuration tab.Click Security Profile in the Software panel.In the Services area, click Properties.Select ssh and click Options.Change the ssh options. To change the Startup policy across reboots, click Start and stop with host and reboot the host.Click OK.

First method from the Direct Console User Interface (DCUI)

Hit Alt+F1, if TSM is enabled, log in with root credentials, elseOnce the DCUI screen appears, press F2 and login as root to enable the TSM.Navigate down the screen and choose Troubleshooting Options, and press enter.Troubleshooting Options provides additional options for TSM in ESXi 4.1.
Local Tech Support - Access command line via Alt+F1 on the console. Remote Tech Support (ssh) - ssh access on the console of the ESXi host. Modify Tech Support Timeout - Tech Support Mode will be disabled after a certain amount of time.

Second Method from the vSphere Client

From the vSphere Client, select the host and click Configuration tab.Then choose Security profile and Properties.Here you can enable Local Tech Support as well as Remote Tech Support (ssh). They are enabled
If the Daemon is running, and disabled if the Daemon is Stopped.
If you want to enable either mode, highlight the mode, then choose Options.Now you can modify the Startup Policy or change the Service to Start, then click OK.

View the original article here

Seven Security Myths of Windows 7

Network security is everyone's concern, and this applies to computer security as well. Many security breaches occur due to user ignorance of basic security principles, not malicious intent. Network and computer security are like an onion - there are multiple layers. Good security begins with understanding what you can do to keep your systems safe and implementing a layered approach. If you depend on one program or feature to secure your computer, then when (not if, but when) that dependency is breached, you may have personal information stolen or even have your computer taken over.

Not all versions of Windows 7 are created equal. This can be confusing to home users and small businesses that do not have an Active Directory domain. Many features that you have heard about when it comes to improved security are only found in the more expensive editions. In fact, only the Ultimate and Enterprise editions contain all of the security features. The Professional edition does have Group Policy controls and Encrypting File System (EFS), but does not include AppLocker or BitLocker. The Home Premium version does not even have the reduced security features found in the Professional Edition. In short, you will have to pay more if you want the more advanced security features, so be careful to purchase the edition of Windows 7 that meets your security requirements. There is not a "one-size-fits-all" version of Windows 7, and there definitely is not an a la carte edition.

This may also be seen as the Principle of Least Privilege. In this principle, users or processes must be able to access only the information and resources required for their specific roles. In this case, we are looking at applying the least-privileged user account (LUA). Many home users are also members of the local administrators group, giving them complete access to the system. In most corporate environments, this is not a safe security practice. Granting administrative access - even on a local computer - can lead to numerous security vulnerabilities. The User Account Control (UAC) component can limit changes being made to a computer that require administrator level permission. The UAC will notify a user if a change is attempted and if the user is an administrator, than the user can click Yes to continue. If the user is not an administrator, than someone with an administrator account on the computer will have to enter their password for the user to continue. Relying solely on the UAC to provide security for changes to your system is an invitation to disaster - especially when UAC is turned off completely.

Network administrators have Software Restriction Policies that can be implemented to control the behavior of software (what can or cannot run). AppLocker can extend the capabilities of Software Restriction policies. Now, an administrator can restrict or permit applications to run based on unique identities of files and to specify which users or groups can run these applications. With AppLocker, an administrator can control the type of applications that can run, which user or security group can run a program, create exceptions for programs, and even use PowerShell to control AppLocker. In short, AppLocker is a powerful utility for network administrators; it cannot replace a more comprehensive security model including a robust anti-virus program. Trojan programs can still be used to install malware on a system and users can be tricked into running other malware programs.

BitLocker Drive Encryption is a feature available on Windows7 Enterprise and Windows 7 Ultimate (another myth-conception of Windows 7). BitLocker and BitLocker To Go provide another layer of security to limit the potential loss of data through the loss or theft of a computer. BitLocker To Go can be used to protect USB flash drives as well as external hard drives. Not all computers can use BitLocker or BitLocker To Go. To use BitLocker, the hard disk on the computer must have two partitions, the operating system and active system partition must be formatted with NTFS, and the BIOS must support Trusted Platform Module (TPM) 1.2, though there is an exception. If the computer does not have a TPM of 1.2 or higher, you can use a USB drive to store the encryption keys. While this is an excellent method to secure your data, BitLocker or BitLocker To Go should be used in conjunction with other security methods to control access to your data.

There is always a secure, remote connection for Windows 7 users. Well, sort of. You would need to configure DirectAccess to provide for a secure automatic remote connection. DirectAccess allows users of Windows 7 Enterprise and Ultimate editions to make remote direct connections to a Windows Server 2008 R2 (as well as Windows 8 Server and beyond) server without having to use a VPN connection. Currently, users must use a VPN connection in order to make a secure remote connection.

View the original article here