In a previous blog post with an introduction of Lync Server 2010 I already showed the setup flow. The most important part is the central SQL server, the Central Management Server or CMS. In this blogpost I’ll continue with the installation of Lync Server 2010.
Lync Server preparations
I’ll start with a simple setup (just like most customers tend to do). I’ll install Lync Server 2010 for instant messaging, presence information and (simple) video conferencing. Initially I’ll setup this up for interal use only, but in a future blog post I’ll connect the Lync environment to the internet so users at home can connect. Or parters (federation) can connect to our Lync environment of course.
Continue reading Install Lync Server 2010
For testing purposes I wanted to Lync Enable the (default) administrator account in Active Directory using the Lync Control Panel. This failed with the following error:
Active Directory operation failed on “wes-dc02.wesselius.local”. You cannot retry this operation: “Insufficient access rights to perform the operation 00002098: SecErr: DSID-03150BB9, problem 4005 (INSUFF_ACCESS_RIGHTS), data 0”. You do not have the appropriate permissions to perform this operation in Active Directory.
Continue reading Insufficient access rights to perform the operation
Using Transport Rules in Exchange Server 2010 you can add fancy disclaimers to your outgoing e-mail messages.
Transport Rule information is stored in Active Directory and shared between all Hub Transport servers in the organization. This way a consistent behavior can be achieved.
To create a Transport Rule that appends a disclaimer open the Exchange Management Console, navigate to the Organization Configuration Container and select the Hub Transport Container.
Continue reading Disclaimers in Exchange 2010
Lync Server 2010 is Microsoft solution for Unified Communication: Instant Messaging, Presence information, Conferencing and Enterprise Voice. There a lot of noise going on around Lync and it is a very rapidly developing solution. On the other hand Lync is in a difficult situation: a typical Windows sysadmin has no affection with telephony and vice versa, a telephony sysadmin doesn’t have too much faith in Windows systems. Oh, and don’t forget the Cisco or Avaya people, it might be a threat for them, or would it be a challenge? Time go get a closer look at Lync Server 2010… Continue reading Lync Server 2010 – An Introduction
When it comes to Exchange Server 2007 or Exchange Server 2010 it is a best practice to use a real world SSL certificate for the Client Access Server. In Microsoft knowledge base article 929395 (http://support.microsoft.com/kb/929395) four vendors are listed as supported vendors for SSL certificates. Of course there are more, and their certificates work fine, but you can also use an internal Windows Server 2008 Certificate Services environment. Especially when you have only domain joined clients this shouldn’t be a problem…
Client Access Server and Certificates
When installing the Exchange Server 2010 Client Access Server, a self-signed certificate, containing just the server name, is generated and installed on the server, and can be used for testing purposes after installing the server. For testing purposes this self-signed certificate also contains the local FQDN in the “Subject Alternative Names” field for testing with Outlook Anywhere. It is naturally a best practice not to use this self-signed certificate in a production environment, but rather to use a third party certificate on the Client Access Server.
Continue reading Exchange 2010 and your own PKI infrastructure