Hi

I am in a process of setting up the streamlined topology based SP13 farm for a small server setup(have total 3 severs) for 500 users. I have 2 WFEs which will take care of WFE and all batch processing services, WFEs and all other application services via distribution scenarioo. I have a SQL Server 2012 enterprise in a mirrored environment but I only use the direct sql server for now. My questons are:

1.Should I configure the load balancing server setup prior to installing the SharePoint or Is this something after I install SharePoint server software on both servers, can I configure the NLB?

2. If I have to install the SharePoint on a 2 NLB web front end servers, 1st server installation is straight forward but 2nd wfe installation, I should point to the existing content database right? If not what is the process I should follow?

3. How do I test that NLB and sharepoint setup is correct in the load balancing scenario.

4. If I install SQL Server 2012 as a stand alone, can I change later for a mirrored/clustered scenario?

5. I do have a 25GB content database from sp 2010 using classic mode. Should I convert them to claim prior to upgrade content database or even after restoring the content database, I can configure?

Many thanks

Shri

HI Shri,Please find the answers below.

1. LB should be configured after Installing share point and configuring sites.
2. NO,WFE should connect to the Config DB not the content DB.after you install sharepoint in WFE servers,Run the PSCONFIG and choose connect to an existing and provide the details of Config DB.
3. Once the WFE servers are built and configured in NLB,You need to browse the sites and check the IIS logs
4. You can convert the classic to claim after Upgrade.please check the link below that shows how to do that.

http://expertsharepoint.blogspot.de/2013/10/how-to-change-sharepoint-authentication.html

Thanks Anil. Still have a few more questions if you can assist:

1. Do you recommend upgrading classic to claim before or after migration?

2. I have a custom dotnet application, which sits in _layouts and after migration in the test server, it keeps on fail authentication(it keeps on prompting multiple times and never load my custom application). Is this because of the different authentication here? Generally what are the configuration changes I should take care after upgrading the _layout custom applications in terms of security and authentication?

3. I believe its a known issue that custom branding wont work, I have a custom branding in 2010 environment which also fails even after deploying wsp in sp13. Should I change the default branding first before taking the content database backup? so it will be upgraded without any issues?

4. I have nearly 50 site collections under one web application and do you think if I go with a brand new installation setup in SP3 and upgrade/migrate content site collection one by one is best way or content database upgrade? The reason is my client is not interested in branding at this time and interested for every site functionalities with all contents.

Thanks again,

Shri