Topic: SME Recent horde Update causes all network computers to..

[hackersoft]

This was a big headache for me after updating with the latest
SME Recent horde Update which causes all my network computers to disengage from the domain.

The effect, I have to redo all permissions settings for 400 users in our Windows 2003 R2 that's acting as our File Server. Not only that, users can no longer logon to any computers by using their user names.

Is there anything in the update that might have caused it to happen? It now gives me a nerve to update my SME Box to the latest if that will happen again. Too much for an experience. I've wasted so much time reconnecting all computers to the updated SME Domain Controller.

I hope that won't happen again the next time I update my SME Box...

     

[CharlieBrady]

This was a big headache for me after updating with the latest

Please use the Bug Tracker link above.

[hackersoft]

Ok, submitted to bug tracker....
Just a friendly advice to SME users... I've learned my lessons now, don't ever update your Production SME acting as a Primary Domain Controller if you received an important update notification or the same will happen to your network. You should have a dummy system and perform the updates from there... If nothing bad happen, continue with the update.

Bug Tracker Number: 2141

[CharlieBrady]

This was a big headache for me after updating with the latest
SME Recent horde Update which causes all my network computers to disengage from the domain.

The only "horde" updates I'm aware of are in the smeserver-testing repository. They shouldn't be used in production servers until they have been verified and released.

Instead of warning people against horde updates you should be warning people about using unverified updates on production servers.

[mdo]

I suspect hackersoft means this recent update for horde (?):

e-smith-horde.noarch 1.12.0-05 smeupdates

The changelog shows:
* Wed Dec 06 2006 John H. Bennett III <bennettj@johnbennettservices.com> 1.12.0-05

- Restrict access to horde scripts directory [SME: 2136]

I cannot see how that could affect Samba's PDC functionality at all?
Michael

[CharlieBrady]

I cannot see how that could affect Samba's PDC functionality at all?

See followup in the bug tracker. I suspect "signal-event post-upgrade ; signal-event reboot" has broken something. Note also that a significant number of contribs were installed.

[kruhm]

Possibly your servers are arguing over which is the PDC. Check to see if the DNS service is running on your 2003. Also note which is providing the DHCP.

[hackersoft]

@kruhm
Probably not the case... Win2k3 is joined to the SME PDC and is only acting as a file server.

It's not only the File Server that has the problem authenticating from SME, all client computers connected to the domain can no longer authenticate. I suspect, after I post-upgrade and rebooted, the system certificate was regenerated and that might have caused the problem.

All clients IPs are manually configured and I don't implement DHCP.