Bug 39074 – Yet another occurrence of the GPO GUID case issue

Bug 39074 - Yet another occurrence of the GPO GUID case issue


Summary:	Yet another occurrence of the GPO GUID case issue

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Takeover
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:	34776
Blocks:
	Show dependency tree / graph

Reported:	2015-08-04 12:37 CEST by Arvid Requate
Modified:	2019-01-03 07:17 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very 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.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Flags:	gohmann: Patch_Available+

Attachments
revised_fix_for_bug_34776.patch (1.24 KB, patch) 2015-08-04 12:37 CEST, Arvid Requate	Details \| Diff
View All 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 Arvid Requate

2015-08-04 12:37:07 CEST

Created attachment 7080 [details]
revised_fix_for_bug_34776.patch

The anoying GPO GUID case issue ("f" vs "F" for those that remember..) which we fixed in Bug #34776 raised its ugly head once again today in my AD Takeover environment.

In my case I had configured the domainname of UCS to be "FooBar.com", matching exactly the domain of the AD DC. And that's why the patch for the bug mentioned above does not fix this issue. In the sysvol the domain directory always seems to be lowercase ("foobar.com"), so we need to fix that as well.


+++ This bug was initially created as a clone of Bug #34776 +++

Comment 1 Stefan Gohmann

2019-01-03 07:17:19 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 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.