s p w i n d o w

original source: http://joelblogs.co.uk/2011/11/06/uninstall-all-sharepoint-2010-solutions-via-powershell/ The Script function Uninstall-AllSPSolutions { param ( [ switch ] $L ocal , [ switch ] $Confirm ) Start-SPAssignment -Global; foreach ($solution in (Get-SPSolution | Where-Object { $_.Deployed })) { write-host "Uninstalling Solution " $solution.Name; if ($solution.DeployedWebApplications.Count -gt 0) { Uninstall-SPSolution $solution –AllWebApplications -Local:$L ocal -Confirm:$Confirm; } else { Uninstall-SPSolution $solution -Local:$L ocal -Confirm:$Confirm; } do { Start-Sleep 5; $solution = Get-SPSolution $solution; } while ($solution.JobExists -and $solution.Deployed) } Stop-SPAssignment -Global; } function Remove-AllSPSolutions { param ( [ switch ] $Confirm ) Get-SPSolution | Where-Object { !$_.Deployed } | Remove-SPSolution -Confirm:$Confirm } Us...

copied from: https://technet.microsoft.com/en-us/library/ff431687.aspx Configure SharePoint 2013 to use Office Web Apps Server Choose one of the following sections depending on whether you want to use HTTP or HTTPS. HTTP is generally recommended only for test environments. In production environments, the more secure HTTPS protocol is the better choice. In a test environment that uses HTTP For this configuration, make sure you have set up Office Web Apps Server by following the steps in  Deploy a single-server Office Web Apps Server farm in a test environment . Be sure to configure the Office Web Apps Server farm to use an internal URL and HTTP. The Video: Configure Office Web Apps for SharePoint 2013  shows how to set up Office Web Apps Server and configure SharePoint 2013 to use Office Web Apps Server in a test environment. Step 1: Open an elevated SharePoint 2013 Management Shell Choose the procedure that corresponds to your server operatin...

Source: https://community.nintex.com/servlet/JiveServlet/previewBody/1017-102-4-2295/Uninstalling%20Nintex%20Workflow%202013.pdf Nintex Workflow 2013 Page | 1 of 2 Uninstalling Nintex Workflow 2013 The following are the steps to be taken for completely uninstalling Nintex Workflow 2013. Removing the Nintex Workflow 2013 Solutions 1. Disable web level features on all webs that use Nintex Workflow 2013. 2. Disable site collection features on all site collections that use Nintex Workflow 2013. 3. Go to SharePoint Central Administration. 4. In the Nintex Workflow Management section, click the Web Application Activation link. 5. Check the All content web applications option. 6. Click Deactivate. 7. In the Quick Launch menu, click System Settings. In the Farm Management section, click the Manage farm solutions link. 8. Retract and remove the solutions installed by Nintex Workflow 2013, in the following order: nintexworkflow2013backwardscompatibility.wsp nintexworkflow201...

Source: http://www.justanothertechnologyguy.com/2011/11/databases-require-upgrade-or-not.html Upgrading Content databases using SharePoint 2010 Management Shell Start the “SharePoint 2010 Management Shell” In the Shell enter : Get-SPContentDatabase –site [url towards your site collection] Cut and paste the GUID to the following command: Upgrade-SPContentDatabase [guid] It will take some time before the 100% appears. Upgrading ‘all other’ type of databases using psconfig.exe Open a command box in ‘run as administrator’ mode. Navigate to the bin directory of the SharePoint root. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN Run the following command: PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures The PSConfig.exe tool will go though several steps to upgrade all the databases in the correct sequence. Validate that all the databases where updated successfully. Open “Central...

Most SharePoint search problems are related to one of the following: 1. Crawler does not have permission to crawl the database. 2. Search does not have the proper URL’s to crawl Original post : http://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=176

When deploying a page to SharePoint through a Modules feature, there are several options adding web parts to this. These are as follows: Add the web parts to the page programmatically via a feature receiver. This approach can be done quickly and easily if you are familiar with coding, however if the feature receiver fails, the web part page may continue to be checked out. Embed references to the web parts directly in the mark-up of the aspx page. The main problem with this approach is that once the page is deployed, the page is still “ghosted”. This means that the normal drop down to “Edit Web Part” is not shown, blocking future modifications to the page. The third approach (the preferred one), is to embed the webpart markup in “AllUsersWebPart” nodes in the modules elements.xml file (as shown in the example below). Copied from : http://blogs.msdn.com/b/uksharepoint/archive/2011/04/04/provisioning-web-parts-to-a-page.aspx

Create claims-based web applications in SharePoint 2013 1. $ap = New-SPAuthenticationProvider 2. New-SPWebApplication -Name "Kuntatalo" -URL "http://e2-web3:13013/"  -ApplicationPool "SP2013-AppPool" -ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\AppPoolUserName")  -AuthenticationProvider $ap Source: https://technet.microsoft.com/en-us/library/ee806885.aspx Create a site collection in SharePoint 2013 1. $template = Get-SPWebTemplate "STS#0" 2. New-SPSite -Url "<URL for the new site collection>" -OwnerAlias "<domain\user>" -Template $template Source: https://technet.microsoft.com/en-us/library/cc263094.aspx

Copied from: http://absolute-sharepoint.com/2013/08/how-to-move-a-list-from-sharepoint-2010-to-sharepoint-2013.html How to move a List from SharePoint 2010 to SharePoint 2013 Fast & Cheap : “Dirty” export and import Fast & Clean : Third party solution Clean & Cheap: Content Database Import 1. Fast & Cheap — > Modify the .CMP file This is the “dirty” method to make it work fast. What I mean by dirty, is that it isn’t supported by Microsoft officially since we will modify the .cmp file. Here is how to do it step by step. Export the list from SharePoint 2010 using either the Central Administration or PowerShell (Export-SPWeb). In the Central Administration, go to Backup and Restore > Export a site or list. Choose your list, and click Start Export Copy the exported list (.cmp file) to your desktop and change the extension to .cab. You can then extract it using a software like WinRar. You will then have those files: Open the SystemData.XML file with an ...

1. Create a new project: 2. Configure as a Sandbox (or as a Farm) Solution: 3. Add a new Module to your project: 4. Download a copy of Seattle.master: 5. Add the copy to your module, rename to CustomMaster.master, and Change your elements.xml file to point to _catalogs\masterpage folder: 6. Change your masterpage, to include a welcome message: 7. Deploy your solution and change your Site master page: 8. Verify that it shows your welcome message: Source: https://raquelalineblog.wordpress.com/2013/04/26/sharepoint-2013-create-a-master-page-based-on-seattle-master-with-vs-2012/

$fileBytes = [system.io.file]::ReadAllBytes("c:\the\full\path\to\your\robots.txt"); $site = Get-SPSite "http://yourdomain:portifneeded"; $site.RootWeb.Files.Add("robots.txt", $fileBytes, $true);    copied from: http://www.jonthenerd.com/2011/08/17/sharepoint-2010-add-a-file-to-the-root-of-your-site-using-powershell/