Deploy to none domain machines with Visual Studio Release Management vNext

There is a lot of documentation on how to deploy to machines outside your domain using agent based deployment ( i.e. on msdn) using shadow accounts. But I couldn’t find any documentation if and how this is done using vNext / agent-less deployment. If you deploy to server outside your domain you get the following error messge: Connecting to remote server <name> failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.  So this is … Continue reading Deploy to none domain machines with Visual Studio Release Management vNext

xSharePointProvisioning Module – PowerShell Desired State Configuration (DSC)

The xSharePointProvisioning module contains DSC resources to provision SharePoint artifacts using the Client Side Object Model (CSOM). There are two versions: one for O365 and ne for SharePoint on premise. Currently the following resources are in the package: xList Ensure a list with a specific title and description at a given URL. If the list does not exist it will be created with the specified template. xField Ensure that a list at a specific url has or has not a specified field. XListItem Ensure that a list at a specific url has or has not a list item with the … Continue reading xSharePointProvisioning Module – PowerShell Desired State Configuration (DSC)

Use the DSC Script resource to change the application pool identity

The Desired State Configuration (DSC) module xWebAdministration does not yet support changing the identity of an application pool. There is a community fork cWebAdministration that seems to support it –  but I have not tested it yet. What I did was to use the script resource to change the identity using the module WebAdministration. This is pretty straight forward so I just share the code here. Note that after changing the identity the state of the application pool is stopped. You can use the xWebAppPool resource to start it again. Continue reading Use the DSC Script resource to change the application pool identity

Configuring your SharePoint farm for DSC with xSharePointAdministration

Getting the xSharePointAdministration module to work has a lot of gotchas. So I decided to write a separate post for it. First of all: the xSharePointAdministration module uses the PSSnapin “Microsoft.SharePoint.PowerShell” for all its work. It therefore must be run on only one server in the farm – this would normally be the server that hosts the central administration. I will refer to this server as the deployment server. Make sure to do all the work on the deployment server. Desired state configurations are run by the Windows Management Instrumentation (winmgmt) service. This service normally runs under the “Local System” … Continue reading Configuring your SharePoint farm for DSC with xSharePointAdministration

Moving from PowerShell DSC to Release Management vNext DSC

If you’ve learned plain PowerShell Desired State Configuration (DSC) and then move to Visual Studio Release Management vNext there are a lot of gotchas that can cost you many hours or event days to figure them out. I thought I share some things I’ve learned the hard way to get people up and running more quickly. If you use plain DSC you normally have one structural configuration for the entire environment and an environment specific configuration that you change for each environment. Environment Configuration(Dev/Test/Prod) $TargetFolder = “C:\inetpub\wwwroot\Demo”$WebServerCount = 2 .psd1 Structural Configuration WindowsFeature IIS{    Name = “Web Server”    Ensure = … Continue reading Moving from PowerShell DSC to Release Management vNext DSC

Packaging DSC configurations for Visual Studio / TFS Release Management vNext

If you are using Visual Studio Release Management vNext to release your applications you’ll probably have DSC (Desired State Configuration) configurations that are shared between applications or provided by your operations team. In both cases they have a different lifecycle than your application and should be provisioned individually. But how do you publish PowerShell scripts or other files with the TFS build engine without creating empty solutions and adding the files? What you can do is to add a simple project file like TFSBuild.proj that calls a PowerShell script. This project file can be used in a team build. The … Continue reading Packaging DSC configurations for Visual Studio / TFS Release Management vNext

Add ApplicationInsights to your O365 SharePoint sites

If you use ApplicationInsights in your SharePoint Apps you might also want to include it in all sites of the hosting web. You can do this by injecting the corresponding JavaScript using the client side object model (CSOM) and UserCustomActions. Go to https://portal.azure.com/ and open your ApplicationInsights-Application or create a new one. Go to “Quick start” – “Get code to monitor my web pages” and copy the code insight the script tags. Save the script to a JavaScript file and upload it to your O365 site (i.e. to /Style%20Library). Use the following PowerShell script to inject the JavaScript file without … Continue reading Add ApplicationInsights to your O365 SharePoint sites

xSharePointAdministration Module – PowerShell Desired State Configuration (DSC)

Today I added the first version of the PowerShell Desired State Configuration (DSC) Module xSharePointAdministration to the Script Center. The module contains resources to configure and deploy SharePoint environments. The current version has only limited resources. I will add more resources in the near future since I have some projects that will build upon the module. The goal is to provision a complete SharePoint farm using DSC so that you can easily deploy it to different environments – either in the cloud or on premise – and avoid the configuration shift that normally takes place after some time between test, … Continue reading xSharePointAdministration Module – PowerShell Desired State Configuration (DSC)

How to get SharePoint developers to automate deployments

In every environment you need to automate the deployment process for SharePoint solutions – weather they’re sandboxed solutions, farm solutions or apps. But developers are lazy – and it’s so easy to click “Deploy” in VS that normally the deployment scripts are poorly tested. To get the developers to use and test the deployment scripts you have to integrate them in visual studio. If you use PowerShell scripts for your deployments and always place them in the same location this is pretty easy. You can add the scripts as “External Tools” and then add them to the context menu. To … Continue reading How to get SharePoint developers to automate deployments

Import von Profilbildern aus einem Fileshare direkt in den SharePoint

Normalerweise ist der übliche Weg die Profilbilder direkt über das AD in den SharePoint zu snychronisieren: In manchen fällen ist das aber nicht möglich, da die Bilder nicht im AD vorgehalten werden sollen. In diesem Fall muss der Import dazu also direkt erfolgen: Bei einem Kunden ist der Fileshare sogar das führende System. Es wird also eine Synchronisation zwischen dem Fileshare und SharePoint benötigt. Das Passende Skript kann im Skript-Galerie heruntergeladen werden: http://gallery.technet.microsoft.com/scriptcenter/Sync-profile-pictures-from-c6d7608a Das Skript wird wie folgt aufgerufen: Folgende Parameter werden verwendet: -path: Der Pfad zu dem Fileshare -url: Die URL des MySite-Hosts -userProfilePropertyName: Der Name der Eigenschaft des … Continue reading Import von Profilbildern aus einem Fileshare direkt in den SharePoint