3.1.4.14.1 ExportConglomeration (Opnum 3)

This method is called by a client to export a conglomeration to an installer package file.

 HRESULT ExportConglomeration(
   [in] GUID* pConglomerationIdentifier,
   [in] LPCWSTR pwszInstallerPackage,
   [in] LPCWSTR pwszReserved,
   [in] DWORD dwFlags
 );

pConglomerationIdentifier: The conglomeration identifier of a conglomeration on the server.

pwszInstallerPackage: A path in UNC that is to be used as the location for the server to create an installer package file.

pwszReserved:  MUST be an empty (zero-length) string.

dwFlags:  MUST be a combination of zero or more of the following flags.

Flag	Meaning
fEXPORT_OVERWRITE 0x00000001	The server SHOULD mark the installer package file with a directive that existing files be overwritten on import (section 3.1.4.12.1).
fEXPORT_WITHUSERS 0x00000010	The server SHOULD include user account information in the installer package file.
fEXPORT_PROXY 0x00000020	The server SHOULD mark the exported conglomeration as a proxy conglomeration by setting the IsProxyApp property to TRUE (0x00000001).
fEXPORT_CATVER300 0x00000080	The server SHOULD only include configuration that is defined in catalog version 3.00.

Return Values: This method MUST return S_OK (0x00000000) on success, and a failure result, as specified in [MS-ERREF] section 2.1, on failure. All failure results MUST be treated identically.

Return value/code	Description
0x00000000 S_OK	The call was successful.

Upon receiving a call to this method, the server MUST verify that catalog version negotiation has been performed by checking the negotiated catalog version (as specified in section 3.1.1.5), and fail the call if not.

The server MUST then attempt to perform an implementation-specific<341>export procedure that creates an installer package file that the server will recognize. This document does not specify the contents of this file, except that it SHOULD contain enough information to make round-trip consistent import (see section 3.1.4.12.1) possible.