Desired State configuration

Desired State configuration.

A simple scenario what felt me to understand it, A lots need to cover and learn, but thought sharing it will be worth for the beginner like me. I am just in love with DSC.  Making sense Ahha :)

Execution happen in three steps, Make the configuration, Call it and Make it so (pointer to MOF)

 - Install PowerShell Version 4.0 and enable PowerShell Remoting.

A common problem on laptops is that the initial PowerShell Remoting configuration will fail because the system is connected to a public network.

Step 1.

Enable-PSRemoting -SkipNetworkProfileCheck -Force

Step 2. Make the configuration
#=====================================

Configuration MyFirstDSC
{


    Node 'Anirban-PC'
    {
        Service VM
        {
            Name = 'VMwareHostd'
            State = 'Running'
            StartupType = 'Automatic'
         

        }
    }
}

MyFirstDSC

#=================================================
Step 3 Execute the Powershell and it will create the Folder MyFirstDSC having the MOF

Step 4 Make it So.

Error-Handling Session in PSBUG

Thanks Ravi Sir for the DSC book and Deepak for giving the opportunity to speak in the group meet and Audience who come and join us today.

Error-Handling in PSBUG meet.

Sync Error Series - An object with DN "CN=" already exists in management agent

Note : This series is for the Beginner and trouble shooting the Error With Sync Engine, Based on Test Lab, Highly advice do not do Full Sync of the Management Agent. Errors are Fun, Debug It...!!

The Management Agent Run and see the error message in the Stack information.

"Microsoft.MetadirectoryServices.ObjectAlreadyExistsException: An object with DN "CN=4,OU=FIMOU,DC=corp,DC=fim2010,DC=com" already exists in management agent "ADMATest".
   at Microsoft.MetadirectoryServices.Impl.ConnectorImpl.Commit()
   at Miis_Metaverse.MVExtensionObject.Microsoft.MetadirectoryServices.IMVSynchronization.Provision(MVEntry mventry)"

The error message arise because there is already an existing object with the same DN in provisioning connector space.

Step 1.  Search the user in metaverse and the object will not existing in MV as it fails during the provisioning, First challenge is to bring the Object in MV.

Step 2.  Disable the Provisioning Rule Extension ( Tool-Options)
             Unchecked the option Enable Provisioning Rule Extension.

Step 3. Go to the connector space of the MA and commit preview, this will project the object in MV.

After Step 3,checked the option Enable Provisioning Rule Extension. See Step 2,
Step 4. See How to join connector Space Object to a MV object, the tech net link is below

Join a Connector Space Object to a Metaverse Object Link

 Go to Joiner Tab and Join the existing disconnect object to newly project object in MV.

This will fix the Error .. !! 

FIM: PowerShell to find manager detail of User

Link Code

Create multiple instances of custom Powershell object

function Aka($x,$y)
{
 $hash = @{          
        Value1       = $x
        Value2       = $y
    }                  
                                   
   New-Object PSObject -Property $hash  
}

$Obj=@()
$Obj+=Aka 1 2
$Obj+=Aka 2 3
$Obj+=Aka 3 4

How to use PowerShell to run FIM MA Profile with CSV configuration file

Link for the CODE

FIM : Group Membership Export GUI with Powershell

Powershell GUI to export the group membership from FIM portal, This will open up a PowerShell console window and simple GUI showing the input box for the name of group and Outbox for the membership of the group.In addition the membership of the group will export with name of the group in CSV in user profile.

To hide the powershell console window running at the background we can use PowerGUI to wrap it as an exe. 
Open the Script in PowerGUI Script Editor and then go to Tools > Compile Script.

Link for the code ....