Comment 1520 for bug 1

Revision history for this message
Dan Kegel (dank) wrote :

http://linux.slashdot.org/comments.pl?sid=2510526&cid=37956760
has a nice example use case for corporate deployment:

" A competent Windows admin can complete the tasks in about five minutes flat, across thousands of workstations:

- Change every users' browser proxy setting, and block them from changing the setting.
- Hide any control panel icon.
- Configure a printer for every workstation on a certain IP subnet, including the driver.
- Force the default desktop wallpaper, home page, and logon message to whatever corporate branding they came up with this month.
- Establish trust across every single server and workstation to a Certificate Authority public key.
- Disable wireless networking across all computers of a particular model. Even new ones that are added after this change is made.
- Configure wireless certificates and enterprise WiFi auth, including automatic certificate renewal.
- Deploy an application to every workstation, including powered off workstations. They're powered on overnight, install the software, and then shut down. Failed installs can be reported. New machines that are deployed later receive the package automatically on first boot.

Before you reply to this: I know. I know! I know Linux can do much of that. I know you know how to do it. The problem is that the 'solutions' are all spread across many inconsistent tools that almost always need scripting to use in a large environment. It takes a huge amount of knowledge to bring all of that together into a consistent whole."