Microsoft iSCSI Software Target 3.

3 Release Notes
Microsoft Corporation Published: March, 2011

Abstract
This document summarizes known issues for Microsoft iSCS Software Tar!et "#"#

Copyright information
This document is pro$ided %as&is'# nformation and $iews e(pressed in this document, includin! )*+ and other nternet ,eb site references, ma- chan!e without notice# .ou bear the risk of usin! it# This document does not pro$ide -ou with an- le!al ri!hts to an- intellectual propert- in anMicrosoft product# .ou ma- cop- and use this document for -our internal, reference purposes# / 2010&2011 Microsoft Corporation# 0ll ri!hts reser$ed# Microsoft, 0cti$e 1irector-, 2-per&3, ,indows, ,indows Ser$er, and ,indows 3ista are trademarks of the Microsoft !roup of companies# 0ll other trademarks are propert- of their respecti$e owners#

Contents
Microsoft iSCS Software Tar!et "#" *elease 4otes#######################################################################1 0bstract#################################################################################################################################### 1 Cop-ri!ht information###################################################################################################################### 2 Contents########################################################################################################################################## " Microsoft iSCS Software Tar!et "#" *elease 4otes#######################################################################5 )pdate 1 issue############################################################################################################################# 5 )pdate 2 issues########################################################################################################################### 5 6eneral issues############################################################################################################################# 7 )ninstallation issues################################################################################################################## 12

Important

Microsoft iSCSI Software Target 3.3 Release Notes

These release notes pro$ide late&breakin! information for Microsoft8 iSCS Software Tar!et "#"# .ou can find more information on the ,indows Stora!e Ser$er blo!# n these release notes: )pdate 1 issue )pdate 2 issues 6eneral issues )ninstallation issues

9or details about known issues with Microsoft iSCS Software Tar!et "#" compliance with industrstandards, see the Microsoft iSCS Software Tar!et "#" mplementation 4otes#

Update

iss!e

The Microsoft iSCSI Software Target "indows #owerShell cmdlet for setting a C$A# or re%erse&C$A# password does not set the %al!e correctly. The Set&IscsiSer%erTarget ,indows PowerShell cmdlet does not correctl- set the $alue for the C20P and re$erse C20P password, re!ardless of the password specified b- the user# There is no indication to the user that the specified password was not set properl-, other than that C20P& enabled connections are not accepted# 0s a workaround, set the password b- usin! the iSCS Software Tar!et MMC snap&in or b- usin! ,M to set the $alue# This !pdate contains the complete Microsoft iSCSI Software Target "indows Installer pac'age and is not a patch. This !pdate sho!ld be installed by ()Ms in "indows Storage Ser%er *++, R* factory images or distrib!ted to- or installed byend !sers that already ha%e the Microsoft iSCSI Software Target 3.3 installed.

Update * iss!es
Increases the ma.im!m n!mber of conc!rrent sessions for a single iSCSI target to /+ sessions. The Microsoft iSCSI Software Target "indows #owerShell cannot display error strings in the following lang!ages0 Simplified Chinese- Traditional Chinese- and 1ra2ilian #ort!g!ese. 9or these lan!ua!es, the resource files are not placed in the correct folders durin! installation, causin! the localized strin!s to not be loaded# There is no workaround for this issue#

Important The $#C pro%ider cannot load any reso!rce strings- which pre%ents the !ser from getting meaningf!l error messages from Microsoft iSCSI Software Target when !sing the $#C Cl!ster Manager. The resource files are referenced incorrectl- b- Microsoft iSCS Software Tar!et, resultin! in anerror messa!e reported b- the Microsoft iSCS Software Tar!et not displa-in! to the user# This issue occurs for all lan!ua!es, includin! :n!lish# There is no workaround for this issue# This !pdate contains the complete Microsoft iSCSI Software Target "indows Installer pac'age and is not a patch. This !pdate sho!ld be installed by ()Ms in "indows Storage Ser%er *++, R* factory images or distrib!ted to- or installed byend !sers that already ha%e the Microsoft iSCSI Software Target 3.3 installed.

3eneral iss!es
These notes appl- to end users of Microsoft iSCS Software Tar!et "#"# 4o! cannot set the minim!m storage si2e %al!e on the Snapshot Storage tab of the iSCSI MMC snap&in to a %al!e less than 3*+ M1. )sers cannot set the minimum stora!e size to "20 M; or less, e$en thou!h the user interface indicates that "00 M; is an acceptable $alue# To work around this issue, set the minimum stora!e size to a $alue !reater than "20 M;# $yper&5 host bac'!p is not s!pported. .ou ma- encounter an error if -ou run 2-per&3 host backup, as this is not supported with the current released $ersion of the 3SS hardware pro$ider# 9or application consistent backup, take a snapshot within the 3M !uest# The ma.im!m s!pported si2e of a parent 5$6 is appro.imately .77 T1. The ma(imum supported size of a parent $irtual hard disk <321= when used with a differencin! 321 is calculated at 2 T; minus 71> M; <rou!hl- 1#?? T;=# This is because of the metadata stora!e re@uirements# A firewall message error appears when yo! install the client on a comp!ter r!nning "indows Ser%er *++3 with S#*. The 31S and 3SS pro$iders show the followin! warnin! when -ou install the Microsoft iSCS Software Tar!et client on ,indows Ser$er8 200" SP2: Creating firewall r!les failed with error code0&* /8** please follow $elp file to config!re firewall r!les. 9/. Set!p will contin!e and

The Microsoft iSCS Software Tar!et client will install successfull-, but it will not work correctluntil -ou ha$e confi!ured -our firewall rules# To resol$e this issue, see the documentation for -our operatin! s-stem for information about confi!urin! the firewall#

iSCSI Software Target reso!rce is dependent on the physical dis' reso!rce type in a cl!ster config!ration. n a clusterin! confi!uration, where the iSCS Software Tar!et is runnin! as a clustered resource on Microsoft failo$er clusters, the iSCS Software Tar!et resource has dependencon Ph-sical 1isk, P 0ddress, P$A 0ddress, and 4etwork 4ame resources# Bther resource t-pes will continue to be supported b- the iSCS Software Tar!et ser$ice# The new cl!ster name does not appear after yo! rename a failo%er cl!ster. f -ou rename a failo$er cluster after installin! Microsoft iSCS Software Tar!et, -ou must stop and restart the Microsoft iSCS Software Tar!et ser$ice before the new cluster name will be displa-ed b- the Microsoft iSCS Software Tar!et console# Une.pected res!lts occ!r if yo! try to rename reso!rces o!tside of the Microsoft iSCSI Software Target console. f -ou rename an iSCS resource with another tool after it is created, une(pected results maoccur# 1ifferent namin! rules ma- appl- that can lead to issues for Microsoft iSCS Software Tar!et# 9or e(ample, the 9ailo$er Cluster Mana!ement tool permits a resource name to contain a space, whereas Microsoft iSCS Software Tar!et does not# To resol$e this issue, if an iSCS resource has been renamed, delete the resource, stop the Microsoft iSCS Software Tar!et ser$ice, and then restart the ser$ice and recreate the resource# After enabling I#sec- comm!nication fail!res can occ!r d!ring failo%er. f -ou enable Psec on connections from iSCS initiators to a failo$er cluster runnin! Microsoft iSCS Software Tar!et, -ou should increase the Microsoft iSCS initiator timeout $alue# ncreasin! the timeout $alue will pre$ent communication failures when a failo$er node !oes offline and the operation in pro!ress is transferred to another node of the failo$er cluster# To work around this issue, increase the followin! re!istr- $alue to ?0: $:;M<S4ST)M<C!rrentControlSet<Control<Class<=/639)781&)3*>& +,++*1) +3 ,@<<Instance Number><#arameters The $alues that can be modified are: Ma.ReA!est$oldTime: ncrease this $alue to ?0 if MP B is not installed# ;in'6ownTime: ncrease this $alue to ?0 if MP B is installed# C)&1?C &

Remo%ing a shared dis' from a reso!rce gro!p may not a!tomatically force %irt!al dis's offline. f -ou remo$e a disk from a resource !roup in the 9ailo$er Cluster Mana!ement tool and mo$e the disk to another resource !roup, an- $irtual disks that are hosted on that disk manot be automaticall- forced offline durin! the mo$e# To work around this issue, -ou can delete the $irtual disks before mo$in! the disk to a new resource !roup, or -ou can use the 9ailo$er Cluster Mana!ement tool to mo$e the $irtual disks to the same destination resource !roup as the hostin! disk# Uninstalling Microsoft iSCSI Software Target from a failo%er cl!ster may ta'e a long time.

,hen -ou attempt to uninstall Microsoft iSCS Software Tar!et from the last node of a failo$er cluster that is currentl- hostin! $irtual disk resources in a pendin! or failed state, the uninstallation ma- take an unusuall- lon! time to complete# To resol$e this issue, delete the resource !roups from the Microsoft iSCS Software Tar!et console prior to uninstallin! the software on the last node of the failo$er cluster# f the resource !roups are not deleted, -ou must wait for the uninstallation process to complete# ?!nctionality does not restore in the failo%er cl!ster when yo! !ninstall Microsoft iSCSI Software Target on a failo%er cl!ster node. f -ou uninstall Microsoft iSCS Software Tar!et from one node of the failo$er cluster, and then choose to reinstall the snap&in, the Microsoft iSCS Software Tar!et ser$ice can fail to start# To resol$e this issue, -ou must uninstall the snap&in, restart the stora!e appliance, and then reinstall Microsoft iSCS Software Tar!et on e$er- node of the failo$er cluster to restore functionalit-# The Microsoft iSCSI Software Target console does not !pdate when yo! create a failo%er cl!ster. f -ou ha$e the Microsoft iSCS Software Tar!et console open when -ou create a failo$er cluster, the wizards in the console will not displa- cluster resources# To resol$e this issue, -ou must close the Microsoft iSCS Software Tar!et console and then open it after the cluster has been created to enable the wizards to displa- the failo$er cluster resources# 6isabling a %irt!al dis' d!ring a rollbac' terminates the rollbac' witho!t warning. f -ou disable a $irtual disk while performin! a rollback operation, the rollback will be silentlended# 0n e$ent is lo!!ed documentin! that the rollback was ended# There is currentl- no work around for this issue# Rollbac' operations on a locally mo!nted %irt!al dis' may ta'e a long time to complete. ,hen -ou mount a $irtual disk locall- in readCwrite mode, an- rollback operation performed on that $irtual disk will take a lon! time to complete# There is currentl- no work around for this issue# ;ocally mo!nted %irt!al dis's cannot be selected when creating a new %irt!al dis'. ,hen -ou create a new $irtual disk, locall- mounted $irtual disks are displa-ed in the list of a$ailable $olumes to host the new $irtual disk# 2owe$er, usin! a locall- mounted $irtual disk to store a $irtual disk is unsupported, and the mport 3irtual 1isk ,izard cannot import $irtual disks if one or more of the files present on the disk are in use# f -ou attempt to select the locall- mounted $irtual disk as the stora!e location for the new $irtual disk, -ou will recei$e the followin! error messa!e: The Import 5irt!al 6is' "i2ard cannot import one or more %irt!al dis's. To resol$e this issue, close an- opened files, and then run the wizard a!ain# Managing Microsoft iSCSI Software Target while mo%ing a reso!rce gro!p ca!ses instability. >

Note ,hen -ou perform operations on a remote Microsoft iSCS Software Tar!et resource !roup in 9ailo$er Cluster Mana!ement, -ou will see the status of the resource !roup chan!e to #ending# f -ou attempt to run another operation while the resource !roup is pendin!, -ou ma- !et unpredictable results# There is currentl- no work around for this issue# The storage appliance stops responding when yo! ma'e shadow copies of local&mo!nted %ol!mes. ,hen -ou locall- mount a $irtual disk, and then tr- to make a shadow cop- of that $olume <for e(ample, b- usin! ,indows8 :(plorer=, the stora!e appliance ma- appear to stop respondin!# ,hen -ou create a shadow cop- of a locall- mounted $irtual disk, the local mount dri$er writes to the $olume that hosts the $irtual disk# This causes an additional copon the differencin! area of the host $olume# The result is a circular series that e$entuallcauses the stora!e appliance to stop respondin!# To resol$e this issue, restart the stora!e appliance# Config!ration iss!es occ!r when adding a storage appliance to a failo%er cl!ster after !ninstalling Microsoft ISCSI Software Target. f -ou ha$e Microsoft iSCS Software Tar!et installed on a failo$er cluster, and -ou destrothat failo$er cluster, confi!uration issues will occur# This issue also occurs when a stora!e appliance is remo$ed from a failo$er cluster before it is added to a different failo$er cluster, or when Microsoft iSCS Software Tar!et is uninstalled on a cluster node <e$en when the node does not own the resources=# To resol$e this issue, -ou must uninstall Microsoft iSCS Software Tar!et, restart the stora!e appliance, create the new failo$er cluster or Doin a node to the failo$er cluster and then reinstall Microsoft iSCS Software Tar!et# This forces Microsoft iSCS Software Tar!et to remo$e its confi!uration for the pre$ious failo$er cluster, and prepares it to reco!nize the new failo$er cluster confi!uration# 2owe$er, to up!rade from a pre$ious $ersion of Microsoft iSCS Software Tar!et on a cluster node, do not uninstall the pre$ious $ersion# nstead, install Microsoft iSCS Software Tar!et "#" directl- on each cluster node# f -ou installed Microsoft iSCS Software Tar!et on a stora!e appliance before confi!urin! the 9ailo$er Clusterin! feature, or after remo$in! and reDoinin! a stora!e appliance to a cluster, confi!uration settin!s used to identif- lo!ical unit numbers <+)4s= ma- be not be identical across all nodes in the cluster# *e$iew the 5endorSpecificI6;ow, 5endorSpecificI6$igh <and, if e(plicitl- set, 5endorI6, #rod!ctI6, and #rod!ctRe%ision= re!istr- $alues in the $:;M<S(?T"AR)<Microsoft<iSCSI Target ke- to ensure that these $alues are identical across all nodes in the cluster# The Microsoft iSCSI Software Target console displays an incorrect location for snapshot storage.

f -ou ha$e not e(plicitl- set a location for snapshot stora!e for a $olume, the Microsoft iSCS Software Tar!et console ma- displa- the incorrect location# ,hen the location is not e(plicitldefined, or if the settin! has been deleted, the 3olume Shadow Cop- Ser$ice will implicitl- set the location to an a$ailable $olume that mi!ht not be appropriate for -our confi!uration, such as a $olume that is not part of the same stora!e !roup# To a$oid this issue, -ou should e(plicitl- define the location of the snapshot stora!e for the $olume# This can be done in the Microsoft iSCS Software Tar!et console <in ,indows :(plorer, click 3olume Properties=, or -ou can t-pe 5ssadmin.e.e at a command prompt# Unpredictable res!lts occ!r when yo! remo%e snapshots. )sin! utilities such as 3ssadmin#e(e or 3shadow#e(e to delete a snapshot that was created with Microsoft iSCS Software Tar!et ma- cause unpredictable results# To resol$e this issue, alwa-s use the Microsoft iSCS Software Tar!et console to remo$e snapshots# Cl!ster nodes may not be a%ailable after failo%er. ,hen the operatin! s-stems for the nodes of a cluster are not on the same partition, the nodes are not a$ailable after failo$er# To resol$e this issue, install the ,indows Ser$er 200E *2 operatin! s-stem on the same partition on each node, t-picall- the C dri$e# Snapshot stat!s %al!e is delayed. ,hen -ou locall- mount a snapshot, the snapshot status $alue in the ,M class "TBSnapshot instance and the Stat!s propert- does not immediatel- recei$e the 65Mo!nted status when the 65Mo!nt method returns# To resol$e this issue, wait briefl- and the status should resol$e# )rror messages appear when yo! attempt to !ninstall then reinstall Microsoft iSCSI Software Target. .ou ma- encounter errors in :$ent 3iewer when attemptin! to uninstall Microsoft iSCS Software Tar!et "#2 and subse@uentl- reinstallin!# To resol$e this issue, stop the Microsoft iSCS Software Tar!et ser$ice prior to uninstallin! the software# f the software has alread- been uninstalled, -ou should restart the computer prior to reinstallin! Microsoft iSCS Software Tar!et# Attempting to manage a client r!nning Microsoft iSCSI Software Target 3.3 from a client r!nning Microsoft iSCSI Software Target 3.* will fail. .ou cannot use the Microsoft iSCS Software Tar!et "#2 snap&in to remotel- mana!e network& attached stora!e appliances that are confi!ured with Microsoft iSCS Software Tar!et "#"# 2owe$er, -ou can use the Microsoft iSCS "#" Tar!et snap&in to remotel- mana!e network& attached stora!e appliances that ha$e been confi!ured with the iSCS Software Tar!et "#2# A reso!rce gro!p may not be not %isible if a cl!ster is created after Microsoft iSCSI Software Target is installed. The Microsoft Mana!ement Console <MMC= does not recei$e updates when the status of a cluster is chan!ed# This means that if a new cluster is created on a stora!e appliance <for ?

e(ample, chan!in! a sin!le node cluster to a two&node cluster=, a user ma- not be able to associate new cluster nodes with pre&e(istin! clusters# To work around this issue, customers should create the desired cluster confi!uration first, and then create the desired iSCS tar!et<s=# 2owe$er, if the cluster alread- e(ists, a customer must e(it the MMC <in this case, Ser$er Mana!er= or close the CT window, and then initialize the MMC or the CT window# Adding an iSNS entry will fail if the reso!rce is in%alid or cannot be reached. f -ou attempt to add an nternet Stora!e 4ame Ser$ice <iS4S= entr-, the process will fail if one or more e(istin! iS4S entries are in$alid or cannot be reached# This occurs because the process $alidates all current iS4S entries before addin! a new iS4S entr-, and it onl- permits additions after current iS4S entries ha$e been disco$ered# This beha$ior can impact the cluster setup process because of the wa- that iS4S entries are replicated on all cluster nodes# 9or e(ample, if a resource !roup owns an iS4S entr- for an P resource <for e(ample, a resource on a different network=, that iS4S entr- is $alid and disco$erable for that resource !roup onl-# *eplication of iS4S entries to clusters nodes that do not own that resource !roup are not disco$erable, and updates to iS4S entries on those clusters will fail# Uninstalling Microsoft iSCSI Software Target deletes reso!rces. 1eletin! 321 resources should be treated differentl- based on whether the node is the first node of a cluster or the last node of a cluster# 2owe$er, the lo!ic to detect the last node of a cluster fails, so when Microsoft iSCS Software Tar!et is remo$ed from a cluster, it remo$es the 321 and tar!et resources for all nodes, not Dust the last node# To work around this issue, users should e$ict the node from the cluster before uninstallin! Microsoft iSCS Software Tar!et# This ensures that associated 321s remain accessible after the snap&in has been uninstalled# The Microsoft iSCSI initiator cannot create a snapshot Cor complete similar actionsD when the cl!ster is attached to more than one networ'. f a cluster is attached to more than one network durin! setup or confi!uration, the Cl!ster Name and 6omain Eoin "i2ard or ?ailo%er Cl!ster Manager ma- not associate the cluster name with the same network as the Microsoft iSCS initiator<s=# f this occurs, the 3SS pro$ider on the Microsoft iSCS initiator<s= will not be able to connect to the cluster or perform operations on the Microsoft iSCS Software Tar!et# To resol$e this issue, the cluster name must be reset so that it is associated with the same domain as the initiator<s=# This can be done usin! the Cl!ster Administrator MMC# Cannot !se the local mo!nt feat!re on Microsoft iSCSI Software Target to mo!nt a snapshot of a dynamic dis' on the iSCSI initiator. f a +)4 on the iSCS initiator is e(posed as a d-namic disk, -ou cannot use the local mount feature on Microsoft iSCS Software Tar!et to mount a snapshot of the disk# To work around this issue, create the +)4s basic disks on the iSCS initiator, or if d-namic disks are re@uired, create the snapshot directl- from the iSCS initiator, and then mana!e the snapshot from the SCS initiator# 10

Note #re%io!s data is accessible after creating a new 5$6. ,hen -ou create a new 321, the ,intar!et ser$ice does not delete the data that will comprise the 321# This is b- desi!n, because writin! zeros to each sector of the disk takes time, especiall- for lar!e 321s# 2owe$er, unless these sectors are deleted before a new 321 is created, an- application on the iSCS initiator that supports raw block B on an iSCS +)4 will be able to read the contents of the 321# To resol$e this issue, use the 1iskPart tool, or the 1isk Mana!ement snap&in <diskm!mt#msc= to create the 321# ;- default, these tools o$erwrite the disk sectors durin! the 321 creation process# Rolling bac' a 5$6 creates a corr!pted file. 1urin! the creation of a 321 file, a correspondin! chan!e bitmap <C;M= file is created# ,hen creatin! a snapshot of a 321, the C;M is used to track the chan!es to the 321 file since the last snapshot, which allows fast rollback of the 321# ;- default, updates to the C;M are made as-nchronousl- and the C;M file ma- not accuratel- reflect the content of the snapshot in the e$ent of an unintended s-stem shutdown# n this case, attemptin! to rollback a 321 to the snapshot b- usin! the corrupted C;M file ma- cause corruption in the resultin! 321 file# To resol$e this issue, users who want to ensure consistenc- between the snapshot and the C;M can enable s-nchronous writes to the C;M b- settin! the followin! $alue of the $:)4B;(CA;BMAC$IN)<S(?T"AR)<Microsoft<iSCSI Target re!istr- ke-:
Name Type 6escription

9lushCbm,riteCache

*:6F1,B*1

Set this $alue to to enable s-nchronous writes to the C;M# n a default installation, this re!istr- $alue is not present in Microsoft iSCS Software Tar!et# To disable s-nchronous writes to the C;M, edit or delete this $alue <an$alue other than 1 disables this feature= or delete the re!istr- ke-#

f -ou add this re!istr- ke- to Microsoft iSCS Software Tar!et, -ou must restart the ser$ice <located at c:GwindowsGs-stem"2Gwintar!et#e(e= to enable the chan!e# 0ddin! this re!istr- $alue can de!rade performance of Microsoft SCS Software Tar!et bup to 20H because of the inline flush# 2owe$er, this re!istr- $alue will not affect performance if -ou do not create snapshots of -our 321, or if -ou delete all 321 snapshots <which can be done after transferrin! the snapshot to portable media=# 11

Uninstallation iss!es
f -ou uninstall the iSCS Software Tar!et "#" <iscsitar!et#msi= on a stora!e appliance, the followin! files remain: 1ri$er&store files: Hs-stemrootHGs-stem"2G1* 3:*SGwtlmdr$#s-s Hs-stemrootHGS-stem"2GcatrootGI9>70:AC"&"E::&1111& E7:7& 00C059C2?7::JGKoemFdri$erFname#catL Hs-stemroot HGS-stem"2G1ri$erStoreG9ile*epositor-Gwtlmdr$#infFamdA5FneutralF1db10AA>c"75ceca Hs-stemroot HGS-stem"2G1ri$erStoreG9ile*epositor-Gwtlmdr$#infFamdA5FneutralF1db10AA>c"75cecaG wtlmdr$#pnf ,mi0p*plMiSCS initiator tri!!ered files: Hs-stemrootHGS-stem"2GwbemGPerformanceG,mi0p*plFnew#h Hs-stemrootHGS-stem"2Gwbem GPerformanceG,mi0p*plFnew#ini Hs-stemrootHGinfG ,mi0p*plG,mi0p*pl#h

Bne of the followin! directories <dependin! on the lan!ua!e that is installed on Microsoft iSCS Software Tar!et=: Hs-stemrootHGinfG,mi0p*plG0022 & if the operatin! s-stem lan!ua!e of the ser$er is Portu!uese <;razil=# Hs-stemrootHGinfG,mi0p*plG0005 & if the operatin! s-stem lan!ua!e of the ser$er is Chinese <Chinese N simplified=# Hs-stemrootHGinfG,mi0p*plG"0>A & if the operatin! s-stem lan!ua!e of the ser$er is Chinese <Chinese& traditional=# Hs-stemrootHGinfG,mi0p*plG000? N if the operatin! s-stem lan!ua!e of the ser$er is :n!lish# Hs-stemrootHGinfG,mi0p*plG0012 N if the operatin! s-stem lan!ua!e of the ser$er is 9rench# Hs-stemrootHGinfG,mi0p*plG000> N if the operatin! s-stem lan!ua!e of the ser$er is 6erman# Hs-stemrootHGinfG,mi0p*plG001A N if the operatin! s-stem lan!ua!e of the ser$er is talian# Hs-stemrootHGinfG,mi0p*plG001> N if the operatin! s-stem lan!ua!e of the ser$er is Oapanese Hs-stemrootHGinfG,mi0p*plG001E N if the operatin! s-stem lan!ua!e of the ser$er is Porean Hs-stemrootHGinfG,mi0p*plG0027 N if the operatin! s-stem lan!ua!e of the ser$er is *ussian# Hs-stemrootHGinfG,mi0p*plG0010 N if the operatin! s-stem lan!ua!e of the ser$er is Spanish# Bne of the followin! files <dependin! on the lan!ua!e that is installed on the Microsoft iSCS Software Tar!et ser$er=: 12

Hs-stemrootHGinfG,mi0p*plG0022G,mi0p*pl#ini <Portu!uese Q;razilR $ersion=

Hs-stemrootHGinfG,mi0p*plG0005G,mi0p*pl#ini <Chinese simplified lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG"0>AG,mi0p*pl#ini <Chinese& traditional lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG000?G,mi0p*pl#ini <:n!lish lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG0012G,mi0p*pl#ini <9rench lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG000>G,mi0p*pl#ini <6erman lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG001AG,mi0p*pl#ini < talian lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG001>G,mi0p*pl#ini <Oapanese lan!ua!e $ersion= Hs-stemrootHGinfG,mi0p*plG001EG,mi0p*pl#ini <Porean lan!ua!e $ersion= Hs-stemrootHGinfG,mi0p*plG0027G,mi0p*pl#ini <*ussian lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG0010G,mi0p*pl#ini <Spanish lan!ua!e $ersion=#

0utoreco$er- Mana!ed BbDect 9ormat <MB9= files Hs-stemrootHGS-stem"2GwbemG0uto*eco$erG 5;A:25A>971E?09;5>1"02>E"C:5>799#mof Hs-stemroot HGS-stem"2GwbemG0uto*eco$erG7>;?C1:2090CA1"0:7"7E120C9C09??;#mof Hs-stemrootHGS-stem"2GwbemG0uto*eco$erG 0791:1"C:C5>>??:;"90;9771>"C::70#mof

B:M Setup nformation < 49= and Precompiled Setup nformation <P49= files: Hs-stemrootHGinfGKoemFdri$erFnameL#inf Hs-stemrootHGinfGKoemFdri$erFnameL#pnf

f -ou uninstall Microsoft iSCS Software Tar!et Client "#" <iscsitar!etClient#msi= on a client, the followin! files remain: Hs-stemrootHGS-stem"2GwbemGPerformanceG,mi0p*plFnew#h Hs-stemrootHGS-stem"2Gwbem GPerformanceG,mi0p*plFnew#ini Hs-stemrootHGinfG ,mi0p*plG,mi0p*pl#h

Bne of the followin! directories <dependin! on the lan!ua!e that is installed on the client=: Hs-stemrootHGinfG,mi0p*plG0022 & if the operatin! s-stem lan!ua!e of the client is Portu!uese <;razil=# Hs-stemrootHGinfG,mi0p*plG0005 & if the operatin! s-stem lan!ua!e of the client is Chinese <Chinese N simplified=# Hs-stemrootHGinfG,mi0p*plG"0>A & if the operatin! s-stem lan!ua!e of the client is Chinese <Chinese& traditional=# Hs-stemrootHGinfG,mi0p*plG000? N if the operatin! s-stem lan!ua!e of the client is :n!lish# Hs-stemrootHGinfG,mi0p*plG0012 N if the operatin! s-stem lan!ua!e of the client is 9rench#

1"

 Hs-stemrootHGinfG,mi0p*plG000> N if the operatin! s-stem lan!ua!e of the client is 6erman# Hs-stemrootHGinfG,mi0p*plG001A N if the operatin! s-stem lan!ua!e of the client is talian# Hs-stemrootHGinfG,mi0p*plG001> N if the operatin! s-stem lan!ua!e of the client is Oapanese Hs-stemrootHGinfG,mi0p*plG001E N if the operatin! s-stem lan!ua!e of the client is Porean Hs-stemrootHGinfG,mi0p*plG0027 N if the operatin! s-stem lan!ua!e of the client is *ussian# Hs-stemrootHGinfG,mi0p*plG0010 N if the operatin! s-stem lan!ua!e of the client is Spanish# Bne of the followin! files <dependin! on the lan!ua!e that is installed on the client=: Hs-stemrootHGinfG,mi0p*plG0022G,mi0p*pl#ini <Portu!uese Q;razilR $ersion=# Hs-stemrootHGinfG,mi0p*plG0005G,mi0p*pl#ini <Chinese simplified lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG"0>AG,mi0p*pl#ini <Chinese& traditional lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG000?G,mi0p*pl#ini <:n!lish lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG0012G,mi0p*pl#ini <9rench lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG000>G,mi0p*pl#ini <6erman lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG001AG,mi0p*pl#ini < talian lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG001>G,mi0p*pl#ini <Oapanese lan!ua!e $ersion= Hs-stemrootHGinfG,mi0p*plG001EG,mi0p*pl#ini <Porean lan!ua!e $ersion= Hs-stemrootHGinfG,mi0p*plG0027G,mi0p*pl#ini <*ussian lan!ua!e $ersion=# Hs-stemrootHGinfG,mi0p*plG0010G,mi0p*pl#ini <Spanish lan!ua!e $ersion=#

15