Microsoft KB Archive/870964

= File shares on iSCSI devices may not be re-created when you restart the computer =

Article ID: 870964

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Small Business Server 2003 Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows XP Home Edition
 * Microsoft Windows XP Professional
 * Microsoft Windows XP Professional x64 Edition
 * Microsoft Windows XP Media Center Edition 2002
 * Microsoft Windows XP Tablet PC Edition
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows XP and Windows Vista



SYMPTOMS
You use the Microsoft iSCSI Initiator service to connect to an Internet SCSI (iSCSI) disk device. The file shares that you create for folders that are located on your iSCSI device may not be re-created when you restart the computer that the shares are created on.



CAUSE
This issue may occur when the iSCSI Initiator service is not initialized when the Server service initializes. The Server service creates file shares. However, because iSCSI disk devices are not available, the Server service cannot create file shares for iSCSI devices until the iSCSI service is initialized.



iSCSI Initiator 2.x
To resolve this issue in iSCSI Initiator 2.x, follow these steps on the affected server:  Make the Server service dependent on the iSCSI Initiator service. For information about how to do this, see the &quot;Make the Server service dependent on the iSCSI Initiator service&quot; section. Configure persistent logons to the target. To do this, use one of the following methods.

Note If you see the target on the Persistent Target tab, the following steps are not required.

Method 1: Use the iSCSI Initiator in Control Panel  In Control Panel, double-click iSCSI Initiator. Click the Targets tab. Click a target in the Select a target list, and then click Log On. Click to select the Automatically restore this connection when the system boots check box, and then click OK.</li></ol>

Method 2: Use the Command Prompt window <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type cmd, and then click OK.</li> At the command prompt, type the following command, and then press ENTER:

iscsicli persistentlogintarget  T * * * * * * * * * * * * * * * 0

Note is the IQN name of the target.</li></ol> </li> Configure the BindPersistentVolumes option for the iSCSI Initiator service. To do this, use one of the following methods.

Method 1: Use the iSCSI Initiator in Control Panel <ol style="list-style-type: lower-alpha;"> In Control Panel, double-click iSCSI Initiator.</li> Click the Bound Volumes/Devices tab.</li> Click Bind All to bind all the persistent targets. Or, click Add, and then enter a drive letter or mount point to bind a specific target.</li> Click OK.</li></ol>

Method 2: Use the Command Prompt window <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type cmd, and then press ENTER.</li> Type iscsicli BindPersistentVolumes, and then press ENTER.

Note This is the same as selecting the Bind All option in Method 1.</li></ol> </li></ol>

Note Use this resolution only if you experience this specific issue with version 2.x of the iSCSI Initiator service.

iSCSI Initiator 1.06
<ol> Make the Server service dependent on the iSCSI Initiator service. For information about how to do this, see the &quot;Make the Server service dependent on the iSCSI Initiator service&quot; section.</li> Configure persistent logons to the target. To do this, use one of the following methods.

Note If you see the target on the Persistent Target tab, the following steps are not required.

Method 1 <ol style="list-style-type: lower-alpha;"> In Control Panel, double-click iSCSI Initiator.</li> Click the Available Targets tab.</li> Click a target in the Select a target list, and then click Log On.</li> Click to select the Automatically restore this connection when the system boots check box, and then click OK.</li></ol>

Method 2 <ol style="list-style-type: lower-alpha;"> Click Start, click Run, type cmd, and then click OK.</li> <li>At the command prompt, type the following command, and then press ENTER:

iscsicli persistentlogintarget  T * * * * * * * * * * * * * * * 0

Note is the IQN name of the target.</li></ol> </li> <li>Configure the BindPersistentVolumes option for the iSCSI Initiator service. To do this, use one of the following methods.

Method 1: Use the iSCSI Initiator in Control Panel <ol style="list-style-type: lower-alpha;"> <li>In Control Panel, double-click iSCSI Initiator.</li> <li>On the Initiator Settings tab, click Bind Volumes, and then click OK.</li> <li>Exit iSCSI Initiator.</li></ol>

Method 2: Use the Command Prompt window <ol style="list-style-type: lower-alpha;"> <li>Click Start, click Run, type cmd, and then press ENTER.</li> <li>Type iscsicli BindPersistentVolumes, and then press ENTER.</li></ol> </li></ol>

Make the Server service dependent on the iSCSI Initiator service
Use one of the following methods to make the Server service dependent on the iSCSI Initiator service.

Method 1: Use the Microsoft Service Control utility (Sc.exe)
Note You do not have to modify the registry when you use this method. Therefore, this method is the preferred way to set the service dependency. <ol> <li>Click Start, click Run, type cmd, and then press ENTER.</li> <li>Type sc config LanManServer depend= MSiSCSI, and then press ENTER.

If you have administrative access to the server, you can perform this command from a network computer. To do this, type the following command, and then press ENTER:

sc \\ config LanManServer depend= MSiSCSI

</li></ol>

Method 2: Use Registry Editor
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Windows XP and Windows Server 2003 <ol> <li>Start Registry Editor.</li> <li>Locate and then click the following subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer

</li> <li>On the Edit menu, point to New, and then click Multi-String Value.</li> <li>Type DependOnService to name the new registry entry, and then press ENTER.</li> <li>Double-click DependOnService, type MSiSCSI in the Value data box, and then click OK.</li> <li>Exit Registry Editor.</li></ol>

Microsoft Windows 2000 <ol> <li>Start Registry Editor.</li> <li>Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManServer

</li> <li>On the Edit menu, click Add Value.</li> <li>Type DependOnService in the Value Name box, click REG_MULTI_SZ in the Data Type box, and then press ENTER.</li> <li>In the Multi-String Editor window, type MSiSCSI in the data box, and then click OK.</li> <li>Exit Registry Editor.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
You can script the procedures that are described in the &quot;Resolution&quot; section by using the Sc.exe and Iscsicli.exe utilities. To do this, create a batch file that uses these commands, and then either run the batch file directly, or run the batch file in another way. For example, run the batch file by using Group Policy.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

To script the whole operation that is described in the &quot;Resolution&quot; section, create a batch file that contains the following text: sc config LanManServer depend= MSiSCSI iscsicli BindPersistentVolumes For more information about iSCSI technology and Microsoft support of iSCSI, visit the following Microsoft Web site:

http://www.microsoft.com/windowsserversystem/storage/technologies/iscsi/default.mspx

Additional query words: SAN iSCSI

Keywords: kbtshoot kbprb KB870964

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.