El conocimiento al alcance de todos.

Thank to: http://blogs.technet.com You might have wondered about how to setup Failover Cluster inside Hyper-V Virtual Machines. As you know, the major element of a cluster is the shared storage piece. Inside Hyper-V VMs, iSCSI is the only supported method of providing shared disks over virtual NICs. Here are detailed steps on how to create Highly Available resources inside Hyper-V Windows Server 2008 R2 VM; 1. VM Preparation: Provision the following VMs on your Hyper-V server; One Windows Server 2008 R2 DC Virtual Machine At least two Windows Server 2008 R2 Virtual Machines Use an iSCSI target software to provide shared storage to each node Update (04/05/2011): Microsoft product group just released Microsoft iSCSI Taget Software 3.3 for public download http://www.microsoft.com/downloads/en/details.aspx?FamilyID=45105d7f-8c6c-4666-a305-c8189062a0d0 http://blogs.technet.com/b/virtualization/archive/2011/04/04/free-microsoft-iscsi-target.aspx If you have access to MSDN

Problem Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch. Mailbox Database: {Database Name} Error Code: 0x80041606 Solution Basically there's a problem with the catalog data for the database, we need to recreate it. WARNING this can use a fair bit of CPU power to recreate, so you might want to do it at the end of the day. 1. On the Exchange server that's hosting the database that's giving you the error. Start > In the search/run box type services.msc {enter} > Locate the Microsoft Exchange Search Indexer Service and stop it. 2. Navigate to the folder that holds the problem Database (Look In Exchange System Manager > Organizational Configuration > Mailbox > Database Management > Right click the problem Database > Properties). Within the folder you will find another folder called CatalogData-xxxxxxxxxxxxxxxxxx > Delete this folder.

Thanks to: http://thommck.wordpress.com   Internet Explorer 10 was released for Windows 7 and Windows Server 2008 R2 machines back in February 2013. Nine months later and we are going through it again with   Internet Explorer 11 . For SysAdmins and IT Pros managing software updates, these new versions led to quite a significant change in how we use Group Policy to manage them. I only recently discovered that when Windows 8 (and along with it IE10) was released they finally got rid of the “Internet Explorer Maintenance” Section of the Group Policy Editor. This section always struck me as an odd place to configure IE settings and I’m still not sure why they couldn’t just use the normal Administrative Template section. Internet Explorer Maintenance in Server 2003 Group Policy Editor Below is an excerpt from the technet article  Replacements for Internet Explorer Maintenance   from the IE10 Deployment Guide In earlier versions of the Windows operating system, Internet Explore

Thanks to: http://www.codeproject.com This is a step by step guide on how you migrate your SharePoint’s (I used 2010 version in this instance) SQL Server to an new SQL Server host.  In this exercise I tried migrating it in a new version of SQL server which is 2012 from 2008 R2, also had tried it in the same version.  There are only 9 steps to perform this task but it takes into consideration you already have a new SQL Server provisioned. Lets start 1. Stop all SharePoint and IIS Related Services SharePoint 2010 Administration SharePoint 2010 Timer SharePoint 2010 Tracing SharePoint 2010 User Code Host SharePoint 2010 VSS Writer SharePoint Foundation Search V4 World Wide Web Publishing Service SharePoint Server Search 14 Web Analytics Data Processing Service Web Analytics Web Service 2. Stop IIS At the command prompt under admin context, type iisreset /stop 3. Detach all related SQL Server databases Configuration database Central Administration content