Migrated to new exc...
 
Notifications
Clear all

Migrated to new exchange server

5 Posts
2 Users
0 Likes
658 Views
Posts: 57
Topic starter
(@dvoijen)
Trusted Member
Joined: 7 years ago

Dear Support,

Yesterday we migrated our customers to the new Exchange server (Exchange 2016).

In the Virtual Server i changed the System, Hosted Organizations and the Hosted Exchange to point to the new server.

Now existing customers cannot use solidcp anymore, when creating a new customer it does work...

4 Replies
Posts: 57
Topic starter
(@dvoijen)
Trusted Member
Joined: 7 years ago

I made a small workaround, i did set the ip of the old server as secondary ip to the new.

So basically the Hosting Space of a customer needs to move to the new server (Database) i guess...

Reply
Posts: 57
Topic starter
(@dvoijen)
Trusted Member
Joined: 7 years ago

Or could i just switch the server id in the database table servers?

Reply
Posts: 1964
Admin
(@m-tiggelaar)
Noble Member
Joined: 8 years ago

Hello,

on creation of each hosting space it assigns the service ID's to the specific hosting space.

So when it later changes in Virtual server existing customers do not pick up on the new servers/ service ID's.

Normally the most easy way is to move over the SolidCP Server to the new server (changing the IP as you done in your comment) and then changing the Provider ID inside the SolidCP database for that service (so it's set to exchange 2016).

Depending on from what exchange server version your coming your then recommended to open the Exchange service settings in the portal, make sure you fill out any new fields and press save.. that should do it.

 

The other way around (so adding a new server + service) requires SQL queries to change the ServiceID in ServiceItems and PackageServices table

Regards,

Marco

Reply
Posts: 57
Topic starter
(@dvoijen)
Trusted Member
Joined: 7 years ago

Mario, ok thanks for the info. i changed the id's in SQL since i allready had created new customers hehe

Reply
Share: