Duplicate LCM AgentID's

Welcome Forums DSC (Desired State Configuration) Duplicate LCM AgentID's

This topic contains 3 replies, has 2 voices, and was last updated by

 
Participant
3 years, 9 months ago.

  • Author
    Posts
  • #27841

    Participant
    Points: 0
    Rank: Member

    Hi,

    I have an AWS environment in which I configure instances from the same base image (AMI) using a DSC pull server. The base image has been syspreped.

    I am using ConfigurationNames to configure the LCM as I have multiple servers performing the same role.

    My problem is the instances created from my base image have the same LCM AgentID. I assume this is the reason they are initially configured correctly but sooner or later receive the wrong MOF from the pull server. This leads to somewhat interesting results.

    Is there a way to ensure each instance has a unique LCM AgentID? How and when is the AgentID set?

    Thanks

  • #27842

    Participant
    Points: 0
    Rank: Member

    Instead of syspreping and creating an AMI, is bootstrapping through userdata an option since creating the DSC pull server is fully scriptable.

  • #27844

    Participant
    Points: 0
    Rank: Member

    Thanks for the suggestion.

    I am syspreping as I need PS5 April Preview installed on my instances. I'm already using userdata to configure the LCM, I suppose I could install PS5 as part of my userdata bootstrap, but that requires a reboot and I would still need to configure the LCM.

  • #27872

    Participant
    Points: 0
    Rank: Member

    Turns out the AgentID is stored in HKLM:\Software\Microsoft\DesiredStateConfiguration.

    If I make sure it's unique before configuring the LCM all is well.

The topic ‘Duplicate LCM AgentID's’ is closed to new replies.

denizli escort samsun escort muğla escort ataşehir escort kuşadası escort