On Mon, Nov 10, 2008 at 08:28:11AM +0100, Roger Oberholtzer wrote:
On Fri, 2008-11-07 at 12:26 +0100, Lars Müller wrote:
Add wins at the end of this line. IIRC we recently had a discussion to support this from inside YaST too.
It would make sense. After all the work to set up letting a machine join the AD, it seems odd to leave this undone.
Microsoft Windows Active Directory heavily relies on DNS. WINS is still available but the default name resoloution mechanism is DNS since ages even for Microsoft. Using a split DNS <-> WINS name scope might result in strange(tm) issues.
Granted they are really different things. But still, it would make sense that if YaST is doing part of the work, it should do the rest.
100% coverage isn't possible. You know the very simple 80:20 rule? You need 80% of your time to implement the remaining 20% of 100% coverage.
Or, as a minimum, in the info panel to the left, tell which obvious things are not being done. That is always the trick with using auto setups like YaST (but not at all exclusive to YaST):
This is valid critic! Such hints would be nice. Maybe with the opportunity to search the Support DataBase (SDB) straight from inside YaST.
knowing how much they did and how much they did not do. All the time saved in letting them set up something that is tricky is often then lost trying to figure out which things they did not do.
Please keep your special setup in mind. A split DNS and WINS data base isn't what the majority of MS AD setups use. Unfortunately in this case you're part of the 20%. ;) I might be completely wrong with my numbers. But that's my experience with customer setups till now. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany