The timestamp gets modified to the current system date, while the files are copied from local drive to mounted NFS drive. File timestamp could be important for auditing purpose, running backup tools or for other reasons. The effected Windows O/S are: Windows 2003, SFU 3.5 , Client for NFS ...

Recently, we have a case where the customer was unable to copy the Password Sync encryption key from SFU 3.5 to Windows 2008 R2. The customer was getting the following error while copying the encryption key from Windows 2003, SFU 3.5 to Windows 2008 R2. However, the same key was getting copied to Windows...

As discussed on my earlier Blog post: http://blogs.technet.com/b/sfu/archive/2011/05/25/scripts-to-populate-the-unix-attributes-when-migrating-from-sfu-3-5-to-rfc-2307-schema.aspx , So after running both the script as dicussed on the above blog, you would be able to populate the User's unix attribute...

We do get lot of issues where customer has migrated\upgraded from SFU 3.5 to Windows 2003 R2\2008\2008 R2 and is having issues with the Unix attributes of the users. In case you want to uninstall SFU 3.5 from your domain controllers and install the inbuilt components (i.e, Server for NIS, Password Sync...

Please find the list of Hotfix for SFU 3.5. For Server for NFS: http://support.microsoft.com/kb/939767 for Nfssvc.exe/Nfssvr.sys ( 8.0.2254.19) http://support.microsoft.com/kb/933397 for Nfssvr.sys ( 8.0.2254.20) ( You would first need to install the above patch to update the nfssvc...

Services for UNIX 3.5 is on maintenance mode now and there will be no other update to this (read expect few scenarios). Additionally Gateway for NFS has been removed in Windows 2003 R2 and onwards. I know still a considerable amount of systems uses Gateway for NFS from Services for UNIX 3.5. The best...