2009-09-29 01:38 PM
We have a customer that wishes to package the Management console (v3.8) for internal deployment, can they just use the nmconsole-setup-2-3-win32.exe file or do I need any other config type files?
Solved! SEE THE SOLUTION
2009-09-29 02:53 PM
I'm a customer who packages the NMC for internal deployment.
Technically the exe file is all you need.
I make some customizations in terms of default ports I use for communication between the NMC and the DFM server.
So as part of my package I include a config.xml file which defines the protocol and port that the NMC will use by default (this saves someone having to set this manually first time). The install location of the config.xml file will vary by platform.
Example of config.xml file is attached to this post as it didn't make the first post response I made via email (the port number shown, 4321, is just an example):
For any of the DFM engineers reading this thread can we start getting these packages as MSI format and not the legacy setup.exe format?
Also can we get an option added in DFM that prevents users from downloading the NMC client from within the Operations Manager GUI?
2009-09-30 09:50 AM
> Also can we get an option added in DFM that prevents users from downloading the NMC client from within the Operations Manager GUI?
A workaround is to move the install files out of their current location - <dfm-install-dir>/web/clients.
# mkdir clients-bak
# mv clients/* clients-bak/
This will make the link to download the clients disappear from the OM UI. The page will still be there, but with no links.