If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Migration from exchange 2003 to 2010: Commandline useful
Hi There,
I am reading a migraton roadmap in order to migration from exchange 2003 to 2010.
I have a DC controller witch exchange 2003 under Windows 2003.
A the beginning, I understand that I need to
1) Install windows 2008 on recent hardware
2) Update windows 2008
3) Integrate new server as member domain
Then we must respect some pre requisites
I am surprised that we use only command setup/preparead and we don’t launch some commands before installing exchange :
- Setup /preparelegacyExchangePerm
- Setup/ prepareschema
- Setup/ preparedomain
- Setup/ preparealldomain
Do you agree ? Please explain me.
Thanks,
Regards,
Fabien
I am reading a migraton roadmap in order to migration from exchange 2003 to 2010.
I have a DC controller witch exchange 2003 under Windows 2003.
A the beginning, I understand that I need to
1) Install windows 2008 on recent hardware
2) Update windows 2008
3) Integrate new server as member domain
Then we must respect some pre requisites
I am surprised that we use only command setup/preparead and we don’t launch some commands before installing exchange :
- Setup /preparelegacyExchangePerm
- Setup/ prepareschema
- Setup/ preparedomain
- Setup/ preparealldomain
Do you agree ? Please explain me.
Thanks,
Regards,
Fabien
Asked:
2
2
- +2
3 Solutions
All these commands are required to prepare current environment for installing Exchange 2010 server. Like Extending Schema will add new attributes, class etc.
Rest to read here
http://technet.microsoft.com/en-us/library/bb125224.aspx
Rest to read here
http://technet.microsoft.com/en-us/library/bb125224.aspx
thank rancy
The reason of setup /prepareAD is to update the schema.
If I launch the others, do you know if are there risks for my organisation ?
I am worry because it is in production !
The reason of setup /prepareAD is to update the schema.
If I launch the others, do you know if are there risks for my organisation ?
I am worry because it is in production !
We do understand how imp things are to everyone as i too work with some clients .... So if you want Amit shared an Article you can go through and if any Queries do let us know so we can share our thoughts :)
- Rancy
- Rancy
If you are on a single forest, single domain then you don't have to run the prep commands manually. The setup.exe GUI will run everything for you. The only time the commands need to be run outside of the GUI is in multiple domain environments, or where you aren't installing Exchange in to every domain, but will have mail enabled users from that domain in Exchange.
Simon.
Simon.
I highly recommend using PeteNetLive.com for this. He has a lot of great stuff out there and has saved me a number of times. The instructions are not taylored to your environment but they've always gotten to very close to where I needed.
http://www.petenetlive.com/KB/Article/0000234.htm
http://www.petenetlive.com/KB/Article/0000234.htm
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
- Rancy