LUSH-PEDIA

function Get-DocInventory() {     [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")     $farm = [Microsoft.SharePoint.Administration.SPFarm]::Local     foreach ($spService in $farm.Services) {         if (!($spService -is [Microsoft.SharePoint.Administration.SPWebService])) {             continue;         }         foreach ($webApp in $spService.WebApplications) {             if ($webApp -is [Microsoft.SharePoint.Administration.SPAdministrationWebApplication]) { continue }             foreach ($site in $webApp.Sites) {                 foreach ($web ...

Need to create web application with the following name: http://intranet.SP2013.com 1. Create Host Name open hosts file from the following path: c:\Windows\System32\drivers\etc enter the below mentioned line and save. 127.0.0.1 intranet.SP2013.com 2. Create Web Application Please note to set the following properties: Port: 80 Host Header: intranet.sp2013.com 3. Disable Loopback May face the following issues:- ·          There is continuous prompt for the credentials ·          HTTP 401.1 error To fix these issues, need to disable Loopback check, Open Registry editor (regedit.exe) and locate the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa Create a new Key ( DisableLoopbackCheck ) Value of type DWORD inside it and set the value to 1 . Now test the host name : http://intranet.s...

This error occurred when you try to deploy app, reason for this error is not activated the developer feature on the SharePoint site where you want to deploy and test your application. The solution is to run SharePoint power shell and run following command:  Enable-SPFeature e374875e-06b6-11e0-b0fa-57f5dfd72085 -url http://webapplication

Please visit: https://community.nintex.com/thread/1417  contains(formatDate( currentdate ,"D"),"Sunday")

The solution is to run database update for Nintex Workflow in SharePoint Central Administration

This is to give you information about how to encrypt or then decrypt web.config particular section i.e. appSettings and connectionstrings. The reason to encrypt important web.config section(s) is the production environment. Following are the examples for encryption and decryption of web.config:- Encryption of the section: Before encryption: < runtime >     < assemblyBinding xmlns = " urn:schemas-microsoft-com:asm.v1 " appliesTo = " v2.0.50727 " >       < dependentAssembly >         < assemblyIdentity name = " System.Web.Extensions " publicKeyToken = " 31bf3856ad364e35 " />         < bindingRedirect oldVersion = " 1.0.0.0-1.1.0.0 " newVersion = " 3.5.0.0 " />       </ dependentAssembly >       < dependentAssembly >       ...

Useful attributes of the control: PermissionContext  - against which user permissions will be tested (possible values: CurrentSite, CurrentList, CurrentFolder, CurrentItem or RootSite) PemissionMode -  does the user have to meet all role definitions or just one of them (possible values: All or Any) PermissionsString -  what permissions does the user need to see the content - can enter some values separated by comma (possible values are from the enumeration SPBasePermissions: EmptyMask,ViewListItems,AddListItems,EditListItems,DeleteListItems,ApproveItems,OpenItems,ViewVersions, DeleteVersions,CancelCheckout,ManagePersonalViews,ManageLists,ViewFormPages,Open,ViewPages, AddAndCustomizePages, ApplyThemeAndBorder,ApplyStyleSheets,ViewUsageData,CreateSSCSite, ManageSubwebs,CreateGroups,  ManagePermissions,BrowseDirectories,BrowseUserInfo,AddDelPrivateWebParts, UpdatePersonalWebParts,ManageWeb,  UseClientIntegration,UseRemoteAPIs,ManageAlerts...