You searched for the word(s):
< 1 second(s)
Commvault couldn't use that IP if it would adher to what Windows defines. You may bind your Service to it, but by the routing defintion you would never use it to talk to any other System in our Env, either you go f.E. 172.27.29.x via the primary NIC, or you go to Default Gateway via primary NIC.
PS C:\windows\system32> route ...
Version of JDK doesn't matter for the executing JRE side, as long as the required VersionLevel is supported it should run.
Was able to load SP18 Console with an netx.jar from SP14, is is somewhat cross-compatible. Still not sure how to ensure Admin and Customer use the latest Version of it to get the rest of the Console. netx.jar does have bugs on ...
Tried out netx.jar back with SP14 and now downloaded new one for SP18 since it doesn't seem to have an update-feature for the jar itself (yet). Any suggestion on how to keep that up to date on the Clients?
Found that I have two Folders ''Commcell Console'' and ''CommCell_Console'' with a total of about 2.1GB in my User-Profile now, one ...
Excelent hint, that should work for the time beeing.
Unfortunately that will break function once we switch to dedicated backend storage network. Wish Commvault would simply stick with the routing defined on OS level and not try to be clever and re-invent the wheel over again by making it square.
The 169.x.x.x Addresses are also by definition ...