Owner's Manual

Issue 2:

You cannot launch the Dell Discovery utility from a network share - (354368).

Workaround:

You must modify the .Net security policy in order to run the application from anetwork share. For more

information, see

http://support.microsoft.com/kb/897296.

Additional Information

Security Consideration For Dell Discovery Utility

When you run Dell Discovery utility on any system, to discover the MD storage arrays, there is a delay of 40-45 seconds to

launch the utility if the system does not have access to the Internet. The delay occurs because in the .NET Framework 2.0,

when the CLR loads an assembly into a process, if the CLR finds an Authenticode signature (which involves a Certificate), it

generates Publisher Evidence from it and validates the Certificate by contacting the issuing authority to ensure the

Certificate has not been revoked. When validating the Certificate the operating system scans the chain of Certificates and

tries to download the Certificate Revocation List from a server on the internet. If you do not have internet access or

network is too slow, then this process is delayed - thereby delaying start of the application.

NOTE:

When you disable signature verification, the .NET Framework 2.0 managed application no longer receives publisher

evidence. This behavior affects the.NET Framework 2.0 managed application only when you use publisher evidence or when

you use the PublisherIdentityPermission class.

To avoid the delay in launching the utility on a system without Internet access:

Open the DellDiscoveryUtility.exe.config file from the location where you have installed the Dell MD Storage

ArrayManagement Pack suite 5.0.

Set the value of <generatePublisherEvidence enabled="True"/> to "False".

For more information, see

http://support.microsoft.com/kb/936707.

Non Responding MD Arrays Shown In OpsMgr

•

MD Storage arrays from OpsMgr Diagram view will disappear if MD Arrays stop responding. The OpsMgr console

displays a new alert provided by the Management Pack. You must take the corrective actions suggested in the

alert to ensure that the storage arrays that have disappeared from the console start responding in the subsequent

discovery cycles, and are displayed in the OpsMgr console.