Excellent tutorial here: http://langui.sh/2009/02/27/creating-a-subjectaltname-sanucc-csr/
Copy your .crt files to /usr/share/ca-certificates
Run: sudo update-ca-certificates
Hit yes to trust the certificates in the wizard (text based for CLI), and away you go! 🙂
a2enmod modulename – this will enable a module
a2dismod modulename – this will disable a module
Once you have made the changes, execute the service apache2 restart command and away you go!
Host sensor data is not updated. The Query Service is not available or was restarted, please retry.
I have run across this issue a couple of times now when shutting down a few of our hosts (including vCenter) and them booting them all back up at the same time in the lab. Due to the way that the VMs were booting back up, some of the VMware services were not starting properly and would result with the inability to view the Hardware status tab in vSphere.
To resolve this issue, simply go through and restart the services on your vcenter box and you should be back in business. Restarting the VMware VirtualCenter service specifically should take care of things (it might ask to restart VMware VirtualCenter Management Webservices as well… that’s fine).
As a side note, I did try going through ADSI and changing some values, however I feel this is more of an issue due to the way your VMs come alive and associated dependencies (SQL backend, DCs, etc.)
Hope this helps!
So today I was digging through event viewer and saw some weird logs with the following error:
Cannot update active Match Making server because SQL Server does not respond.
The service failed to register an active Match Making because of a failure to connect to the SQL Server domainfrontend.local\rtc.
Exception: System.Data.SqlClient.SqlException – A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)
Inner Exception: ~
Cause: The server lost the connection to the backend database.
Make sure the machine has connectivity to the backend SQL Server.
After doing a quite Google search, nothing came up like usual, however I believe I have found a fix. When installing the latest cumulative update for your front end server, make sure that you don’t forget to run the following command (I forgot to finish the install running this command on my second front end, which is when these errors started to popup).
- Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
- Run the Set-CsUser cmdlet to configure the user account for hosted voice mail. For example, run:
Set-CsUser -HostedVoiceMail $True -Identity “contoso\kenmyer”
The preceding example sets the following parameters:
- HostedVoiceMail enables a user’s voice mail calls to be routed to hosted Exchange UM. It also signals Microsoft Lync 2010 to light up the “call voice mail” indicator.
- Identity specifies the user account to be modified. The Identity value can be specified using any of the following formats:
- The user’s SIP address
- The user’s Active Directory User-Principal-Name
- The user’s domain\logon name (for example, contoso\kenmyer)
- The user’s Active Directory Domain Services Display-Name (for example, Ken Myer). If using the Display-Name as the Identity value, you can use the asterisk (*) wildcard character. For example, the Identity “* Smith” returns all the users who have a Display-Name that ends with the string value “Smith”.
This was copied from Vince Quinto’s website. All credit goes to him for this article, be sure to check out his blog: http://ucbyvince.blogspot.com/2011/04/enabling-hd-video-for-lync-2010.html
To enable HD video for Lync 2010, you have to allow the maximum resolution to support HD 720p video. Here’s how…
- In your Lync Front End Server, Click Start
- Click All Programs
- Click Microsoft Lync Server 2010
- Click Lync Server Management Shell
- Run the following commands by typing or copy/paste in Lync Server Management Shell
- Set-CsMediaConfiguration -Identity:Global -MaxVideoRateAllowed HD720p15m
- Restart the Lync Front End service from services.msc.
This command extends the client policy to support HD. Once Lync Front End service has restarted, plug your webcam that is 720p capable, and your video calls can now utilize HD quality videos.
Take note that HD only works in peer-to-peer. For conferencing, the maximum is still VGA.
Want to move a file store from one server to another? Here’s how to do it!
Right from Microsoft: http://technet.microsoft.com/en-us/library/gg195742.aspx
Here is how to get a list of everyone’s username out of active directory.
Get-ADUser -Filter * | FT SamAccountName -A
Today, I ran across the issue of some Lync clients not being able to connect up to our Lync 2010 server. They were receiving the following error:
Sign in to Microsoft Lync failed because the service is not available or you may not be connected to the internet.
Turned out this was caused by having an invalid SSL certificate. The reason the certificate was invalid was this particular Mac was not apart of the domain and therefore the root CA’s certificate was not trusted. Simply importing the root certificate into the keychain logged the user right in.