You are asked to clone your Juniper Mist primary site configuration to use for a...

The Clone Site feature in the Juniper Mist dashboard is a powerful tool designed to streamline the deployment of new physical locations by duplicating the environmental and operational logic of an existing "gold standard" site. However, to avoid configuration conflicts (such as duplicate addresses) and to maintain the integrity of the hierarchy, Mist is selective about which objects are carried over during the cloning process.

According to Juniper Mist documentation, only the settings visible on the Site Configuration page are copied to the new site. This specifically includes:

Auto Firmware Upgrade settings (A): The specific versioning (Production vs. RC) and the weekly or daily maintenance windows defined for the site are preserved. This ensures that the new site follows the same lifecycle management policy as the primary site.

RF Templates (B): The radio resource management (RRM) profile assigned to the site is copied. This includes channel planning, bandwidth settings (20/40/80 MHz), and power level constraints tailored for that environment.

Other Site-Level Settings: This also includes Webhooks, Rogue/Honeypot AP detection rules, and Location Services settings.

Conversely, certain objects are explicitly not copied. The Site Location (C) and Site Name are excluded because each site must be geographically unique for accurate mapping and time zone calculation. WLANs (D) are also not copied through the Clone Site function; SSIDs are typically managed at the Organization level via WLAN Templates, which are then mapped to sites or site groups rather than being "hardcoded" into an individual site's local configuration. By cloning the site-specific parameters like RF templates and upgrade schedules, Mist allows administrators to rapidly scale their infrastructure while ensuring the core network access (WLANs) is maintained through the overarching organizational policy.