Arsen; Unless you use "Inherit from Site", you can only Stage ONE Bundle during Staging.  If you choose to specify "Content - Site" as the Staging Bundle, then you cannot deploy anything other than that Production Site Bundle during Staging.  If you use "Inherit from Site", then you can use both a User Defined Staging Bundle AND a Production Site Bundle. There are several goals that were intended to be met by using "Inherit from Site". First, it allows you to reduce the number of Staging Profiles when you have many Staging Sites and you want to have different Settings applied per Staging Site.  For example: if each Staging Site uses different WLAN Settings, you would need to create a Staging Profile for each Staging Site if you were going to specify the WLAN Settings IN the Staging Profile.  But by specifying the WLAN Settings in the Staging Site, a single Staging Profile can inherit the WLAN Settings from the Staging Site.  This can be especially important since there is no way to bulk create Staging Profiles, but there IS a way to bulk create Settings and Sites.  Note also that you can inheirt other types of Settings besides just WLAN Settings and Relay Server Settings from a Staging Site, and they all go into the Staging Profile. Second, it allows you to deploy two Bundles in one Staging Profile.  This is primarily intended to be used when Staging at one Site (a Staging Site) for use at another Site (a Production Site).  In such a scenario, you generally need Staging Settings that get the device onto a Staging network and in contact with a Staging Relay Server, from which the Staging Bundle will be pulled.  Once the Staging Bundle has been pulled and completely processed, then if the Staging Profile inherits from a Production Site, then it will ALSO pull the Production Site Bundle for the Production Site from the Staging Relay Server over the Staging network.  This only makes sense to do at the very end since the Production Site Bundle may have new Production network Settings and Production Relay Server Settings.  Applying the Production Site Bundle may well cause the device to drop off the network and stay off until it arrives at the Production Site.  Note also that you can inheirt other types of Settings besides just WLAN Settings and Relay Server Settings from a Production Site, and they all go into the Production Site Bundle. As for not "having control of" the Production Site Bundle, you have indirect, limited control over it.  MSP creates the Production Site Bundle automatically for every Production Site and you cannot directly control its content.  You cannot put software into a Production Site Bundle, period.  But all Settings in a Production Site go into the Production Site Bundle, so you can elect to put more Settings into the Production Site Bundle, if you choose.  All such Settings will get applied when the Production Site Bundle is pulled at the end of Staging. Allan

Alan, thanks for detailed answer. Still, one thing remains unclear: the "Content - Site" option seems redundant. Is there a scenario where one would prefer pulling "Content-Site" bundle instead of Production Site inheritance?

Arsen; The "Content - Site" option is really not intended for Staging, since to use that, you would have to ONLY Stage a Production Site Bundle and nothing else, which is seldom the case.  The The "Content - Site" option is most commonly used to PUSH a Production Site Bundle to devices, such as to change Sites or send down updates to a Site, not to PULL Site information. Allan

Arsen; If a Staging Profile uses the Inherit from Sites option and specifies a Production Site, then the Production Site Bundle for that Production Site will be pulled by the device as the very last step of Staging.  This is done at the very end because the Production Site Bundle may contain Settings that don't apply at the place where the device is being Staged and thst would interfere with Staging if they were done ealier.  The intent is that once the Production Site Bundle has been pulled and processed by the device, the device is ready for operation at that Production Site. It is also possible to push a Production Site Bundle through Provisioning, which is when Content - Site would be used. Allan

So, in a way it means that I can stage two bundles during the staging operation, even though I have control only over one of them (User Defined). Right? If so, what is the practical difference between

a) using "Inherit from Site" and specifying Production Site
b) using "Content - Site" to specify the same production site?

(except that the site settings will be applied at different steps of staging)?