http://blogs.msdn.com/b/sfu/archive/2009/07/13/using-unix-attributes-tab-without-installing-idmu.aspxUsing UNIX Attributes tab without installing IdMU Starting with the Windows Server 2003 R2 release, Microsoft has made it clear that the AD Lookup feature would be the preferred direction to go for identity mapping between Windows and *nix when iten-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/sfu/archive/2009/07/13/using-unix-attributes-tab-without-installing-idmu.aspx#10336660Fri, 03 Aug 2012 17:21:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:10336660ashisa<p>The dir command shows the location of the niscnfg.exe file. Once you have found where it resides, you have to run it once.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10336660" width="1" height="1">http://blogs.msdn.com/b/sfu/archive/2009/07/13/using-unix-attributes-tab-without-installing-idmu.aspx#10335323Tue, 31 Jul 2012 20:52:51 GMT91d46819-8472-40ad-a661-2c78acb4018c:10335323Jay<p>I ran the command as specified on my Windows 2008 SP2 Enterprise x86 server to manage Unix Attributes tab - DIR NISCNFG.EXE /S/A</p> <p>The objects still require a NIS domain to modify those attributes. &nbsp; We are not leveraging NIS and will go through our standard LDAP calls. &nbsp; How I modify these attributes without specifying a NIS domain? </p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10335323" width="1" height="1">