IT Information that works!

Exchange 2010 SP3 Rollup 7 install with Forefront on a 2 node DAG 2 Exchange 2010 multi-role servers with ForeFront and EndPoint Protection for Exchange on a 2 node DAG READ Installing Update Rollups on Database Availability Group Members http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx How to use the Fscutility.exe program to disconnect the Forefront Security services from Exchange Server. Program folder:   C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server http://support.microsoft.com/kb/929076 DOWNLOAD Hotfix Microsoft Knowledge Base article 2550886 http://support2.microsoft.com/kb/2550886/en-us   Exchange Server 2010 Service Pack 3 http://www.microsoft.com/en-us/download/details.aspx?id=36768   Update Rollup 7 for Microsoft Exchange Server 2010 Service Pack 3 http://support.microsoft.com/kb/2961522   #1. CHECK/UNINSTALL   HOTFIX Check for non-Exchange supp

Online Meeting Add-in for Microsoft Lync 2010 disabled ISSUE: When trying to create an online meeting in Outlook the Online Meeting control is missing. RESOLUTION: Make sure the Online Meeting Add-in for Microsoft Lync 2010 is not disabled. STEPS: In Outlook go to FILE >>> OPTIONS >>> ADD-INS Under DISABLED APPLICATION ADD-Ins make sure the Online Meeting Add-in for Microsoft Lync 2010 is not listed. If it is listed then go to the bottom of the Add-Ins screen and click on the drop down box that says COM Add-Ins next to Manage:. Click on “Disabled Items” then Click on “Go”. In the “Disabled Items” select to highlight “Addin: Online Meeting Add-in for Microsoft Lync 2010 ( ucaddin.dll) ”. Click the “Enable” button. Click “Close” then click “OK”. Restart Outlook. The “Online Meeting Add-in for Microsoft Lync 2010” control icon will be available.

SHAREPOINT 2010 – Site User Information unavailable The website declined to show this webpage - 403 error This website requires you to log in. /_layouts/userdisp.aspx PROBLEM In a site, when working with a user account, all functions are available except when you click on the user and the user information page does not display. The 403 error appears stating “The website declined to show this webpage.” And “This website requires you to log in”. The website url shows you cannot reach “https://yourwebsite/_layouts/userdisp.aspx...”   FIX On your SharePoint server browse to the folder C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS and find the userdisp.aspx file. Open the file with Notepad or Visual Studio and find the line that includes Scope=”Farm”. In my file it was at the end of line #13. Change Farm to Web so the line now reads Scope=”Web”. Save the file and test your site.   PS – Before making

Unable to connect to the MKS: Internal error after cloning or vMotion fails with the error: A general system error occurred   This issue occurred for me after cloning a server in vSphere 5.5. Once the vm was powered on and the new configuration was applied I could not connect to the vm console. I received the "Unable to connect to the mks: internal error". No specific error message was given but I found a few post that lead me in the right direction. After a failed vMotion attempt which gave me the "vMotion failed with the error: A general system error occurred" I found a fix that worked for me. I was able to access the server and save time from rebuilding another server from scratch. I hope this helps you too.   SIMPLE FIX   Remove the vm from inventory then register the .vmx file from the original data store.   In the vSphere 5.5 client; Select "Hosts and Clusters" or VM's and Templates" Select the affected v

VMware   vSphere Web Client 5.5U1   Single Sign-On - Identity Source After a recent upgrade from 5.0U1 to 5.5U1 I ran in to a problem configuring Single Sign-On (SSO) to join Active Directory. I went through all the support KB's and even called tech support. Nothing worked until I change my server name from FQDN to the IP address. I deployed a vCenter 5.5 Appliance that was not joined to Active Directory thus I believe is the reason our LDAP connection could not find our FQDN's in DNS. So the trick was to change the "Primary Server URL" to an IP address. Additionally I change the suggested LDAP port from 3269 to 3268. I am not sure if we had change the default port on our DC's but both port 3269 and port 3268 would not connect with a FQDN. The default LDAP port is 389 and the default LDAPS port is 3269. Here is the change that worked for me: Suggested - Primary Server URL: ldap://servername.domainname.com:389 Successful - Primary Server URL: l

Exchange 2010 SP2 Rollup 8 install with Forefront on a 2 node DAG Environment: Exchange 2010 multi-role server with ForeFront Protection for Exchange on a 2 node DAG READ Installing Update Rollups on Database Availability Group Members http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx How to use the Fscutility.exe program to disconnect the Forefront Security services from Exchange Server or from SharePoint Portal Server Program folder: C:\Program Files (x86)\Microsoft Forefront Protection for Exchange Server http://support.microsoft.com/kb/929076 DOWNLOAD Rollup 8 for Exchange Server 2010 Service Pack 2 (KB2661854) http://www.microsoft.com/en-us/download/details.aspx?id=41394   Exchange 2010 Hotfix problem Check for non-Exchange supported Hotfix by running this command in a Window s Power Shell session: Get-hotfix KB2506143 If it is installed then uninstall the Hotfix and reboot. It seems that Windows Management Fr