Exchange 2003 SP2 / mode issues (on SBS 2003 detected during attemptto migrate to 2008 SBS)

Unfortunately not.

Using the SBS migration docs
([url]http://go.microsoft.com/fwlink/?LinkId=91366[/url]). I could have changed
this modes, in any order, at any time. It just needs to be done before
the migration. Nothing states you can't do this unless you migrate.

Regards

Ens Mith wrote:[color=blue]
> AllenM wrote:[color=green]
>> I'll ask you the same question I asked Freaky and that is what
>> documentation are you following and using for your migration?
>>
>> "slappy" <patgrayjr@yahoo.com> wrote in message
>> news:bd32bd56-509a-486e-a9be-d8e68d51d25e@g1g2000vbr.googlegroups.com...[color=darkred]
>>> I'm having a very similar problem. I was having some issues getting
>>> the network setup on SBS 2008 so I blew away the install in the hopes
>>> of starting over. I also wanted to set my answer file to automated, so
>>> after blowing away the 2008 install I reran the migration tool and it
>>> failed on the Exchange step. I created my answer file, and when I
>>> attempt to install SBS 2008 on the new server I get "Run the MIgration
>>> Prep Tool on the Source Server" as an error (in the same dialog the OP
>>> posted) and cannot continue.
>>>
>>> The log from the migration prep wizard seems to indicate everything is
>>> already done, and I've validated that the AD and forest levels have
>>> been raised. The odd wrinkle is that like the OP, Exchange SA reports
>>> that native mode is active, yet BPA reports the server is still in
>>> mixed mode. I'm unable to change the exchange mode using the MS
>>> documentation since it already reports itself as in native mode.
>>>
>>> I have a backup that's a couple days old (everything is virtual so
>>> it's easy to go back) but I'm hesitant to go there for fear of losing
>>> email and having to deal with a network that's out of sync.
>>>
>>> Is there any registry setting to fake out the migration wizard having
>>> run, or am I stuck doing a manual migration or restoring from backup
>>> and dealing with whatever issues that creates?
>>>
>>> Here's my migration log:
>>>
>>> 10/07/2009 16:12:16 Starting task Update the schema
>>> 10/07/2009 16:12:17 adprep.exe Exists: False
>>> 10/07/2009 16:12:17 adprep\adprep.exe Exists: True
>>> 10/07/2009 16:12:17 Running C:\Program Files\Windows
>>> Small Business Server 2008 Migration Preparation Tool\adprep
>>> \adprep.exe /forestPrep /wssg /silent
>>> 10/07/2009 16:12:18
>>> 10/07/2009 16:12:18 Adprep returned:
>>> ForestUpdateAlreadyDone(13)
>>> 10/07/2009 16:12:18 adprep.exe Exists: False
>>> 10/07/2009 16:12:18 adprep\adprep.exe Exists: True
>>> 10/07/2009 16:12:18 Running C:\Program Files\Windows
>>> Small Business Server 2008 Migration Preparation Tool\adprep
>>> \adprep.exe /domainPrep /gpprep /wssg /silent
>>> 10/07/2009 16:12:18
>>> 10/07/2009 16:12:18 Adprep returned: GpoUpdateAlreadyDone
>>> (15)
>>> 10/07/2009 16:12:18 Adprep has succeeded.
>>> 10/07/2009 16:12:18 Task finished successfully
>>> 10/07/2009 16:12:18 Starting task Provide licensing support
>>> 10/07/2009 16:12:18 Current version: 5.2.3790.131072
>>> 10/07/2009 16:12:18 Service pack version = 2
>>> 10/07/2009 16:12:18 Running C:\Program Files\Windows
>>> Small Business Server 2008 Migration Preparation Tool
>>> \KB943494\WindowsServer2003-KB943494-x86-ENU.exe /quiet /norestart
>>> 10/07/2009 16:12:23 Package returned: 3010 (0xBC2)
>>> 10/07/2009 16:12:23 Task finished successfully
>>> 10/07/2009 16:12:23 Starting task Configure Exchange to
>>> support migration
>>> 10/07/2009 16:12:23 Changing Exchange to be native mode.
>>> 10/07/2009 16:12:23 Begin adding Authenticated Users to
>>> Pre Windows 20008 Compatible Access group
>>> 10/07/2009 16:12:23 AU:
>>> LDAP://XXX.local/CN=S-1-5-11,CN=ForeignSecurityPrincipals,DC=XXX,DC=local
>>>
>>> 10/07/2009 16:12:23 PreWin2k:
>>> LDAP://XXX.local/CN=Pre-Windows
>>> 2000 Compatible Access,CN=Builtin,DC=XXX,DC=local
>>> 10/07/2009 16:12:23 AU is already a member, no-op
>>> 10/07/2009 16:12:23 auSuccess=True, exchangeSuccess=False
>>> 10/07/2009 16:12:23 Task Finished with Error
>>> 10/07/2009 16:13:34 Setting migration ready flag to False
>>> 10/07/2009 16:13:34 Setting time stamp[/color]
>>
>>[/color]
> Freaky or Slappy, did you manage to sort this?
> Got the same problem.
>[/color]

[Gabriele]

Hi all,
I've got the same identical issue as yours. I've done the preptool on source server, everything is fine except for exchange 2003 mode, that from ESM appears as "native" (I did that manually before running preptool) but the analyzer tool tells me that it's still mixed. :( then, on destination server the SBS wizard hangs on start and tells me that the preparation tool has not been run on source server. Do anyone has the solution? :S thank you all,
- Gabriele




[QUOTE=Freaky;79811]Hi there,

sorry to post this here as well. It's somewhat urgent and although it
concerns SBS (it's posted in microsoft.public.windows.server.sbs too)
the issue appears to be with exchange.

Basically we can't do the migration to 2008 with the migration tools.
The 2008 installer claims that Exchange 2003 SP2 is not installed.

The SBS Best Practice Analyser reports SP2 is installed but says it's
still in mixed mode.

TIA[/QUOTE]

Not sure if that's the same issue. I finally found the solution to mine
though, maybe it helps you. There is a command prompt, press shift-F10.
That might help a lot :)

Credits to sharedit, who posted this on experts-exchange.com:

------------------------------------------------------------------------
Ok, problem solved. Im going to include as much information as
possible, so that others may benefit.

The problem was the site uses a class B network, SBS 2008 assumes a Class C.

I called microsoft, and worked with them, but had I known you could
access a command prompt on the destination server by hitting shift +f10
this would have been very easily solved.

the sbs 2008 would install fine until the wizard page confirming source
name, domain name, dest name, admin account/pwd, etc. At this point I
would get the error: Cannot find the Source Server Verify that the
Source Server name is correct,
and then try again

In troubleshooting, I could take the network cable and put it in the
second nic and it would then go on to the next step. That is where I
would get the next set of errors.

source server does not meet minimum requirements for migration

if the domain/forest functional level is not windows server 2003 you
will encounter setup errors
you must raise the functional level of the Active directory domain and
forest on the source server. & Source server does not meet service
pack requirements. you must first install service pack 2 for exchange
server 2003. for instructions see....

Solution:
At the first error, shift + f10 will bring up a command prompt.
from there you can test with ping (IP, fqdn, netbios), Ipconfig, to find
out what is actually not working or configured incorrectly.

to get to the SBS setup log.
go to C:\Program Files\Windows Small Business Server\Logs\SBSSetup.log
the command "notepad SBSSetup.log" will open it in notepad. you'll get
alot of info from this, this is where I noticed the Mask it was
assigning was incorrect.

the command "control" will open up the control pannel. From here you
can configure many things(duh), you can enable Remote connections an RDP
to the server if youd like (assign an admin pwd first). What I did was
change the subnet mask to its correct /16. and tryed again. At this
point the Install continued without a problem.

with the incorect mask I was able to ping the source from the
destination by IP and Fqdn but not name. after the change and IPconfig
/flushdns i was able to ping all 3.

This was a very simple solution, i was completely frustrated/embaraced
that I found no reference to the shift +f10 for the command prompt on
the destination server durring my searching. it made troubleshooting
the destination server like a pc and not just a Wizard screen that you
cannot advance past.
------------------------------------------------------------------------

Thanks again sharedit :).

Gabriele wrote:[color=blue]
> Hi all,
> I've got the same identical issue as yours. I've done the preptool on
> source server, everything is fine except for exchange 2003 mode, that
> from ESM appears as "native" (I did that manually before running
> preptool) but the analyzer tool tells me that it's still mixed. :( then,
> on destination server the SBS wizard hangs on start and tells me that
> the preparation tool has not been run on source server. Do anyone has
> the solution? :S thank you all,
> - Gabriele
>
>
>
>
> Freaky;79811 Wrote:[color=green]
>> Hi there,
>>
>> sorry to post this here as well. It's somewhat urgent and although it
>> concerns SBS (it's posted in microsoft.public.windows.server.sbs too)
>> the issue appears to be with exchange.
>>
>> Basically we can't do the migration to 2008 with the migration tools.
>> The 2008 installer claims that Exchange 2003 SP2 is not installed.
>>
>> The SBS Best Practice Analyser reports SP2 is installed but says it's
>> still in mixed mode.
>>
>> TIA[/color]
>
>[/color]

SOLVED! :)

Damn retarded wizards :D

Credits to sharedit, who posted this on experts-exchange.com:

------------------------------------------------------------------------
Ok, problem solved. Im going to include as much information as
possible, so that others may benefit.

The problem was the site uses a class B network, SBS 2008 assumes a Class C.

I called microsoft, and worked with them, but had I known you could
access a command prompt on the destination server by hitting shift +f10
this would have been very easily solved.

the sbs 2008 would install fine until the wizard page confirming source
name, domain name, dest name, admin account/pwd, etc. At this point I
would get the error: Cannot find the Source Server Verify that the
Source Server name is correct,
and then try again

In troubleshooting, I could take the network cable and put it in the
second nic and it would then go on to the next step. That is where I
would get the next set of errors.

source server does not meet minimum requirements for migration

if the domain/forest functional level is not windows server 2003 you
will encounter setup errors
you must raise the functional level of the Active directory domain and
forest on the source server. & Source server does not meet service
pack requirements. you must first install service pack 2 for exchange
server 2003. for instructions see....

Solution:
At the first error, shift + f10 will bring up a command prompt.
from there you can test with ping (IP, fqdn, netbios), Ipconfig, to find
out what is actually not working or configured incorrectly.

to get to the SBS setup log.
go to C:\Program Files\Windows Small Business Server\Logs\SBSSetup.log
the command "notepad SBSSetup.log" will open it in notepad. you'll get
alot of info from this, this is where I noticed the Mask it was
assigning was incorrect.

the command "control" will open up the control pannel. From here you
can configure many things(duh), you can enable Remote connections an RDP
to the server if youd like (assign an admin pwd first). What I did was
change the subnet mask to its correct /16. and tryed again. At this
point the Install continued without a problem.

with the incorect mask I was able to ping the source from the
destination by IP and Fqdn but not name. after the change and IPconfig
/flushdns i was able to ping all 3.

This was a very simple solution, i was completely frustrated/embaraced
that I found no reference to the shift +f10 for the command prompt on
the destination server durring my searching. it made troubleshooting
the destination server like a pc and not just a Wizard screen that you
cannot advance past.
------------------------------------------------------------------------

Thanks again sharedit :).


Freaky wrote:[color=blue]
> Unfortunately not.
>
> Using the SBS migration docs
> ([url]http://go.microsoft.com/fwlink/?LinkId=91366[/url]). I could have changed
> this modes, in any order, at any time. It just needs to be done before
> the migration. Nothing states you can't do this unless you migrate.
>
> Regards
>
> Ens Mith wrote:[color=green]
>> AllenM wrote:[color=darkred]
>>> I'll ask you the same question I asked Freaky and that is what
>>> documentation are you following and using for your migration?
>>>
>>> "slappy" <patgrayjr@yahoo.com> wrote in message
>>> news:bd32bd56-509a-486e-a9be-d8e68d51d25e@g1g2000vbr.googlegroups.com...
>>>> I'm having a very similar problem. I was having some issues getting
>>>> the network setup on SBS 2008 so I blew away the install in the hopes
>>>> of starting over. I also wanted to set my answer file to automated, so
>>>> after blowing away the 2008 install I reran the migration tool and it
>>>> failed on the Exchange step. I created my answer file, and when I
>>>> attempt to install SBS 2008 on the new server I get "Run the MIgration
>>>> Prep Tool on the Source Server" as an error (in the same dialog the OP
>>>> posted) and cannot continue.
>>>>
>>>> The log from the migration prep wizard seems to indicate everything is
>>>> already done, and I've validated that the AD and forest levels have
>>>> been raised. The odd wrinkle is that like the OP, Exchange SA reports
>>>> that native mode is active, yet BPA reports the server is still in
>>>> mixed mode. I'm unable to change the exchange mode using the MS
>>>> documentation since it already reports itself as in native mode.
>>>>
>>>> I have a backup that's a couple days old (everything is virtual so
>>>> it's easy to go back) but I'm hesitant to go there for fear of losing
>>>> email and having to deal with a network that's out of sync.
>>>>
>>>> Is there any registry setting to fake out the migration wizard having
>>>> run, or am I stuck doing a manual migration or restoring from backup
>>>> and dealing with whatever issues that creates?
>>>>
>>>> Here's my migration log:
>>>>
>>>> 10/07/2009 16:12:16 Starting task Update the schema
>>>> 10/07/2009 16:12:17 adprep.exe Exists: False
>>>> 10/07/2009 16:12:17 adprep\adprep.exe Exists: True
>>>> 10/07/2009 16:12:17 Running C:\Program Files\Windows
>>>> Small Business Server 2008 Migration Preparation Tool\adprep
>>>> \adprep.exe /forestPrep /wssg /silent
>>>> 10/07/2009 16:12:18
>>>> 10/07/2009 16:12:18 Adprep returned:
>>>> ForestUpdateAlreadyDone(13)
>>>> 10/07/2009 16:12:18 adprep.exe Exists: False
>>>> 10/07/2009 16:12:18 adprep\adprep.exe Exists: True
>>>> 10/07/2009 16:12:18 Running C:\Program Files\Windows
>>>> Small Business Server 2008 Migration Preparation Tool\adprep
>>>> \adprep.exe /domainPrep /gpprep /wssg /silent
>>>> 10/07/2009 16:12:18
>>>> 10/07/2009 16:12:18 Adprep returned: GpoUpdateAlreadyDone
>>>> (15)
>>>> 10/07/2009 16:12:18 Adprep has succeeded.
>>>> 10/07/2009 16:12:18 Task finished successfully
>>>> 10/07/2009 16:12:18 Starting task Provide licensing support
>>>> 10/07/2009 16:12:18 Current version: 5.2.3790.131072
>>>> 10/07/2009 16:12:18 Service pack version = 2
>>>> 10/07/2009 16:12:18 Running C:\Program Files\Windows
>>>> Small Business Server 2008 Migration Preparation Tool
>>>> \KB943494\WindowsServer2003-KB943494-x86-ENU.exe /quiet /norestart
>>>> 10/07/2009 16:12:23 Package returned: 3010 (0xBC2)
>>>> 10/07/2009 16:12:23 Task finished successfully
>>>> 10/07/2009 16:12:23 Starting task Configure Exchange to
>>>> support migration
>>>> 10/07/2009 16:12:23 Changing Exchange to be native mode.
>>>> 10/07/2009 16:12:23 Begin adding Authenticated Users to
>>>> Pre Windows 20008 Compatible Access group
>>>> 10/07/2009 16:12:23 AU:
>>>> LDAP://XXX.local/CN=S-1-5-11,CN=ForeignSecurityPrincipals,DC=XXX,DC=local
>>>>
>>>> 10/07/2009 16:12:23 PreWin2k:
>>>> LDAP://XXX.local/CN=Pre-Windows
>>>> 2000 Compatible Access,CN=Builtin,DC=XXX,DC=local
>>>> 10/07/2009 16:12:23 AU is already a member, no-op
>>>> 10/07/2009 16:12:23 auSuccess=True, exchangeSuccess=False
>>>> 10/07/2009 16:12:23 Task Finished with Error
>>>> 10/07/2009 16:13:34 Setting migration ready flag to False
>>>> 10/07/2009 16:13:34 Setting time stamp
>>>[/color]
>> Freaky or Slappy, did you manage to sort this?
>> Got the same problem.
>>[/color][/color]