SharePoint Secrets

AZ-300: Microsoft Azure Architecture Technologies Passed.

AZ-203: Developing Solutions for Microsoft Azure Passed.

AZ-400 Microsoft Azure DevOps Engineer Expert Passed.

An Agent that you set up and manage on you own to run jobs is a self-hosed agent.  You can use self-hosted agents in Azure Pipelines. In Azure DevOps Sever, agent pools are scoped to the entire server; so you can share the agent machines across projects and collections. When you create a pipeline, you specify which pool it uses. You create and manage agent pools from the agent pools tab in admin settings. Security of agent pools. Understanding how security works for agent pools helps you control sharing and use of agents. Roles are defined on each agent pool, and membership in these roles governs what operations you can perform on an agent pool. Role on an agent pool in organization settings Purpose Reader Members of this role can view the agent pool as well as agents. You typically use this to add operators that are responsible for monitoring the agents and their health. Service Account ...

How to easily deploy the Angular app to Azure by configuring build and release pipelines in Azure DevOps Create build pipeline definition To create a build pipeline that will create the optimized version of the app. Start with creating a new build pipeline from Pipelines >> Build on your team project in the browser. In this pipeline, you will add following tasks: Once this build pipeline is defined, you can queue the build. The created artifact should contain a file named dest.zip which will be used to do the deployment. Release & Deploy To do the deployment of the app, we will create a Release Pipeline. Under the Pipeline tab, select the build pipeline that you have created earlier as the artifact source to be deployed. Let the default version be the “Latest”. Under the Tasks tab, Select your Azure Account and authorize Azure DevOps to access resources from that Azure account when prompted. Now, select the task that is automatically ad...

Detecting SharePoint environment from an SPFX. SPFX web parts can be added to modern and classic SharePoint pages and we might need to load different resources depending of the environment type. The environment type can be detected using the EnvironmentType enumeration, directly from your SPFX code. Member Description ClasicSharePoint Indicates that the framework was loaded from a classic SharePoint page Local Indicates that the framework was loaded from the workbench SharePoint Indicates that the framework was loaded by a client-rendered SharePoint page Test Represents the scenario of the framework hosted in a unit/integration test To detect the environment type start by importing the enumeration from the sp-core-library: import { Environment, EnvironmentType} from '@microsoft/sp-core-library'; Use the code below to target...

The following REST commands are available for creating a modern SharePoint Communication site: Create . Create a new SharePoint site. Delete . Deletes a SharePoint site. Status . Get the status of a SharePoint site. The base URL for the REST commands is  _api/SPSiteManager . Create a modern site Using the following REST api you can create both Communication sites and non-group associated Team Sites. To specify which type of site to create you use the WebTemplate attribute. Use one of the following templates to select which type of site to create: Communication Site:  SITEPAGEPUBLISHING#0 non-group associated Team Site:  STS#3 JSON url: /_api/SPSiteManager/create accept: application/json;odata.metadata=none odata-version: 4.0 method: POST body: { "Title" : "Communication Site 1" , "Url" : "https://contoso.sharepoint.com/sites/commsite1" , "Lcid" : 1033 , "ShareByEmailEnabled" : false , ...

Deploying SharePoint Server Hybrid MS-301  Completed.

Protocol Port Usage Comment TCP 80 http Client to SharePoint web server traffic (SharePoint – Office Web Apps communication) TCP 443 https/ssl Encrypted client to SharePoint web server traffic (Encrypted SharePoint – Office Web Apps communication) TCP 1433 SQL Server default communication port. May be configured to use custom port for increased security UDP 1434 SQL Server default port used to establish connection May be configured to use custom port for increased security TCP 445 SQL Server using named pipes When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP port 445 TCP 25 SMTP for e-mail integration Cannot be configured TCP 16500-16519 Ports used by the search index component Intra-farm only Inbound rule Added to Windows firewall by SharePoint TCP 22233-22236 Ports required for the AppFabric Caching Service Distributed Cache… TCP 808 Windows Communication Foundation communic...

SharePoint 2016 70-339 Completed.

High Level Steps to enable TDE Create the DMK Create the TDE Cert Backup the TDE Cert Create the DEK Encrypt the DB Monitor Progress 1. Creating the Database Master Key (DMK) Symmetric key used to protect private keys and asymmetric keys Protected itself by Service Master Key (SMK), which is created by SQL Server setup Use syntax as follows:   USE master; GO CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'P@ssword1'; GO 2. Create Certificate Protected by DMK Protected by the DMK Used to protect the database encryption key Use syntax as follows: USE master; GO CREATE CERTIFICATE CompanyABCtdeCert WITH SUBJECT = 'CompanyABCTDE Certificate' ; GO 3. Backup Master Key and Cert Without a backup, data can be lost Backup creates two files, the Cert backup and the Private Key File Use following syntax: USE master; GO BACKUP CERTIFICATE CompanyABCtdeCert TO FILE = 'c:\Backup\BackupCompanyABCtdeCERT.cer' WITH PRIVATE KEY ( FILE = 'c:\Backup\Backu...

WebHost failed to process a request.  Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/17653682  Exception: System.ServiceModel.ServiceActivationException: The service '/SecurityTokenServiceApplication/securitytoken.svc' cannot be activated due to an exception during compilation.  The exception message is: Exception has been thrown by the target of an invocation.. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: The farm is unavailable.    at Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceManager.get_Local()    at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceConfiguration..ctor()    --- End of inner exception stack trace ---    at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle...

In my web part I used followig code I used to write the code like this using (SPSite _site = SPContext.Current.Site) { using (SPWeb _web = site.RootWeb) { // your code } } To correct this issue use code like following in my web part SPSite currSite = SPContext.Current.Site; SPWeb currWeb = currSite.RootWeb; using (SPSite eSite = new SPSite(currSite.ID)) { using (SPWeb eWeb = eSite.OpenWeb(currWeb.ID)) { //Your code } } Happy coding…

Step 1 :  Take backup of Managed Metadata server application DB. Step 2 :  Restore the MMS DB in SP 2013 SQL environment. Step 3 :  To Store the application pool that you want to use as a variable for this service application, at the PowerShell command prompt, type the following command : $applicationPool = Get-SPServiceApplicationPool -Identity 'SharePoint Web Services default' * SharePoint Web Services default  is the name of the service application pool that will contain the new service applications. Step 4 :  To upgrade the MMS, type the following command in PowerShell command prompt: $mms = New - SPMetadataServiceApplication - Name 'My Managed Metadata Service Application' - ApplicationPool $applicationPool - DatabaseName 'Managed Metadata Service_DB' Step 4 :  Type the following command in PowerShell command prompt for creating proxy service: New - SPMetadataServiceApplicationProxy - Name " My Managed Metadata Service Proxy"...

Welcome to SharePoint 2013  I just finished upgrading my SP 2010 website  to SP 2013 by attached content database More details about upgrade process from here: http://technet.microsoft.com/en-us/library/cc262483(v=office.15)

Unable to start User Profile sync service from Central administration site -system settings-Services on server. The service freezes at "starting" and never start. Below are the information from event viewer and verbose enabled ULS logs. I found the below solution at  Here Resolution - Stop User profile service and User profile sync service on ALL SharePoint servers in the farm - Clear timer config cache by following the "resolution" documented at http://support.microsoft.com/kb/939308 - Deleted the Pending timer job related to the UPA sync service provisioning using Central administration-Monitoring-check job status - Confirmed that the security token service has only windows and anonymous enabled ( from IIS manager-SharePoint web services-Security token service-Authentication (under IIS)) - On the SharePoint server access the registry editor and confirm that the information related to FIM ( database servername , sync DB name etc ) are prope...

I have encountered the  User cannot be found  error a few times when accessing the  List Settings  or  Library Settings . Solution: To republish the workflows you can follow the next steps: Open your site in SharePoint Designer 2010 Click on the  Workflows  link from the  Site Objects  menu Click on the workflow name, this will open your workflow Click on the  Publish  button Do step 3 and 4 for all the workflows. Go back to your  List  or  Library Settings  and the error should be gone.

Found article at http://www.lamber.info/post/2010/12/12/Setting-up-a-managed-metadata-service-application-to-server-one-or-more-web-applications.aspx Assigning two or more managed metadata service applications to a single web application You are also able to assign multiple service applications to a single web application. When doing so with a managed metadata service application, however, you have to consider some settings before proceeding. Imagine that you have to maintain two separate managed metadata service applications for two different departmental projects. You can do this by creating two separate managed metadata service applications and assign them to the corresponding web applications. After a while, you need to combine both service applications for a single web application. You can do this by following the same steps as seen in the previous scenario. Choose the service applications that you want to consume in your web application by selecting a proxy group or def...

Here is message from the log file C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\LOGS High     #160005: Bad response from SMTP host'mail.mydomain.com': 554 5.7.1 : Client host rejected: Access denied. I resolved this SMTP issues after adding all WFE server IP into SMTP relay address. One of our DMZ WFE IP was not added into SMTP relay address. That's the reason all the OOTB overdue mail notification failed and got the below message: The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly. 

 I added robots.txt on our preview server to prevent Google’s bot or Bing’s bot from indexing our business’s preview sites. Original robots.txt: User-agent: * Disallow: / Effectively it should stop all legitimate bots from indexing preview sites. However this also stopped SharePoint 2010’s search crawler from crawling the sites. Any full crawl gave me 0 results. Updated robots.txt: User-agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 6.0 Robot) Allow: / User-agent: * Disallow: /