Subscribe

OnCommand Insight v7 staging Auto-updates to non-OCI server

Customer wants to stage OCIv7+ updates to be downloaded to a non-OCI Windows server then installed on OCI from that other server.  

OCI User Guides appear silent on this.  Anyone successfully configure this to work in lab or production environments or is staging always to OCI server?

Re: OnCommand Insight v7 staging Auto-updates to non-OCI server

If the goal is to download OCI files on one server, and then access them from the OCI server to install, that may work - User Authentication Control can get weird with remote files, so often the easiest thing to do in UAC environments is to copy the OCI binary locally, spawn a cmd prompt as Administrator, and launch the .msi from the admin-level cmd prompt , as anything spawned from the cmd prompt will inherit the admin level / UAC free rights (in theory - there are some Active Directory driven UAC configs that may cause more pain)

Re: OnCommand Insight v7 staging Auto-updates to non-OCI server

Matt,

Thank you, I will explore more in the Lab.

Bret