So this post is definitely going to fall into the "rants" category of my blogging.  

I can't tell you the number of times that I've attempted to setup Microsoft's IIS FTP services.  IIS6, IIS7, IIS7.5.  Now, don't get me wrong, if you want a simple FTP site so you can maybe publish web content or simply have one user account, it's a quick solution without adding any software to your box.  But the second you even start to think about user directory isolation - RUN.

Today and for the last time I attempted to enable FTP User Isolation - specifically the "Isolate users.  Restrict users to the following directory:" and selecting the "User name physical directory (enable global virtual directories)".  Per usual, I follow the published Microsoft instructions to the letter.  I try to log in and get: 530 Home Directory Inaccessible.

I hunt the web for almost 2 hours searching for reasons or ideas: 530 Home Directory Inaccessible

I reinstall the FTP services: 530 Home Directory Inaccessible

IISRESET, Services restarts, server reboots: 530 Home Directory Inaccessible

Permissions fiddling until my eyes are bulging: 530 Home Directory Inaccessible

Almost start smoking again: 530 Home Directory Inaccessible

FINALLY, I found the proper solution to the IIS7 530 Home Directory Inaccessible error.
It was so obvious and right in front of me.....

GO DOWNLOAD FILEZILLA FTP SERVER.
It took literally 6mins to find, download, install, configure, add user, open firewall on alt port, test, and confirm working.

IIS FTP, until Microsoft can publish instructions on how to properly enable your FTP User Isolation, I am never touching you again - AD integration or not, you are a gianormous PITA without explanation.

Moral of the story:  Friends don't let friends IIS FTP