[cifs-protocol] [REG:110101173790653] MS-SAMR 126.96.36.199.1 objectClass; UF_PASSWD_NOT_REQD when objects using UF_WORKSTATION_TRUST_ACCOUNT are created
bburgin at microsoft.com
Mon Oct 11 15:23:24 MDT 2010
[Changing case title to reflect new case number]
I created a new case for this issue: SR 110101173790653. Also, please respond to Hongwei's question below ("could you give a little more description about the blackbox test which reproduces the behavior?")? Once we receive that information, someone from the team will follow-up with you.
From: Hongwei Sun
Sent: Monday, October 11, 2010 1:35 PM
To: Matthias Dieter Wallnöfer
Cc: cifs-protocol at samba.org; Bryan Burgin
Subject: RE: [REG:110091558099846] RE: Incompleteness in MS-SAMR section 188.8.131.52.1 objectClass
This seems a new issue even it is in the same section of the document. We will create a new case to keep track it. If there is a new issue in our communication in the future , please also copy docHelp, which is monitored by our team, so it will not be missed in case I am out of office or so.
As of this issue, could you give a little more description about the blackbox test which reproduces the behavior ?
From: Matthias Dieter Wallnöfer [mailto:mdw at samba.org]
Sent: Monday, October 11, 2010 11:29 AM
To: Hongwei Sun
Cc: cifs-protocol at samba.org; MSSolve Case Email
Subject: Re: [REG:110091558099846] RE: Incompleteness in MS-SAMR section 184.108.40.206.1 objectClass
I think I've found another issue: always MS-SAMR 220.127.116.11.1 "objectClass"
trigger - this time item 1.5.
Windows doesn't seem to add always UF_PASSWD_NOT_REQD when objects using UF_WORKSTATION_TRUST_ACCOUNT are created. We've a blackbox test which reproduces this. Probably there is some explaination missing; that means under which cases PASSWD_NOT_REQD is added.
More information about the cifs-protocol