In Part 1 of this series I talked about how I demo’d the building of a Domain Controller. In Part 2 I talked about demoing the building of a Pull Server, an App Server, and then using the two servers to show how a Pull Server works and what needs to be done to make
Demo DSC – Part 2
In Part 1 of this series I talked about how I demo’d the building of a Domain Controller. In Part 2 I am going to talk about how I demo’d building a Pull Server, an App Server, and used the two servers to show how a Pull Server works and what needs to be done
Demo DSC – Part 1
This is the first in a series of posts outlining how I presented a demo of Desired State Configuration (DSC) for the organization I work for. This was never intended to demonstrate all the features and capabilities of DSC (there’s a lot!), but instead was done to show at a high level the kinds of
Exploring the PowerShell DSC xPendingReboot Resource
While building a DSC Demo for the new job this week I got the chance to explore using many of the “new” Resources that have been released. One of those Resources is the xPendingReboot which I am going to talk about here, because the documentation wasn’t very clear (to me anyways after having been away
Moving SCOM 2012 R2 Data Warehouse Database to New SQL Server Cluster
This is the second of two posts in regards to moving Operations Manager 2012 R2 Databases. The first post about moving the OperationsManager database can be found here. I won’t rehash any of that information but will instead just get right into the How To portion. The TechNet article for moving the SCOM DataWarehouse Database
Moving SCOM 2012 R2 Database to New SQL Server Cluster
When our System Center environment (VMM, Orchestrator, SCOM, DPM) was originally setup all the databases were installed on a single SQL Server VM (but in separate instances). For a variety of reasons I made the decision that our System Center databases needed to at least be in a cluster configuration. Luckily I stumbled across this excellent guide
2015 PowerShell Resolutions
I am stealing this idea from Boe Prox. He blogged about his own PowerShell Resolutions for 2015. I will keep this short and sweet. In no particular order here are my PowerShell Resolutions for 2015: Figure out a PowerShell related topic to speak about that I won’t get bored with in a month or two
Creation of the VMM Resource Group Failed
While trying to install VMM as a Highly Available following the steps in this article, I kept running into the same issue over and over and over again. The installation would start, run for a few minutes, and then fail and rollback with this error at the end: “Creation of the VMM resource group VMM
PowerShell DSC Journey – Day 23
No intro. Going right back into trying to add a Network Adapter and a VMNetwork to that adapter. I look first at the hardware profile, and lo and behold I have 9 legacy network adapters, which is interesting because yesterday I had none. So, I remove them all first. Ok, first things first, let’s make
PowerShell DSC Journey – Day 22
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.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
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.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 |
$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.