With more companies from different industries getting started with OPC UA and time pressure in their release we experience oversights in the release process of such products. In several cases we have noticed SDK artefacts still being present in the products. Examples for such artefacts are:

• Demo Address Space Nodes
• SDK Username/Password combinations
• BuildInformation not updated

Possible test strategies to identify such cases are:
Demo Address Space Nodes
Check the namespace array for listing of known SDK Demo Namespaces. If they are present and the Manufacturer and ApplicationUri does not match the information of a known SDK we print a Warning and indicate it may be a left over.
SDK Username/Password combinations
Create a list of known username/password combinations from SDK vendors and try to activate the session with it. Remember to use a valid username/password combination every 3rd attempt to ensure we are not blocked out/delayed from a brut force protection.
Build Information not updated
Check if the build information match known information from SDKs.

Create a setting called "SDK Product" in the Advanced section which will then omit all the SDK artefact checks.