Skip to main content

Desired state configuration – xComputer domain join


PowershellContact

Here we go again. This is just a short post on how to use the resource to join a computer to the domain. Steps we will perform:

  1. Download the resource from here. Follow the instructions to add it to the modules folder on you target computer.
  2. Create configuration data
  3. Build a very short configuration


Here is the configuration data we will use:


$ConfigData = @{  
   AllNodes = @(       
        @{    
            NodeName = "*"                    
            PSDscAllowPlainTextPassword = $true
         }
        @{    
            NodeName = "localhost"      
        }
);
   NonNodeData = @{
            domainName = "try.local"
      }
   } 


A few points to note here:
  1. We have a node called “*”. It is kind of a “wildcard”, however wildcards are not supported in DSC. All key/values you specify in this node, will get inherited by all nodes. That is why I do not need to specify the PSDscAllowPlainTextPassword for my node localhost.

  2. There is something called NonNodeData. Well as the name implies, it is configuration data that is not related specifically to any node. The data is available for all nodes. i have added the FQDN for my lab domain here.

Moving on to the configuration:



configuration DomainJoin
{
Param(
        [pscredential] $domainCred
)

    node $allnodes.nodename
    {
        xComputer join
        {
            Name = $allnodes.nodename
            DomainName = $ConfigurationData.NonNodeData.domainName
            Credential = $domainCred
        }
    }
}


As you can see, we are using the NonNodeData in the configuration and giving the configuration the domain name to join. Here is a screenshot of the applied configuration:

image

That is all there is to it.

Cheers

Comments

  1. Wont every computer this is run on be renamed to localhost?

    ReplyDelete
  2. Hi,

    No, it will not. DSC may consist of 2 parts. Configuration data (input) and the configuration itself. The separation is there to be able to scale the configuration to the level you want. The configuration data specifies the input/information your configuration (DSC) needs to execute, like domain name, credentials and what else. When you compile the configuration, that is run it, you pass in the configuration containing the name of the nodes this configuration should apply to. I have specified "localhost" as one node and the xComputer DSC resource will execute on the localhost and join it to the domain "try.local" with the current computername. Hope that explains it?

    Regards

    Tore

    ReplyDelete

Post a Comment

Popular posts from this blog

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:
Create a Management Pack for our customizations Create rules that collects the events from the orchestrator serverOff we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):



Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:



Give the…

Build your local powershell module repository - ProGet

So Windows Powershell Blog released a blog a couple of days ago (link). Not too long after, a discussion emerged about it being to complicated to setup. Even though the required software is open source (nugetgalleryserver), it looks like you need to have Visual Studio Installed to compile it. I looked into doing it without visual stuidio, however I have been unable to come up with a solution. I even tweeted about it since I am not an developer. Maybe someone how is familiar with “msbuild” could do a post on how to do it without VS.

Anyhow one of my twitter-friends (@sstranger) came to the rescue and pointed me in the direction of ProGet, hence the title of this post. ProGet comes in 2 different licensing modes
Free (reduced functionality)Enterprise (paid version with extra features)The good news is that the free version supports hosting a local PowershellGet repository which was my intention anyway. So off we go and create a Configration that can install ProGet for us. This is the conf…

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.


Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.


What should you log?

Anyt…