Microsoft's own iSCSI client requirements for IQN

Node Name:
The Microsoft iSCSI Initiator strictly adheres to the rules specified for the ISCSI node name. These rules also apply to the Microsoft ISCSI initiator node name and any target node names that are discovered. The rules for building iSCSI node names, such as the iSCSI specification and the "string profile for iSCSI names" Internet Draft, are described below:
The node name is encoded using the UTF-8 character set. Note that the Microsoft ISCSI initiator service does not support UCS-4 characters. RFC 2044 describes UTF-8 encoding.

The node name is 223 bytes or less.

Node names can contain alphabetic characters (A to Z), numbers (0 to 9), periods (.), hyphens (-), or colons (:).

Always map uppercase characters to lowercase characters.

Additionally, when you violate the rules for node names, the Microsoft ISCSI initiator takes the following actions:
An error was returned when attempting to set the node name to an invalid string.

An error was returned when attempting to manually configure a target with an invalid target node name.

The node name is dynamically generated when the node name is not set (based on the computer name).

The mapped character is not valid. For example, if the computer name contains an underscore, the Microsoft ISCSI initiator changes it to a hyphen (-). (If the computer name is COMPUTER1_DEPT1, the corresponding part of the node name becomes COMPUTER1-DEPT1.) ）

The event log is generated when the target has an invalid node name. It ignores the target and, in some cases, ignores all targets found with it (for example, if a target in the Sendtargets node has an invalid node name, the Microsoft ISCSI initiator ignores all targets in the Sendtargets text response)

Microsoft's own iSCSI client requirements for IQN