Bug 41094 - AD Connector: sync also macAddress
AD Connector: sync also macAddress
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-21 16:52 CEST by Michael Grandjean
Modified: 2019-03-25 20:57 CET (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2016-04-21 16:52:56 CEST
The current version of the AD-Connector is able to sync also computer objects, but the mapping only takes care of these attributes:

- cn
- samAccountName
- description
- operatingSystem
- operatingSystemVersion

We should (optionally) sync "macAddress", too. This would help in certain scenarios like running opsi in UCS-Member-Mode.
Comment 1 Stephan Hendl 2016-04-22 08:52:14 CEST
Additionally the password synchronization program should also sync computer-account passwords.
Comment 2 Stefan Gohmann univentionstaff 2016-12-13 08:10:43 CET
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:20:47 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.