ChristianWirth
asked on
WIndows Server 2003 / Exchange 2003 Installation with problems switch to SBS 2008
Dear all,
we are facing the following situation.
A windows 2003 servers with Exchange 2003 enterprise and 10 user accounts is at its end and should be replaced with a new server. Physical limit are reached, software installation is outaged and savaged.
SBS 2008 would be a very good solution for the company.
Due to a crash of the old server that occured in January 2011 Acrtive Directory is not working properly.
A few of the attached workstations and laptop can only login by disattaching the network cable during the authentication process as the backup that was restored was more than 3 month old.
Beside that there are 2 exchange databases. One is crashed and has a size of 109 GB as well as the streaming file size.
The second database is 65 GB of size and is missing 3 month of email data.
The former administrator is not longer acitve and can not be asked what happened exactly.
The preferred procedure should be to have a new Domain Controller and a fresh user setup.
Special care has to be taken of the mailboxes.
My favorite plan was to extract all active users mailboxes with Outlook at one dedicated PC to get rid of all the stuff that might have blown up the database.
I am aware the overall mailbox limit might not be larger than 72 GB on EX2K7.
Is it possible to attach a second database and have users splitted among these databases?
Any preferred archiving solutions in case that this does not work?
To minimize the total amount of work to do it would be really appreciated to transfer the current user profiles to the new environment.
What is the best way to do this? Or are there any ways to do a proper migration.
In a product trailer of SBS 2011 there was a wizard that guided through the process of merging a client machine to the domain and transfering all the client informtation to the new domain.
The most necessary information would be files, favorites, outlook and office settings (signatures, autotext etc.) , favorites nk2-files etc.
Your help would be very much appreciated here!
best regards,
Christian Wirth.
we are facing the following situation.
A windows 2003 servers with Exchange 2003 enterprise and 10 user accounts is at its end and should be replaced with a new server. Physical limit are reached, software installation is outaged and savaged.
SBS 2008 would be a very good solution for the company.
Due to a crash of the old server that occured in January 2011 Acrtive Directory is not working properly.
A few of the attached workstations and laptop can only login by disattaching the network cable during the authentication process as the backup that was restored was more than 3 month old.
Beside that there are 2 exchange databases. One is crashed and has a size of 109 GB as well as the streaming file size.
The second database is 65 GB of size and is missing 3 month of email data.
The former administrator is not longer acitve and can not be asked what happened exactly.
The preferred procedure should be to have a new Domain Controller and a fresh user setup.
Special care has to be taken of the mailboxes.
My favorite plan was to extract all active users mailboxes with Outlook at one dedicated PC to get rid of all the stuff that might have blown up the database.
I am aware the overall mailbox limit might not be larger than 72 GB on EX2K7.
Is it possible to attach a second database and have users splitted among these databases?
Any preferred archiving solutions in case that this does not work?
To minimize the total amount of work to do it would be really appreciated to transfer the current user profiles to the new environment.
What is the best way to do this? Or are there any ways to do a proper migration.
In a product trailer of SBS 2011 there was a wizard that guided through the process of merging a client machine to the domain and transfering all the client informtation to the new domain.
The most necessary information would be files, favorites, outlook and office settings (signatures, autotext etc.) , favorites nk2-files etc.
Your help would be very much appreciated here!
best regards,
Christian Wirth.
ASKER
terrygreensill, thank you for your answer and time.
When I read correctly the Quest Migration Manger allows to transfer Active Directory Information.
As the current Active Directory Structure seems to be damaged or broken it would be sufficient to move all local user file and programm settings but not the ADS information.
Are there any proven working tools for moving XP, Vista and Win7 profiles on the same machine?
reagrds,
Christian
When I read correctly the Quest Migration Manger allows to transfer Active Directory Information.
As the current Active Directory Structure seems to be damaged or broken it would be sufficient to move all local user file and programm settings but not the ADS information.
Are there any proven working tools for moving XP, Vista and Win7 profiles on the same machine?
reagrds,
Christian
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Profile Migration.... Backup the data before if your not sure but below is a process for a XP profile migration. Otherwise use a toll like Quest Migration manager.
To get the old profile: Log new user on then follow this
a. Browse the following registry key and locate the user's latest profile and modify the profile image path value to match the physical file location
b. HKEY_LOCAL_MACHINE\SOFTWAR
c. For example, if usera.b is logged and new profile created as usera.b in C:\documents and settings folder
d. If user's old profile (the correct profile) folder name is "usera b" then modify the profile image path to match this folder.
e. Give full NTFS permission to physical profile folder in documents and settings
f. Run regedit and select HKey_User and click fileà Load hive and point to user’s ntuser.dat file. (You may need to show all files)
g. In the name box just type anything, this is just how it will appear in regedit
h. Right click the name you gave it and Give full registry permission for the new user account to loaded hive.
i. Unload the hive and close registry editor
j. Restart the machine and login as user and it should give the proper profile.