...

[toxico.livejournal.com]

Me: We recommend against the use of Terminal Services for this procedure.

Him: Oh, okay, I'll just use Remote Desktop.


O.o

Comments

[thalionar.livejournal.com]

cutest icon :)

[redqueenmeg.livejournal.com]

ZOMG, you talked to that guy too?

He called me last week complaining that he couldn't remote desktop into his other computer so he could access the personal folders stored on its hard drive. My solution of moving the personal folders to his network drive did not impress him.

[jecook]

Heh.

Our crap-tastic HR software at work pretty much says that in order to really run it multiuser, you need to have the database files ON THE TERMINAL SERVER, instead of a network drive, and instead of having all the users in one office talk with it over the LAN, and have all the remote users pop in via the terminal server.

So it's no wonder that the terminal server users get booted out of the thing rather often, because you have several users each connecting to the databases (It's a Foxpro database, I might add) via a mapped network share. This means when user A on the TS logs out, it frequently crashes user B's session on the TS as well.)

The company that wrote the damn thing recommended that we put the databases on the terminal server itself, instead of the network share (where it's backup on a nightly basis. I don't know IF the terminal server has EVER been backed up...) IT also does not help that the data tables are several GIGs, as we've never run any real maintainance or consistancy checks on the thing either.. ::shudder::

All I can hope for at this point is that we migrate to Something Else, rather then wait for the company to push out a "real" database server setup (i.e., SQL server and have clients hit it directly or something, ala Great Pains)

[toxico.livejournal.com]

Large... databases... on...term....

*Event ID 0666: Error accessing higher brain functions at memory address 0x80OMGWTF*

[jacobine.livejournal.com]

My company runs its massive financials program on a set of three load-balanced terminal servers... argh. The fun we've had teaching our users that yes, they must hit logoff, not just X out. They always call and gripe that they can't log in.

Fortunately, said software is actually an interface with the as400, so its data is backed up with both mirroring software on the 400 and tapes daily. We tried running the clients across the network. It killed our network it was so load-intensive.

Oh yes, I just love having to remote desktop into a terminal server whenever I need to set permissions.