When unfolded, this panel provides the option to either enable or disable standard file sharing on this server. When enabled, a dialog will appear providing the option to make the shared folders available only to the private network on which the system resides, or to make sharing available to public networks. The choice here depends on the requirements of the organization but for security purposes it is typically best to limit sharing to the private network unless external access is required.
The Network and Sharing Center also allows password access to shared folders to be configured. When the arrow next to Password protected sharing is selected the options to enable or disable password protection sharing are provided.
When enabled on workgroup servers, only users with user accounts and passwords on the server will be able to access shared files and folders. Shared folders can be configured using Windows Explorer, simply by navigating to the folder to be shared, right clicking on the folder and selecting Properties from the menu. In the properties dialog, click on the Sharing tab to display and modify the current shared folder settings as illustrated in the following figure:. Within the sharing property panel, click on the Share Within this dialog, the users who may access this shared folder are specified.
If file sharing has been restricted to users with local accounts and passwords, a list of users can be obtained by clicking on the down arrow. In this situation, select and add users, or select Everyone if access is to be made available to all users with local accounts:. Once these settings are complete, click on the Share button to initiate the file sharing process.
Once this initial phase of the share setup is complete a dialog will appear announcing this fact, listing the full Universal Naming Convention UNC path to the shared folder and providing the option to email users to notify them of this fact:. Having specified which users will have access to the folder the next step is to enable the sharing of the folder, specify share permissions and configure a Share Name by which the folder will be referenced and accessed.
In addition caching of shared files can be configured. Caching allows users to maintain local copies of shared files so that they can be accessed off-line for example when the server hosting the files is not available to the user's local system. With caching configured, local copies of shared files are stored on the user's local system so that they can be accessed without a connection to the server. When a connection is re-established, any changes made to the local copy of the file are synchronized with the original copy on the server.
In this dialog, set the Share this folder option to enable the sharing of the folder. Once this has been selected the Share name field and associated button will activate enabling a share name to be entered. By default the name of the folder being shared will be displayed, although this may be changed to another name if desired.
If the number of concurrent users accessing a shared folder is of concern, modify the number of simultaneous users accordingly. Learn more. Asked 12 years, 6 months ago. Active 10 years, 11 months ago. Viewed 75k times. How do I find all the folders that are shared on Windows Server ? Improve this question. Raj More. Raj More Raj More 1 1 gold badge 3 3 silver badges 11 11 bronze badges. You should give your question a more meaningful title.
Add a comment. However, I'm not seeing which server needs the registry mod. IS It the source server? Or the target server? Or both? You don't need a registry mod if you use Robocopy. It's about changing the behaviour when you copy files using Windows Explorer, which is about the least efficient way to move files.
Remember the default copy type for files in Robocopy is DAT data,attributes,timestamps , while directory copies are only DA data,attributes.
This is really the best way of migrating data to a new server, assuming your backup solution isn't any faster - it should be tested - and assuming you've got time to pre-seed the data prior to the actual move date.
That's going to copy with the DAT options and perms, in Backup mode "restartable mode" is inefficient over a reliable link, and in fact is just inefficient full stop, unless you're copying a few very large files - it's better to simply retry a few times. After that, run the copy at least a couple times leading up to the changeover to ensure you won't need to copy too many new files during your change window.
Obviously each iteration will take less time assuming you do it at regular intervals and your users don't do massive changes , and it'll give you a feel for the general time it'll take to catch up the data changes for X interval. During the actual change window, deny access to your end users to stop them making changes. This avoids issues with file locks as well you can use the file system tools to close any open files.
Do the final data copies per the above, rerunning the command if there are any errors fix the actual problem first! Particularly across a network.
You can also mix-and-match - do the bulk seeding via a restore from backup. Do some catch-up copies - at least a few days prior to the change, so you get an idea of the "worst", then a couple more progressively closer to the date. I highly recommend that whether you're doing a restore from backup first or just pure Robocopy, you test the results with a sample of your data - a bunch of directories with different perms or properties, preferably, but not big ones.
Test each step that you are going to carry out with your sample, including deletions and adds, permission changes etc, the various Robocopy commands for each "catch-up" and ensure that the final result is what you expect.
If you mix up your source first! Also, for copying from an older OS to a newer one, always run from the new server and "pull" the data from the old to the new - newer versions of Robocopy get incrementally better. It's much quicker.
And why would you copy onto a R2 server in ? Home Windows Windows Server How-tos. Move shares and permissions to a new disk in Windows Server. Windows Server. Casey Crowe. Move a shared folder and keep the share Ask Question. Asked 10 years, 11 months ago. Active 9 years, 2 months ago. Viewed 6k times. Improve this question.
Add a comment. Active Oldest Votes. Thank You. Improve this answer. Rhak Kahr Rhak Kahr 4 4 bronze badges.
0コメント