-------- Original Message --------
Subject: Re: NF: [NF] Question(s) about Windows Server software
From: Ted Roche <[email protected]>
To: [email protected]
Date: 12/6/2012 8:24 AM
On Wed, Dec 5, 2012 at 5:40 PM, Mike Copeland <[email protected]> wrote:
Yes, the software vendor needs a Windows OS to run his support utilities
on.
Well, that's one way of developing an app, I suppose. Next time you're on a
support call with them, you ought to ask "What version of Clipper or Visual
Objects are you running?"
Talking to them is a real education in tech support (how not to). I bet
I've asked, at LEAST, 30 questions in the last couple of months talking
to the software vendor, and not one question has received a reply. They
simply continue through the process as if I hadn't said anything. Very
odd folks.
My client, though, has years invested with them so working with them is
not optional.
I wonder why they insist on RDP on the server rather than doing workstation
installs. When you're RDP'ing into the server, you're launching a separate
desktop, right? Is this single user or multi-user software? Perhaps they
don't have locking protocols in place.
They don't actually insist, they just say that "you'll continue to have
data problems and speed issues until you change..." which, to my client
is the same as saying "you must" because heck, who wants data problems
and speed issues?
RDP is what the rest of the world calls virtual terminal, yes. It
launches a little virtual machine in the server's memory and provides a
desktop experience unique to that connection.
The software is multi-user and they do have locking protocols based on
some error messages I've seen ("that record is in use, please wait",
etc.) But they have their data segmented and indexed out the wazoo, plus
they keep log files (text) for EVERYTHING. The folder the application
and the data files are in (all in together) has over 2,500 files in it.
That alone could be a source of speed problems as Windows manages that
many nodes in a single tree.
I've asked if some of the older log files can be moved or deleted to
reduce what is simply clutter...no response.
To be honest, I kind of smelled this coming.
I've worked with a few dev shops who have insisted on hanging onto old
technology, despite the inconvenience it causes their customers. I can't
understand their long-term business vision (if any).
From brief chats with Bob, the actual software coder, I think he's
working to retirement and then lights off. I can identify, but he
clearly doesn't have larger growth on his future-scope just by looking
at his design, his website, his companies staffing. I think they have a
total of 3 people on staff including him. Nothing wrong with that, but
after 15+ years on the market...this is where he's at.
Anyway, thanks to Christof's input and clarification of the MS SERVER MUD,
I've got some $ recommendations together for my client so that if he wants
to "go there" and become another MS-Minion then hey, I see it as a $-income
provider for me! Plus, it'll provide another story for my future clients
about how bad it is to get in bed with any one source of functionality
which then defines your options before you ask.
Viva la OPEN SOURCE!
I've tried to keep my business to database software development, and avoid
being the in-house technical support person for every workstation, router,
cable, printer, etc. However, for client situations like this, I have in
some cases pitched a separate LAMP box for various utility functions: I use
one for secure access into the office (via SSH, and then relaying RDP or
VNC through there), remote backups, fallback copies of their key files if
(when) the Windows server fails, in-house intranet apps, etc. A utility
server like this doesn't have to be anywhere near top-of-the-line and with
some clients I've even set it up as a monthly service fee rather than a
purchase or lease: I own the box, and the client pays for monthly support
hours, part of which funds the cost of the box.
So, even if the client requires one WIndows server, all is not lost. FOSS
still wins in the end.
Agreed. What is a shame, though, is that this client is the "service
repair" department of a larger retail client, and they already have
several Linux boxes that, sometimes, have been online without a hiccup
or reboot for two years+.
Anyway, I'm moving his app and its data to a new, faster, fatter (more
RAM) Linux box this weekend. It has 16GB RAM, and a quad-core I5 running
at 3.3Ghz, a 254GB solid state drive and a 1GB NIC. If he still needs
more go-fast after that, we can build him a MS box and he can start the
march with the other minions.
Mike
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
