This was one of the problems I’ve come across a few years back when I did my first Exchange 2007 Unified Messaging deployment and since I’m currently on a Exchange UM project, I thought I
I seem to come across this 4 or 5 times each year during my Exchange UM deployments and I find that I always forget the answer having to look into my old notes so I
I’m not sure if this is a but or not but I ran into an minor annoyance today while configuring auto attendants within Exchange Server 2010 RTM (Version 14.0 – Build 639.21). The AA’s aren’t
I ran into a strange problem that stumped me for a good 30 minutes before I figured out what the issue was. What’s funny is that the problem was actually quite simple but seeing how
We ran into an interesting issue during installing the Nexus 1000v which we ended up calling VMware for support and I thought this post might be useful if anyone experiences the same issue. This isn’t
Not much of a problem but it looks like vCenter caches the management network and takes a bit of time to refresh after you make a change to the Management Network port group. I noticed
I’ve been meaning to write a post about an issue we experienced in a project for a client earlier in the summer but kept forgetting or was too busy so now that I have a
I made the mistake in typing in a different Domain ID during a Nexus 1000v deployment (see post: https://blog.terenceluk.com/2010/11/installing-cisco-nexus-1000v-404sv13b.html) with 2 VSMs and had problems configuring the 2 VSMs in HA until I was able
I thought about this several times as to whether I should write this post as it’s part of the steps I had to take while working with Cisco and VMware in resolving our orphaned Nexus
Have you ever tried clicking on the Download and Install option for the Nexus 1000v? What you’ll notice is that when you do, you’ll get the following error: An internal error occurred in the vSphere
