Running commands locally

[casey-robertson]

Just trying to test this out and it's not going well. Folder from dev branch has been cloned to C:\Windows\System32\WindowsPowerShell\v1.0\Modules\ServiceBusForWindowsServerDsc

if I run the following:
$RunAsAccount = 'Administrator'
$SBFarmDBConnectionStringDataSource = 'localhost'

$result = Invoke-DscResource -Name SBFarm -Method Test -ModuleName ServiceBusForWindowsServerDsc -Property @{

                                            RunAsAccount=$RunAsAccount;
                                            SBFarmDBConnectionStringDataSource=$SBFarmDBConnectionStringDataSource } -Verbose
        $result | fl * 

I get:

Invoke-DscResource : Failed to create an object of PowerShell class SBFarm.
At line:1 char:11

• $result = Invoke-DscResource -Name SBFarm -Method Test -ModuleName Se ...

•       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidOperation: (root/Microsoft/...gurationManager:String) [Invoke-DscResource], CimEx
    ception
  • FullyQualifiedErrorId : InstantiatePSClassObjectFailed,Microsoft.PowerShell.DesiredStateConfiguration.Commands.I
    nvokeDscResourceMethodCommand

Ideas? I'm going to attempt to leverage DSC via Chef but to test it out I just wanted to get it running in a local context. Not sure what I'm doing wrong.

[ryanspletzer]

Hi @casey-robertson, thanks for reporting this issue. This is still a very early pre-release version of this module and I appreciate your feedback. I wanted to get an initial early pre-release version out there so I can find out about issues like this.

For full transparency, I was pursuing developing this resource module heavily for use in automating a standalone Service Bus for Windows Server 1.1 instance at work (as, much to my surprise, Microsoft had made DSC resource modules for most other products but not for SB4WS).

However recently Microsoft announced that there will not be a follow-up on-premises version of Service Bus for Windows Server:

https://azure.microsoft.com/en-us/blog/collaboration-and-federation-azure-service-bus-messaging-on-premises-futures/

Long term support will only be available for Service Bus for Windows Server used in conjunction with SharePoint 2013+ products. (Sidenote: I was hoping to write a DSC module for Workflow Manager 1.0 at some point, too, again to run standalone, but that product is following similar route of SB4WS, will only be supported long term in conjunction with SharePoint 2013+ and won't have a follow-up on-premises — see comments in that linked blog post above.)

Anyways, I do want to try to help to maintain this as I think it will be helpful for SharePoint 2013 / 2016 administrators with its SharePointDsc module for the foreseeable future. (I have a soft spot for SharePoint since I used to develop for it). But as my primary standalone use case will not be supported over time, and there won't be another version of this product, I have not investing large amounts of time recently into working on this...

I welcome any help / support from the community who would like to contribute.