How To Install A Wsp In Sharepoint Foundation 2010 Help' title='How To Install A Wsp In Sharepoint Foundation 2010 Help' />Tendance Free Share. Point 2. 01. 0 Theme. Were always excited when we release a new free Share. Point theme for you guys, so here it is TendanceThe theme features a modern, simple and light design. We like to keep it simple and elegant. This work is licensed Creative Commons Attribution Share Alike 3. License. You may modify the theme as you wish at your own risk. However, it is forbidden to sell or redistribute the theme without Top. Share. Point. com permission. Please link to this article if you would like to spread the word. Features Two columns Fixed width CSS based One master page and two page layouts provided Slider powered by h. Slides on the homepage Top and left dynamic navigation Ideal for 1. Suitable for small Share. Point 2. 01. 0 Publishing Sites. Instructions. To enable Tendance theme for Share. Point 2. 01. 0 Publishing Site follow these simple steps. GVDXgc/TqRNM4IX8GI/AAAAAAAAB4A/hNeVSSHgqiY/s1600/configuring%2Bsharepoint%2Bfoundation%2Bfor%2BInternet%2Bfacing%2B-%2B030%2B-%2Balternate%2Baccess%2Bmapping%2B_%2Bedit%2Bzone%2Bursl%2B_%2BInternet%2Bzone%2Bcreated.jpg' alt='How To Install A Wsp In Sharepoint Foundation 2010 Help' title='How To Install A Wsp In Sharepoint Foundation 2010 Help' />Were always excited when we release a new free SharePoint theme for you guys, so here it is Tendance The theme features a modern, simple and light design. So you are excited by SharePoint 2013s new features and tend to migrate from SharePoint 2010 to SharePoint 2013 Well, this article walks through moving from. Download the Tendance. After unzipping the file you will see one folder called Tendance with three folders under it Master. Pages folder contains two masterpages. Main master page Tendance. Tendance search. Import Tendance. Master Page site objects in Share. Point Designer. I will talk about Tendance search. Page Layouts folder contains two custom page layouts created for this theme. Both page layouts allows you to display the left navigation and other custom functions. Tendance Home. aspx will be used for the homepage and Tendance. Import these custom page layouts into Page Layouts site objects in Share. Point Designer. And finally, the third folder called Tendance contains a css folder, images folder and html folder. Place the Tendance folder under your site root. Make sure Network and Network Service accounts have read permissions on this folder. Once all the files are put into place, it is time to set the Tendance. Go to your site homepage and click on Site Actions Site Settings. Under Look and Feel click on Master page and under Site Master Page select Tendance. OK. Go back to the Site Settings and click on Page layouts and site templates. Make sure you have the Article Page Tendance Home and Article Page Tendance on the right side pane for Page Layouts. Go to your site and edit all the pages to inherit the custom page layout Tendance. Now, we need to take care of the homepage. Go to the homepage Site Action Edit Page Page tab Page Layout Select Tendance Home page layout. Next, click on Add a Web Part under Categories select Media and Content under Web Parts Page Viewer Click Add button. Edit the newly added Page Viewer web part and type this path in the Link textbox TendancehtmlTendance. Add 5. 30 pixels for the Height and 1. Width. Set Chrome Type to None and click OK. Next, make sure you see the Page Viewer web part populated with the custom slider and Publish the page. And finally lets take care of the search page. We need to change the search results page first. On the homepage go to Site Actions Site Settings and under Site Collection Administration click on Search settings. Under Site Collection Search Results Page change the default setting to Searchresults. OK. Go to Share. Point Designer and Open Site http yourdomain. Search. Under Site Objects click on Master Pages and import Tendance search. Tendance package. Right click on the Tendance search. Set As Custom Master Page. And, thats all folksEnjoy the theme and if you like it or not leave us a comment. It does help us to improve the next themes. If you would like to show your appreciation buy me a beer Download Tendance Theme. Migrate from Share. Point 2. 01. 0 to Share. Point 2. 01. 3. Salaudeen Rajacks Share. Point Diary. So you are excited by Share. Point 2. 01. 3s new features and tend to migrate from Share. Point 2. 01. 0 to Share. Point 2. 01. 3 Well, this article walks through moving from Share. Point 2. 01. 0 to Share. Point 2. 01. 3 step by step, assuming all necessary migration preparations and planning strategies are done, lets move to the core migration process. Before you start Change the Authentication to Claims Claims authentication is the default authentication in Share. Point 2. 01. 3. Many dependent services like Office Web Apps require Claims authentication in Share. Point 2. 01. 3. So before migration convert your Share. Point 2. 01. 0 web applications from Classic mode which is default in Share. Point 2. 01. 0 to Claims. Technet Reference http technet. Also, If you have Forms authentication, make sure its configured in your target farm before migration. Cleanup Before Migration Clean up an environment before an upgrade to Share. Point 2. 01. 3 This includes deleting unused sitessite collections, Removing unused features and solutions, Delete orphaned users and sites, Cleanup old document versions, Removing features which are not supported by Share. Point 2. 01. 3 such as Web Analytics. Technet Reference http technet. Its recommended that you run database consistency check before taking database backup from Share. Point 2. 01. 0 farm. No more In place upgrade from Share. Point 2. 01. 0 to Share. Point 2. 01. 3 In. No direct upgrade is possible from Share. Point 2. 01. 0 to. Share. Point 2. 01. You cant install Share. Point 2. 01. 3 on top of Share. Point. 2. 01. 0 as we can install Share. Point 2. 01. 0 on top of Share. Point 2. 00. 7. So. Share. Point 2. 01. You cant re use your. Hardware for Share. Point 2. 01. 3 Also you cant install both. Share. Point 2. 01. Share. Point 2. 01. Migration Steps Summary Create new Share. Point 2. 01. 3 Farm, Setup necessary configurations. Backup Restore Share. Point 2. 01. 0 Content Databases to Share. Point 2. 01. 3s SQL Sever or perform a detach attach processVerify content databases by running Test SPContent. Database from Share. Point 2. 01. 3 farm. Attach Content Databases to Share. Point 2. 01. 3 web application by running Mount SPContent. Database. Upgrade Site Collections to move them into Share. Point 2. 01. 3. Step 1. Create New Share. Point 2. 01. 3 Farm. Install and configure new Share. Point 2. 01. 3 farm. All farm configurations should be setup as in source Share. Point 2. 01. 0 Farm, including All necessary configurations like AAM, Email settings, Managed pats, etc. Install any 3rd party software, language packs, custom features and solutions you had in your Share. Point 2. 01. 0 farm into your new Share. Safeway Media Player Software. Point 2. 01. 3 Farm. Create web applications to Share. Point 2. 01. 3. environment as in your existing Share. Point 2. 01. 0 farm. As we are going to use the existing content database from Share. Point. 2. 01. 0, Delete the default. If you failed to delete the web applications root site database, you. Orphaned Sites issue on running Test SPContent. Database cmdlet as part of migration process. This. is because the root site collection exists in both content databases and leads to conflict Alright, This article assumes new Share. Point 2. 01. 3 Farm is already installed and configured. Step 2. Backup Restore Share. Point 2. 01. 0 Content Databases to Share. Point 2. 01. 3 SQL Sever Backup Share. Point 2. 01. 0 content databases, Restore them. Share. Point 2. 01. SQL Server instance. Identify and take a list of your source content databases either from. Central Administration Central Administration Application. Management Manage Content Databases Or use this Power. Shell cmdlet to retrieve all content databases of a particular web application Get SPContent. Database Web. Application lt Web App URL Select Name. Optionally, you can Setting Share. Point Content databases to read only before taking backup. But why because you may want users to continue using Share. Point 2. 01. 0, same time preventing any data in consistency on content migrated to Share. Point 2. 01. 3. To do so Go to SQL Management Studio database. Options Set Database Read only to True. Backup Databases from Share. Point 2. 01. 0 SQL Server Log in to SQL Server box of your Share. Point 2. 01. 0 Farm. Open SQL Server Management Studio, Expand Databases node. Right Click your content database, Choose Tasks Backup Set the backup type to FULL, specify the backup destination and click on OK to start backup process. Wait for the backup to complete. Repeat this procedure for All content databases of desired Share. Point 2. 01. 0 web applications. Restore Database on Share. Point 2. 01. 3s SQL box Next step is to Restore. Share. Point 2. 01. Share. Point 2. 01. SQL Server. Copy. Share. Point 2. 01. SQL Server.  Open SQL Server Management Studio Right click databases node Click Restore Database. Specify the source as Device and Click on the. Click on Add button to locate backup files. Once done, Click on OK to return to the restore window. In Destination section, you can type new database. Database field if you wish to rename your database. Click on OK button to start restore process. Wait for the restore successful message. Once restored, Go to Database properties, Click on Options Tab, Set Database Read only to False. If you made it read only before taking backup Step 3. Verify content databases with Test SPContent. Database. No more STSADM o Pre. Upgrade. Check and its replaced with the Power. Shell cmdlet Test SPContent. Database. So we got to execute Test SPContent. Database cmdlet which scans content databases of the provided web application and addresses any issues found. Syntax Test SPContent. Database Name lt Database name Web. Application lt Web App URL. E. g. Test SPContent. Database Name SP2. OperationsContent Web. Application http Share. Point. 13. Crescent. This would report potential issues such as Missing Features Solution dependencies, Orphaned Sites, wide Lists, etc. Resolve Migration issues reported by Test SPContent. Database. Test All Content Databases and produce Report. Lets execute Test SPContent. Database for all Content Databases Add PSSnapin Microsoft. Share. Point. Power. Shell EA Silently. Continue. Array to hold Content Databases to Test. Content. DBS SP2. Intranet. RootContent, SP2. Salescontent, SP2. OperationsContent. Web Application to Host. Web. App. URL http Share. Point. 13. Crescent. Loop through each web web application. Foreach DB in Content. DBS. Checking Content Database DB Write Host Foreground. Color Green. Report to Content Database db Out File Encoding default File. Path D DBCheck. Append. Test Content Database and output report to a CSV file. Test SPContent. Database Name DB Web. Application Web. App. URL Convert. To Csv No. Type. Information Out File Encoding default File. Path D DBCheck. Append. This script gives nice report in CSV format for easier analysis. To troubleshoot upgrade issues reported, use http technet. Check the. upgrade log and deploy any missing components and re run. Test SPContent. Database cmdlet to verify again. Make sure Upgrade. Blocking is false to move furtherStep 4. Attach Content Databases to Share. Point 2. 01. 3 by running Mount SPContent. Database. After. fixing all issues reported by Test SPContent. Database, we can start attaching content databases to Share. Point 2. 01. 3 web application. Remember Always mount the root site collections database firstAlso, if you migrating My sites, Migrate My Site Host First Mount SPContent. Database name SP2. OperationsContent Database. Server G1 SP2. 01. DB0. 1. Crescent. Web. Application http sp.