Compare an iSCSI Target design with supported and enforced limits

Source facts

Microsoft’s iSCSI Target Server reference separates tested support limits from limits enforced by the implementation. Its tables distinguish target instances, logical units, sessions, and snapshots rather than presenting one overall capacity figure. Microsoft marks converting between standalone and clustered iSCSI Target Server configurations as unsupported and warns that target, virtual-disk, and snapshot configuration metadata is lost during conversion. Microsoft documentation.

Applicability

Use this review before expanding an iSCSI Target Server or changing its deployment model. Match the operating-system version to the relevant table entries and identify which resource each proposed increase consumes.

DSE recommendation

Build a capacity worksheet using the source’s individual categories and the actual planned topology. Record current counts, proposed additions, and the applicable limit for each category. Have the storage owner review architectural changes separately from ordinary growth. Do not interpret a configuration being accepted by a tool as evidence that it remains within Microsoft’s tested support boundaries.

Verification

Compare the approved worksheet with the completed target, virtual-disk, and initiator inventory. Check the planned connection paths through a representative workload test. Retain any count discrepancy or unsupported conversion proposal as an unresolved design issue. Revisit the worksheet before the next expansion, using the then-current vendor reference.

Official references

Microsoft Learn: iSCSI Target Server Scalability Limits. Source reviewed September 8, 2026.