Understanding the process
The Windows service HNKTConversionService running on the Hyper.Net Transformation Server is responsible for completing each transformation request placed in the Hyper.Net Request Queue. This service selects the next transformation request, deposits the source file onto the hard disk and performs the required transformations. But you might ask: How does Hyper.Net know which transformation to execute? What if the transformation should be different for different files (Word, Excel, etc.)? The answer is: the HNKTConversionService reads this information from the hypernetconfig.xml. Hyper.Net then calls the appropriate built-in transformation code to create the result defined in the configuration. So, although the hypernetconfig.xml file is not actually executed, you can think of it as a sequential listing of actions that are to take place for any given conversion. In the case of metadata stamping, the task shown in the image above is "executed". You need only configure this task to meet your needs.