Skip to main content

IIS FTP Hide folders and Files

Create the FTP Folder



  1. Create a folder that you want the FTP service to point to.

  2. Right-click the folder, click Properties, and then click the Security tab. Grant Full Control permissions to only the Administrators group.NOTE: Remove the Everyone group if it is present.

  3. Click Advanced, and then click Add to add a new rule.

  4. In the account selection list, double-click the Anonymous User account or the group that is used for FTP access.

  5. In the Apply Onto drop-down list, select Files Only.

  6. Click to select Allow for the following permissions:

    • List Folder/Read Data

    • Read Attributes

    • Read Extended Attributes

    • Read Permissions



  7. Click OK.

  8. Click Add to add another rule.

  9. Select the account that you selected in step 4.

  10. In the Apply Onto list, click to select This Folder only.

  11. Click to select Allow for the following permissions (note that List permissions are not listed):

    • Create Files/Write Data

    • Create Folders/Append Data

    • Write Attributes

    • Write Extended Attributes

    • Read Permissions



  12. Click OK until you have closed all of the property windows.




It doesn't seem to be working...?

If you are using virtual directories make sure you remove the tick box for virtual directories in "FTP Directory Browsing".  This will now remove the directory from view however, with a complete path you have access to the file without revealing other items in folder.  i.e ftp.domain.com\TechSales\file.txt

Virtual directories that i want displayed are no longer available?

The use of place holders will help.  Virtual directories have higher priority over physcial paths, as we have told iis not to display VD's a place holder will assist you with redirecting the user neatly.

To display an alias called CustomerDownloads (VD path F:\virtualDirectory\CustomerDownloads) previous displayed in the public folder; create an empty folder as a place holder visible to the anonymous user:  ftproot\LocalUser\Public\CustomerDownload

Comments

Popular posts from this blog

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil

SCCM Client Certificate (PKI) Value is None

SCCM Client Certificate (PKI) Value is None Stopping WMI service Stopping CCMExec SC Delete any sccm services (ccmexec, smstsmgr, cmecservice, ccmsetup) Delete C:\windows\ccm, C:\windows\ccmsetup, C:\windows\ccmcache, C:\Windows\SMSCFG.ini Go into regedit and remove: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS Then restart WMI, and reinstall the client. You shouldn't need a reboot to complete this. Once this has been done the client will install and pick up the cert. https://www.windows-noob.com/forums/topic/12644-sccm-2012-client-certificate-pki-value-is-none/

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys