Setting your Demo PC as a Named device is the LF recommended method of handling the named license assignment.  They normally say to assign a license to the device and to your administrative user(s).

This would then allow your administrative users up to 4 concurrent connections each and leaves you with 8 concurrent connections for all other users to share.

Yep--giving the machine a Named Device license solves just about everything. The exception to this rule is the licensing for Forms. Forms doesn't see Named Device licenses, so each Forms user will need a Named User license.

We build most of our Forms demos around one user (who may be assigned multiple tasks, or represent multiple people), which helps reduce the amount of logging in and out we need to do. It also keeps the number of required licenses very low. 

Thanks for the feedback! I'm looking into possible updates to the current Kit definitions right now so that workarounds like those mentioned above don't need to basically become requirements of running demos. We're still working our way through different possibilities, but we are definitely aware of the current concerns with the provided number of users and I'm hoping to address that.

We could use additional licenses as well.

Also, the ability to test restricted user licenses through the VAR kit.

Great feedback, but as Justin said, these are excellent workarounds for a problem that can be solved easily via other means.  In our case, we use SSD Drives which generate a speedy and crisp demo, but do not have as much space as HDDs.  That knocks VM's out of the running.  Also, for approvals and security, we like to show the different users all logged in at the same time, so items can flow from one to another in a way that is close to what the real users would see.  We don't like to do a lot of task switching, as we generally have enough to be thinking about.  So, Justin, upping that limit will be very nice - do we need to send anyone chocolate or other goodies to make that happen?