All here-
I used Hyper-V as a role 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
I used Hyper-V as a role 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
