Page 5

PowerShell DSC Journey – Day 22

July 10, 2014 Jacob Benson

Alright, after my little fiasco yesterday I need to do a little re-configuring of my Configuration because of course DSC will not allow a Plain text password.

PS C:\Scripts> C:\Users\jacob.benson\SkyDrive\PowerShell\DSC\TestSCVMMHardware.ps1
ConvertTo-MOFInstance : System.InvalidOperationException error processing property 'Credential' OF TYPE 'cSCVMM_Hardware': Converting and storing encrypted passwords as plain text is not recommended for security reasons. If you understand the risks, you 
can add a property named “PSDscAllowPlainTextPassword” with a value of “$true” to your DSC configuration data, for each node where you want to allow plain text passwords. For more information about DSC configuration data, see the TechNet Library topic, 
http://go.microsoft.com/fwlink/?LinkId=386620.
At C:\Users\jacob.benson\SkyDrive\PowerShell\DSC\TestSCVMMHardware.ps1:13 char:9
+   cSCVMM_Hardware
At line:180 char:16
+     $aliasId = ConvertTo-MOFInstance $keywordName $canonicalizedValue
+                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], InvalidOperationException
    + FullyQualifiedErrorId : FailToProcessProperty,ConvertTo-MOFInstance
Errors occurred while processing configuration 'TestSCVMMHardware'.
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:2203 char:5
+     throw $errorRecord
+     ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (TestSCVMMHardware:String) [], InvalidOperationException
    + FullyQualifiedErrorId : FailToProcessConfiguration

PS C:\Scripts> C:\Users\jacob.benson\SkyDrive\PowerShell\DSC\TestSCVMMHardware.ps1

ConvertTo-MOFInstance : System.InvalidOperationException error processing property 'Credential' OF TYPE 'cSCVMM_Hardware': Converting and storing encrypted passwords as plain text is not recommended for security reasons. If you understand the risks, you

can add a property named “PSDscAllowPlainTextPassword” with a value of “$true” to your DSC configuration data, for each node where you want to allow plain text passwords. For more information about DSC configuration data, see the TechNet Library topic,

http://go.microsoft.com/fwlink/?LinkId=386620.

At C:\Users\jacob.benson\SkyDrive\PowerShell\DSC\TestSCVMMHardware.ps1:13 char:9

+ cSCVMM_Hardware

At line:180 char:16

+ $aliasId = ConvertTo-MOFInstance $keywordName $canonicalizedValue

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (:) [Write-Error], InvalidOperationException

+ FullyQualifiedErrorId : FailToProcessProperty,ConvertTo-MOFInstance

Errors occurred while processing configuration 'TestSCVMMHardware'.

At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\PSDesiredStateConfiguration.psm1:2203 char:5

+ throw $errorRecord

+ ~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (TestSCVMMHardware:String) [], InvalidOperationException

+ FullyQualifiedErrorId : FailToProcessConfiguration

Here is the new version of the Configuration.

$ConfigData = @{
    AllNodes = @(
        @{
            NodeName = "localhost"
            PSDSCAllowPlainTextPassword = $True
            }
    )
}

Configuration TestSCVMMHardware
{

    param
    (
        [PSCredential]$Credential = (Get-Credential)
    )

    Import-DscResource -Module cSCVMM

    node $AllNodes.NodeName
    {
        cSCVMM_Hardware MyHardwareProfile
        {
            VMMServer = "MY-VMM-SERVER1"
            CPUCount = 2
            DVDDrive = $True
            Ensure = "Present"
            Name = "Jacobs Profile"
            VMNetwork = "Server Traffic"
            Credential = $Credential
       }

    }

}

TestSCVMMHardware -ConfigurationData $ConfigData

$ConfigData = @{

AllNodes = @(

NodeName = "localhost"

PSDSCAllowPlainTextPassword = $True

}

)

}

Configuration TestSCVMMHardware

{

param

(

[PSCredential]$Credential = (Get-Credential)

)

Import-DscResource -Module cSCVMM

node $AllNodes.NodeName

{

cSCVMM_Hardware MyHardwareProfile

{

VMMServer = "MY-VMM-SERVER1"

CPUCount = 2

DVDDrive = $True

Ensure = "Present"

Name = "Jacobs Profile"

VMNetwork = "Server Traffic"

Credential = $Credential

}

TestSCVMMHardware -ConfigurationData $ConfigData

Now, let’s try to run this and see what breaks. And. Nothing breaks. I am literally speechless. Seriously.

Tecumseh Poem from Act of Valor

July 10, 2014 Jacob Benson

So live your life that the fear of death can never enter your heart. Trouble no one about their religion; respect others in their view, and demand that they respect yours. Love your life, perfect your life, beautify all things in your life. Seek to make your life long and its purpose in the service

PowerShell DSC Journey – Day 21

July 9, 2014 Jacob Benson

Alright, when I left off I had added in some testing for the $Credential Property of the Resource in the Get-TargetResource and Test-TargetResource functions. Today I am going to do the same with Set-TargetResource, and then test my Configuration to see what I did wrong. If I survive that I will try to create a

PowerShell DSC Journey – Day 20

July 8, 2014 Jacob Benson

When I left off yesterday I was trying to actually run a Configuration to create a Hardware Profile, and quickly realized that I was going to need a Credential parameter in order to do this, because not just anyone can connect to a Virtual Machine Manager server. So today’s post is going to be about

PowerShell DSC Journey – Day 19

July 7, 2014 Jacob Benson

Alright, so in my last post I was able to resolve the issue with my Custom Resource not showing up under Get-DSCResource (because as usual I was doing something dumb). Proof!

PS C:\Scripts> Get-DscResource

ImplementedAs   Name                      Module                         Properties                                        
-------------   ----                      ------                         ----------                                        
Binary          File                                                     {DestinationPath, Attributes, Checksum, Content...
PowerShell      SCVMM_Hardware            cSCVMM                         {Name, VMMServer, CPUCount, DependsOn...}

PS C:\Scripts> Get-DscResource

ImplementedAs Name Module Properties

------------- ---- ------ ----------

Binary File {DestinationPath, Attributes, Checksum, Content...

PowerShell SCVMM_Hardware cSCVMM {Name, VMMServer, CPUCount, DependsOn...}

Now, let’s try and write a Configuration! Look ma, no errors!

Configuration TestSCVMMHardware
{

    Import-DscResource -Module cSCVMM

}

Configuration TestSCVMMHardware

{

Import-DscResource -Module cSCVMM

}

Let’s build this out for a test.

Configuration TestSCVMMHardware
{

    Import-DscResource -Module cSCVMM

    node localhost
    {
        SCVMM_Hardware MyHardwareProfile
        {
            VMMServer = "SC-VMM01"
            CPUCount = 2
            DVDDrive = $True
            Ensure = "Present"
            Name = "Jacobs Profile"
            VMNetwork = "Server Traffic"
       }

    }

}

TestSCVMMHardware

Configuration TestSCVMMHardware

{

Import-DscResource -Module cSCVMM

node localhost

{

SCVMM_Hardware MyHardwareProfile

{

VMMServer = "SC-VMM01"

CPUCount = 2

DVDDrive = $True

Ensure = "Present"

Name = "Jacobs Profile"

VMNetwork = "Server Traffic"

}

TestSCVMMHardware

I run this

PowerShell DSC Journey – Day 18

July 2, 2014 Jacob Benson

Yesterday I finished up modifying the Set-TargetResource function and doing all the tests and it seems to be working exactly the way that I want. The next step today is to turn this into a module, import it, write a DSC Configuration and see if it actually works. I already have my SCVMM_Hardware.psm1 file, so

PowerShell DSC Journey – Day 17

June 30, 2014 Jacob Benson

Alright. So yesterday I worked through some issues in the Set-TargetResource Function and left off with a big one still remaining. Namely, that even though I have Ensure = Present in my test of the Function, it is running through the Ensure = Absent portion of the script if the Hardware Profile already exists, which

PowerShell DSC Journey – Day 16

June 27, 2014 Jacob Benson

When I left off yesterday I had a somewhat functioning Set-TargetResource function. I use functioning in the way that when something kind of works and doesn’t throw errors but doesn’t actually do anything functions. So, today I am going to be figuring out where I screwed up my logic and getting this Resource to work.

PowerShell DSC Journey – Day 15

June 25, 2014 Jacob Benson

So when I left off yesterday I appeared to have my Get and Test TargetResource functions working properly, now it’s time to work on the Set-TargetResource function, which is probably where the fun will happen. When I go to set the Resource, I have a couple of different scenarios I need to work through. Hardware

PowerShell DSC Journey – Day 14

June 24, 2014 Jacob Benson

When I left off yesterday, I had modified my Get-TargetResource to work (hopefully) with all the new properties I had setup for my Custom Resource. Now, I am going to test this, and DSC willing I will be able to move on to the Target Resource functions today before I finish this thing out. First