Show Posts

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.


Messages - dafatbloke

Pages: [1]
1
You are most welcome. Update the open ticket you have - it may help others / developers

2
Same issue here and it's been making my weekends non-existent. Until now ......

Don't install SFU it doesn't work, remove it.

My AD is on Server 2003 Standard ( 32bit )

Usual warnings about backing up etc, this could be considered as dangerous ( by M$ ) although its mostly painless - this is the process you do when you want to install a Server 2008 R2 Domain Controller into a 2003 Forest.

Resolved like this :
Logon as a schema admin ( enterprise admin )
Drive through your DNS Tree and remove ALL the entries ( apart from your A Record ) relating to your Zentyal Server, be careful not to delete any of the Windows Server entries or you will be in trouble  :'(

You need the Windows Server 2008 R2 Installation DVD
start a cmd prompt
cd \support\adprep
adprep32 /forestprep

Now thats about all you need to do as it upgrades the schema as required but you should do the following as well  :

adprep32 /domainprep /gppprep

I removed File Sharing Module, reinstalled it, configured it and enabled it whilst tailing the zentyal.log and it worked like a charm  :)

This is the M$ note about the last command :

http://support.microsoft.com/kb/324392
The functionality of the adprep domainprep /gpprep command depends on the state of the domain. If the updated adprep /domainprep command has not been run, this command is the functional equivalent of the adprep /domainprep command in the original release of Windows Server 2003. In these circumstances, the command performs all the domain operations that are listed in Microsoft Knowledge Base article 309628. These operations include setting the permissions for GPOs in the SYSVOL. If the updated adprep /domainprep command has already been run, the adprep /domainprep /gpprep command adds only the inheritable access control entries (ACEs) on GPOs in the Sysvol shared resource. The additional ACEs give enterprise domain controllers read access permissions on GPOs. These permissions are required to support Resultant Set of Policy (RSoP) functionality for site-based policy.

3
Installation and Upgrades / Additional Domain Controller Issues
« on: October 15, 2012, 01:46:48 am »
File Sharing module 3.0.4
Home directories & ACL shares don't work unless there is a share with guest access enabled
AD Administrator account gets imported as user root ( uuid 0 ) possibly wrong guid as well ( users ), files created have wrong uuid/guid and fail to delete
Existing AD users get wrong uuid and possibly guid ( users ) on initial import
Users created in Server 2008 AD User Manager get wrong uuid & possibly guid on created files, these fail to delete by same user
Users moved to a different OU than Users fail to delete from AD using Zentyal Users Tab, user gets deleted from zentyal users list
Users home directory value in AD fails to be created, workround of disable/save enable/save a share fixes entry

 

4
That has resolved that issue but there is a bigger issue at hand now. Will post as new.

5
Trying that now .... willl report back.
Thanks for listening.

6
I managed to add the zentyal server as an additional server to my server 2008 AD in file sharing and users / groups replicate ok although frustratingly it doesn't replicate from any other OU apart from the Users container which is a serious issue for me.
I have users defined under (for example) a 'MyUsers' OU and then OU's underneath for Departments so I can apply Group Policies, Security Groups are also defined in another OU for ease of adminstration.
I can't see how I'm going to migrate from the old AD Sync type method ( I would like to :) ) where all my users and groups are replicated from all containers and OU's from the top of the AD Tree.
Any suggestions ?

7
I have the same issue, DNS fails to start.
I noticed that the nsupdate is failing an SOA query so I did a dig and the status is REFUSED, maybe a permissions problem ( i don't know - thats a guess ) ?

I'm also guessing that the file shares issue I now have which fail in Win7 : access denied on home ( which has mapped ok ) and any shares I created is related.
 

8
Undo that, domain logons work ( user is authenicated ) but some rather nasty issues occur :
logon script fails to run
roaming profiles are not recognised ( cannot locate roaming profile, using temp message )
Policies fail to implement

Had to roll it back again.

9
Success, already had updated ebox-samba, saved smb.conf,ldap.conf & fstab ( just in case ). Stopped file sharing module.
Installed new version of samba,samba-common,samba-common-bin ( did I need that ??? ) and restarted samba.
Started module and 'a really nasty bug' showed that it failed to net setlocalsid because it couldn't find 'net'. Did a quick whereis and did a dirty
ln -s net.samba3 net in /usr/bin
restarted module again - success.
Test XP logon and file shares etc - success.
log.smbd shows version 3.4.3
Next job is Vista Home to Windows 7 Pro upgrade / join Domain on clients laptop, you know it's not going to upgrade ...........

10
Installation and Upgrades / Re: Setting up shared group profiles
« on: December 07, 2009, 02:51:57 pm »
You need a bit of this :
http://wiki.samba.org/index.php/Implementing_System_Policies_with_Samba

Its a bit of pain having to download 129mb of SP just to get it but nevermind .....
And don't forget the custom ADM :
http://www.pcc-services.com/custom_poledit.html

You will need Jedi like paitence with this tool as applying to XP then checking can sometimes be hit and miss ( I don't know why ), but with time it will allow you to setup policies as you requested.

11
I tried the same upgrade of samba and I also lost logins and samba usage, I was able to backtrack to original versions this morning.
I got repeated messages for this in /var/log/samba/smbd after the initial upgrade of samba,samba-common

[2009/12/07 09:38:19,  0] lib/smbldap.c:656(smb_ldap_start_tls)
  Failed to issue the StartTLS instruction: Protocol error

any ideas ?

12
Installation and Upgrades / Home Drive Maps Incorrectly
« on: November 25, 2009, 03:56:27 pm »
I have successfully installed eBox 1.3.x and have even managed to get Windows 7 to join the Domain correctly and map shares properly but I have a strange issue :
Users home drive appears in the list of mapped drives on logon within explorer ( H: ) but is inaccessible ( Red Cross ), when clicked on a message box eventually appears with :

H:\ is not accessible.
The filename, directory name, or volume label syntax is incorrect.

You can browse the Server via Network in explorer and the share appears on the list of available shares as expected and is browsable with a click.

From command line I am successfully able to map the share to another drive :
net use I: \\server\user.name

The killer information here is :
net use

H: \\server\homes\user.name NFS Network
I:  \\server\user.name Microsoft Windows Network

If you attempt :
net use H: /delete

Error message is :
The Network Connection does not exist.

smb.conf has not been manually altered :
[homes]
 comment = Home Directories
 valid users = %S
 read only = No
 browseable = No
 vfs objects = full_audit recycle
 recycle: versions = Yes
 recycle: repository = RecycleBin
 recycle: keeptree = Yes
 recycle: excludedir = /tmp|/var/tmp
 recycle: directory_mode = 0700

An ideas ? I guess the issue is that Windoze 7 thinks the share is of type NFS but i'm not sure how it gets to this point.

Regards

Martin Ward

 

Pages: [1]