Anyone tried to install rtm when preview was already installed, I mean first remove preview and then installed rtm. AD extended/upgraded ok ? Any other possible problems ? (Guess it is not possible to just Upgrade the preview)

It is standard Microsoft practice that you must remove the Preview before installing RTM. The Preview Notes clearly tell you not to deploy it in production.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks, I am aware of that, but what about AD ?

What about it?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

The schema, will the schema be correct after rtm installation or has the preview detour damaged it ?

I wouldn't trust it to be the same. But I can't answer your question definitively as I throw away my lab and start over when I use preview software that modifies the schema.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks for your effort. I wouldn't ruin a fine lab neither. That is why I asked in the threadstart, if anyone have tried.

For a lab, you can try removing the Exchange organization using ADSI Edit in the Configuration naming context, under Services > Microsoft Exchange (if I recall correctly). Just remove your organization and everything under it. Do not do this in production! It is not supported and may mess up your Active Directory! If the schema is different, you may have trouble, but I think there's a reasonalby high likelihood that you can reinstall Exchange in your lab after removing your organization like I described above.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

For a lab, you can try removing the Exchange organization using ADSI Edit in the Configuration naming context, under Services > Microsoft Exchange (if I recall correctly). Just remove your organization and everything under it. Do not do this in production! It is not supported and may mess up your Active Directory! If the schema is different, you may have trouble, but I think there's a reasonalby high likelihood that you can reinstall Exchange in your lab after removing your organization like I described above.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

For a lab, you can try removing the Exchange organization using ADSI Edit in the Configuration naming context, under Services > Microsoft Exchange (if I recall correctly). Just remove your organization and everything under it. Do not do this in production! It is not supported and may mess up your Active Directory! If the schema is different, you may have trouble, but I think there's a reasonalby high likelihood that you can reinstall Exchange in your lab after removing your organization like I described above.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I was able to "successfully upgraded" my lab from Preview to RTM bits. Here are the exact steps (not saying it's the right steps): Snap shot, back up and snap shot the Domain Server (just to be sure)On the DC, run all the /PrepareSchema, /PrepareAD, and /PrepareDomain using the RTM bit. Take a look at Justin Gao's Step by Step document here (http://blogs.technet.com/b/justin_gao/archive/2012/11/04/exchange-server-2013-rtm-deployment-document.aspx). The important thing he listed are the Version IDs of the AD's schema once you successfully prep/extend the schemaReboot: Exchange continue to work at this stage with RTM's schema and Preview's code.Next, I set up a new server (Hyper-V Windows Server 2012). Install the Mailbox server role. The installation went smoothly (just remember to install the released version of UMA API 4.0) instead of the beta, and you don't have to remove the VS11 beta as in the preview.Then I migrate the mailboxes from the Preview server to RTM server. Had lots of problems with the batch migrate. It's stuck at 95% with bad items (missing) for many accounts. I finally was able to move all the account with New-MoveRequest ... -BadItemLimit 12000 -AcceptLargeDataLoss. I had to do it manually, but I dont have many accounts, so not a problem.Reboot: Everything stills works. If you go to ECP, and click on Server. You should see 2 servers with different version numbers.Next, I re-install Exchange 2013 on the Preview server. It did not give me any options, just the license stuffs, and then wen through 17 steps to install the new bits.Reboot. Things still working. Both servers show the same version now. Obviously, your mileage might varies, but it seems to be ok for the last week or so. Caveat: I got a simple lab, just mails, address books, autodiscover, and mobiles. No UM, Lync...etc.My single DC is on Windows Server 2012, as well as all my host OS. I think that might helped.I'm sure MS will not support this scenarios, so just beware. Good luck.

I was able to "successfully upgraded" my lab from Preview to RTM bits. Here are the exact steps (not saying it's the right steps): Snap shot, back up and snap shot the Domain Server (just to be sure)On the DC, run all the /PrepareSchema, /PrepareAD, and /PrepareDomain using the RTM bit. Take a look at Justin Gao's Step by Step document here (http://blogs.technet.com/b/justin_gao/archive/2012/11/04/exchange-server-2013-rtm-deployment-document.aspx). The important thing he listed are the Version IDs of the AD's schema once you successfully prep/extend the schemaReboot: Exchange continue to work at this stage with RTM's schema and Preview's code.Next, I set up a new server (Hyper-V Windows Server 2012). Install the Mailbox server role. The installation went smoothly (just remember to install the released version of UMA API 4.0) instead of the beta, and you don't have to remove the VS11 beta as in the preview.Then I migrate the mailboxes from the Preview server to RTM server. Had lots of problems with the batch migrate. It's stuck at 95% with bad items (missing) for many accounts. I finally was able to move all the account with New-MoveRequest ... -BadItemLimit 12000 -AcceptLargeDataLoss. I had to do it manually, but I dont have many accounts, so not a problem.Reboot: Everything stills works. If you go to ECP, and click on Server. You should see 2 servers with different version numbers.Next, I re-install Exchange 2013 on the Preview server. It did not give me any options, just the license stuffs, and then wen through 17 steps to install the new bits.Reboot. Things still working. Both servers show the same version now. Obviously, your mileage might varies, but it seems to be ok for the last week or so. Caveat: I got a simple lab, just mails, address books, autodiscover, and mobiles. No UM, Lync...etc.My single DC is on Windows Server 2012, as well as all my host OS. I think that might helped.I'm sure MS will not support this scenarios, so just beware. Good luck.

I was able to "successfully upgraded" my lab from Preview to RTM bits. Here are the exact steps (not saying it's the right steps): Snap shot, back up and snap shot the Domain Server (just to be sure)On the DC, run all the /PrepareSchema, /PrepareAD, and /PrepareDomain using the RTM bit. Take a look at Justin Gao's Step by Step document here (http://blogs.technet.com/b/justin_gao/archive/2012/11/04/exchange-server-2013-rtm-deployment-document.aspx). The important thing he listed are the Version IDs of the AD's schema once you successfully prep/extend the schemaReboot: Exchange continue to work at this stage with RTM's schema and Preview's code.Next, I set up a new server (Hyper-V Windows Server 2012). Install the Mailbox server role. The installation went smoothly (just remember to install the released version of UMA API 4.0) instead of the beta, and you don't have to remove the VS11 beta as in the preview.Then I migrate the mailboxes from the Preview server to RTM server. Had lots of problems with the batch migrate. It's stuck at 95% with bad items (missing) for many accounts. I finally was able to move all the account with New-MoveRequest ... -BadItemLimit 12000 -AcceptLargeDataLoss. I had to do it manually, but I dont have many accounts, so not a problem.Reboot: Everything stills works. If you go to ECP, and click on Server. You should see 2 servers with different version numbers.Next, I re-install Exchange 2013 on the Preview server. It did not give me any options, just the license stuffs, and then wen through 17 steps to install the new bits.Reboot. Things still working. Both servers show the same version now. Obviously, your mileage might varies, but it seems to be ok for the last week or so. Caveat: I got a simple lab, just mails, address books, autodiscover, and mobiles. No UM, Lync...etc.My single DC is on Windows Server 2012, as well as all my host OS. I think that might helped.I'm sure MS will not support this scenarios, so just beware. Good luck.