# Administration notes

Normal use: copy public key from admin unit:

- should be static, e.g. not a mobile unit unless you are a roaming repair guy (see DeNiro in "Brazil")
- should have large antenna to join distant nodes directly, without hops
- can be in client mode, not client mute
- public key is generated FROM private key, so is unit dependent

<div id="bkmrk-except">EXCEPT</div><div id="bkmrk-it-is-possible-to-co">

- It is possible to copy a private key from one admin unit to another, then generate a new "cloned" public key

<div>n.b.</div></div><div id="bkmrk-channels-cannot-%28so-">

- channels cannot (so far) be remotely administered
- changes in role may be contested (e.g. moving to/from router may balk)
- wait at least a minute before trying to change settings on a remote unit
- best practice: add your three admin public keys to all machines, once added locally, you can then remotely admin these
- chrome app only allows one admin key, iOS allows three, python allows three (at least)
- be careful to check config both by the admin screens and by looking at local meshsense maps to confirm config changes

</div>---

<small>Migrated from Apple Server Wiki. Original page ID: b4o5M77</small>