MIS Systems Thread, Whoops! Made a boo boo with Connect.ini in Technical; Ok, was setting up SIMS on classroom workstation. Got distracted when pasting connect.ini and pasted over the one on the ...
-
6th January 2012, 09:47 AM #1 Whoops! Made a boo boo with Connect.ini
Ok, was setting up SIMS on classroom workstation. Got distracted when pasting connect.ini and pasted over the one on the S Drive where SIMS lives instead of the local one.
So what should the one on the server say and what should the one on the workstation say?
Thanks lol
-
-
IDG Tech News
-
6th January 2012, 09:49 AM #2 Same thing... probably.
As long has you point the machine to the server and the database it should connect. As long as that machine can see the IP or Server name.
-
Thanks to creese from:
Little-Miss (6th January 2012)
-
6th January 2012, 09:51 AM #3
-
Thanks to X-13 from:
Little-Miss (6th January 2012)
-
6th January 2012, 09:53 AM #4 Ours says
Server connect.ini
Code:
[SIMSConnection]
ServerName=ServerName\SIMS2008
DatabaseName=sims
commandtimeout=120000
ConnectionType=Trusted
If you don't use Current Windows User then I think you can drop the ConnectionType line.
Workstation
Code:
[SIMSConnection]
REDIRECT=S:\SIMS
-
Thanks to sjatkn from:
Little-Miss (6th January 2012)
-
7th January 2012, 09:18 PM #5 @Little-Miss - tut tut, surely you have backups to double check! The above from is @sjatkn is what i'd expect. I would drop the connection type unless you use single sign-on and also the commandtimeout, it's usually only put in when people are having timeout issues, though it wont harm to leave it in.
You could use the first full version on all machines, but it's a pain if you ever move the server.
-
-
7th January 2012, 09:36 PM #6 
Originally Posted by
vikpaw
@Little-Miss - tut tut, surely you have backups to double check! The above from is @
sjatkn is what i'd expect. I would drop the connection type unless you use single sign-on and also the commandtimeout, it's usually only put in when people are having timeout issues, though it wont harm to leave it in.
You could use the first full version on all machines, but it's a pain if you ever move the server.
Just rename the new sims server the old ones name
Works! Or use GPO to replace but i would redirect to S: drive.
-
-
7th January 2012, 10:08 PM #7 My old sims server was called admin-six and before that, admin-eight, not the most original. Now it's virtual and has a new meaningful name. I like change, just not the hassle that goes with it.
As i don't manage the network, it's easier to have a system that doesn't rely on GPOs and scripting where possible. Redirect is the way to go.
-
-
9th January 2012, 09:37 AM #8 Redirect are so old school. SOLUS3 baby, one button and you can deploy a new connect.ini across the entire network 
redirect are old because:
- it means you have to have a s drive - teachers don't need it so it's a waste of a connect for most users
- you can get yourself into a messy if you replace your local (redirected) with your central connect.ini - and if staff have read\write to it 
- some 3rd party don't like it
- just plan stupid having to look at a file only to be told to look in another file
-
SHARE: 
Similar Threads
-
By mcnallyfc in forum Windows 7
Replies: 14
Last Post: 31st January 2011, 10:16 AM
-
By EduTech in forum General Chat
Replies: 15
Last Post: 24th January 2010, 02:48 PM
-
By ptaylor in forum MIS Systems
Replies: 1
Last Post: 17th April 2008, 04:44 PM
-
By PHolland in forum MIS Systems
Replies: 8
Last Post: 16th May 2007, 04:31 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules