Managing private files through the home folder in a Windows system

In the Microsoft operating system, there are two places that can be used to store users ' private files by default. One is the very familiar "My Documents". Because My documents are saved in a user profile, if the roaming user Profile management policy is used, managing the user's private files through My Documents can affect the performance of the operating system. Because if a user uses a roaming user profile stored on the server side, the system will need to spend a certain amount of time on the server to download the contents of My Documents. It also takes a certain amount of time to save data to the server when the system logs off. So this one time on the operating system to boot, the speed of the shutdown has an impact.

In addition to my Documents, the Microsoft operating system can manage users ' private files through the home folder. In my daily work, I like to let Enterprise employees use the "home folder" instead of "My Documents" to manage their files. Because the home folder has a certain security protection. Typically, the home folder only has the user and the system administrator user (Administrator) access to the folder, which is very similar to the user folders in the Linux operating system's/home directory. and the home folder is not included in the user profile, so even a system administrator using a roaming user profile does not negatively affect the operating system.

First, the location where the home folder is stored

The home folder can be set either to the user's own computer or to a shared folder on a computer on the network (as shown in the following illustration). And regardless of whether the enterprise has a domain environment enabled, you can use the home folder to manage the user's private files. This is not the same as roaming user profiles. Roaming user profiles must be implemented in a domain environment, and there is no limit to the main folder's words. Both the domain user and the local user can make the home folder.

As shown in the figure above, there is now a domain user SA01. It can store its home folder on a single server in the network. This way, it can access the information in this home folder even if you are using a different computer. Simply put, this home folder feature is a simple file server. Only this file server is not able to implement file sharing among employees. Only users and system administrators can access these files.

Second, the main folder configuration points.

The following is an example of the above diagram, the specific configuration of the main folder and the key points in the configuration process.

First step: Create a shared folder on the server. First, the system administrator logs in as a domain administrator's user account. Otherwise, the follow-up work will not be completed successfully. The system administrator has to establish a shared folder on the server in advance. For ease of management, it is a good idea to create a subfolder below, with the user's name (such as SA01) command. After the build is complete, you must also modify the permissions for this shared folder. Let the domain system administrator have "change" share permissions on the shared folder. Note there is no need to set permissions for user SA01. In subsequent configurations, the system automatically assigns the user SA01 the necessary permissions. This ensures that the domain system administrator has the relevant modify permissions.

Step two: Turn on start, administrative Tools, Active Directory Users and Computers, and locate the organizational unit or container where the user SA01 resides, and double-click the user account. Select "Profile" in the open window again. In the Open tab, set the location of its primary file to the \ server IP address \ shared file name \ User folder through the Connect to feature. The operating system then automatically creates subfolders named after this user name, and the system administrator does not need to establish a folder beforehand. When a folder is established, the user is given permission to modify this folder as long as the folder is located within an NTFS disk partition. Although the system has no mandatory rules for naming this folder, it is best to be named after the user for ease of administration. When a folder is automatically created by the system, if the folder named by this user already exists, the system prompts you whether the home folder already exists and you want to overwrite the similar error message. When the system administrator can select the button, the system automatically sets the user to access the folder.

After the two steps above, the home folder is configured to complete. Later, the user SA01 saves the file and is saved in the home folder by default. And only users and system administrators can see access to the contents of this folder.