Event id 59

Disk x will not be used because it is a redundant path for disk y

Event ID: 59
Disk 7 will not be used because it is a redundant path for disk 2

The above warning comes when there is a problem with the multipathing software or problem in storage level zoning.

Windows can detect if a lun has multipule path, sytem activly uses the first path and keeps the other path for redundancy. Incase if there is a problem with multipathing software or miconfiguration in zoning, we may see two disk of same size in diskmgmt.msc.

We need to check if both x and y disks are of same size on diskmgmt.msc and the status of both the disk.

Acction Plan
1. Zoning configuration need to be checked and rectified.
2. Multipathing software need to be reinstalled.

Remote desktop slow login- fix

The below registry settings can be used to ignore the user logon related errors which cause delay in login process. This can be used as a workaround to fix delay user login issues.

Take backup of your registry before doing any changes.

1. Click Start, click Run, type regedit in the Open box, and then click OK.

2. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

3. Click Edit, point to New, and then click DWORD Value.
4. In the New Value #1 box, type IgnoreRegUserConfigErrors, and then press ENTER.
5. Right-click IgnoreRegUserConfigErrors, and then click Modify.
6. In the Value data box, type 1, click Decimal, and then click OK.
7. Exit Registry Editor.

Activate Windows through command if phone activation is disabled

To Activate windows manually ( in case if the phone activation is disabled on the server) try the below steps.
1. On command prompt  give the below command to see the system id.
slmgr.vbs –dti

2. Here on this screen pass Ctrl+ C to copy the text and paste it in a notepad file.

Please place gaps( space or -) in between every 6 digit ( it will be easy to read the blocks while entering the code on phone, 6 digit in one block)
3. Then call the Microsoft to activate the windows.  (For UK – 8000188364 )
It will ask for the system Id, then provide the blocks obtained from the above steps one after other, once complete it will read back the confirmation id for you, make sure you note it down.
4. The confirmation id will be 8 blocks having  6 digits each.  Note down each blocks on notepad.
 And at last remove the “spaces” or “–“  if you have entered in between the blocks while writing it.

 
5. Now enter the below command to activate the window
Slmgr.vbs /atp  above _confirmation_id

6. Check the system properties to see if it gets activated.

User profile cannot load due to insufficient system resources

This article is documented on  “http://support.microsoft.com/kb/935649”

When you try to log on to a Microsoft Windows Server 2003-based terminal server, you receive the following error message:

Windows cannot load the user’s profile but has logged you on with the default profile for the system.
Detail: Insufficient system resources exist to complete the requested service.

The below events you will see on the server

Event ID 1505

Event Type: Error
Date: date
Time: time
Event ID: 1505
Source: Userenv
User: Example\Username
Computer: ServerName
Description: Windows cannot load the user’s profile but has logged you on with the default profile for the system.
DETAIL – Insufficient system resources exist to complete the requested service.

Event ID 1508

Event Type: Error
Date: date
Time: time
Event ID: 1508
Source: Userenv
User: NT AUTHORITY\SYSTEM
Computer: ServerName
Description: Windows was unable to load the registry. This is often caused by insufficient memory or insufficient security rights.
DETAIL – Insufficient system resources exist to complete the requested service. for C:\Documents and Settings\Username\ntuser.dat

In addition you may also see event id 333 on the system event log. (http://support.microsoft.com/kb/970054)

CAUSE

You experience this problem if many users are logged on to the terminal server.

Basically this happens if the pagedpool is temporarily exhausted due to load or some other reason.  It has been also noticed that the error stops automatically when user load reduces.

You can use Process Explorer to see the Pagedpool size and its current utilization. ( To see the Pagepool limit symbols need to be configured on for process explorer)

Monitor the server for few days and see the utilization, if it is always near to the limit then increase the page file limit and configure to trim processes  when it reaches 60%. Perform below mentioned steps.

 Screenshot taken just after the issue fixed automatically

If it occurs frequently then the below steps can be followed

follow the steps: ( http://support.microsoft.com/kb/935649)

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
3. On the Edit menu, point to New, and then click DWORD Value.
4. In the New Value #1 box, type PoolUsageMaximum, and then press ENTER.
5. Right-click PoolUsageMaximum, and then click Modify.
6. In the Value data box, type 60, click Decimal, and then click OK.
7. If the PagedPoolSize registry entry exists, go to step 8. If the PagedPoolSize registry entry does not exist, create it. To do this, follow these steps:
   1. On the Edit menu, point to New, and then click DWORD Value.
   2. In the New Value #1 box, type PagedPoolSize, and then press ENTER.
8. Right-click PagedPoolSize, and then click Modify.
9. In the Value data box, type ffffffff, and then click OK.
10. Exit Registry Editor, and then restart the computer.

Ifconfig command is not included in ESXi 5.0

Linux commands for retrieving networking information are not included in the ESXi Shell. You can instead use ESXCLI commands.

On ESXi 5.0, ifconfig information is the information for the VMkernel NIC that attaches to the Management Network port group. You can retrieve that information by using ESXCLI commands.

Also these commands will work on SSH console (Putty)

esxcli network ip interface list
esxcli network ip interface ipv4 get -n vmk<X>
esxcli network ip interface ipv6 get -n vmk<X>
esxcli network ip interface ipv6 address list
You can retrieve information about DNS with the esxcli network ip dns command in the following two namespaces:
esxcli network ip dns search
esxcli network ip dns server

For information corresponding to the Linux netstat command, use the following ESXCLI command.
esxcli network ip connection list

Configuring complete memory dump for NMI crash

 

 

Enable complete memory dump:

 

Step 1:  Create a paging file

 

a)      Click Start , right-click Computer , and then click Properties . 

b)      Click Advanced system settings on the System page, and then click the Advanced tab. 

c)       Click Settings under the Performance area. 

d)      Click the Advanced tab, and then click Change under the Virtual memory area. 

e)      Select the system partition where the operating system is installed.

Note To enable the system partition, you have to click to clear the Automatically manage paging file size for all drives check box. 

f)       Set the value of Initial size and Maximum size to the amount of physical RAM that is installed plus 1 megabyte (MB) under the Custom Size button. 

g)      Click Set , and then click OK three times. 

 

Step 2: Create a complete memory dump file

 

a)      Click Start , right-click Computer , and then click Properties . 

b)      Click Advanced system settings on the System page, and then click the Advanced tab. 

c)       Click Settings under the Start and Recovery area, and under Write Debugging information, make sure Complete memory dump is selected. 

 

Note By default, Complete memory dump is disabled. You can enable the option if your computer has more than 2 GB of physical RAM.

Note If you want to enable the Complete memory dump option, manually set the CrashDumpEnabled registry entry value to 1 under the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

 

By default the dump file will be generated under system disk, if your system disk has no enough space, you could change the path manually:

a)      Click Start , right-click Computer , and then click Properties . 

b)      Click Advanced system settings on the System page, and then click the Advanced tab. 

c)       Click Settings under the Start and Recovery area, and then replace the path with an appropriate value in the Dump file field. In other words, you can change the path from %SystemRoot%\Memory.dmp to point to a local drive that has enough disk space, such as E:\Memory.dmp. 

 

Note A network drive, a shared drive, or a Network Attached Storage (NAS) drive cannot be used as a destination for a memory dump file because it might not be available before the file copy begins.

 

Step 3 : Enable NMI crash

 

a)       In Registry Editor, locate the following registry subkey:
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
b)       Right-click CrashControl, point to New, and then click DWORD Value.
c)       Type NMICrashDump, and then press ENTER.
d)       Right-click NMICrashDump, and then click Modify.
e)       In the Value data box, type 1, and then click OK.

 

 

Step 4: Enable generating dump by keyboard

 

a.       Start Registry Editor. 

b.       Add following registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters 

Name : CrashOnCtrlScroll

Data Type : REG_DWORD

Value : 1 

 

And

 

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters

Name : CrashOnCtrlScroll

Data Type : REG_DWORD

Value : 1

 

c.       Exit Registry Editor.
 

Step 4: Restart the server to make above configuration take effect

 

 

After configuring the above settings press CTRL+ ScrLk+ ScrLk to test if the server is getting crashed with a BSOD. Modern servers have NMI option in the remote management console (Like HP ILO and Dell Drac). Dell servers have NMI button on Power management tab of the DRAC. Once the server shows the blue screen after the NMI, wait and watch till the memory dumping reaches 100% and complete 
 

 

 

 

 

 

How much RAM your video card is using?

Under Windows 7 if you see your PC is not actually using the amount of RAM you have installed on it then first thing you should check how much RAM is allocated to the video card.

To check the amount of RAM allocated for Video card

1. Go to Control Panel ->Appearance and Personalization -> Display
2. Click on change display settings

3. Click on Advance Settings

4. Here you can find the amount of Ram  dedicated for the video card

Shared System Memory is the amount of system RAM which is configured to use for video card. Dedicated video memory is the memory present on the display card (inbiult chip).

As per requirement Shared System Memory can be reconfigured through system BIOS to fine tune the performance.

test

testing