Weber Endpoints

Caveats on the use of machines as Weber Endpoints

The use of Weber comes with a huge policy overhead. These are not technical restrictions, but they hinder one's ability to use a computer in the manner that one might be used to.

Some such "GOTCHA!'s are listed below.

• At ANY time: No admin, localadmin, VMs with admin, or any kind of administrative access.

While the WeberVPN is active:

• No RDP so these machines need local keyboard/mouse/video access
• No network-licensed software available
• No mapped network drives available
• No onedrive/Box/equivalent
• No webex/zoom/skype/teams/jabber soft client for phones
• No screen sharing software (Teamviewer, VNC, etc)

Other caveats:

• Operating system must be up to date – machines must be online and check in at least once a week, and, the machines may be redeployed/reimaged if standard updates and/or upgrades do not work (eg 1809 to 1909)
•  If server class machine, consider purchasing with an enterprise LOM/iDrac style module
• If non server class, consider purchasing a very low cost, low powered desktop for use only with Weber. Attempting to use such a machine for "normal" every day tasks can be incredibly frustrating.

Please read the Export Controls Office's Guidelines for Weber Endpoints, version 11/10/2020 - this can be obtained after logging in here