11/30/2007 3.3 Minor Made technical and editorial changes based on feedback. 1/25/2008 3.4 Minor Clarified the meaning of the technical content. 3/14/2008 4.0 Major Updated and revised the technical content. 5/16/2008 5.0 Updated and revised the technical content. 6/20/2008 5.1 Clarified the meaning of the technical content. 7/25/2008 5.2 Minor Clarified the meaning of the technical content. 8/29/2008 6.0 Major Updated and revised the technical content. 10/24/2008 7.0 Major Updated and revised the technical content. 12/5/2008 8.0 Major Updated and revised the technical content. 1/16/2009 9.0 Major Updated and revised the technical content.
2/27/2009 9.1 Clarified the meaning of the technical content. 4/10/2009 9.2 Clarified the meaning of the technical content. 5/22/2009 10.0 Major Updated and revised the technical content. 7/2/2009 10.1 Minor Clarified the meaning of the technical content. 8/14/2009 11.0 Updated and revised the technical content. 9/25/2009 12.0 Major Updated and revised the technical content. 11/6/2009 13.0 Major Updated and revised the technical content. 12/18/2009 14.0 Major Updated and revised the technical content. 1/29/2010 15.0 Major Updated and revised the technical content. 3/12/2010 16.0 Major Updated and revised the technical content. 4/23/2010 17.0 Major Updated and revised
the technical content. 6/4/2010 17.1 Minor Clarified the meaning of the technical content. 7/16/2010 17.2 Minor Clarified the meaning of the technical content. 8/27/2010 17.3 Minor Clarified the meaning of the technical content. 10/8/2010 18.0 Updated and revised the technical content. 11/19/2010 18.1 Clarified the meaning of the technical content. 1/7/2011 18.2 Minor Clarified the meaning of the technical content. 2/11/2011 19.0 Updated and revised the technical content. 3/25/2011 20.0 Updated and revised the technical content. 5/6/2011 21.0 Major Updated and revised the technical content. 6/17/2011 21.1 Minor Clarified the meaning of the
technical content. 9/23/2011 21.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 22.0 Major Updated and revised the technical content. 3/30/2012 23.0 Major Updated and revised the technical content. 7/12/2012 23.1 Clarified the meaning of the technical content. 10/25/2012 24.0 Updated and revised the technical content. 1/31/2013 24.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 25.0 Major Updated and revised the technical content. 11/14/2013 25.0 None No changes to the meaning, language, or formatting of the technical content.
Protocol Details The methods comprising this interface MUST all return 0x00000000 on success, and a non-zero, implementation-specific error code on failure. Unless otherwise specified in the following sections, a server implementation of this protocol can choose any non-zero Win32 error value to signify an error condition, as discussed in section . The side of the Workstation Service Remote Protocol MUST NOT interpret returned error codes. The of the protocol MUST simply return error codes to the invoking application without taking any protocol action. Note that the client side and refer to the initiating and receiving ends of the protocol, respectively, rather than to client or versions of an operating system. These methods MUST all behave the same regardless of whether the server side of the protocol is running in a client or server version of an operating system. wkssvc Client Details Abstract Data Model No abstract data is required. Timers No protocol timers are required beyond used internally by the to implement resiliency to network outages, as specified in . Initialization The MUST create an connection to the remote computer, using the details specified in section . Message Processing Events and Sequencing Rules No sequence of method is imposed on this protocol. When a method completes, the values that the returns MUST be returned unmodified to the upper layer. The MUST ignore errors that the RPC returns and notify the application invoker of the received in the higher layer. Otherwise, no special message processing is required on the client beyond the processing required in the underlying RPC protocol. Timer Events There are no timer events. Other Local Events are no local events. wkssvc Server Details Abstract Data Model This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the
Index A Abstract data 44 45 19 C 19 157 Client 44 44 44 44 44 44 44 125 D Data - abstract 44 45 21 38 37 43 Domain join 83 E 43 35 37 21 Events 44 130 44 130 Examples 133 132 132 F 19 137 G 8 I 137 136 136 136 15 Initialization 44 50 8 J 20 20 35 37 34 L Local events 44 130 30 42 39 41 39 42 41 42 41 24 25 28 28 25 28 26 34 29 33 33 29 32 29 33 M 20 Message processing 44 51 Messages 21 21 processing ( 81, 83, 87) 24 20 20 23 Methods 125
43 Security 136 136 Sequencing rules 44 51 Server 45 125 50 130 51 102 123 99 76 78 108 90 115 87 66 71 73 68 95 53 55 63 64 61 60 75 51 130 50 19 30 24 Syntax 21 21 20 24 23 T Timer events 44 130 Timers 44 50 157 20 U 38 23 42 39 41 39 42 41 42 41 V 19 19 W 24 25 28 28 25 28 26 34 29 33 33 29 32 29 33 87