[MS-DFSRH]: DFS Replication Helper Protocol Specification

More documents

Recommendations

Info

versionVector: MUST be the version vector for the replicated folder whose GUID is specified bythe contentSetGuid field.The version vector is either compressed (that is, an encoded field whose format is specified bythe Windows Server 2003 decompression algorithm in [MS-DRSR] or uncompressed. Theversion vector MUST be represented by a VARIANT field that has a VT_BSTR variant type.The client MUST determine whether the version vector is compressed by applying the followingrules:• If the sum of the number of characters, including the terminating NULL character in theBSTR, multiplied by the size, in bytes, of a Unicode character (the size MUST be 2) is lessthan the value of the uncompressedSize field, the version vector is sent in compressedform.• Otherwise, the version vector is uncompressed.The compressed or uncompressed version vector MUST be encoded in a BSTR and passed byusing the versionVector.bstrVal field.The compressed or uncompressed version vector buffer MUST be encoded in a BSTR byapplying the following rules:• The length, in bytes, of the BSTR buffer MUST be greater than or equal to the value of thesize of the binary data that is to be encoded.• The part of the BSTR buffer between offsets 0 and "length - 1" MUST be filled by thecompressed or uncompressed data, as specified previously. The remainder of the BSTRbuffer (if any) MUST be ignored by the server.2.2.1.5 Server Health Report XMLThe server health report is an XML document that contains the data that is related to DFS-R servicehealth.2.2.1.5.1 xs NamespaceThe xs namespace that is used in subsections of section 2.2.1.5 refers to the XMLSchemanamespace that is specified in [XMLSCHEMA0], [XMLSCHEMA1], and [XMLSCHEMA2].2.2.1.5.2 timestamp ElementThe timestamp XML element represents the time in a specific time zone.
type="xs:int"/>Child ElementsElement Type DescriptionfileTime xs:long MUST be the time, in FILETIME format, as specified in the [MS-DTYP] AppendixA. Because the FILETIME is provided in Coordinated Universal Time (UTC), thedaylight time adjustment MUST NOT be included in this field. Instead, theadjustment MUST be included in the timezone field.systemTime xs:string An implementation-specific textual representation of the date and time.AttributesName Type Descriptiontimezone xs:int MUST be the difference, in minutes, between the time in the server time zone andCoordinated Universal Time (UTC). This field SHOULD account for the daylight timeadjustment.2.2.1.5.3 folder ElementThe folder XML element represents a folder on the disk.
Page 2 and 3: DateRevisionHistoryRevisionClassCom
Page 4 and 5: 2.2.1.5.17.11 EVENT_DFSR_VOLUME_JOU
Page 6 and 7: 1 IntroductionThe Distributed File
Page 8 and 9: [UNICODE4.0] The Unicode Consortium
Page 10 and 11: • IServerHealthReportThe IADProxy
Page 12 and 13: For more information about this LDA
Page 16 and 17: Child ElementsElement Type Descript
Page 18 and 19: Element Type DescriptionbacklogInbo
Page 20 and 21: Child ElementsElement Type Descript
Page 22 and 23: Element Type DescriptionfileFilter
Page 24 and 25: 24 / 81[MS-DFSRH] - v20080207DFS Re
Page 26 and 27: Element Type Descriptionerror error
Page 28 and 29: Element Type Descriptionimplementat
Page 30 and 31: 2.2.1.5.15 errorReferences ElementT
Page 32 and 33: When the server detects any of the
Page 34 and 35: Error parameters:Ref IDMeaning1312.
Page 36 and 37: 2.2.1.5.17.13 EVENT_DFSR_CS_ERROR M
Page 38 and 39: Ref IDMeaning4206.8 The name of the
Page 40 and 41: Ref IDMeaning4304.2 The file path.4
Page 42 and 43: Ref IDMeaning4502.4 The name of the
Page 44 and 45: Ref IDMeaning5102.1 The replicated
Page 46 and 47: Ref IDMeaning6008.1 The configurati
Page 48 and 49: Ref IDMeaning6402.8 The member GUID
Page 50 and 51: Ref IDMeaning6410.3 The overlapped
Page 52 and 53: 3 Protocol Details3.1 Server Role D
Page 54 and 55: If the user does not have sufficien
Page 56 and 57: 3.1.5.2.3 ModifyObject Method (Opnu
Page 58 and 59: [in] BSTR distinguishedName,[in] SA
Page 60 and 61: [in] BSTR distinguishedName,[in] SA
Page 62 and 63: flags: Any values of the DfsrReport
Page 64 and 65:
and 0xFFFFFFFF on failure. For prot
Page 66 and 67:
3.1.5.4.6 GetReferenceBacklogCount
Page 68 and 69:
4 Protocol Examples4.1 Example of M
Page 70 and 71:
0127727764510000000Monday, October
Page 72 and 73:
6 Appendix A: Full IDLThe DFS-R Hel
Page 74 and 75:
[in] long flags,[out] SAFEARRAY(_Ve
Page 76 and 77:
The IADProxy2 interface is availabl
Page 78 and 79:
Section 2.2.1.5.17.22: This error i
Page 80 and 81:
GlossaryHHealth report XML exampleH
show all

[MS-DFSRH]: DFS Replication Helper Protocol Specification

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?