Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2007 issue

Status
Not open for further replies.

blade1000

IS-IT--Management
Mar 1, 2009
133
US
All-

During the initial install of Exchange 2k7 server, while running setup.com /ps or if I try setup.com /prepareAD.. I immediately get a return response with this ODD error below

c:/users/administrator/AppData/Local/Temp/1/default.htm error..

I have sure that this "path" does exist.. Full control to entire path is there as checked.. I am attempting to run this Exchange 2008 64 bit on a beefed up Windows 2008 64 bit server.

This is an Internet Explorer Script error..

Has anyone seen this at all during an Exchange 2k7 install?
I've run this install on previous projects before and never have I been stumped at the initial installation piece at cmd prompt running setup.exe. or setup.com.

I will stay here all night to figure it out, if anyone has any suggestions, please let me know..

thanks

blade
 
Pat-

Yes, running dcdiag I still have issues... its mind bending but am trying to work thru it..

the child DC is not seeing the root dc (schema).. odd rpc unavailable issues....

man, this is getting layers deep..

blade
 
You need to get AD right first before you start on Exchange otherwise you'll hit roadblocks downstream that you can't fix.
 
All here-

I haven't gotten back to anyone as I ended up using Hyper-V and restaged all my DC's and member servers which are fine. Now, the Exchange 2007 issues once again.

Yesterday evening I extended the schema, which resulted fine based on the return message from Windows (am running Windows 2000 64 bit Full install). I have an empty root DC and a member server in the root (which I am trying to install Exchange 2007 64 bit). So the schema is extended, I made sure that the local Admin acct is a member of the Schema and Enterprise groups, ran thru all the ServerManagerCmd's at cmd line (many of them for Exchange 2007 -got them from Petri's site where Pat created this nice doc) which executed nicely... tested a dcdiag on the forest root dc (which is also a gc), no errors.

So here is the Exchange install part: at the cmd prompt on the member server which is part of the root test domain, I run setup.exe (also tried setup.com /ps and PrepareAD) and it launches the Exchange 2007 gui, it finds .net and powershell installed nicely but then starts the pre analysis and once again -returns these three errors as before: 1) my account is "not a Windows acct" or "does not have proper permission for this install" 2) "Cannot contact a domain controller for this domain" 3)I forgot the actual wording of this error but revolved around the 2 above to some degree.

I made sure that on the member server contains the IP of my root dc is added to the nic since the root dc is a dns server (this is a test domain for the sole purpose to see Exchange actually install with no errors,

So... what am I missing, obviously it is the way I am installing it, or not prepping something correctly in my domain where Exchange's install fails...

If anyone has any ideas, suggestions, other methods or additions to what I may be missing here -please let me know. I need to get this working as proof of concept but if I can't install it with a clean bill of health, then what's the use.

I will post this as a new post as well hoping for any direction.

thanks to all!
blade


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top