Tag: ALM

ALM, DevOps, DSC, PowerShellLeave a comment

Don’t forget the NodeName in your DSC ConfigurationData

Michael (Mike) Kaufmann

Today I created a new configuration data for a DSC configuration and got the following error: all elements of AllNodes need to be hashtable and has a property ‘NodeName’. The config looked good: AllNodes was a hashtable and it had the desired node name. So where was the error? I forgot one little thing: the global configuration needs a property NodeName set to an asterisk. Adding this fixed the error. This is really easy – but a search for the error message did not return any useful results. Therefor I decided to share it anyway… Continue reading Don’t forget the NodeName in your DSC ConfigurationData

ALM, DevOps, DSC, PowerShell2 Comments

Be careful with custom variable names in Release Management

Michael (Mike) Kaufmann

If you use Visual Studio Release Management vNext / 2013 with PowerShell/DSC you probably have a lot of custom configuration variables that you pass to your scripts. Be careful when you choose the names for these variables because! There are a lot of reserved words. For example the word UserName is reserved. This leads to very odd error messages that are really hard to track down: System.AggregateException: One or more errors occurred. —> Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException: Permission denied while trying to connect to the target machine <hostname> on the port:5985 via power shell remoting. Please check the following link for instructions: http://go.microsoft.com/fwlink/?LinkID=390236System.Management.Automation.Remoting.PSRemotingTransportException: … Continue reading Be careful with custom variable names in Release Management

ALM, DevOps, PowerShellLeave a comment

Deploy to none domain machines with Visual Studio Release Management vNext

Michael (Mike) Kaufmann

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

ALM, Development, DevOps, O365, SharePointLeave a comment

Side notes for SharePoint and O365 developers from #MSIgnite

Michael (Mike) Kaufmann

I’m not trying to cover all relevant aspects of SharePoint announcements that are made the last days on Microsoft Ignite – I’m sure you’re all following it closely. I just want to highlight the most important aspects for SharePoint developers and the impact they have on my work. Provisioning Engine The Office365 Developer Patterns and Practices group announced a provisioning engine for provisioning SharePoint artifacts (sites, lists, fields, content types etc.). It takes a xml file with a custom syntax as the input and provisions the content using the API. It also works both ways – you can use the … Continue reading Side notes for SharePoint and O365 developers from #MSIgnite

ALM, DevOps, DSC, O365, PowerShell, SharePointLeave a comment

xSharePointProvisioning Module – PowerShell Desired State Configuration (DSC)

Michael (Mike) Kaufmann

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)

ALM, DevOps, DSC, PowerShellLeave a comment

Moving from PowerShell DSC to Release Management vNext DSC

Michael (Mike) Kaufmann

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

ALM, ScrumLeave a comment

Agile Entwicklung mit TFS 2013 und der Scrum Prozessvorlage – Part 1

Michael (Mike) Kaufmann

Der Microsoft Team Foundation Server 2013 zusammen mit Visual Studio unterstützt Sie bei der agilen Planung und Entwicklung einer Lösung mit Scrum. Ich zeige Ihnen die neuen Features und wie sie im Prozess eingesetzt werden können. Scrum ist der De-Facto-Standard bei den agilen Entwicklungsmethoden. In den Schulungen und Kursen wird immer noch viel mit Flipcharts und Whiteboards gearbeitet. Dies ist zwar sehr haptisch und mag pädagogisch sinnvoll sein – in der Praxis hat es aber mehr Nach- als Vorteile. So eignen sich Whiteboards nicht für die Verwendung in agilen Teams, die Archivierung ist nur bedingt möglich und eine langfristige Zuordnung … Continue reading Agile Entwicklung mit TFS 2013 und der Scrum Prozessvorlage – Part 1