Exchange Server Forums

Transition from E2K3 to E2K7 on W2008

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Migration >> Transition from E2K3 to E2K7 on W2008

Page: [1]

Message

<< Older Topic Newer Topic >>

Transition from E2K3 to E2K7 on W2008 - 17.Jun.2008 1:19:55 PM

9milbill

Posts: 66
Joined: 4.Feb.2003
From: United Kingdom
Status: offline

Scenario: Single server, AD, DNS, Exchange 2003 SP2 on W2003 32 bit, single forest needs to transition to Exchange 2007 on W2008, both 64 bit, AD, DNS etc. Yes, I know not great running DC on a single server.

W2003 server OK after running ExBPA 2007 transition scan. W2008 full edition not core, (64bit) installed OK.

I'm following Henrik's Part 1 (of 3) article but I'm stuck at the Setup.com /PrepareLegacyExchangePermissionsPrepareLegacyExchangePermissions
which is failing because it (W2008) doesn't see another domain controller, even though I'm successfully logged on to the W2008 server as domain administrator. I'm running this command from the Ex2007 installation DVD.I can't see why it's failing.

Anyone come across this problem?

TIA, Stephen

Post #: 1

Featured Links*

RE: Transition from E2K3 to E2K7 on W2008 - 22.Jun.2008 11:35:15 AM

Sembee

Posts: 3130
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Have you tried just running setup.exe from the Exchange 2007 SP1 DVD? If not, do that. In your scenario you do not need to run the setup.com manually, setup will prep the domain for you, or give you an error.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to 9milbill)

Post #: 2

RE: Transition from E2K3 to E2K7 on W2008 - 6.Jul.2008 1:14:57 AM

Exchange_Geek

Posts: 424
Joined: 31.Dec.2006
Status: online

Can we have the exact error posted please.

What i can understand that the cmdlet isnt progressing with lack of availibility of DC (atleast thats what E2k7 is telling you with that cmdlet) - so why not provide it.

Run setup.com /pl /dc: FQDN of your GC.

Check this out.

(in reply to Sembee)

Post #: 3