Administrator SDK: OEMExtension member function and COM class enhancements.
The OEMExtension of the DSH_PrebootConfigurations COM class is an integer value defaulting to 1. There is no way to create any user defined OEM extensions with this member declared this way.
A new build of the ASDK for Deployment Solution 7.1 SP1a MR1 is now available with the following enhancements:
- The OEMExtension member in the DSH_PrebootConfiguration was changed from an integer to a string. This allows users to have their own "named" OEM extension.
- DSH_OEMExtension and DSOH_OEMExtension helper classes (COM classes) were added for ease of use in creating the XML needed for RunDeploymentServer and parsing the information returned.
If you have a need for this updated functionality, a copy of this new build can be found attached to this article. The attached file is a replacement for the Deployment Solution component of the Administrator SDK only.
Note: This build of the ASDK will only work with Deployment Solution 7.1 SP1a MR1 and no other versions of Deployment Solution. Future full releases of the ASDK will also contain these changes.
Before installing the attached MSI you must first remove the previous installation. If you do not do this, then it will leave your registry in an unstable state, as regards to this product, and you may not be able to remove it without an additional tool such as MSIZAP or other registry cleaner. You can download the attached files and unzip them to a known location.
The MSI file, Symantec_ASDK_DS_COM_x64.msi, will normally be located in the Symantec installation folder,
|%ProgramFiles%\Altiris\Symantec Installation Manager\Installs\Altiris|
You must run the following from a command shell from that folder:
call msiexec /x Symantec_ASDK_DS_COM_x64.msi skipaim=true /passive
call msiexec /x Symantec_ASDK_DS_Server_X64.msi skipaim=true /passive
call msiexec /x Symantec_ASDK_DOCS_X64.msi skipaim=true /passive
Then from the location where you downloaded/placed the unzipped file you can install the new MSI with the following command:
call msiexec /i Symantec_ASDK_DS_COM_7_1_sp2_x64.msi skipaim=true
call msiexec /i Symantec_ASDK_DS_Server_7_1_sp2_x64.msi skipaim=true
call msiexec /i Symantec_ASDK_DOCS_7_1_sp2_x64.msi skipaim=true
Once this is done, then the update to the DS ASDK component should be installed.
There are additional files attached to this article. The documentation file, Symantec_ASDK_Docs_7_1_sp2_x64.rar, which contains the updated information regarding these OEMExtension classes, the Symantec_ASDK_DS_COM_7_1_sp2_x86.rar for those who are developing scripts on a 32 bit system, and the Symantec_ASDK_DS_Server_7_1_sp2_x64.rar file that contains the updated DS DLL.. The same removal/installation process as described above must be used.
The Docs and Server files should only be installed on the SMP machine. The x86 COM file would only be installed on a separate 32 bit system.