1. Generate a Windows Installer file which contains the *.cmdtx file, and UX files. The Windows Installer file will be responsible for installing the UX files in the correct locations, using the standards defined by the Admin Console team. Basically, this will involve including the following files:

   1. UX Assembly, e.g. AdminUI.DeploymentType.<AssemblySuffix>.dll
      
      This file is required and contains the UX implementation, which is then bound to the Configuration Manager console using the below XML files.
      
      The Installer should copy this file to sms\AdminConsole\bin.
      
      
   2. CreateApp_<TechnologyID>.xml
      
      This file is required and provides the console extension for the Create Application Wizard.
      
      The Installer should copy this file to sms\AdminConsole\XmlStorage\Extensions\Forms.
      
      
   3. CreateDeploymentWizard_<TechnologyID>.xml
      
      This file is required and provides the console extension for the Create Deployment Type Wizard.
      
      The Installer should copy this file to sms\AdminConsole\XmlStorage\Extensions\Forms.
      
      
   4. <TechnologyID>DeploymentTypePropertySheet.xml
      
      This file is required and provides the Deployment Type property page.
      
      The Installer should copy this file to sms\AdminConsole\XmlStorage\Forms.
      
       
      
      

2. The Windows Installer file should contain code to invoke the DeploymentTypeExtender.Extend method, which is located in the Microsoft.ConfigurationManagement.ApplicationManagement namespace. This will then register the extension files for a given site server computer. For an administrator console computer, this will initialize the cache for that user. The Extend method call requires the *.cmdtx file created earlier.

   1. Make a standard WqlConnectionManager connection to the site server.
      
      
   2. Call the Extend method, passing the *cmdtx file, the ConnectionManagerBase object through an instance of ConsoleDcmConnection for the method connection parameter, and the connection path (example below).
      
      

   Warning
   In order to use ConsoleDcmConnection, you will need to add an assembly reference to AdminUI.DcmObjectWrapper.dll.

   	Copy Code
   using DCM = Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement; [...] ConnectionManagerBase connectionManager = new WqlConnectionManager(); connectionManager.Connect("SiteServerName"); DeploymentTypeExtender.Extend(@"C:\RdpTechnology.cmdtx", new DCM.ConsoleDcmConnection(connectionManager, null), @"\\SiteServerName\root\sms\site_ABC");

3. Client Installation (HandlerApplication.zip)

   To install the client extension files, either as part of the HandlerApplication or as a separate installation:

   1. Compile the AppSynclet MOF file. On the client, compile the custom synclet MOF file to create the necessary instance of the CCM_AppHandler class and the corresponding instances of the CCM_HandlerSynclet classes.
      
      

      	Copy Code
      C:\> mofcomp appsynclet_<technologyid>

   2. Copy the handler .dll to the Configuration Manager client directory and register the .dll on the system.
      
      

      	Copy Code
      C:\> regsvr32 <technologyid>handler.dll

   Note
   The handler .dll must be compiled to match the operating system – either 32-bit or 64-bit.

Namespaces

Assemblies

Concepts