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
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
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 –
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
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
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
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
I made the mistake in typing in a different Domain ID during a Nexus 1000v deployment (see post: https://blog.terenceluk.com/installing-cisco-nexus-1000v-404sv13b/) with 2 VSMs and had problems configuring the 2 VSMs in
