Seamless integration into a Windows domain environment (Active Directory)

Registered by amichair on 2007-04-20

Any Windows environment larger than a basic home network (workgroup) works with a Window domain controller and Active Directory. A new Windows installation in such an environment connects to the domain out of the box, however K/Ubuntu requires much manual work even just to be able to authenticate a user via Active Directory, and it doesn't always work. There are a bunch of wikis and forums with howtos for this, each with their own configuration suggestions, required packages (winbind etc.), and manual tweaks (and many troubled users) as well as the sadms project which officially supports only up to Dapper and isn't even in the repositories. In all of these solutions, vague error messages need to be traced to try and guess what's wrong when it doesn't work. This makes it very difficult to introduce a K/Ubuntu workstation into such a standard windows environment at an average workplace, which in turn eliminates the possibility of making a case towards migrating Windows workstations to the K/Ubuntu alternative (see bug #1). This whole thing should be working out of the box, or with as minimal and easy (gui-based) configuration as possible - a demonstration with a live cd or dualboot installation on an existing Windows machine should integrate into the domain automatically and seamlessly so as to easily demonstrate the K/Ubuntu alternative and enable workers to switch to it with ease.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

This is currently possible to some extent using likewise-open, which is in the repositories. Personally I think using samba/winbind etc. is a better, more portable solution.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.