Bug 13724 - operatingSystemVersion not updated when updating samba.
Summary: operatingSystemVersion not updated when updating samba.
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.8.8
Hardware: All Linux
: P5 trivial (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-19 09:53 UTC by Louis
Modified: 2019-03-27 07:06 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Louis 2018-12-19 09:53:55 UTC 
Hai, 

I noticed a really realy small bug.. 

I noticed in my AD that on the AD-DC object in AD the field:  operatingSystemVersion

is not updated when samba is updated. 
Here it still shows ..   :  4.1.17-SerNet-Debian-10.wheezy

and while i started my production setup with 4.1.17.. im now running 4.8.8 on stretch..
Comment 1 Amit Kumar 2019-03-27 06:16:40 UTC 
Hey Louis,

For me,

When joined using 
# net ads join -U administrator
ADSI Edit -> CN=Computers -> CN=<Linux-Machine-Name> -> Properties -> operatingSystemVersion[Not set]

# net ads join -U root osVer=4.8.6 osName=samba
ADSI Edit -> CN=Computers -> CN=<Linux-Machine-Name> -> Properties -> 
operatingSystemServicePack = Samba 4.8.6
operatingSystemVersion = 4.8.6
operatingSystem = samba

Am I able to understand issue correctly?
Comment 2 Andrew Bartlett 2019-03-27 07:06:39 UTC 
Yes, it is known we don't update that, except at join/provision time.

Winbindd should probably call netr_LogonGetDomainInfo().