A Windows 2003 host connects to the S2600 in iSCSI mode. A file system is created on the storage disks mounted to the operating system, and a share folder is created on the file system. However, after the operating system restarts, the share property of the folder is lost.
The solution released on the Microsoft Web site is to set the startup of the server service to be dependent on the MS iSCSI service. However, this solution fails to completely rectify the fault. After that, the script batch processing method is adopted during the system startup. The script design is as follows:
1. External disks are identified by iSCSI services; therefore, the script must check the status of iSCSI services and be modified only after the startup of iSCSI services.
2. Under normal circumstances, lanmanserver
is already enabled before iSCSI services are started up; therefore, confirm that the status of lanmanserver
is identified after the startup of iSCSI services.
3. If the status of lanmanserver
is enabled and normal, restart it and add external disks to the share folder. If lanmanserver
fails to be enabled, enable it again.
The detailed procedure is as follows:
Step 1 Download the attachment and decompress it to the system directory.
Step 2 Run gpedit.msc
to enable the group policy:
Choose Local Computer Policy > Computer Configuration > Windows Settings > Script (Startup/Shutdown).
Add the prepared script.
Step 3 Restart the operating system.
Step 4 Check whether the share service is recovered.
The share property of file folders on the Windows 2003 is managed by the server service. During the startup process of the operating system, the server service (in name of lanmanserver in the registry) is enabled before the iSCSI service. Therefore, after the iSCSI service is enabled, it detects that the share folder of storage disks fails to be managed by lanmanserver, causing the loss of the share property.
After the script is added as a boot item, during the startup process of the operating system, the script is being processed for a long time. It is a normal phenomenon, because the script is detecting whether iSCSI services are normal. The script is processed only after the iSCSI services are normal. It takes about three minutes for the script to disable and enable lanmaserver again.