Windows Server

John Chapman · Guest

Hi

Trying to forklift an Exchange database from 5.5 to 2003 using legacyDN.
Renamed PRIV.EDB and PUB.EDB to PRIV1.EDB and PUB1.EDB. Re-named existing
MDBDATA folder on SBS2003 to MDBDATA.SAV. Put above files in new folder
named MDBDATA. Started Exchange. Got expected error message "The information
store could not be loaded..etc...." Found what changes needed to be made
(minor as domain and server name unchanged). Started LegacyDN with
forcewrite switch but when I enter new values, the verify and change buttons
are greyed out. I can't make the changes.

What is wrong? Can any changes I make damage Exchange requiring a re-install
or will it just damge the old data files (obviously I have backup copies).

Regards

John Chapman

Nathan Liu [MSFT] · Guest

Hello John,

Thank you for posting in the SBS newsgroup.

According to your description, I understand that you would like to migrate
the Exchange database from Exchange 5.5 to Exchange 2003 Server. If I have
misunderstood the problem, please don't hesitate to let me know.

If the case and the issue is urgent to your business, it is recommended
that you contact Microsoft Product Support Services via telephone so that a
dedicated Support Professional can assist you recover the server in a more
efficient manner. Please be advised
that contacting phone support will be a charged call.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

It is your decision if you would like me to work with you on this issue in
this thread. I will be glad to assist you.

1. First of all, in SBS Server environment, we strongly recommend you
refer to the following White-paper to migrate the Exchange 5.5 to Exchange
2003 Server:

Migrating from Small Business Server 4.5 or Windows NT Server 4.0 to
Windows Small Business Server 2003
http://go.microsoft.com/fwlink/?LinkId=49929

2. For the Legacydn.exe tool, please kindly refer to the following KB
article:

How to use Legacydn.exe to correct Exchange organization names or
Administrative Group names in Exchange Server 2003 or in Exchange 2000
Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;324606

3. If the issue persists, please help me collect the following information
for further analysis:

A. Please kindly describe the exact Server environment.

B. Please provide the exact error message with any screenshots if
possible.

To do this, please follow the steps below:

a) When the screen appears, press PrScrn (this key is located to the right
of the
F12 key on the keyboard)
b) Create a new Word document and open it.
c) Press Ctrl + V to paste the screen shot into the document.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

Nathan Liu [MSFT] · Guest

Hi John,

Thanks for the email.

Considering the current condition, please kindly refer to the following
information:

=================
For public folder migrating:

1. Use an account on Outlook client computer that has administrative rights
to log on to a mailbox on the original server.

2. On the File menu, point to New, and then click Outlook Data File.

3. Click Personal Folders File (.pst), and then click OK.

4. Name the file Public.pst, save the file to a path that has a lot of free
disk space, and then write down the location where the file is saved.
NOTE: The .pst files have storage limits of 2 gigabytes (GB) each.

5. Accept the default settings that are listed in the "Create Microsoft
Personal Folders" dialog box, and then click OK. A new folder group that is
named Personal Folders is created in Outlook.

6. In the Outlook folder list, expand Public Folders, and then expand All
Public Folders.

7. Drag each top-level public folder that you want to export to the
Personal Folders folder that you created in step 4. All top-level public
folders and their subfolders are copied.

8. Log off the Outlook client.

9. From the Outlook client, use an account that has administrative rights
to log on to a mailbox that is homed on the SBS 2003 server.

10. Create new public folders.

11. On the File menu, point to New, and then click Outlook Data File.

12. Click Personal Folders File (.pst), locate and click the .pst file that
you created in step 4, and then click OK two times.

13. Drag the folders from the Personal Folders folder to All Public Folders
in the Outlook folder list.

===========
For Outlook rules:
You can use Outlook to export the current rules. Go to the client
workstations, open Outlook application. Click ''Tools''->''Rules and
alerts''. Click ''Options'' and then ''Export rules'' button. You can
export the rules to a file.

===========
For User profiles:
The above steps will help you install the SBS 2003 server. To preserve
client user profiles and settings that were on the original domain to the
new SBS 2003 installation, a manual way is documented in the KB article:
314045 HOW TO: Restore a User Profile in Windows 2000
http://support.microsoft.com/?id=314045

Another way is to create a local profile, copy the original domain profile
to the local profile, and then let the "Setup Computer" wizard do the task
"map local profile to new domain profile" for you.

As long as you create your computer accounts using the server manager''s
"to do list" you will be prompted to migrate profile information. When you
join the workstations to the domain by using the web site (ie
http://servername/connectcomputer) part of the process of joining the
domain will allow you to migrate user settings. However, to use this
method, you need to make sure that the profile you want to migrate from is
a local user profile (Not a previous domain profile):

1. Before joining the client to SBS 2K3 domain, create a local profile, and
then copy the old domain profile to a local profile.

2. Add the SBS Server into the network

3. Use the Setup Computer Wizard in SBS 2003 to join the (now) XP Pro
machines to the SBS domain: Server Management, Standard Management, Client
Computers, Set Up Client Computers.

4. On the client, access http//<Server name>/connectcomputer to bring up
the Setup Computer Wizard, it will then allow you to map domain user
accounts to local profiles on the machine thus preserving your profiles:
"Assign Users to this Computes and Migrate their Profiles".

5. You will Add a domain account to "Users assigned to this computer!/, and
then choose the existing local user profile in the "Current User Settings".
By Default, the value for "Current User Settings" is "None".

In addition, if you use this method to map your domain account profile to
the existing local computer account when using the Connectcomputer wizard,
the resulting domain account will not have the Outlook Exchange profile
configured automatically, you will need to create the Outlook profile to
connect to your SBS Exchange server.

During server setup, a default .prf file named SBSDefault.prf is copied
from CD to \\%sbsserver\clients\Setup. The setup then updates two instances
of %SBSServer% with the name of the server. During client configuration
(ConnectComputer,) the file is copied to the client folder ''C:\Program
Files\Microsoft Windows Small Business Server\Clients'' and %FaxTransport%
is replaced with either MSFax XP (for Windows XP) or SHAREDFAX XP (for
Windows 2000).

The easiest way to create the SBS 2K3 Outlook profile is to remove all the
Outlook Profile, make sure Outlook is closed, and then locate to the client
computer folder ''C:\Program Files\Microsoft Windows Small Business
Server\Clients'' (or ''\\SBS2003Server\clients\Setup'' if the folder is not
created on the client computer,) double click sbsdefault.prf, this will
automatically create the outlook profile with the correct settings (which
also include the FAX Transport) for the corresponding domain user.

I hope the above information helps. If you have any questions, please feel
free to let me know.

Best regards,
Nathan Liu (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

======================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

======================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Nathan Liu [MSFT] · Guest

Hi John,

Thanks for the email, I'm glad to hear that things are working correctly
for you now. I appreciate your shared issue resolution, please do not
hesitate to post in this great newsgroup if you need any assistance in the
future. I look forward to working with you again.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1