For more details, refer to Microsoft Edition Comparison by Technical Specification
Tuesday, November 30, 2010
Memory Limits for Windows Releases
This topic describes memory limits for supported Windows releases: Click Here
For more details, refer to Microsoft Edition Comparison by Technical Specification
For more details, refer to Microsoft Edition Comparison by Technical Specification
Friday, November 26, 2010
How to create dumps of applications or the whole machine
Instruction manual on how to gather data Click Here.
Thursday, November 11, 2010
Tuesday, November 9, 2010
Your message wasn’t delivered because of security policies in Exchange 2007
When you’re trying to send an email to a distribution group, the following error may be returned:
Delivery has failed to these recipients or distribution lists
Your message wasn’t delivered because of security policies in Exchange 2007. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
In most cases, this error appears because you’re trying to send email from outside your organisation to an internal distribution list. By default, only authenticated users are allowed to email to a distiribution group.
Answer Available Here
Credit to Christian Gude from itexperiencenet.
Delivery has failed to these recipients or distribution lists
Your message wasn’t delivered because of security policies in Exchange 2007. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
In most cases, this error appears because you’re trying to send email from outside your organisation to an internal distribution list. By default, only authenticated users are allowed to email to a distiribution group.
Answer Available Here
Credit to Christian Gude from itexperiencenet.
Monday, September 27, 2010
Tuesday, August 3, 2010
Upgrade from ESX to ESXi
We have just recently finalised the migration of our vmware infrastructure from vCneter 2 and ESX 3.5 to vSphere 4. If you reference the vmware web site, they already talking about migration path to vSphere 4.1 and more prefered path of ESXi.
So, now once again I have to plan for upgarde and complete all the business requirements and formalities to migrate to ESXi. I have started looking for information and reading on ESXi and durning this process, if I find any useful information which can assist me with graceful migration process to ESXi, I"ll add the info to my blog for my future references.
My starting point for gathering information VMware ESXi and ESX Infor Center
So, now once again I have to plan for upgarde and complete all the business requirements and formalities to migrate to ESXi. I have started looking for information and reading on ESXi and durning this process, if I find any useful information which can assist me with graceful migration process to ESXi, I"ll add the info to my blog for my future references.
My starting point for gathering information VMware ESXi and ESX Infor Center
Tuesday, July 20, 2010
How to Remove old hardware after performing P2V in Windows environment
When performing P2V action on a Windows machines, the virtual machine still holds a lot of hardware components of physical machine. These components might be hidden, but still they are there and drivers are loaded for them. They might comsume resources or create issues on your virtual machine.
Which is generally not a good thing. So, how to detect those unused hardware components and drivers. All you need to do is to open the command prompt:
Enter set devmgr_show_nonpresent_devices=1
Then, open the device manager by entering the command of:
devmgmt.msc
Finally, Select View ----> Show hidden devices
You should delete all the grayed-out hardware which is not in use anymore.
Which is generally not a good thing. So, how to detect those unused hardware components and drivers. All you need to do is to open the command prompt:
Enter set devmgr_show_nonpresent_devices=1
Then, open the device manager by entering the command of:
devmgmt.msc
Finally, Select View ----> Show hidden devices
You should delete all the grayed-out hardware which is not in use anymore.
Wednesday, July 14, 2010
VMware vSphere Online Library ESX 4.0 and vCenter Server 4.0
I found VMware online library very handy when you need to find out any information related to VMware, you can view VMware product documentation, search across all books in a product documentation set, and print or bookmark topics.
VMware vSphere Online Library
VMware vSphere Online Library
Monday, June 28, 2010
Migrating to vSphere 4
Very handy information, if you are planing to migrate from VI3 to vSphere 4. You can check out the step-by-step vSphere migration videos. For more details on the migration from VI 3 to vSphere 4. click on vSphere Update Center
Vmware Resolution Path
I found these are very handy when I'm trying to troubleshoot VM, vCenter, or any ESX issues. All you just need to do is to identify the path for the issue and read the vmware KBs to resolve the issue.
Many common tech support issues in VMware products can be solved using Resolution Paths. Resolution Paths are collections of modular steps that can be used to solve tech support issues.Resolution Paths Published
Many common tech support issues in VMware products can be solved using Resolution Paths. Resolution Paths are collections of modular steps that can be used to solve tech support issues.Resolution Paths Published
How to enable Web Access on vSphere ESX 4
During our migration to vSpher 4, I noticed that for some reason the Web Access on the new hosts were not working. and I'm not sure why the Web Access to ESX 4 is disabled by default.
To enable this, all you need to do is, you need to ssh to the service console and log in as root.
[root@testone]# chkconfig --level 345 vmware-webAccess on
Once the above command is initiated. then you need to verify if it has been enabled for run level 3, 4, and 5 by executing the below command:
[root@testone]# chkconfig --list vmware-webAccess
vmware-webAccess 0:off 1:off 2:off 3:on 4:on 5:on 6:off
finally, you need to start the service:
[root@testone]# service vmware-webAccess start
Starting VMware Virtual Infrastructure Web Access:
VMware Virtual Infrastructure Web Access [ OK ]
For more details, refer to: vSphere Web Access Administrator's Guide
To enable this, all you need to do is, you need to ssh to the service console and log in as root.
[root@testone]# chkconfig --level 345 vmware-webAccess on
Once the above command is initiated. then you need to verify if it has been enabled for run level 3, 4, and 5 by executing the below command:
[root@testone]# chkconfig --list vmware-webAccess
vmware-webAccess 0:off 1:off 2:off 3:on 4:on 5:on 6:off
finally, you need to start the service:
[root@testone]# service vmware-webAccess start
Starting VMware Virtual Infrastructure Web Access:
VMware Virtual Infrastructure Web Access [ OK ]
For more details, refer to: vSphere Web Access Administrator's Guide
Tuesday, June 1, 2010
ESX Server is Disconnected or Not Responding in VirtualCenter
This morning when I try to log in to my vCenter Server using vSphere Client to verify my virtual farm. The vSphere Client show one of the ESX host had been disconnected from the virtual center by itself. The ESX host itself should be running in critical mode as production and had HA and DRS enable on the cluster.
The first thing I did is to verify that the entire VM’s and ESX host itself is still in production without any issues. Which was the case, all the VM were up and running as normal while the status is disconnected.
After that I had to resolve the issue by reconfigure my ESX host and rejoin it back to the HA and DRS cluster in my production farm.
These are the steps I had to go through to resolve the issus:
1) Disable the HA and DRS features from the cluster
2) SSH to the host in question and then path your way to the /etc/init.d and look for the services "mgmt-vmware status" command.
Then you need to issue the command "services mgmt-vmware restart". This process usually takes a minute or so to get the service fully restarted.
Once the services restarted, you can easily add host to the virtual center and reconfigure the HA and DRS cluster mode again. The ESX host is back to normal and status of all the VM's running on that host should change back to normal and should work perfectly as usual.
In some instances by just restarting the mgmt-vmware might not resolve the issues, and you might need to restart the vmware-vpxa services as well. To restart the vmware-vpxa, all you nedd to do is to initiate the "services vmware-vpxa restart" at the CLI.
For more details, refer to VMware KB
The first thing I did is to verify that the entire VM’s and ESX host itself is still in production without any issues. Which was the case, all the VM were up and running as normal while the status is disconnected.
After that I had to resolve the issue by reconfigure my ESX host and rejoin it back to the HA and DRS cluster in my production farm.
These are the steps I had to go through to resolve the issus:
1) Disable the HA and DRS features from the cluster
2) SSH to the host in question and then path your way to the /etc/init.d and look for the services "mgmt-vmware status" command.
Then you need to issue the command "services mgmt-vmware restart". This process usually takes a minute or so to get the service fully restarted.
Once the services restarted, you can easily add host to the virtual center and reconfigure the HA and DRS cluster mode again. The ESX host is back to normal and status of all the VM's running on that host should change back to normal and should work perfectly as usual.
In some instances by just restarting the mgmt-vmware might not resolve the issues, and you might need to restart the vmware-vpxa services as well. To restart the vmware-vpxa, all you nedd to do is to initiate the "services vmware-vpxa restart" at the CLI.
For more details, refer to VMware KB
Subscribe to:
Posts (Atom)