Export (0) Print
Expand All

7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:

  • Windows NT operating system

  • Windows 2000 operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

  • Windows Server 2008 operating system

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 1.3: The server end of the RSM Remote Protocol is implemented by the Windows RSM service on Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, Windows XP, and Windows 2000. The RSM Remote Protocol is an optional feature on Windows Server 2008 and Windows Vista machines. The client end of the RSM Remote Protocol is implemented by a number of components, including the Windows RSM user interface and the RSM.exe command-line tool. This protocol is supported on Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, Windows XP, and Windows 2000.

<2> Section 1.4: The RSM Remote Protocol is used by the Ntbackup.exe application.

<3> Section 1.7.1: The following interfaces are implemented by Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, Windows XP, and Windows 2000.

The following interfaces are implemented by Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, and Windows XP.

<4> Section 1.7.2: The following interface is implemented by Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, Windows XP, and Windows 2000.

The following interface is implemented by Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, and Windows XP.

<5> Section 1.7.3: The following interface is implemented by Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, Windows XP, and Windows 2000.

The following interface is implemented by Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows Vista, and Windows XP.

<6> Section 1.7.4: The following interface is implemented by Windows 2000, Windows XP, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008

The following interfaces are implemented by Windows XP, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008.

<7> Section 2.2.4.16: Windows uses the application name "Removable Storage".

<8> Section 2.2.4.16: Windows sets this value to the name of the user running the client.

<9> Section 2.2.4.16: Windows sets this value to the name of the client computer.

<10> Section 2.2.4.16: Windows returns the error code of the request that failed.

<11> Section 2.2.4.17: Windows uses the application name "Removable Storage".

<12> Section 2.2.4.17: Windows returns the error code of the request that failed.

<13> Section 2.2.4.20: Windows sets this value to a blank string.

<14> Section 2.2.4.21: The Windows client uses a null-terminated string.

<15> Section 2.2.4.26: In Windows, this value is 259,200.

<16> Section 2.2.4.26: In Windows, this value is 259,200.

<17> Section 3.1.5.2.1.1: Windows displays event notification to the operator, and may perform processing based on the type of the notification.

<18> Section 3.2.1.2.3: The RSM server maintains all the media IDs in a database that can persist across the server sessions.

<19> Section 3.2.1.3: The RSM server maintains all of the storage object IDs in a database that can persist across the server sessions.

<20> Section 3.2.5.2: RSM provides security for media pool and library objects. Media pool security controls access to media, including physical media, sides, and logical media. When nested pools are used for media pools, the security of the lowest-level media pool determines the security of the media objects. Library security controls access to physical library units, including drives, changers, slots, and IE ports.

Applications can use the SetNtmsObjectSecurity and GetNtmsObjectSecurity methods to set and check security for an RSM object.

The following tables identify the security requirements for the RSM methods, which use the following key.

Code

Value

Description

U

NTMS_USE_ACCESS

Permission to use an NTMS object. For example, NTMS_USE_ACCESS would allow a user to get an object's attributes or mount media within a library .

M

NTMS_MODIFY_ACCESS

Permission to make changes to an NTMS object. For example, NTMS_MODIFY_ACCESS would allow a user to change the name of an object or change its attributes.

C

NTMS_CONTROL_ACCESS

Permission to control an NTMS object. For example, NTMS_CONTROL_ACCESS would allow a user to inject media, eject media, clean, or open the door.

R

READ_CONTROL

Permission to read the security attribute.

W

WRITE_DAC

Permission to write a security attribute.

In Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008, the following table identifies the RSM methods and their security requirements.

Method

Media Pool

Library

Computer

INtmsLibraryControl1::AccessNtmsLibraryDoor

 

C

 

INtmsMediaServices1::AddNtmsMediaType

 

M

 

INtmsMediaServices1::AllocateNtmsMedia

C

   

INtmsLibraryControl1::CancelNtmsLibraryRequest

 

C

 

INtmsSession1::CancelNtmsOperatorRequest

   

C

INtmsMediaServices1::ChangeNtmsMediaType

M

 

M

INtmsLibraryControl1::CleanNtmsDrive

 

C

 

INtmsObjectInfo1::CreateNtmsMediaA

INtmsObjectInfo1::CreateNtmsMediaW

M

 

M

INtmsMediaServices1::CreateNtmsMediaPoolA

INtmsMediaServices1::CreateNtmsMediaPoolW

C

   

INtmsMediaServices1::DeallocateNtmsMedia

C

   

INtmsMediaServices1::DecommissionNtmsMedia

C

   

INtmsLibraryControl1::DeleteNtmsDrive

 

M

 

INtmsLibraryControl1::DeleteNtmsLibrary

 

M

 

INtmsMediaServices1::DeleteNtmsMedia

M

 

M

INtmsMediaServices1::DeleteNtmsMediaPool

M

   

INtmsMediaServices1::DeleteNtmsMediaType

 

M

 

INtmsLibraryControl1::DeleteNtmsRequests

   

M

INtmsObjectManagement1::DisableNtmsObject

 

M

 

INtmsLibraryControl1::DismountNtmsDrive

 

M

 

INtmsMediaServices1::DismountNtmsMedia

U

U

 

INtmsLibraryControl1::EjectNtmsCleaner

 

C

 

INtmsLibraryControl1::EjectNtmsMedia

 

C

 

INtmsObjectManagement1::EnableNtmsObject

 

M

 

INtmsSession1::ExportNtmsDatabase

   

C

INtmsObjectManagement1::GetNtmsObjectAttributeA

INtmsObjectManagement1::GetNtmsObjectAttributeW

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

 

U

U

 

 

U

U

 

 

 

U

 

 

U

 

U

U

U

U

 

 

 

 

 

 

U

 

 

 

U

U

 

U

 

 

 

 

 

 

U

U

 

 

 

INtmsObjectInfo1::GetNtmsObjectInformationA

INtmsObjectInfo1::GetNtmsObjectInformationW

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

 

U

U

 

 

U

U

 

 

 

U

 

 

U

 

U

U

U

U

 

 

 

 

 

 

U

 

 

 

U

U

 

U

 

 

 

 

 

 

U

U

 

 

 

INtmsObjectManagement1::GetNtmsObjectSecurity

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

R

R

 

 

R

R

 

 

R

 

 

R

 

R

R

R

R

 

 

 

 

 

 

R

 

 

R

R

 

R

 

 

 

 

 

 

R

R

 

 

 

INtmsLibraryControl1::GetNtmsRequestOrder

   

C

INtmsObjectManagement2::GetNtmsUIOptionsA

INtmsObjectManagement2::GetNtmsUIOptionsW

NTMS_COMPUTER

NTMS_LIBRARY

 

 

 

 

 

 

 

U

 

 

U

 

INtmsSession1::ImportNtmsDatabase

   

C

INtmsLibraryControl1::InjectNtmsCleaner

 

C

 

INtmsLibraryControl1::InjectNtmsMedia

 

C

 

INtmsLibraryControl1::InventoryNtmsLibrary

 

C

 

INtmsMediaServices1::MountNtmsMedia

U

U

 

INtmsMediaServices1::MoveToNtmsMediaPool

C

   

INtmsSession1::OpenNtmsServerSessionA

INtmsSession1::OpenNtmsServerSessionW

   

U

INtmsLibraryControl1::ReleaseNtmsCleanerSlot

 

C

 

INtmsLibraryControl1::ReserveNtmsCleanerSlot

 

C

 

INtmsSession1::SatisfyNtmsOperatorRequest

   

C

INtmsMediaServices1::SetNtmsMediaComplete

C

   

INtmsObjectManagement1::SetNtmsObjectAttributeA

INtmsObjectManagement1::SetNtmsObjectAttributeW

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

 

U

U

 

 

U

U

 

 

 

U

 

 

U

 

U

U

U

U

 

 

 

 

 

 

U

 

 

 

U

U

 

U

 

 

 

 

 

 

U

U

 

 

 

INtmsObjectInfo1::SetNtmsObjectInformationA

INtmsObjectInfo1::SetNtmsObjectInformationW

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

 

M

M

 

 

M

M

 

 

 

M

 

 

M

 

M

M

C

M

 

 

 

 

 

 

M

 

 

 

M

M

 

M

 

 

 

 

 

 

M

M

 

 

 

INtmsObjectManagement1::SetNtmsObjectSecurity

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

W

W

 

 

W

W

 

 

W

 

 

W

 

W

W

W

W

 

 

 

 

 

 

W

 

 

W

W

 

W

 

 

 

 

 

 

W

W

 

 

 

INtmsLibraryControl1::SetNtmsRequestOrder

   

C

INtmsSession1::SubmitNtmsOperatorRequestA

INtmsSession1::SubmitNtmsOperatorRequestW

NTMS_OPREQ_CLEANER

NTMS_OPREQ_DEVICESERVICE

NTMS_OPREQ_MESSAGE

NTMS_OPREQ_MOVEMEDIA

NTMS_OPREQ_NEWMEDIA

 

 

 

 

 

C

C

 

 

C

C

 

 

 

 

 

 

 

U

 

 

INtmsObjectManagement2::EnumerateNtmsObjectR

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

U

U

 

 

U

U

 

 

U

 

 

U

 

U

U

U

U

 

 

 

 

 

 

U

 

 

U

U

 

U

 

 

 

 

 

 

U

U

 

 

 

INtmsObjectManagement2::SetNtmsUIOptionsA

INtmsObjectManagement2::SetNtmsUIOptionsW

NTMS_COMPUTER

NTMS_LIBRARY

 

 

 

 

 

 

 

U&M

 

 

U&M

 

INtmsMediaServices1::SwapNtmsMedia

M

   

In Windows 2000 or Windows XP, the following table identifies the RSM methods and their security requirements.

Method

Media Pool

Library

Computer

INtmsLibraryControl1::AccessNtmsLibraryDoor

 

C

 

INtmsMediaServices1::AddNtmsMediaType

 

C

 

INtmsMediaServices1::AllocateNtmsMedia

M

   

INtmsLibraryControl1::CancelNtmsLibraryRequest

 

C

 

INtmsSession1::CancelNtmsOperatorRequest

   

C

INtmsMediaServices1::ChangeNtmsMediaType

M

   

INtmsLibraryControl1::CleanNtmsDrive

 

C

 

INtmsObjectInfo1::CreateNtmsMediaA

INtmsObjectInfo1::CreateNtmsMediaW

C

M

 

INtmsMediaServices1::CreateNtmsMediaPoolA

INtmsMediaServices1::CreateNtmsMediaPoolW

M

   

INtmsMediaServices1::DeallocateNtmsMedia

M

   

INtmsMediaServices1::DecommissionNtmsMedia

M

   

INtmsLibraryControl1::DeleteNtmsDrive

 

M

 

INtmsLibraryControl1::DeleteNtmsLibrary

 

M

 

INtmsMediaServices1::DeleteNtmsMedia

M

   

INtmsMediaServices1::DeleteNtmsMediaPool

C

   

INtmsMediaServices1::DeleteNtmsMediaType

 

C

 

INtmsLibraryControl1::DeleteNtmsRequests

   

C

INtmsObjectManagement1::DisableNtmsObject

 

C

 

INtmsLibraryControl1::DismountNtmsDrive

 

C

 

INtmsMediaServices1::DismountNtmsMedia

U

U

 

INtmsLibraryControl1::EjectNtmsCleaner

 

C

 

INtmsLibraryControl1::EjectNtmsMedia

 

C

 

INtmsObjectManagement1::EnableNtmsObject

 

C

 

INtmsSession1::ExportNtmsDatabase

   

C

INtmsObjectManagement2::GetNtmsUIOptionsA

INtmsObjectManagement2::GetNtmsUIOptionsW

NTMS_COMPUTER

NTMS_LIBRARY

 

 

 

 

 

 

 

U

 

 

U

 

INtmsLibraryControl2::IdentifyNtmsSlot

 

C

 

INtmsSession1::ImportNtmsDatabase

   

C

INtmsLibraryControl1::InjectNtmsCleaner

 

C

 

INtmsLibraryControl1::InjectNtmsMedia

 

C

 

INtmsLibraryControl1::InventoryNtmsLibrary

 

C

 

INtmsMediaServices1::MountNtmsMedia

U

U

 

INtmsMediaServices1::MoveToNtmsMediaPool

M

   

INtmsSession1::OpenNtmsServerSessionA

INtmsSession1::OpenNtmsServerSessionW

   

U

INtmsLibraryControl1::ReleaseNtmsCleanerSlot

 

C

 

INtmsLibraryControl1::ReserveNtmsCleanerSlot

 

C

 

INtmsSession1::SatisfyNtmsOperatorRequest

   

C

INtmsMediaServices1::SetNtmsMediaComplete

M

   

INtmsObjectManagement1::SetNtmsObjectInformationA

INtmsObjectManagement1::SetNtmsObjectInformationW

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_PARTITION

NTMS_STORAGESLOT

 

 

C

C

C

 

 

 

 

 

 

C

 

 

 

 

 

 

INtmsObjectManagement1::SetNtmsObjectSecurity

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

W

W

 

 

W

W

 

 

W

 

 

W

 

W

W

W

W

 

 

 

 

 

 

W

 

 

W

W

 

W

 

 

 

 

 

 

W

W

 

 

 

INtmsObjectManagement2::EnumerateNtmsObjectR

NTMS_CHANGER

NTMS_CHANGER_TYPE

NTMS_COMPUTER

NTMS_DRIVE

NTMS_DRIVE_TYPE

NTMS_IEDOOR

NTMS_IEPORT

NTMS_LIBRARY

NTMS_LIBREQUEST

NTMS_LOGICAL_MEDIA

NTMS_MEDIA_POOL

NTMS_MEDIA_TYPE

NTMS_OPREQUEST

NTMS_PARTITION

NTMS_PHYSICAL_MEDIA

NTMS_STORAGESLOT

 

 

 

 

 

 

 

 

 

 

U

U

 

 

U

U

 

 

U

 

 

U

 

U

U

U

U

 

 

 

 

 

 

U

 

 

U

U

 

U

 

 

 

 

 

 

U

U

 

 

 

INtmsObjectManagement2::SetNtmsUIOptionsA

INtmsObjectManagement2::SetNtmsUIOptionsW

NTMS_COMPUTER

NTMS_LIBRARY

 

 

 

 

 

 

 

U&M

 

 

U&M

 

INtmsMediaServices1::SwapNtmsMedia

M

   

<21> Section 3.2.5.2.1: Opnums reserved for local use apply to Windows as follows.

Opnum

Description

9

Only used locally by Windows, never remotely.

<22> Section 3.2.5.2.1.15: The RSM Remote Protocol servers currently sort NTMS_LM_MOUNT requests in the request queue by order number. The order number set by the SetNtmsRequestOrder method is specific to the type of request, because the types are processed in a predetermined order. For example, a NTMS_LM_DISMOUNT request is processed prior to a NTMS_LM_MOUNT request. Within a specific class of requests the queue can be ordered, however, with the lower-ordered requests processed first. To immediately process a request, a client can set the order number to 1. To defer processing, a client sets the order number to a large number or 0xFFFFFFFF. The order number of a request which currently has an order number of 0 cannot be changed.

<23> Section 3.2.5.2.1.17: Only RSM Remote Protocol servers on Windows 2000 support this functionality.

<24> Section 3.2.5.2.1.17: Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 always returns S_OK (0x00000000) because no operation is performed.

<25> Section 3.2.5.2.1.18: Only RSM Remote Protocol servers on Windows 2000 support this functionality.

<26> Section 3.2.5.2.1.18: Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 always returns S_OK (0x00000000) because no operation is performed.

<27> Section 3.2.5.2.1.19: Only RSM Remote Protocol servers on Windows 2000 support this functionality.

<28> Section 3.2.5.2.1.19: Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 always returns S_OK (0x00000000) because no operation is performed.

<29> Section 3.2.5.2.2: Opnums reserved for local use apply to Windows as follows.

Opnum

Description

5

Only used locally by Windows, never remotely

<30> Section 3.2.5.2.2.3: In Windows Server 2003, if media are being allocated from the free pool, NTMS_USE_ACCESS to the free pool and NTMS_CONTROL_ACCESS to the destination pool are required. If the free pool is not the source media pool, NTMS_CONTROL_ACCESS is required on both source and destination pools.

<31> Section 3.2.5.2.2.4: In Windows Server 2003, if media are being returned to the free pool, NTMS_USE_ACCESS to the free pool and NTMS_CONTROL_ACCESS to the source pool is required. If the free pool is not the destination media pool, NTMS_CONTROL_ACCESS is required on both source and destination pools.

<32> Section 3.2.5.2.2.13: In Windows Server 2003 if the free pool is the source pool, then NTMS_USE_ACCESS to the free pool and NTMS_CONTROL_ACCESS to the destination pool are required. If the free pool is the destination pool, then NTMS_CONTROL_ACCESS to the source pool and NTMS_USE_ACCESS to the free pool are required. If the free pool is neither a source pool nor a destination pool, then NTMS_CONTROL_ACCESS is required on both source and destination pools. The free pool MUST not be both a source pool and a destination pool simultaneously.

<33> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the library.

<34> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the computer.

<35> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the computer.

<36> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the library.

<37> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the computer.

<38> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the library.

<39> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the library.

<40> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_CONTROL_ACCESS to the library.

<41> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the library.

<42> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the media pool.

<43> Section 3.2.5.2.3.3: Windows XP, Windows 2000, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the media pool.

<44> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the computer.

<45> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the computer.

<46> Section 3.2.5.2.3.3: Windows XP, Windows 2000, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the media pool of the side.

<47> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the media pool.

<48> Section 3.2.5.2.3.3: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the library.

<49> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<50> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<51> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<52> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<53> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<54> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<55> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<56> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_CONTROL_ACCESS to the library.

<57> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<58> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<59> Section 3.2.5.2.3.4: Windows XP, Windows 2000, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the media pool.

<60> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<61> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<62> Section 3.2.5.2.3.4: Windows XP, Windows 2000, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require NTMS_MODIFY_ACCESS to the media pool of the side.

<63> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<64> Section 3.2.5.2.3.4: In Windows XP and Windows 2000, no access rights are required.

Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008 require access rights.

<65> Section 3.2.5.2.3.5: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<66> Section 3.2.5.2.3.5: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<67> Section 3.2.5.2.3.5: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<68> Section 3.2.5.2.3.5: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<69> Section 3.2.5.2.3.5: Windows applications do not use this member.

<70> Section 3.2.5.2.3.6: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<71> Section 3.2.5.2.3.6: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<72> Section 3.2.5.2.3.6: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<73> Section 3.2.5.2.3.6: Windows maintains a database of all the media that are currently under RSM control and available to RSM. It checks this database for duplication.

<74> Section 3.2.5.2.4.3: When the input parameter lpdwAttributeBufferSize is not large enough, ERROR_INSUFFICIENT_BUFFER (0x8007007A) is not returned. Instead, RPC_S_INVALID_BOUND (0x800706c6) is returned.

<75> Section 3.2.5.2.5: Opnums reserved for local use apply to Windows as follows.

Opnum

Description

13

Returns ERROR_NOT_IMPLEMENTED. It is never used.

<76> Section 3.2.5.2.5.1: If the lpApplication parameter has been set to NULL by the client, the server uses "RSM" as the default lpApplication value.

<77> Section 3.2.5.2.5.9: The Windows RSM Remote Protocol server saves the exported database by creating an export directory under the database directory. By default, the database directory is %SystemRoot%\System32\NtmsData and can be set by the user by using a registry key HKLM\System\CurrentControlSet\Control\NTMS\NtmsData.

<78> Section 3.2.5.2.5.10: The Windows RSM Remote Protocol server saves the exported database by creating an Export directory under the database directory. By default, the database directory is %SystemRoot%\System32\NtmsData and can be set by the user by using a registry key HKLM\System\CurrentControlSet\Control\NTMS\NtmsData.

<79> Section 3.2.5.2.6: This interface is not supported on Windows 2000. It is available on Windows Server 2003, Windows XP, Windows Vista, and Windows Server 2008.

This interface is implemented by the server to support management of media libraries. INtmsLibraryControl2 inherits all objects and methods from the INtmsLibraryControl1 interface (opnums 0–22).

<80> Section 3.2.5.2.7: This interface is not supported on Windows 2000. It is available on Windows Server 2003, Windows XP, Windows Vista, and Windows Server 2008.

<81> Section 3.2.5.2.8: This interface is not supported on Windows 2000. It is available on Windows Server 2003, Windows XP, Windows Vista, and Windows Server 2008.

<82> Section 3.2.5.2.9: This interface is not supported on Windows 2000. It is available on Windows Server 2003, Windows XP, Windows Vista, and Windows Server 2008.

<83> Section 3.2.5.2.10: This interface is not supported on Windows 2000. It is available on Windows XP, Windows Server 2003, Windows Server 2003 R2, Windows Vista, and Windows Server 2008.

<84> Section 3.2.7: Windows RSM Remote Protocol servers register with the operating system to receive notifications of changes to the storage devices.

<85> Section 5: On Windows Server 2003, Windows Vista and Windows Server 2008, BUILTIN\Administrators on RSM servers will have access to all RSM objects no matter what the access control list indicates.

 
Show:
© 2014 Microsoft