Displaying 6 results from an estimated 6 matches for "chdcdomain".
2018 Oct 12
2
backup of tdb files
...ber password:
secrets_fetch_machine_password(lp_workgroup(), …)
== SECRETS/MACHINE_DOMAIN_INFO/WORKGROUPNAME
This approach works well with a manually joined AD member but not
with any of the blackbox testsuites. In the secrets.tdb used
during tests I find only the domain SID (e. g. SECRETS/SID/CHDCDOMAIN)
but not the machine sid (probably SECRETS/SID/CLIENT).
How come that machine sid is absent in the tests? Is there
another means of retrieving it?
Thank you and enjoy the weekend,
Philipp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: appl...
2018 Oct 15
2
backup of tdb files
...workgroup(), …)
> > == SECRETS/MACHINE_DOMAIN_INFO/WORKGROUPNAME
> >
> > This approach works well with a manually joined AD member but not
> > with any of the blackbox testsuites. In the secrets.tdb used
> > during tests I find only the domain SID (e. g. SECRETS/SID/CHDCDOMAIN)
> > but not the machine sid (probably SECRETS/SID/CLIENT).
> >
> > How come that machine sid is absent in the tests? Is there
> > another means of retrieving it?
>
> This is due to the test environment you are running in. If you ran it
> in ad_member:local it wo...
2018 Oct 12
0
backup of tdb files
...etch_machine_password(lp_workgroup(), …)
> == SECRETS/MACHINE_DOMAIN_INFO/WORKGROUPNAME
>
> This approach works well with a manually joined AD member but not
> with any of the blackbox testsuites. In the secrets.tdb used
> during tests I find only the domain SID (e. g. SECRETS/SID/CHDCDOMAIN)
> but not the machine sid (probably SECRETS/SID/CLIENT).
>
> How come that machine sid is absent in the tests? Is there
> another means of retrieving it?
This is due to the test environment you are running in. If you ran it
in ad_member:local it would be there.
The 'client'...
2018 Oct 15
0
backup of tdb files
...> == SECRETS/MACHINE_DOMAIN_INFO/WORKGROUPNAME
> > >
> > > This approach works well with a manually joined AD member but not
> > > with any of the blackbox testsuites. In the secrets.tdb used
> > > during tests I find only the domain SID (e. g. SECRETS/SID/CHDCDOMAIN)
> > > but not the machine sid (probably SECRETS/SID/CLIENT).
> > >
> > > How come that machine sid is absent in the tests? Is there
> > > another means of retrieving it?
> >
> > This is due to the test environment you are running in. If you ran it...
2018 Oct 18
1
backup of tdb files
...ACHINE_DOMAIN_INFO/WORKGROUPNAME
> > > >
> > > > This approach works well with a manually joined AD member but not
> > > > with any of the blackbox testsuites. In the secrets.tdb used
> > > > during tests I find only the domain SID (e. g. SECRETS/SID/CHDCDOMAIN)
> > > > but not the machine sid (probably SECRETS/SID/CLIENT).
> > > >
> > > > How come that machine sid is absent in the tests? Is there
> > > > another means of retrieving it?
> > >
> > > This is due to the test environment you...
2018 Sep 24
2
backup of tdb files
Hi Andrew,
thanks for addressing all my points. This is rather helpful.
-<| Quoting Andrew Bartlett <abartlet at samba.org>, on Friday, 2018-09-21 08:23:26 AM |>-
> On Fri, 2018-09-21 at 11:29 +0200, Philipp Gesang via samba wrote:
> > how would I go about dumping tdb files in a “neutral” format,
> > preferably JSON?
> >
> > The goal is to have a domain