Hi @MiracErde et al
I was looking at the ADMX install/update procedure and all instructions seem to be clear, except that related to deleting the admx files from the current location.
I never tried to do it like that on a Windows Server nor on another SAMBA implementation, so not entirely sure what is going to happen when all admx are gone from the domain (even for a very brief period of time). What I always did was to overwrite files in place and make them sync with the rest of the domain (settings).
Could you clarify if skipping Step 3 is possible, and if samba-tool gpo admxload
from Step 5 could experience issues?
Cheers
I did this in a different way. Just extract the admx files and copy the ADMX/ADML files manually (e.g. WinSCP) to the folder on your UCS-DC.
Hi Frank,
I guess, as the saying goes, there’s more than one way to skin a cat.
Your suggestion worked too.
For posterity:
- ADMX and language files must be placed in
/var/lib/samba/sysvol/<domain>/Policies/PolicyDefinitions/
- they need to be owned by
Administrator:Administrators
with 770
permissions
- All currently set GPOs reside in
/var/lib/samba/sysvol/<domain>/Policies/
and thus are not linked to the templates in PolicyDefinitions. Templates can be removed/replaced, when needed, without affecting the current state of the domain.
- It is near impossible to extract all GPO templates on UCS command line. Templates for various software come packaged in .msi, .cab, .zip and .exe with no common structure inside.
Although the UCS guide worked for some files, I would suggest to extract files on a Windows workstation and then delivering them to UCS.
1 Like
Ack, extracting the packages w/ 7z is working in most cases. I had only 1 EXE-file I needed to run to extract the content to a defined local folder. SFP from this local folder works for me.
Permissions need to be set according to the existing files to avoid trouble …