Hmmm. If something does what you need it to do, and does it reliably, then in what way does it suck a fat nut, or any other kind of nut? Our company does very well with Outlook, thank you. The integration of its various components is quite impressive to me, and as yet is not matched by anything I've seen on any other platform. Downtime has been minimal in the last five years.
Sincerely, I appreciate where you're coming from. Believe me, we've done the Ghost thing, and we've done windiff until it hurt. Because we tend to buy machines in lots of no more than 5 at a time, we end up having a lot of disparate hardware to support.
Now, we've got various tricks for doing application installs (SMS installer packages) - - but, still, we find that debugging Ghost screw-ups takes as much time as doing a load by hand. Of course, we pull service packs, hotfixes, etc., from a gigabit file server, which speeds things up a little. Still, if you've got people taking a day to load a Windows 2000 machine, there's a real problem. I'm not kidding, there's no excuse for that on a regular basis. You might run into a troublesome unit from time to time, but commodity desktops from folks like HP, Dell, etc., should go very quickly. Heck, we even have to wipe off the XP installation before we start, because we do not allow that OS on our network at this point. The longest part of the process is formatting large partitions, and in many cases, we choose to use only a fraction of the available disk bytes.
Heh, I know what you mean. Where I work, I supervise a couple of techs who each generally have to do at least 2-3 installs per day of Windows 2000. We don't use imaging because, frankly, we find that it sucks - - quicker to do straight loads of the OS as well as our company apps. Anyway, I or my techs can have four units on a KVM at one time, and we can knock those out in a little over an hour for the whole bunch. I don't know why Linux people seem to have so much trouble with it.;)
Also, with regard to Windows Update - - it's a good service. I'm an apt-get user myself (Redhat), and, hey, that first distribution update can be plenty big. Nobody should blame MS for putting out updates - - it's what they've needed to do for many years.The rebooting in Windows gets very old, though, without a doubt.
Yep, I'd missed this detail - - apologies to Boies, et.al. Doesn't change my opinion of Boies' involvement - - just means he'd like an even bigger take if SCO's bullsh*t case pans out.
Mr.Boies, heading the SCO "legal" team, epitomizes what a great many people despise about lawyers. Truth is not what Boies seeks - - it's billable hours, and SCO are the suckers who'll have to pay the bill. I'm sure that, by now, even Boies recognizes that there's no stopping the Open Source juggernaut. But why should he care about that? Even if his case is flushed down the crapper, he'll walk off with millions. Gates, likewise, will capitalize from this sad and misguided effort by SCO for a while. But I submit to you that even Gates sees the inevitable outcome, which, at the very least, is a MORE publicized Open Source movement. In the advertising world, all publicity, good or bad, is exposure which can be spun to one's own benefit. Unfortunately, SCO stockholders will profit from this very principle, too, even if their case tanks.
Harrison Ford escapes from the old folks' home in his wheelchair and finds the Fountain of Middle Age in a Roman temple, where a 19-year-old nymphomaniac falls hopeless in love with him for 17 minutes and then he flies away in his airplane.
We have a Systems Management Server running on NT4/SQL2000 that inventories hardware and software on about 220 workstations and a couple dozen servers on a daily basis. It churns the data and produces a patch report indicating what patches have been distributed and which ones, available from Microsoft, need to be distributed based on the OS, browser version, etc., that each host is running. I construct the patch package and distribute it once a week. Maybe a network that size doesn't impress many readers here, but for me and only two other techs, it's a lot of work, and the reliability of that SMS server counts for a lot. I can remember when the patch process was mostly manual, and it was no fun.
I can go along with that. And, indeed, most of our NT servers were set up to do a general sort of job and live out their lives in that one configuration. It is also true that, before NTFSDOS and the advent of other bootable recovery tools we take for granted now, NT admins lived in fear of the BSOD. This went double for Exchange 5.5 running on NT. DLT tape drives have been our friends and saviors on many occasions. All in all, though, and even as a Linux-head, I still have an appreciation for NT. Compaq did a particularly good job of supporting NT in its Proliant line of servers, and setups, ROM updates, etc., were always comfortable operations as long as one had the latest version of SmartStart. Running hardware RAID5 - - as we always have on the venerable Smart 2SL and SA 3200 boards - - helped us sleep at night, too. Now, we find that these old Proliants adapt well to Linux, and as NT4 licenses are retired, RedHat proliferates. Fun!
Yeah, NT is not *nix. Yeah, NT isn't a lot of things. But I've worked with it since SP1, and, you know, once you get used to it, you can get a lot of productivity out of it. So much depends on drivers and, of course, program code. These days, NT lacks some refinement. So does Linux, for that matter. Nonetheless, after 6 1/2 service packs, NT delivered (and continues to deliver) a fair amount of bang for your hardware buck. In some ways, it is refreshing to use a product that is not weighed down with useless features. Our remaining NT servers, running on Compaq Proliant 1600 hardware, are fine producers. And contrary to myth, they do NOT have to be rebooted every day, every week, or even every month. This isn't a Microsoft ad - - I'm leading the charge away from MS products at my company. But I will give some credit where it's due.
How about they come up with a Kona plant that grows to maturity in your back yard in less than one month?
Ask anyone in HR . . . .
on
Ageism in IT?
·
· Score: 2, Informative
When available at a price within budget, a qualified person with maturity will get the job at a company worth working for. Why? Because every survey shows older workers are more loyal, more stable, and more willing to commit. I was at the hiring end for 10 years, and I endorse this point of view. When youthful energy is needed, hire on a contract basis, then get them out the door. Between the ages of 20 and 30, most intelligent people are looking for the very best gig they can find, which means they'll dump you in a second if need be. The older worker typically is not quite so quick to move, and gives you all the other premium character traits one associates with maturity to boot.
"Remember that a good flame, even one with such base ghetto trash talk and grammatical errors to make even myself blush takes a considerable amount of intelligence and wit to write."
Actually, I've seen robots in chatrooms provide wittier and more coherent rebuttals. So, you are wrong, whoever you are. It takes intelligence to write the bot code, but not to spew blather.
Proving malice is a bitch. Showing that someone wrote with reckless disregard for the truth with the intent to do harm can be difficult if the writer can back up even a part of his work with facts. The gamer's online records can be brought into court, as can any number of other factual items having to do with this gamer's lifestyle.
I do know of a group that pulled it off very nicely, and they - - as well as the former (university)employer were, and are, happy. The spinoff group was able to take on consulting jobs while, at the same time, selling their services back to the university. The university was happy because they no longer had to offer benefits, do payroll, etc. After more than two years, this arrangement is still working out for everyone involved. Sorry, I can't give names, but the university in question is a top-rated one in the southeast, and the IT group in question primarily provided web and data management services.
. . . the SuSE or Redhat collaboration product that will allow me to pull the information store from Exchange 5.5 right onto an Outlook-compatible platform running on Linux or *BSD. And yes, my company will pay good money for it if it comes from either of the aforementioned firms. But this is certainly a nice looking and ambitious product from a company that is already known for bringing good stuff to commercial Linux.
Slashdot Mirror
Hmmm. If something does what you need it to do, and does it reliably, then in what way does it suck a fat nut, or any other kind of nut? Our company does very well with Outlook, thank you. The integration of its various components is quite impressive to me, and as yet is not matched by anything I've seen on any other platform. Downtime has been minimal in the last five years.
Still, the quest for quality must go on. Which is easy for me to say, since I don't do code. Sorry.
My parents never seemed to feel safe when I was blowing things up.
Sincerely, I appreciate where you're coming from. Believe me, we've done the Ghost thing, and we've done windiff until it hurt. Because we tend to buy machines in lots of no more than 5 at a time, we end up having a lot of disparate hardware to support.
Now, we've got various tricks for doing application installs (SMS installer packages) - - but, still, we find that debugging Ghost screw-ups takes as much time as doing a load by hand. Of course, we pull service packs, hotfixes, etc., from a gigabit file server, which speeds things up a little. Still, if you've got people taking a day to load a Windows 2000 machine, there's a real problem. I'm not kidding, there's no excuse for that on a regular basis. You might run into a troublesome unit from time to time, but commodity desktops from folks like HP, Dell, etc., should go very quickly. Heck, we even have to wipe off the XP installation before we start, because we do not allow that OS on our network at this point. The longest part of the process is formatting large partitions, and in many cases, we choose to use only a fraction of the available disk bytes.
Heh, I know what you mean. Where I work, I supervise a couple of techs who each generally have to do at least 2-3 installs per day of Windows 2000. We don't use imaging because, frankly, we find that it sucks - - quicker to do straight loads of the OS as well as our company apps. Anyway, I or my techs can have four units on a KVM at one time, and we can knock those out in a little over an hour for the whole bunch. I don't know why Linux people seem to have so much trouble with it.
Also, with regard to Windows Update - - it's a good service. I'm an apt-get user myself (Redhat), and, hey, that first distribution update can be plenty big. Nobody should blame MS for putting out updates - - it's what they've needed to do for many years.The rebooting in Windows gets very old, though, without a doubt.
http://www.zdnet.com.au/newstech/os/story/0,20000
Yep, I'd missed this detail - - apologies to Boies, et.al. Doesn't change my opinion of Boies' involvement - - just means he'd like an even bigger take if SCO's bullsh*t case pans out.
Where did you get this information? I've not seen anything to suggest Mr. Boies' firm is working on a contingency basis. Links?
Mr.Boies, heading the SCO "legal" team, epitomizes what a great many people despise about lawyers. Truth is not what Boies seeks - - it's billable hours, and SCO are the suckers who'll have to pay the bill. I'm sure that, by now, even Boies recognizes that there's no stopping the Open Source juggernaut. But why should he care about that? Even if his case is flushed down the crapper, he'll walk off with millions. Gates, likewise, will capitalize from this sad and misguided effort by SCO for a while. But I submit to you that even Gates sees the inevitable outcome, which, at the very least, is a MORE publicized Open Source movement. In the advertising world, all publicity, good or bad, is exposure which can be spun to one's own benefit. Unfortunately, SCO stockholders will profit from this very principle, too, even if their case tanks.
Harrison Ford escapes from the old folks' home in his wheelchair and finds the Fountain of Middle Age in a Roman temple, where a 19-year-old nymphomaniac falls hopeless in love with him for 17 minutes and then he flies away in his airplane.
We have a Systems Management Server running on NT4/SQL2000 that inventories hardware and software on about 220 workstations and a couple dozen servers on a daily basis. It churns the data and produces a patch report indicating what patches have been distributed and which ones, available from Microsoft, need to be distributed based on the OS, browser version, etc., that each host is running. I construct the patch package and distribute it once a week. Maybe a network that size doesn't impress many readers here, but for me and only two other techs, it's a lot of work, and the reliability of that SMS server counts for a lot. I can remember when the patch process was mostly manual, and it was no fun.
I can go along with that. And, indeed, most of our NT servers were set up to do a general sort of job and live out their lives in that one configuration. It is also true that, before NTFSDOS and the advent of other bootable recovery tools we take for granted now, NT admins lived in fear of the BSOD. This went double for Exchange 5.5 running on NT. DLT tape drives have been our friends and saviors on many occasions. All in all, though, and even as a Linux-head, I still have an appreciation for NT. Compaq did a particularly good job of supporting NT in its Proliant line of servers, and setups, ROM updates, etc., were always comfortable operations as long as one had the latest version of SmartStart. Running hardware RAID5 - - as we always have on the venerable Smart 2SL and SA 3200 boards - - helped us sleep at night, too. Now, we find that these old Proliants adapt well to Linux, and as NT4 licenses are retired, RedHat proliferates. Fun!
It appears our system has been penetrated by an actual real-world administrator. All hands on deck. Attack! Attack!
Yeah, NT is not *nix. Yeah, NT isn't a lot of things. But I've worked with it since SP1, and, you know, once you get used to it, you can get a lot of productivity out of it. So much depends on drivers and, of course, program code. These days, NT lacks some refinement. So does Linux, for that matter. Nonetheless, after 6 1/2 service packs, NT delivered (and continues to deliver) a fair amount of bang for your hardware buck. In some ways, it is refreshing to use a product that is not weighed down with useless features. Our remaining NT servers, running on Compaq Proliant 1600 hardware, are fine producers. And contrary to myth, they do NOT have to be rebooted every day, every week, or even every month. This isn't a Microsoft ad - - I'm leading the charge away from MS products at my company. But I will give some credit where it's due.
Mine does THAT as well.
How about they come up with a Kona plant that grows to maturity in your back yard in less than one month?
When available at a price within budget, a qualified person with maturity will get the job at a company worth working for. Why? Because every survey shows older workers are more loyal, more stable, and more willing to commit. I was at the hiring end for 10 years, and I endorse this point of view. When youthful energy is needed, hire on a contract basis, then get them out the door. Between the ages of 20 and 30, most intelligent people are looking for the very best gig they can find, which means they'll dump you in a second if need be. The older worker typically is not quite so quick to move, and gives you all the other premium character traits one associates with maturity to boot.
Fear not.
Interesting, in a clinical sense. One can only imagine the number of psych dissertations spawned in these sites.
"Remember that a good flame, even one with such base ghetto trash talk and grammatical errors to make even myself blush takes a considerable amount of intelligence and wit to write."
Actually, I've seen robots in chatrooms provide wittier and more coherent rebuttals. So, you are wrong, whoever you are. It takes intelligence to write the bot code, but not to spew blather.
Let's get you educated in the fine art of spelling. From there, grammar. Then, onto rational thought.
Proving malice is a bitch. Showing that someone wrote with reckless disregard for the truth with the intent to do harm can be difficult if the writer can back up even a part of his work with facts. The gamer's online records can be brought into court, as can any number of other factual items having to do with this gamer's lifestyle.
LOL! Somehow, though, I suspect the "real" thedeacon is more articulate.
Truly, truly pathetic. Get busy living, or get busy dying, to quote that guy from Shawshank.
I do know of a group that pulled it off very nicely, and they - - as well as the former (university)employer were, and are, happy. The spinoff group was able to take on consulting jobs while, at the same time, selling their services back to the university. The university was happy because they no longer had to offer benefits, do payroll, etc. After more than two years, this arrangement is still working out for everyone involved. Sorry, I can't give names, but the university in question is a top-rated one in the southeast, and the IT group in question primarily provided web and data management services.
. . . the SuSE or Redhat collaboration product that will allow me to pull the information store from Exchange 5.5 right onto an Outlook-compatible platform running on Linux or *BSD. And yes, my company will pay good money for it if it comes from either of the aforementioned firms. But this is certainly a nice looking and ambitious product from a company that is already known for bringing good stuff to commercial Linux.
. . . not such a great indicator for future productivity of males between the ages 3-21 years.