Interview over wiki ninja

-

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 User Profile synchronization versus import

-
Reference is : 2013 advanced Training User Profile Service administrators in SharePoint 2013 can use profile synchronization to manage and synchronize the user and group profile data stored in the SharePoint 2013 profile store with profile data stored in directory services and BDC systems. There are two distinct forms of profile import and synchronization available in SharePoint 2013: ·          One-way profile import. This is a new implementation of a simple import process that was first provided in SharePoint Server 2007. It uses the SharePoint Active Directory Import option to import user profile data from Active Directory Domain Services (AD DS). Note: One-way profile import only works with Active Directory and does not support other directory services. ·          Two-way profile synchronization. This uses the SharePoint Server 2013 profile synchronization method that was first introduced...
Read more

PowerShell scripts to Create personal site

-
$site=Get-SPSite "https://mysitesp2013.x.com"; $serviceContext = Get-SPServiceContext -Site $site $userProfileConfigManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($serviceContext) $testuser = $userProfileConfigManager.GetUserProfile("domain\user") $testuser.PersonalSiteInstantiationState $testuser.CreatePersonalSite()
Read more

SharePoint 2013 Host Named Site Collection (HNSC) Overview

-
Image
With the rising of the amazing SharePoint 2013 technology and introducing of a type of Site Collection called Host Named Site Collection (HNSC) which is suitable for models where depending on DNS host names and in multi- tenant environments. I will be collecting some data from several sources and based on my personal experience about host-named site collections. In SharePoint 2013, you can either create path based site collections or host-named site collections. Host-named site collections enable you to assign a unique DNS name to site collections. For example, you can address them as  http://TeamA.domain.com    and  http://TeamB.domain.com    . This enables you to deploy many sites with unique DNS names in the same web application. It also enables hosters to scale an environment to many customers. If you do not use host-named site collections, your SharePoint web application will contain many path-based site collections that share the same ho...
Read more