wait for a minute then you will see in your notification area that it is installed

or follow this site for more instructions
http://portal.sivarajan.com/2010/05/installing-forefront-client-security.html

Good question, I’d be pretty sure that it is smart enough to do the autodetect.

J.Ja

nucrash :

I think an easier lesson would be to just setup users as “users” by default. Unfortunately every admin I know still uses the default for setting up new users. This gets to be even more exciting on Novell Networks.

My biggest issue is that I shouldn’t have this problem. I tried to combat this years ago and was swatted down by other admins saying that trying to have users run as users was simply too difficult.

Setting up users as non-admin by default is easy, it’s the default. Where it becomes a hassle, is when every 10 minutes they need an admin to install an application. It’s a cultural issue that is very difficult to address.

J.Ja

My biggest issue is that I shouldn’t have this problem. I tried to combat this years ago and was swatted down by other admins saying that trying to have users run as users was simply too difficult.

Dietrich Schmitz :

Bad analogy because nobody hands out the root password on Unix, GNU/Linux systems, unless they plan on being summarily dismissed.

You delegate via sudo to individuals for select tasks or with group membership but not handing over root.

Sorry, you argument doesn’t hold water.

Sorry, but you are failing to see my point. I am not saying that anyone would hand out the root password on *Nix. I agree, it’s INSANE. What I *am* saying, is that due to decisions made by some application developers, their applications require full administrative privs to work. So, for these applications to be used, you have to perform the equivalent of giving the root account to users (the “Administrator” user does not have any special privs that putting someone in the “Administrators” group does not).

Once again, this is not a defect in Windows, it is a defect in the applications. Too many of them demand full privs, even if they do not actually need them, in order to operate.

I may add, the UAC system is similar (by no means identical) to sudo in that it requests permission on a per-task basis.

At this point, I am not making any kind of arguement. I am simply laying out some facts for you, since you do not seem to understand the full scope of the problem. It is simple to go along with the “common sense” that the Windows architecture is all wrong. And yes, there are some underlying issues with it, like the backdoors that exist for “Genuine Windows Validation” to work. But to say, “gee, the existence of viruses and security holes on Windows shows that it is a piece of junk” is foolish. Mac OSX is riddled with security holes, depite being built on top of BSD, which is a well regarded system when it comes to security. Every OS has its problems. The big problem with Windows at this time, is that application developers keep working like it’s 1989 or 1999, not 2009, and write code that acts like it owns the system. As a result, users often end up in a position to own the system, because it’s the only way to usefully use certain applications. That being said, UAC has proven to be such an impediment to using these application without breaking into tears, that it has finally forced application developers to follow the rules that were in place but unenforced for over 10 years.

J.Ja

You delegate via sudo to individuals for select tasks or with group membership but not handing over root.

Sorry, you argument doesn’t hold water.