Rename SIMS server

[cookie_monster]

We have a new server to replace our old SIMS server and i would like to call the new server a different name so it can be build side by side, i seem to remember there being an issue with this last time i built a SIMS server.

 

Has anyone here managed to rename a SIMS server successfully and if so what pitfalls did you encounter?

 

Cheers.

[JAYC]

The main problem with renaming, is that each workstation has a line in the Sims.ini file which looks to the UNC path of the Setups folder, so this needs to be amended to reflect the new server name.

[cookie_monster]

Ok i can cope with that if that's the only issue.

 

Cheers.

[pete]

The one that springs to mind is make sure you get the Document Server setup correct as by default part of the save path uses the server name.

 

i.e: ours is c:\sims\Documents\SERVERNAME\SIMS\sims

 

IIRC you have to change the SERVERNAME folder to NEWSERVERNAME, but I suggest you check this.

 

I'm reliably informed that trying to repair the problem caused by not setting it correctly is "interesting".

[robinhood]

The one that springs to mind is make sure you get the Document Server setup correct as by default part of the save path uses the server name.

 

i.e: ours is c:\sims\Documents\SERVERNAME\SIMS\sims

 

IIRC you have to change the SERVERNAME folder to NEWSERVERNAME, but I suggest you check this.

 

I'm reliably informed that trying to repair the problem caused by not setting it correctly is "interesting".

 

Oh dear - my site may well have the above problem - by "interesting" what is involved? A document server has been recently re-named (not the SIMS server) and now many bespoke report templates are not readable.

 

Any advice/experience would be much appreciated.

 

--

RH

[DMcCoy]

run dmconfig from the command line and it will tell you where its currently looking. You can alter it with dmconfig too if you need to.

 

The server name is also held in the master database somewhere, I can't remember the command to change it at the moment, this being wrong will cause things like b2b to fail.

[pete]

^what he said, basically.

 

You have to catch the problem early, as there's no* way to consolidate or link the contents of the two document servers together again.

 

So any reports done since the renaming are likely unretrievable.

 

*Or there wasn't when I went on a SIMS course a couple of years ago and the guy from Capita pleaded with us to make sure we didn't screw that part up as there was no way they could repair it.

[Jawloms]

KB36318 on SupportNet claims you can. I don't know how well it works, but it could be worth a look!

 

Stuart

[pete]

hmm, I stand corrected then. Might have to try that on the test server.

[cookie_monster]

Anyone here had issues with having SQL express on the same box as full SQL 2005.

 

We have Backup exec 11D on our server that uses a SQL express instance, when i install SQL 2005 it wont install the management tools as it thinks they're already installed.

 

This guy seems to be having a similar problem.

 

http://forums.asp.net/p/1170124/1963691.aspx

 

Cheers.

[vikpaw]

I've had a situation where when setting up virtual sims servers for test purposes i've forgotten to repoint the document server to the correct place. When you create a report it just creates a new folder with the new server name in the original location.

 

Also, I found that when i renamed my Virtual servers the location of the document storage would go to a brand new folder called C:\sims\documents which may be the new default location, except my setup uses C:\DOCSTORAGE.

 

Anyway, repointing to the correct location using dmconfig works.

 

I've followed the advice in the SupportNet article and it works okay.

 

If i want to update my virtual docstorage from the live system, i do an xcopy to copy the newer files over:

 

XCOPY /D /H /S source destination

 

- copies directory, folders and files inc hidden but only if source is newer - the benefit being it's quicker than copying the whole 2.5GB over.

 

I sometimes do testing on a Virtual Server because reports especially tables in word, can corrupt and become irrecoverable. Although i do also export all reports that i want to preserve as a backup for this very reason. The benefit of the VM is when my reports run into an endless loop or try to return too much data and crash out, it's not the live system i'm slowing down

 

If i ended up with two servername folders in docstorage, i would backup both folders somewhere safe, and then try doing the xcopy above from the old folder structure to the new. That way all the old reports should come over and go to the correct place.

[matt40k]

Before you transfer SIMS, untick the B2B box, this should sort out any problems with B2B.

 

DocStorage like they said, you're need to rename the folder to the correct server name.

 

Connect.ini and FMSconnect.ini should redirect to the SIMS share (s:), this should mean you just change 1 file, also you'll need to update the mapped drive (you're be suprised how many people forget this)

 

sims.ini on each workstation will need to amend with the new setups path, there is a utility on supportnet in the file download area.

 

 

@cookie_monster

SQL Express and SQL "full"... believe you can do it. Not tried to be honest, just install another instance on "full" SQL and move BackupExec onto IMHO.

[GREED]

I have (somewhere) a document I put together with everything needed from start to finish to build and transfer SIMS to a new server, including what to do about new names and doc servers etc. I'll try and did it out if anyone wants it.

[Ron_Bate]

Yes please - it sounds very useful.

 

Many thanks.

 

[email protected]

[Soulfish]

I have (somewhere) a document I put together with everything needed from start to finish to build and transfer SIMS to a new server, including what to do about new names and doc servers etc. I'll try and did it out if anyone wants it.

 

That would be very handy. Going to be moving our SIMS server to our lovely virtualised server farm sometime soonish. It's currently the only non-virtualised server we're running

[mounters]

To check and change the SQL server name in the master database then do the following:

 

Check:

 

To view the server's internal name (ensure you are logged in as Administrator):

1. Run OSQL -E -SSERVER\INSTANCE (e.g -S'name server'\SIMS) on the server from command prompt and a 1 will appear on next line. The Server and instance must be in Upper Case.

2. Type: select @@servername and press enter

3. Type: go and press enter

4. Write down the returned servername (after all the ---) and type: Exit and press enter.

 

 

To alter servername:

 

1. Run OSQL -E -SSERVER\INSTANCE on the server from the command prompt

2. Type: use master and press enter

3. Type: GO and press enter

4. Type: sp_dropserver 'OLDSERVER\INSTANCE' (as displayed in Diagnosis) and press enter

5. Type: GO and press enter

6. Type: sp_addserver 'NEWSERVER\INSTANCE', 'local' and press enter

7. Type: GO and press enter

8. Type: exit and press enter

9. Restart the SQL Server service(s). This will remove the server name from the internal local and remote server databases (step 4), and add a new local server name (step 6). Resolution can be confirmed by repeating the steps in Diagnosis (above).

 

Please ensure a FULL SQL backup is taken before executing this procedure.

[GREED]

This is basically it (Copied from my word doc!)

 

New Server Install for SIMS.net/FMS

 

• Install Windows Server 2003 (if you can), and update using windows update, install all updates and service packs. When installing, ensure you split the server HDD (or combined, RAIDed HDDs) into at least 2 partitions, c: for program files, d: for SQL and SIMS.

 

• Install SQL Server 2005 (or Express), and again update with all service packs. When installing, remember the instance name of the installation, you will need it later. Also, ensure you install to the secondary drive, not the C: drive (If SQL fills up the drive, you will not be able to start the server)

 

• Copy your SIMS Set-Ups folder to the new server, and put into a shared folder called Capita (or whatever you want to call your shared network drive)

 

• Run the SIMSINST application (from the SIMS setups folder), and ensure that the server option AND the document management server option are selected. Follow the onscreen instructions from here. You will need the SQL instance name from earlier.

 

• Once complete, login to test the new server. Use the username/password: 'SYSMAN' & 'password'. Once you can log in ok, you know this server installation is working.

 

• Now, make a full SQL backup of the original database. Copy this to the new server, and put into a suitable place (usually d:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data, where d is the drive where SQL is installed.

 

• ON THE NEW SERVER, restore this new database backup to the SQL, over the top of the new SIMS installation.

 

• Open dbAttach, and detach and reattach the SIMS database to SQL(Remember to drop SQL Logins). This should allow you to login with the normal usernames/passwords from the original database.

 

• Try logging into SIMS again on the new server. Remember you will need a new/updated connect.ini file wherever you are logging on from to do this (see below)

 

• Things to remember to do: Change the location of the Document Management Server in SIMS.net (Tools -> Setups -> DMS), import all the reports again (Reports -> Import).

 

• Now, copy the contents of the following folders to the new server:

SIMS/DocStorage/*Old Server Name Here*/ -> Copy to: SIMS/DocStorage/*New Server Name Here*/

o Options

o SNova

o DocStorage (When copied, change the name of the sub folder to match that of the new server.)

 

• If your connect.ini files on the local workstations connect direct to the SIMS server, you will need to alter these individually to now point to the new server name/instance name. If you redirect to a central connect.ini, you only need to ensure that this one is correct (this is what I use).

 

 

 

 

 

 

Hope it is useful!

[vikpaw]

I've used that document before Graham , and think i've even posted it in another thread

I was just checking though, are you sure about dropping sql logins? I thought that you shouldn't drop them, and the detach, reattach then allows you to use the ones saved in the backup from the old system. dropping them means you have to go back to square one...

[GREED]

Vik

 

It depends if you are using the AD integration with SIMS to auto-logon. If yes, then it is advisable, in my experience if not the logins and the database don't seem to match up and no logins work properly.

 

If you do use SIMS logins, then you are right and probably best not to drop the logins (although even so it does seems to solve problems every now and then!).

 

I still havn't had my invitation for a holiday... I mean visit... to your place yet!!!

[minxy]

What about renaming in Brian?