• Installed Puppet Master server
  • Node joined to Domain


We are using Facter for deploying nodes. Recommended way is to do the following:


mkdir -p /etc/facter/facts.d
echo "atomia_role=domainreg" >> /etc/facter/facts.d/atomiarole.txt



Replace "domainreg" with the role you want this node to have. 

In order for this to work there needs to be a matching .yaml file in /etc/puppet/hieradata folder.

Example yaml file


# domainreg.yaml
# Defines classes and variables needed to deploy domainreg
# Update file with valid values
  - atomia::domainreg

atomia::domainreg::service_url: ""
atomia::domainreg::service_username: "domainreg"
atomia::domainreg::service_password: "@tomiaPa11"
atomia::domainreg::opensrs_user: "atomia" 
atomia::domainreg::opensrs_pass: "83434c9300f6eba65f7ff971494bd2a4f4cc12d689b674bf5a95d71d469328b7a756f8abdc16a039$


Template files for each role can be found at 


If you used test modules so far, you will need to remove them from transformation files and replace with valid resources. Respectively "C:\Program Files (x86)\Atomia\AutomationServer\Common\ProvisioningDescriptions\Transformation Files\ProvisioningDescription.TestModules.xml" and "C:\Program Files (x86)\Atomia\AutomationServer\Common\Transformation Files\Resources.TestModules.xml"

An example of Domainreg section at Resources.TestModules.xml after changing back from test modules


			<module name="Atomia.Provisioning.Modules.DomainRegistration.DomainRegistration" resourceAsignmentPolicy="RoundRobin"  />
		<resource name="AtomiaDomainRegistration" >
			<property name="URL"></property>
			<property name="Username">domainreg</property>
			<property name="Password">@tomiaPa11</property>
			<property name="AcceptEmptyAuthcode">true</property>
			<property name="UpdateContacts">1</property>


Apply changes and restart Automation server


Start-Process "C:\Program Files (x86)\Atomia\AutomationServer\Recreate config files.lnk"
Get-Service AtomiaAutomation* | Stop-Service -PassThru
Get-Service AtomiaAutomation* | Start-Service -PassThru