<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Patrick Morris wrote: <blockquote cite="mid20070105231225.GI17454@pmorris.usa.hp.com" type="cite"> <pre wrap="">On Fri, 05 Jan 2007, Glenn wrote: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">So if I have some object classes and attributes required for AD that are not allowed in DS, and vice-versa, how can I make Windows Sync work? I'm sure I'm missing something here. I'm including sample ldif entries from each import below. Thanks. -Glenn. </pre> </blockquote> </blockquote> <pre wrap=""> It seems to me (but I'm no expert on Windows sync) that the easiest solution would be to update your DS schema with the required AD attributes and classes so that it will accept the ones from AD. </pre> </blockquote> No this isn't necessary. Winsync takes care of the schema translation. All you need is to have entries that are 'syncable'. On the FDS side this means special objectclass and attribute values. On the AD side it only means having the entries in the container configured in the sync agreement. </body> </html>