UAC and ALL these problems...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I realize how much MS wants to prevent malware, phishing, etc, but...
There MUST be another way. Everything security related in Beta2 and from
what I've read in these newsgroups, and MSDN Blogs -- are just totally
UNACCEPTABLE.
I'm an experienced user/programmer, and even I am about to give up on Vista
totally!

Surely there must be a way for the OS to tell whether 'the action taken'
(driver, program, installs, moving files, etc) comes from the locally logged
on user OR from over the network?

Just my 2cents, but I believe MS developers need to back up, look at the BIG
picture, and re-think their plan!

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://windowshelp.microsoft.com/co...d2&dg=microsoft.public.windows.vista.security
 
At the moment it seems that it works oddly but you can surely disable the
questions if you want. Personally i think they will change the behaviour of
the action. At this point its crucial to test how its triggered and how its
affecting usage.
 
Have you ever used any operating systems than from Microsoft? This security
model is the way most modern OSs work. I use Vista Beta 2 as a standard user
with UAC turned on. I am connected to a domain. I get a UAC prompt to run a
vbs script when logging in to the domain. I could probably fix this but
haven't had time. That's pretty much it for UAC during normal daily use
which consists of Office 2007 beta use, Expressions Web Design Beta use, and
Windows Mail for newsgroup access. In other words pretty much what a
standard user would do - office type applications and Internet use. I have
purposely limited my use of older apps that don't take the new security
features into account. If I need to do any maintenance I log on to an
administrator account with UAC disabled. Are your problems with the programs
you develop or with normal use of Vista? You may need to learn a new way of
programming for this security model. Look to open source for examples. If
it's just a problem during normal use then it may be the programs you are
using. As programs are updated to take account of the new security model
these types of problems should go away. It will be a pain in the a%& until
this happens but this doesn't mean we should abandon security to make legacy
apps run. That is one of the reasons why previous MS OSs have so many
security problems.
 
Have you ever used any operating systems than from Microsoft? This
security model is the way most modern OSs work.
Click to expand...

Not quite. I've seen (or heard of) an equivilant to UAC in Mac OS X or any
POSIX type (Linux, Unix, BSD....) OS. What a lot of them use is "Sudo"
(Superuser Do - superuser being the "root" or "administrator" account. You
get a box popping up (or a question at the command prompt) asking you for
your password. It's basically a way of telling you that "You're about to
possibly screw things up of you do this - beware". And for the time you're
doing whatever it is your doing (usually just one single command) you have
Root/Administrator privlidges (sometimes it lasts for 15 minutes if you want
to go back an do something else in a few.

On a user account in Vista, you do get this same type of thing (Which
thrills me to no end - it's long overdue). The problem is, MS takes it a
steep further with that UAC dialog box. It's overkill for an administrator
to be getting that, expecially if they had just entered their passord in
order to have access to the program.


......I log on to an administrator account with UAC disabled.
Click to expand...

I'm still trying to figure out how to disable UAC....
 
Scott said:
Not quite. I've seen (or heard of) an equivilant to UAC in Mac OS X
or any POSIX type (Linux, Unix, BSD....) OS. What a lot of them use
is "Sudo" (Superuser Do - superuser being the "root" or
"administrator" account. You get a box popping up (or a question at
the command prompt) asking you for your password. It's basically a
way of telling you that "You're about to possibly screw things up of
you do this - beware". And for the time you're doing whatever it is
your doing (usually just one single command) you have
Root/Administrator privlidges (sometimes it lasts for 15 minutes if
you want to go back an do something else in a few.
On a user account in Vista, you do get this same type of thing (Which
thrills me to no end - it's long overdue). The problem is, MS takes
it a steep further with that UAC dialog box. It's overkill for an
administrator to be getting that, expecially if they had just entered
their passord in order to have access to the program.




I'm still trying to figure out how to disable UAC....
Click to expand...

To find out how to disable UAC try Google. There are several ways to do it.

http://www.google.com/search?hl=en&q=vista+disable+uac&btnG=Google+Search
 
It's done in the user manager. :)

Scott said:
Not quite. I've seen (or heard of) an equivilant to UAC in Mac OS X or any
POSIX type (Linux, Unix, BSD....) OS. What a lot of them use is "Sudo"
(Superuser Do - superuser being the "root" or "administrator" account. You
get a box popping up (or a question at the command prompt) asking you for
your password. It's basically a way of telling you that "You're about to
possibly screw things up of you do this - beware". And for the time you're
doing whatever it is your doing (usually just one single command) you have
Root/Administrator privlidges (sometimes it lasts for 15 minutes if you want
to go back an do something else in a few.

On a user account in Vista, you do get this same type of thing (Which
thrills me to no end - it's long overdue). The problem is, MS takes it a
steep further with that UAC dialog box. It's overkill for an administrator
to be getting that, expecially if they had just entered their passord in
order to have access to the program.




I'm still trying to figure out how to disable UAC....
Click to expand...
 
Back
Top