β05-17-2011 05:56 AM
I'm evaluating (test environment) the DLOCommandu option to update the agent for DLO.
I've managed to get it to work from an installation point of view but it seems that if I use a remote sql server or rather not the DLO instance, that information don't seem to be updated correctly on the client.
E.g. if I use a remote sql server called "SQL" and the default SQL Instance (meaning no other instances) the registry states DBServer = SQL, DBInstance = DLO
With the standard setup you have arguments in the setup.ini that states the different settings but haven't found similar info in regard to the agent update through dlocommandu.
So is there any way to get the dlo agent update to not use DLO as instance name without having to fix the registry key afterwards ?
This was tested going from 6.1 MP4 to 6.1 MP6