I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05 C:\Temp>facter domain none C:\Temp> Thanks a lot, Mohamed. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Mohamed, On Fri, Nov 18, 2011 at 6:02 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote:> I could swear this worked fine earlier.. Now facter, and hence puppet, > do not see the domain name anymore: > > What could cause this? > > C:\Temp>facter --version > 1.6.2 > > C:\Temp>facter | findstr kernel > kernel => windows > kernelmajversion => 6.1 > kernelrelease => 6.1.7601 > kernelversion => 6.1.7601 > > C:\Temp>facter fqdn > NCS-VDI-05.none > > C:\Temp>facter hostname > NCS-VDI-05 > > C:\Temp>facter domain > none >Facter uses WMI to retrieve the DNSDomain property for the first IPEnabled interface, similar to what is done on other platforms. If you''ve added a new IPEnabled interface that doesn''t have a DNSDomain, then facter may be choosing that one first. Try running the following: wmic path Win32_NetworkAdapterConfiguration get caption, ipenabled, dnsdomain Thanks, Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Indeed, I started a VPN connection, and that connection did not have domain set... maybe setting certname in all Windows clients, along with show_diff=false, would be a best practice. Thanks, Mohamed. On Sat, Nov 19, 2011 at 4:04 PM, Josh Cooper <josh@puppetlabs.com> wrote:> Hi Mohamed, > > On Fri, Nov 18, 2011 at 6:02 PM, Mohamed Lrhazi <lrhazi@gmail.com> wrote: >> >> I could swear this worked fine earlier.. Now facter, and hence puppet, >> do not see the domain name anymore: >> >> What could cause this? >> >> C:\Temp>facter --version >> 1.6.2 >> >> C:\Temp>facter | findstr kernel >> kernel => windows >> kernelmajversion => 6.1 >> kernelrelease => 6.1.7601 >> kernelversion => 6.1.7601 >> >> C:\Temp>facter fqdn >> NCS-VDI-05.none >> >> C:\Temp>facter hostname >> NCS-VDI-05 >> >> C:\Temp>facter domain >> none > > > Facter uses WMI to retrieve the DNSDomain property for the first IPEnabled > interface, similar to what is done on other platforms. If you''ve added a new > IPEnabled interface that doesn''t have a DNSDomain, then facter may be > choosing that one first. Try running the following: > wmic path Win32_NetworkAdapterConfiguration get caption, ipenabled, > dnsdomain > Thanks, > Josh > -- > Josh Cooper > Developer, Puppet Labs > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.