Since migrating to OMW 9 (Win2008R2) from OMW 8 (Win2003) it seems the ovownodeutil.cmd command takes awhile to run.
I'm just running the .cmd without any parameters and it takes roughly 30 seconds to respond back.
When I execute this on my old OMW 8, it responds back immediately.
I've seen articles indicating it might be db performance but without any parameters there should be no db lookup.
I've run SQL profiler and see no activity.
I've even copied the binaries between the two systems. The same binaries always run faster on the Win2003/OMW8 combination.
It looks like there is a big signature block at the end of the ovownodeutil.vbs and cmdutilscommon.vbs
Seems if I delete this signature block from the vbs script everything runs quickly.
odd that it's impacted the script.
Good you found the cause. when you run a signed script, the sign should be verified by windows script host - and this is done with verisign, inc usually, unless you have a certificate validation authority (system) within your network.
Now, if your OM server is in a network without access to www, then the certificate validation is still attempted, but it will fail to work. The timeout is what causes the delay in the script run. all vbscripts shipped with OM/OA will run delayed.
you can turn off signature verification at your system level. that would speed up things.
PS: in the next release of the OM agent, we will provide you the option to remove the sign from the scripts for the OM agent. This will help to speed up OM agent installs.