First of all, thank you for your quick response
Regarding new panel installation as you said, i have two options
1.- Do a complete migration from exchange 2010 to 2016 and after that do a fresh installation of the new panel
In this case, I have a doubt regarding the users code. Currently the samaccount name is created automatically with a code where de client code
Is there anyplace in the new panel where I sould to write it down? Or may be, it could be a better Idea create a new company code in order to start the users code from the begining and after that, upgrade the customattribute for the client with the new values in order to integrate all users in the new oab
2.- Other option, could be install the new panel attached to exchange 2010, do the full migration to exchange 2010 and after that, swap the panel to exchange 2016.
In this case, could you please how to do it.
I'm searching on your webpage and I've only found an article that I have to modify a value inside SQL table. Is that correct? In this case, I dont understand whats happen regarding Public Folders, OAB etc
Thank you in advanced
In the case I decide to install the solidcp panel prior to do the migration to exchange 2016 I have other questions
Can I have installed in the same server (Exchange 2010 server) two agents. Currently the server have instaled the agent for webpanel which one listen by the port 9003.
In this case, I'll have to add a new IP address and modify the bindings, I guess. Is that correct?
- If you go the import method --> you will need to re-create SolidCP users, setup an OU --> go to the database and modify it to the customers original OrgID --> import the Exchange users / contacts etc using the Enterprise import tool.
- This is indeed another option, the reason why OAB and PF's matter is from the ProviderID in the database, based up on that SolidCP runs specific codes that is compatible with that particular version (where Exchange 2010 handles OAB's and PF's completely different then Exchange 2016, so other commands need to be executed).
Yes you can assign any url or port to the SolidCP server using IIS bindings.
I'm thinking about another option in order to do the migration
I've thinked to do next:
1.- Install SolidCp Web Panel and Enterprise server in a new Server
2.- Install solidCP server in the exchange 2010 servers. Previously I'll add a new IP in those servers for the IIS bindings because all of them are working currently with Wepanel
3.- Add in SoldCP Web panel the exchange 2010 Server.
4.- Create clients, hosted plan, etc in SolidCP
5.- Import the users
6.- Inform to my clients the new IP of SolidCP Web Panel
8.- Migrate all mailboxes, OAB and Public Folders to Exchange 2016
9.- Add Exchange 2016 to solidCP web Panel
Here, in this step I've serveral doubts
In web panel I have a virtual server attached to Exchange 2010 servers
I guess, I'll have to add the exchange 2016 server to this virtual Server and remove the exchange 2010 servers
Just after that I'm not sure what else do I have to do
The step 9 you could just convert the 2010 provider ID to the 2016 one in the mssql database. this way it's much more easy.
You then check the provider settings (make sure things like Powershell url is set), after that check hosting plans if everything is still set correctly (should be fine but always double check).
