Re: Exchange 2007 on new Win2008x64 Hyper-v won't install...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



In the context of UAC, 'Run As Administrator' is actually just requesting elevated privileges for your current account (assuming it's in the local administrators group). So the Install is *still* running under whatever account you logged on with, but UAC prevents an account from exercising elevated priviledges without further prompting. That's what the 'Run As' menu item does.

Gaurhoth



Steve Jones wrote:
WOW.. That was exactly it... Why am I seemingly either the least observant person ever to have used Google, or the only person to have had this problem!!

It's odd - I would have thought that a local administrator (vs. a domain user/administrator) should be the LAST account to be used to install something like Exchange!!

Well, thanks so much!! I Should be well on the way now!

-Steve


"Gaurhoth" <gaurhoth.usenet@xxxxxxxxxxxx> wrote in message news:OQhD2UePJHA.4760@xxxxxxxxxxxxxxxxxxxxxxx
Steve,

Are you running SETUP from your install media/source 'As Administrator'? I found this necessary in Windows 2008. Doesn't seem exchange team included whatever flag/manifest is necessary for UAC prompt.

Just open the source media folder, right click on SETUP and choose 'Run As Administrator'.

Gaurhoth

Steve Jones wrote:
That file doesn't exist.. Even searching the entire C: drive, including hidden/system files.. I guess it's dying even before the logging is starting..


"Tony Brown" <TonyBrown@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B9FAD616-72FF-42F0-BA65-32D6A71B47CD@xxxxxxxxxxxxxxxx

Hi Steve,

there should be an exchangesetuplog in the root of the drive - can you
delete it - try running setup again, then post the contents of the file??

(deleting it just makes it easier to read - as it will contain all attempts
to install...)

thanks,

Tony Brown MCSE +M +S
www.phillipstaylorbrown.com

"Steve Jones" wrote:


Thanks for the response... Right after my post, I actually did copy the
whole source disk local just to exclude that as a problem... same result.

Looking at the link you provided (thanks!) I tried the "Setup
/PrepareLegacyExchangePermissions" and it gave me the same error in the
command prompt window, as what I got from the GUI before...: So, that
apparently is the cause of my problem... Still dont know the root cause, or
solution though.. According to:
http://technet.microsoft.com/en-us/library/aa997914(EXCHG.80).aspx that
command can be run on the server which will later run Exchange (which I
presume is what the setup is trying to do) but it fails on that machine and
on a new 2008 DC I installed in the domain. I also tried, just to make
sure, on a 2003 DC, and was told that the app wasn't compatible w/ that OS
(presumably, it's x64 I guess)..

Any idea why that would fail?? It seems from the description, to be a
fairly straight forward rights modification process..

-Steve





"Tony Brown" <TonyBrown@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C7009195-CAAA-41EF-8EA7-CE82C7B1E7AA@xxxxxxxxxxxxxxxx

Hi Steve,

I think the 'source' error is only referring to the event log.... I don't
think it's referring to the install source - but copy the whole CD to the
c:
drive anyway just to be sure....

Have you done the domain preps?

http://blogs.technet.com/ucedsg/archive/2008/09/29/exchange-2007-and-windows-2008-ad.aspx

Tony Brown MCSE +M +S
www.phillipstaylorbrown.com

"Steve Jones" wrote:


I've got a lab (aka: home) with an established Win2k3 / Exchange 2k3
environment that's working fine.

I installed a brand new server for 2008x64 (AMD x64 Quad-core with 6
gigs
RAM) and have sucessfully moved a couple pre-existing VMs over to the
Hyper-V environment, but now I'm trying to create a new Exchange 2007
server...

The server comes up fine, and I did get through the prerequisites as
listed
on the setup wizard. I also found reference to turning on remote
administrative roles, which I did. I am logged in as a domain admin, but
when I try to hit "step 4: Install Microsoft Exchange", it starts, then
quickly tells me:

"Setup Failed due to insufficient permissions. Please make sure the
current
user has local administrator permissions. Error: The source was not
found, but some or all event logs could not be searched. Inaccessible
log:
Security."

Even though it makes no sense, I put my domain account in the local
administrators group, and I have made sure I can get to the security
event
log. I'm not sure what this thing is trying to tell me.. Regarding
"Source
not found", I have the install media mounted virtually from an ISO, but
it
seems to be reading it fine..

Anyone have a clue what this could be? I can't believe I'm having this
problem, and haven't seen anyone else post about it!!

Thanks in advance!

-Steve Jones







.



Relevant Pages

  • Re: how to disable reset password in Administrator account
    ... there are about 4 ways to change an account password ... backup set a deny permission on his administrator account for the ... > reset the local administrator password, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Group Policy Lofon Script
    ... corporate LAN, so during initial setup, a network cable was connected. ... After setup was complete, the 'secret' administrator ... account was enabled, the LAN's administrator account was ... with the username in the username@domainname syntax. ...
    (microsoft.public.windows.server.sbs)
  • RE: Change in installation procedure -- Why?
    ... You get the administrator logon if no other accounts are created during ... Since that is the only account you are prompted for administrator to ... You can also get this if you join a domain during setup. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: security account login failed
    ... local administrator attempting access to a domain-authenticated resource ... All user using their domain user account to connect the network, ... this on a DC event log or a local event log? ...
    (microsoft.public.windows.server.security)
  • Re: LOG IN
    ... So to logon, use the username: Administrator ... account and create new accounts for your daily use. ... >I RE-LOADED WINDOWS 2000 AFTER RE-FORMATING MY C DIVE DUE TO A VIRUS IN IT. ... I HAVE NOT SETUP ANY USER ...
    (microsoft.public.win2000.new_user)