Although I agree about being consistent, I completely disagree about using the registry and GPO to administer Revit. As I'm not the Network Administrator, I don't manage our company's GPO, nor should I. I do however create the Revit.ini file which easily sets the few settings I need to be distributed once installed.
By using the Registry I'll end up having to do weird registry hacks to get the deployment correct, like I have to do with AutoCAD. Our users are not administrators on their machines and so therefore don't do their own installs. Since the Network Admin logs in to install the products, non of the AutoCAD registry settings are assigned to the user that actually uses that machine (hence the registry hacks).
Also, with the INI file I can quickly reset the settings of the workstation and any users back to the company standard just by deleting and copy/pasting the INI file. With the registry I'd need to delete those keys in the registry directly. Here's where that sucks even more, if the non-admin user is logged in, they CAN'T edit the registry to fix those settings. If I login, then, to fix the registery, only MY settings would be reset, since I'm then the Current User of that workstation.
I hate the way AutoCAD installs now and I'd NEVER, EVER, want Revit to go that route!!