Our deployments are engineered by a centralized Dev Shop and pushed out to various sites. The required infrastructure will include multiple FlexNet Publisher sites each having their own Product Keys. With this in mind how can the use of the embedded FlexNet .Net code utilize an external IdentityClient.cs file so that the identity of the deployment isn't bound to one specific FlexNet Publisher? The deployment payload encapsulates the product source which includes the code used to query the FlexNet Publisher for updates so we need a method for not binding the IdentityClient.cs for one specific Publisher site. How can this been done?