Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey
Launch to Device does not work for NMC 1 devices on the DCE private network
DCE FAQ
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
In DCE 7.9.0 and newer, the Launch to Device option does not work for NMC 1 devices that use HTTPS on the DCE private network.
Connect a computer to the DCE private network to directly access the device's web user interface.
NMC 1 does not support SSL protocols more recent than TLS 1.0. Updated security policies introduced in DCE 7.9.0 do not include TLS 1.0. The option to choose between TLS versions was removed from DCE for security reasons.
Sensor information, alarms, alarm notification, graphing, etc. for NMC 1 devices are not affected since they do not rely on web functionality.
This applies to devices with NMC 1 (AP9617, AP9618, AP9619) and devices with an embedded NMC 1 including, but not limited to: Metered/Switched Rack PDUs (AP78XX, AP79XX); Rack Automatic Transfer Switches (AP77XX); Environmental Monitoring Units (AP9320, AP9340, NetBotz 200).