Well, I'm taking the plunge and I'm going with HSphere, the entry price for the distributed/cluster platform vs everything on a single server just seems the better solution and should be better for my clients.
I just have have one question, after giving the installer complete controll over my servers for the install how do I insure that there are no back doors or bombs waiting to go off?
Originally posted by ckpeter There is really not too many ways; you just have to trust them. This is like asking "How do I ensure Dell will not install spyware on the PC they sell me?"
Except in a couple cases, always install the OS yourself! Especially if you have a Dell... I actually tried using the preinstalled version of windows that came with my Dell for a few days, but it was almost impossible to work with. It came with plenty of adware, probably a little spyware as well...but the worse part was that I couldn't use it for more than 15 minutes without it crashing. I think I *may* have gotten it up to 20 once, but I wouldn't bet on it.
Of course, I wanted to use Windows 2000, so I was going to reformat anyways (it came with Windows ME), but I thought I'd at least see if they made it usable. You're probably thinking what I thought at first too, that most of the crashes were ME's fault. However, I have ME installed now too (mostly for games), and it's been by far the most stable install of a 9x I've ever used. Not quite as stable as 2k of course, but pretty good nonetheless (much more stable than 98SE was on this comp).
Let me restate another example - this is like asking "how do I know CIA isn't installing some kind of device in my PC to monitor my usage?"
The truth (and this is also my point) is that somewhere along you will just have to implicitly trust the technology. If someone is truly paraniod, he should simply build his PC from raw metals and install the control panel he write himself.
Of course, this is an extreme case. But in this case, psoft should be trusted to install h-sphere, just as you trust intel to build your CPU.
In all my internet years, I have not heard a single instance of software developer "activating" any type of bomb. Quite simply, this would instantly kill their sales, since no one would buy such a product.
The only instance where it may be *similar* is when unisys wanted to profit from the GIF format, but they do it from a legal mean, not technical mean.
>>>>I just really wanted to know if anyone had a regiment or written policy they went by after the install...or any horror stories
Like make sure you close all ports on the mail server except 25,110,143 & whatever port the CP uses to control the server and make sure certain directories have this 555 attribute...and so on and so on.
Besides the real bomb maker would be a disgrutle employee not someone who create the software. (or makes money from selling it)
Hey I'm new to the board....I didn't know if any one shared policies or not.