Ran across a known issue with Exchange 2010 and IE9. How do I know it was a known issue? I happened to be on the phone with Microsoft Support at the time for another issue...
The error that this combination causes is that you cannot close the Exchange Management Console in Exchange 2010. When you try to close it you receive the error message "You must close all dialog boxes before you can close Exchange Management Console."
My friendly guy on the Microsoft call told me that there is currently no fix - they are expecting to have a patch out around Q4 2011. The current fix, according to him, was "Don't install it. And uninstall it if you have already." I almost forgot to mute the phone before I started laughing. Gotta love when Microsoft tells you to not keep your computer up to date because it will break it...
So I decided to do some research on my own and (easily) found an article here with the fix.
Basically what you need to do is disable the Internet Explorer Enhanced Security Configuration, then add https://localhost to the trusted sites in IE and your good to go.
------
Dustin Shaw
VCP
Saturday, August 13, 2011
Tuesday, July 12, 2011
vSphere 5
A number of vSphere 5 official announcements came out today. You can check them out on VMware's official site.
------
Dustin Shaw
VCP
------
Dustin Shaw
VCP
Friday, June 24, 2011
View Pool Issues
Had a client call me this morning with an issue with one of his VMware View 4.5 pool. He said that his users were having issues logging into their desktops. They could login, but it was taking a long time to login. When he went to double check the settings in the pool he found that his vCenter Settings tab was red and the error it stated:
Cannot find host or cluster for this pool.
Since I set it all up for him initally, he stopped there and thought he'd better differ to the expert. Oh, and yes it does say "Data-Denter" - he's dislexic (aren't we all?)
I dug in further and found the following other errors. When clicking on "Browse" to chose Host or cluster, I received this error:
Server Error
One of the required objects is not found in vCenter Server vcenter.
When I looked at the desktops, they all had the same error listed:
Status
Resource Cluster \'/Data-Center/host/Cluster/Resources\' not found for pool: Poolname
Since it was a Floating resource pool with no persistent desktops, I decided the quickest and easiest thing to do for him would be to just create a new pool based of the same image (I'm going to have to give him a refresher on Recomposing; it looks like he is still running off the image I helped him create over a year ago). I disabled his old pool and told him to delete it once he felt comfortable that everything was running good on the new one.
Afterwords, I decided to glance around for an answer, and found this VMware KB article:
Editing an existing pool in the VMware View web admin interface fails with the error: One of required objects is not found in the VirtualCenter server <IP address>
Nothing has changed on his environment. He only has the vSphere Essentials bundle (he has a small shop with only 2 hosts), so he doesn't have any actual Resource Clusters. This is my thought as to where the corruption came from, but I've got nothing to confirm my suspicions. If anyone has some thoughts on this, I'd love to hear them.
------
Dustin Shaw
VCP
Cannot find host or cluster for this pool.
Since I set it all up for him initally, he stopped there and thought he'd better differ to the expert. Oh, and yes it does say "Data-Denter" - he's dislexic (aren't we all?)
I dug in further and found the following other errors. When clicking on "Browse" to chose Host or cluster, I received this error:
Server Error
One of the required objects is not found in vCenter Server vcenter.
When I looked at the desktops, they all had the same error listed:
Status
Resource Cluster \'/Data-Center/host/Cluster/Resources\' not found for pool: Poolname
Since it was a Floating resource pool with no persistent desktops, I decided the quickest and easiest thing to do for him would be to just create a new pool based of the same image (I'm going to have to give him a refresher on Recomposing; it looks like he is still running off the image I helped him create over a year ago). I disabled his old pool and told him to delete it once he felt comfortable that everything was running good on the new one.
Afterwords, I decided to glance around for an answer, and found this VMware KB article:
Editing an existing pool in the VMware View web admin interface fails with the error: One of required objects is not found in the VirtualCenter server <IP address>
Nothing has changed on his environment. He only has the vSphere Essentials bundle (he has a small shop with only 2 hosts), so he doesn't have any actual Resource Clusters. This is my thought as to where the corruption came from, but I've got nothing to confirm my suspicions. If anyone has some thoughts on this, I'd love to hear them.
------
Dustin Shaw
VCP
Wednesday, April 20, 2011
Purple Screen of Death - Dell issues
You may notice I don't post a lot of issues on here. That's because we frankly don't have a whole lot of issues. I personally attribute it to using Best Practices, and regular maintenance. That said, things will still get lost in the weeds occasionally.
We ran into the Purple Screen of Death on one of our ESX 4.1 boxes yesterday. It is a Dell R610, and apparently had a hardware hiccup, and kicked out errors stating:
We rebooted the box, and it came back online just fine, but we didn't feel comfortable with it, so we stuck it in maintenance mode and had someone contact Dell. Dell reports that we need to update the Bios on it:
-----
Yes, it appears your system is affected by some of the microcode updates released from Intel on the 5500 and 5600 series processors. That is likely the cause of these PCI errors. The course of action we need to take is:
· Update the BIOS
· Update the iDRAC
· Clear out the old log entries
· Monitor for re-occurance.
------
So it's sitting in maintenance mode until someone has some time to love on it. The awesome thing is that we run N+1 (one more box than we need) so we have that luxury. I know plenty of people that refuse to listen to why you should go N+1 who would be scrambling to make a maintenance window to update it.
The downside to this whole fiasco was that when it hiccupped, it stayed online (as is the default with ESX), and held onto the Storage of it's VMs. Therefore, HA couldn't restart them on another box until someone manually SHUT OFF the pretty Purple-VM-Eater. As soon as they did that, all was well in the world and the phone stopped ringing.
Since I'm not fond on relying on manual intervention to make HA work, I found the command for auto-restart when a PSoD happens and applied to ALL our hosts:
esxcfg-advcfg -s X /Misc/BlueScreenTimeout
Were X = number of seconds before restart
I went with 30 seconds, that way I have the opportunity of seeing the screen if I so happen to be looking at it when it dies.
------
Dustin Shaw
VCP
We ran into the Purple Screen of Death on one of our ESX 4.1 boxes yesterday. It is a Dell R610, and apparently had a hardware hiccup, and kicked out errors stating:
| | | Tue Apr 19 21:09:15 2011 | | PCIE Fatal Err: Critical Event sensor, bus fatal error (Bus 1 Device 0 Function 1) was asserted | | 0xA10002FBF9AD4DB1000413186FAA0101h |
| | | Tue Apr 19 21:09:15 2011 | | Err Reg Pointer: OEM sensor, OEM Diagnostic data event was asserted | | 0xA00002FBF9AD4DB10004C11A7E011610h |
| | | Tue Apr 19 21:09:15 2011 | | PCIE Fatal Err: Critical Event sensor, bus fatal error (Bus 1 Device 0 Function 0) was asserted | | 0x9F0002FBF9AD4DB1000413186FAA0001h |
| | | Tue Apr 19 21:09:15 2011 | | Err Reg Pointer: OEM sensor, OEM Diagnostic data event was asserted | | 0x9E0002FBF9AD4DB10004C11A7E011610h |
We rebooted the box, and it came back online just fine, but we didn't feel comfortable with it, so we stuck it in maintenance mode and had someone contact Dell. Dell reports that we need to update the Bios on it:
-----
Yes, it appears your system is affected by some of the microcode updates released from Intel on the 5500 and 5600 series processors. That is likely the cause of these PCI errors. The course of action we need to take is:
· Update the BIOS
· Update the iDRAC
· Clear out the old log entries
· Monitor for re-occurance.
------
So it's sitting in maintenance mode until someone has some time to love on it. The awesome thing is that we run N+1 (one more box than we need) so we have that luxury. I know plenty of people that refuse to listen to why you should go N+1 who would be scrambling to make a maintenance window to update it.
The downside to this whole fiasco was that when it hiccupped, it stayed online (as is the default with ESX), and held onto the Storage of it's VMs. Therefore, HA couldn't restart them on another box until someone manually SHUT OFF the pretty Purple-VM-Eater. As soon as they did that, all was well in the world and the phone stopped ringing.
Since I'm not fond on relying on manual intervention to make HA work, I found the command for auto-restart when a PSoD happens and applied to ALL our hosts:
esxcfg-advcfg -s X /Misc/BlueScreenTimeout
Were X = number of seconds before restart
I went with 30 seconds, that way I have the opportunity of seeing the screen if I so happen to be looking at it when it dies.
------
Dustin Shaw
VCP
Tuesday, March 29, 2011
vSphere 5 Around the Corner!
VMware recently announced vSphere 5 will be coming July-August time frame 2011.
Three big new features will be included when it does come:
Storage DRS
Just like you use DRS to help you manage the workload on your hosts, Storage DRS will help you manage the workload on your SANs. The essential workup is that you'll be able to group your storage into storage pods that you can allow Storage DRS to manage what goes where based on capacity. Pretty cool, if you are dealing with some complicated storage situations.
SRM Host-Based Replication
This buys you the ability to use SRM even if you have disparing storage at your different locations.
Network I/O Control for VMs
This allows you the option to reserve bandwidth for high-priority VMs when you've got a congested network. Very useful control to have, depending on your network layout and configuration.
Another anouncement that VMware has made about vSphere 5 - it's ESXi all the way. That's right, ESX will be discontinued in favor of it's lighter, tigher cousin. I mentioned that this was coming before, but now it's actually here. Hope you are ready for migration!
VMware won't leave you figuring it out on your own, though. They recommend that you start migrating off ESX to ESXi now in preparation for the move to vSphere 5. Here is their Info Center about it, and here is their Migration Guide.
------
Dustin Shaw
VCP
Three big new features will be included when it does come:
Storage DRS
Just like you use DRS to help you manage the workload on your hosts, Storage DRS will help you manage the workload on your SANs. The essential workup is that you'll be able to group your storage into storage pods that you can allow Storage DRS to manage what goes where based on capacity. Pretty cool, if you are dealing with some complicated storage situations.
SRM Host-Based Replication
This buys you the ability to use SRM even if you have disparing storage at your different locations.
Network I/O Control for VMs
This allows you the option to reserve bandwidth for high-priority VMs when you've got a congested network. Very useful control to have, depending on your network layout and configuration.
Another anouncement that VMware has made about vSphere 5 - it's ESXi all the way. That's right, ESX will be discontinued in favor of it's lighter, tigher cousin. I mentioned that this was coming before, but now it's actually here. Hope you are ready for migration!
VMware won't leave you figuring it out on your own, though. They recommend that you start migrating off ESX to ESXi now in preparation for the move to vSphere 5. Here is their Info Center about it, and here is their Migration Guide.
------
Dustin Shaw
VCP
Friday, March 11, 2011
Basics of Installing VMware View 4.6
We just got View 4.6 up and running in our Demo environment, and here are the basic take-aways that we have.
------
Dustin Shaw
VCP
- Windows 2008R2 is the minimum for VMware View Secure Gateway. Or Demo Environment was previously on 2003R2, so we had to do an upgrade.
- You have to update all of your View Base Images to the View 4.6 Agent.
- You have to install the latest version of VMware Tools in your View Base Images
- A number of Microsoft Patches need to be installed on your View Base Images:
- You must remove all previous Snap Shots, and start fresh for your Linked Clones
------
Dustin Shaw
VCP
VMware View released for iPad
VMware released the VMware View App for the iPad this week.
You can see the app in iTunes here.
VMware has also created a forum for the VMware View for iPad App to discuss feature requests, issues, and ideas.
The new app will work with VMware View 4.6 or later, not with View 4.5, so if you aren't yet upgraded to View 4.6 (which came out at the end of Febrary), you'll need to first.
Dustin Shaw
VCP
Subscribe to:
Posts (Atom)