This post is yet another component in OCS 2007 R2 that can be broken if you don’t restart your services after renewing the certificates. Seeing how I’ve already written other posts that are similar, you
It was that time of the year again when our OCS certificates were to expire and to add to that, our root certificates was expiring as well. My colleague and I went on to renew
As indicated in some of my earlier posts such as this one: OCS 2007 R2: “Some calls to and from people outside of your corporate network may not connect due to server connectivity problems… ”
Since I never had the time to document the process of the deployments I did earlier with OCS 2007 R2 on a Windows Server 2008 R2 server, I took last week while I was deploying
I ran into an interesting problem last week while deploying an OCS 2007 R2 Edge Server on a Windows Server 2008 R2 for an existing client and found little documentation that was able to help
The following is a perfect example of the smallest misconfiguration on my part in something seemingly so trivial can cause calls to fail. I’d have to say that what tipped me off was a problem
Unfortunately, the policy applied to my computer is set to overwrite logs which meant I wasn’t able to capture the local logs on my laptop in time to see what was written so the only
Ran into an interesting problem/discovery today while in the office when a colleague of mine was trying to assist someone in Montreal who had an issue. What he noticed was whenever he opened the registry
I ran into an interesting problem while performing a Nortel CS1000, NET VX1200 and OCS 2007 R2 integration for a client who are trying to have users slowly migrated to OCS. The problem happened when
We had a client out West who have been undergoing network infrastructure changes and after completing the majority of the project, they began to notice that an error message intermittently gets displayed for users when
