Ok, you asked, so I'll tell you the one UAC issue that is bugging me right now: File sharing.
On XP members of both Power Users and Administrators can share folders on the network. The same appears to be true on Vista, but only if you create a custom MMC snap-in, as the 'Share...' context menu item insists that you must elevate to a full Administrator
account (both with and without the wizard). Is there any workaround for delegating the right to share folders to standard users, or at least to make the experience a little less odd for members of the Power User group?
The other (minor) annoyance is the way Journal bugs you to elevate to add the printer driver every time you start it until you finally let it. Grrr.
Overall though, the UAC implementation is really well done and I'd congratulate everyone who worked on it as you've done a great job of making my job (a sys admin) a whole lot easier!
Very interesting video. Having been involved in rolling out a similar environment without granting developers full administrative rights, it's certainly interesting to see how Microsoft deal with things.
MS should have moved the WinKernel from Ring0 to Ring1 in that onion. PatchGuard can then secure Ring1 Code. This way you get rid of the impracticality of securing code with same priviliage level that exist in Vista.
Nice idea, but it would have broken every bit of virtualisation software out there. It is the way they are going by introducing low-level virtualisation support and a hypervisor though.
Well nobody sounded even remotely like what I'd have imagined (well except Charles obviously), but cool video nonetheless. Could probably do the weekend of the 28th/29th too, assuming it's nowhere too remote.
I don't understnad if I have hardware that has a 5% utilization rate then just add more apps to this server instance itself - instead of loping off another x percent for the virtualization software to run an entire new instance of the OS?
Imagine you're running Exchange and a web server on the same machine. If a patch comes out for Exchange that requires a reboot, you have to take down the web server unnecessarily.
With virtual servers, you can keep separate applications in separate VMs, thus improving availability. Plus you know with absolute certainty that the Exchange patch won't break the web server since they are running on separate (albeit virtual) machines.
Printing to PDF is easy (there are already free solutions), the problem is that you lose a lot of information that way (hyperlinks, document flow etc) - this is something that can only really be added by native PDF support at the application level.
PDF support in Vista would be great, not sure we'll see it though (sadly)