I answered my own problem in another post, but to anyone that is having repeated problems installing Exchange 2007 SP1 on Windows Server 2008 because it doesn't have permission to write to its own setup logs there is a simple answer: Disable UAC and you will have no more problems. This one had me stumped for a while. *Note - to disable UAC, it is the same as in Vista: Go to Control Panel | Users, and it is an option in there.

You can also run MSCONFIG and go to theTools tab. Itsat the bottom. Just click an run.

Is there a CLI to do this?

UAC is a security feature that should be turned on.Run the setup program with "run as admiinistrator"lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

If you select "DISABLE UAC" in MSCONFIG, it will show you the CLI in the Bottom .....

UAC is a security feature that should be turned on . Run the setup program with "run as admiinistrator" lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com This is not always going to be the answer. Not everyone's needs for features and security are the same, hence the ability exists to turn it off. We have one 2008 server that we really struggled with, trying to fit all the functionality that we needed into the new UAC model/feature. Ultimately we had to disable UAC. Thankfully we all get to make these choices and of course live with any downsides that may exist (either way).

That is true that sometimes applications dont work ok with UAC, but Exchange is one application that do work ok with UAC turned on.lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Using administrator account is not a solution for a web application.

Ditto SQL Server Reporting Services. We are not able to utlize Report Manager role settings with groups when UAC is enabled even the individual users in the group are able to be view reports when assigned those priviledges. I was hoping Windows Server 2008 did not utilize UAC. I am disappointed that it does.Edward R. Joell MCSD MCDBA

Same applies with WMI. UAC screws that up completely!

I agree with rhuston, even the simple act of creating files when logged in as an administrator blocked. There are 2 work around, disable UAC or give "users" permissions to write since the administrator account is treated as a "user". Oddly enough, disabling UAC is the more secure solution.

I am moving lots of directories from 2003 to 2008. Getting permissions cleaned up and set correctly with UAC on is a pain in the arse. "There are 2 work around, disable UAC or give "users" permissions to write since the administrator account is treated as a "user". Oddly enough, disabling UAC is the more secure solution." Well said.

What a ridiculous response. As everyone as noted, UAC _HAS_ to be disabled. It is a security feature, but it is a BROKEN security feature. To work around the failure, it has to be disabled. Please don't answer with responses like this if you have no idea about the situation as it doesn't help anyone. Real-world situations require real-word answers, not "theory".