This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / Outgoing mail domain missing ... how to configure it?
« on: June 04, 2015, 05:10:11 pm »
Hi,
I know this variable is missing since zentyal 4.0 . Is there anyone who can explain how to set it up a virtual mail domain with outgoing mail domain which works?
I have been reading a lot of supposed documentation but in anyone there seems to be some pieces missing ...
Thanks
Fed
I know this variable is missing since zentyal 4.0 . Is there anyone who can explain how to set it up a virtual mail domain with outgoing mail domain which works?
I have been reading a lot of supposed documentation but in anyone there seems to be some pieces missing ...
Thanks
Fed
2
Installation and Upgrades / OpenChange provicioning error
« on: June 03, 2015, 05:29:41 pm »
Dear all,
I'm facing this annoying error on provicioning Open Change.
I happened after having upgrade from 4.0 to 4.1 and have unistalled open change module before the upgrade and installed back after the upgrade.
Some modules reported error when saving changes . More information on the logs in /var/log/zentyal/
Error provisioning: root command openchange_provision --firstorg='EUCAP Sahel Mali' --standalone failed. Error output: params.c:pm_process() - Processing configuration file "/etc/samba/shares.conf" Traceback (most recent call last): File "/usr/sbin/openchange_provision", line 109, in openchange.provision(setup_path, provisionnames, lp, creds) File "/usr/lib/python2.7/dist-packages/openchange/provision.py", line 968, in provision install_schemas(setup_path, names, lp, creds, reporter) File "/usr/lib/python2.7/dist-packages/openchange/provision.py", line 453, in install_schemas provision_schema(sam_db, setup_path, names, reporter, schema['path'], schema['description'], schema['modify_mode']) File "/usr/lib/python2.7/dist-packages/openchange/provision.py", line 240, in provision_schema sam_db.add_ldif(el, ['relax:0']) File "/usr/lib/python2.7/dist-packages/samba/__init__.py", line 224, in add_ldif self.add(msg, controls) _ldb.LdbError: (68, 'Entry CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=xxxxx-domain,DC=lan already exists') Command output: NOTE: This operation can take several minutes
Any idea?
Fed
I'm facing this annoying error on provicioning Open Change.
I happened after having upgrade from 4.0 to 4.1 and have unistalled open change module before the upgrade and installed back after the upgrade.
Some modules reported error when saving changes . More information on the logs in /var/log/zentyal/
Error provisioning: root command openchange_provision --firstorg='EUCAP Sahel Mali' --standalone failed. Error output: params.c:pm_process() - Processing configuration file "/etc/samba/shares.conf" Traceback (most recent call last): File "/usr/sbin/openchange_provision", line 109, in openchange.provision(setup_path, provisionnames, lp, creds) File "/usr/lib/python2.7/dist-packages/openchange/provision.py", line 968, in provision install_schemas(setup_path, names, lp, creds, reporter) File "/usr/lib/python2.7/dist-packages/openchange/provision.py", line 453, in install_schemas provision_schema(sam_db, setup_path, names, reporter, schema['path'], schema['description'], schema['modify_mode']) File "/usr/lib/python2.7/dist-packages/openchange/provision.py", line 240, in provision_schema sam_db.add_ldif(el, ['relax:0']) File "/usr/lib/python2.7/dist-packages/samba/__init__.py", line 224, in add_ldif self.add(msg, controls) _ldb.LdbError: (68, 'Entry CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=xxxxx-domain,DC=lan already exists') Command output: NOTE: This operation can take several minutes
- Step 1: Register Exchange OIDs
- Step 2: Add Exchange attributes to Samba schema Error: "(68, 'Entry CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=eucap-domain,DC=lan already exists')" when adding element: # # ms-Exch-Access-Control-Map # Contains the mapping for the access controls. # dn: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=xxxxx-domain,DC=lan objectClass: top objectClass: attributeSchema cn: ms-Exch-Access-Control-Map distinguishedName: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=xxxxx-domain,DC=lan attributeID: 1.2.840.113556.1.4.7000.102.64 attributeSyntax: 2.5.5.12 isSingleValued: TRUE showInAdvancedViewOnly: TRUE adminDisplayName: ms-Exch-Access-Control-Map adminDescription: ms-Exch-Access-Control-Map oMSyntax: 64 searchFlags: 0 lDAPDisplayName: msExchAccessControlMap name: ms-Exch-Access-Control-Map #schemaIDGUID: 8ff54464-b093-11d2-aa06-00c04f8eedd8 isMemberOfPartialAttributeSet: FALSE objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration,DC=xxxxx-domain,DC=lan [!] error while provisioning the Exchange schema classes (68): Entry CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=xxxxx-domain,DC=lan already exists . Exit value: 1
Any idea?
Fed
3
Installation and Upgrades / Users have access to admin rights???
« on: December 05, 2014, 02:46:05 am »
Hello,
I have just tried to install RSAT on user desktop and by connecting to the domain I notice that the user has access to admin rights.
I mean the user can see all the properties of other user and he can also changes some settings.
Is there a method to avoid this?
Thanks
FedericoP
I have just tried to install RSAT on user desktop and by connecting to the domain I notice that the user has access to admin rights.
I mean the user can see all the properties of other user and he can also changes some settings.
Is there a method to avoid this?
Thanks
FedericoP
4
Installation and Upgrades / External NAS to be mounted and then shared via Zentyal File Sharing module
« on: November 14, 2014, 08:42:08 pm »
Hello,
I'm trying to mount on the zentyal server a nas folder to be than exported via the file sharing module to windows user.
My fstab line looks like this:
//10.0.0.3/samba /media/smb cifs username=guest,password=,acl,user_xattr,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0
When I run getfacl command in the mounted folder I received this output:
# getfacl .
# file: .
# owner: root
# group: root
user::rwx
group::rwx
other::rwx
But each time I save the folder in the sharing module I see this error in zentyal log:
Failed to set security descriptor: NT_STATUS_ACCESS_DENIED
By the way the users are able to mount the shared drive which is empty and cannot write on it
What am I doing wrong?
Federico
I'm trying to mount on the zentyal server a nas folder to be than exported via the file sharing module to windows user.
My fstab line looks like this:
//10.0.0.3/samba /media/smb cifs username=guest,password=,acl,user_xattr,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0
When I run getfacl command in the mounted folder I received this output:
# getfacl .
# file: .
# owner: root
# group: root
user::rwx
group::rwx
other::rwx
But each time I save the folder in the sharing module I see this error in zentyal log:
Failed to set security descriptor: NT_STATUS_ACCESS_DENIED
By the way the users are able to mount the shared drive which is empty and cannot write on it
What am I doing wrong?
Federico
5
Installation and Upgrades / Dist-upgrade of 3.2 premium trial (original problem was OpenChange provisioning)
« on: September 24, 2014, 08:09:45 pm »
hello everybody,
I have the same problem explained here: https://forum.zentyal.org/index.php?topic=21280.0
but since I'm running a 3.2 premium trial zentyal server I haven't find any way to do a dist-upgrade in order to resolve the problem.
I'm allowed to upgrade the whole system or not?
If yes, how does it work?
Btw, if I can resolve the native problem of openchange provisioning there is no need to do any upgrade.
thanks
Federico
I have the same problem explained here: https://forum.zentyal.org/index.php?topic=21280.0
but since I'm running a 3.2 premium trial zentyal server I haven't find any way to do a dist-upgrade in order to resolve the problem.
I'm allowed to upgrade the whole system or not?
If yes, how does it work?
Btw, if I can resolve the native problem of openchange provisioning there is no need to do any upgrade.
thanks
Federico
Pages: [1]