[sims] Renaming SIMS Server

[snagrat]

We need to remove a SIMS server from the domain and join it to another domain as part of a MAT.

 

I was wondering what effect the following would have :

 

1) Just removing from Domain A and join Domain B

 

2) At the same time as Q1 look at renaming the server at the same time.

 

The LEA supports SIMS at these schools and so reinstalling isn't the cheapest thing to do as the LEA would need to do it.

[matt40k]

Contact your LEA, they'll have a guide. You also could always create a cname for the old name so it still resolves. The only other problem will be updating permissions from using the old domain to the new

[yac2016]

This is possible, I wouldn't rename the server as this can cause some issues within SQL. So you would need to change a few settings.

 

Are you using Solus3?

[localzuk]

Our LEA (Somerset), have a guide for migrating SIMS to a new server (that'd be my preferred method of doing this, rather than moving domains and renaming the existing server). You do everything yourself except the Discover and Solus move IIRC, as they are weird, and need other stuff doing, so the support team do it for you (for free IIRC).

 

So, I'd hope your LEA do the same.

[snagrat]

This is Cornwall LEA who will charge to move SIMS and I don't believe they give out the sa details like Somerset do.

 

I'll diesel to them to see what they say

[Banjo]

Domain changes aren't generally an issue. If your renaming the server then deattach the Sims DB - rename Sims server and then reattach Sims Db.

[jinnantonnixx]

Don't forget the document server. This uses a file structure based on your SQL server name (it can't cope with DNS aliases - I've tried). It's simply a matter of renaming the root-level folder on the DMS, but it's often overlooked during a move if the SQL server name changes. If it's being grafted to a new domain without a name change, it shouldn't need attention. Edited February 27, 2017 by jinnantonnixx

[matt40k]

It's the @@servername that also gets overlooked. So if you query the SQL Server it thinks its name is still the old one. Simple fix:

sp_dropserver <old_name>;

GO

sp_addserver <new_name>, local;

GO

 

Again, LA\SIMS Support Team should have advise (its their job after all)