Slashdot Mirror


IT Practice Within Microsoft

SilentChris writes "Good article over at CNet regarding Microsoft's internal IT practices. Some intriguing statements from the CIO, from the obvious ('It's an easy choice for me--to run Microsoft technology. We don't run Unix. We don't run Linux. We don't run Oracle.') to the not-so-obvious ('Our users are the admins of their machines. They can load whatever software they want on their machines, but we do audit the network continuously.') I wonder how much time is spent combatting spyware?"

88 of 508 comments (clear)

  1. No wonder they're laggin behind... by Folmer · · Score: 4, Insightful

    I thought that it was normal corporate behaviour to look at their competitors. Long time ago there was a story here on /. where one of the lead devs of IE admitted that he ran firefox. But when this guy doesnt run *nix and oracle, how should he be able to compete with them?

    1. Re:No wonder they're laggin behind... by ERJ · · Score: 5, Insightful

      Eh, this is talking about their IT infrastructure. It would look pretty bad if it was based on unix servers and oracle databases.

      I'll bet you anything that they have unix servers and oracles databases for comparison purposes though.

    2. Re:No wonder they're laggin behind... by fitten · · Score: 5, Insightful

      Maybe because this is the company's internal IT practices, basically what they do to run their shop. He isn't talking about the product strategy groups who go off and do exactly what you are saying.

    3. Re:No wonder they're laggin behind... by nadadogg · · Score: 2, Funny

      Maybe because this is the company's internal IT practices, basically
      I know I'm not the only person who read that as infernal IT practices.

      --
      i use linux and windows oh god how can i have an opinion
    4. Re:No wonder they're laggin behind... by sphealey · · Score: 4, Interesting

      A few years ago I read an interview with Novell's IT Director. She stated that she had NT, Unix, etc running on her network and when asked why replied that there were two reasons: because she deployed the best application for any purpose regardless of platform, and so that Novell employees would experience what their customers experience.

      I know which philosophy I as a customer prefer my vendors have.

      sPh

    5. Re:No wonder they're laggin behind... by danheskett · · Score: 2, Interesting

      It's impossible for Novell to eat only their own dogfood. Microsoft, on the other hand, can and should be forced to do exactly that.

    6. Re:No wonder they're laggin behind... by Tassach · · Score: 2, Insightful
      if [Microsoft products] were inadequate for even internal use, how could they hope to compete on the open market
      A few ideas:
      • Spread FUD about competing products
      • Shmooze CEO/CIOs of large companies, send them on expense-paid junkets & other semi-legal bribery tactics to get them to purchase MS product.
      • Bundle defective/inferior software with operating system.
      • Force OEM hardware vendors to ship product pre-installed on their systems and prohibit them from pre-installing competing products.
      • Sell product at a loss (or give it away) until all serious competitors go bankrupt.
      • Buy out competing company to suppress their product, preferably after having forced them into bankruptcy (or at least seriously damaging their market value)
      • Release "service pack" which breaks competing product
      • Illegally use monopoly power to extend monopoly into new markets.

      Did I miss any typical M$ business practices?

      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    7. Re:No wonder they're laggin behind... by banzai51 · · Score: 2

      Horsepuckey. If you (and slashdot) found out MS was running anything else BUT MS products for internal use you'd throw a fit and condemn 'em. And personally, I'd rather use a product that the developer themselves would trust end to end.

    8. Re:No wonder they're laggin behind... by Tassach · · Score: 2, Informative
      Microsoft is developing apps only for their own platform
      Wrong.
      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    9. Re:No wonder they're laggin behind... by tomhudson · · Score: 3, Interesting
      Funny how they (Microsoft) change their story as time goes on ...

      Remember this (the original link no longer works, but a copy of the relevant text was preserved) http://support.microsoft.com/support/kb/articles/Q 80/5/20.ASP

      http://www.elists.org/pipermail/lugga/2000-May/000 468.html
      - quoted below, describing Microsoft's process for making their master CDs using UNIX:

      -snip-

      Release Insertion Into Manufacturing Network

      The master is read into a UNIX-based disk duplication system. The system creates an exact disk image of the master, duplicating the format and data. A duplicated masters is created from the original read in image. This silver master is used by the Product Group in their review, before they sign-off. The silver master is not to be used in the Release to Manufacturing (RTM) process. The golden master, delivered by the product group to the release group, is the original image, and is released to manufacturing when the final approvals are received from the product groups.

      -snip-

      Duplication Process

      Disks are duplicated on a variety of industrial strength, quality focused systems. Most of these systems are UNIX-based. The UNIX-based duplication systems used in manufacturing are impervious to MS-DOS-based, Windows- based, and Macintosh-based viruses. The few MS-DOS-based and Windows-based standalone duplication systems do not allow MS-DOS-based operating systems to access the duplication system. Virus protection systems used by these MS-DOS-based and Windows-based duplication systems strictly govern the duplication process, even when they are not running.

    10. Re:No wonder they're laggin behind... by Profane+MuthaFucka · · Score: 2, Interesting

      That would be impossible, because it's a violation of the Oracle license to do a benchmark. MS would never violate the license, I am sure.

      --
      Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
    11. Re:No wonder they're laggin behind... by Homology · · Score: 2, Insightful
      It's MS's "eat-your-own-dogfood" policy.

      MS does not use the crappy Visual Source Safe, but an adapted Perforce

    12. Re:No wonder they're laggin behind... by FuzzyBad-Mofo · · Score: 2, Interesting

      Embrace and extend, though that might be part of "Illegally use monopoly power to extend monopoly into new markets."

    13. Re:No wonder they're laggin behind... by dingfelder · · Score: 4, Informative

      errr.. they do have unix boxes:

      Although MS has replaced some of hotmail from bsd to win2k, for other portions, win2k is just not powerful enough to replace the Solaris UNIX back-end.

      Quote:

      (from http://www.freebsd-corp-net-guide.com/rejrev/pref- 1.html)

      In the first section of the Preface, I cite the Microsoft-owned Hotmail service as an example of a major production facility that uses FreeBSD. Several reviewers pointed out that after Hotmail was purchased by Microsoft, they commenced a program to eliminate all usage of FreeBSD and replace it with Windows 2000, and that citing Yahoo as being entirely run on FreeBSD (which it is) would be a better cite.

      I rejected this purely for political reasons. Most people aren't aware of this, but Microsoft itself extensively used BSD UNIX for years for Internet serving through the Windows NT 3.51 days. This continued well into the Windows NT 4.0 days, although during that time the company began hard efforts to switch away from BSD UNIX to NT. This was not done because NT was technically superior but rather because Microsoft wanted to "eat their own dog food" as the industry line goes.

      The upshot of this is present even today. Microsoft uses Conexxion as their principal offsite FTP service to distribute upgrades of Microsoft Internet Explorer and other programs, purely for this reason. It is simply because NT 4.X and even Windows 2000 is not capable of serving such a large volume of files onto the public Internet. Other companies, such as Walnut Creek/BSDi and Sun, have no problems distributing just as large an amount of data because they use UNIX. Microsoft has mandated that this kind of file update only occur over NT/Win2K. As a result, it takes an entire plant stuffed to the gills with NT servers to accomplish the same thing that only a few UNIX servers are needed to do. After all, when the work is continually subdivided, eventually the limits of NT's abilities are reached. Because of having to involve so many NT servers, it turns what would be a simple task under UNIX into a giant task involving hundreds of people. In short, it cannot be done in-house anymore and must be turned over to an entirely separate company that specializes in distributing large quantities of files with Windows platforms. While every other major company that uses UNIX like Solaris or the FreeBSD operating system can distribute large numbers of files over the Internet without a lot of expense and effort, Microsoft--purely for marketing reasons--has to hamstring themselves and spend millions of unnecessary dollars. The fact that they admit this and were unable to redesign Hotmail into an Windows-only service deserves to be made obvious.

      The final word on the Hotmail affair is this: FreeBSD is used as the "front end" mail processing part of the service. Sun's Solaris is used as the "back end" mail processing part of the service. Only the FreeBSD front-end has been replaced with Windows. Microsoft still cannot get Windows 2K to be powerful enough to replace the Solaris UNIX back-end.

      end quote

      Additionally, in their own whitepaper about the bds portion being migrated to win2k, (references here - http://www.theregister.co.uk/2002/11/21/ms_paper_t outs_unix/) they themselves state all sorts of advantages of unix, such as kernel stability, processing ability and complexity of windows.

      a good read :)

    14. Re:No wonder they're laggin behind... by YU+Nicks+NE+Way · · Score: 3, Informative

      Except that statement is no longer true. The back end migrated to Win 2K about two years ago. All the FreeBSD servers are long gone.

  2. Longhorn? by kmmatthews · · Score: 5, Funny
    I wonder how much time is spent combatting spyware?

    Aha! So that's why longhorn is taking so many years to write..

    --
    feh. stuff.
    1. Re:Longhorn? by alw53 · · Score: 4, Funny

      At least their marketing department has figured out how dumb it is to name an OS for the year of its anticipated release.

    2. Re:Longhorn? by mallardtheduck · · Score: 3, Informative

      NTFS was first used in Windows NT 3.1... Its more like 10 years old...

  3. I wouldn't want that guy's job by Trekologer · · Score: 2, Funny

    I'm sure his relatives call him up constantly when their computer has problems.

  4. Spam by Fruvous · · Score: 2, Insightful

    "We get 10 million e-mails a day coming into Microsoft. We delete more than 9 million of those as spam." Well I wonder why you're so popular...

    --
    This is one of those witty signatures that you'll remember.
  5. Misquoted by HungWeiLo · · Score: 5, Funny

    "We don't run Linux....we run GNU/Linux"

    --
    There are a huge number of yeast infections in this county. Probably because we're downriver from the bread factory.
  6. Comedy... by NecroPuppy · · Score: 5, Funny

    users are the admins of their machines.

    So even Microsoft has realized you can't do crap under a limited login in XP.

    --
    I like you, Stuart. You're not like everyone else, here, at Slashdot.
    1. Re:Comedy... by EnronHaliburton2004 · · Score: 2, Informative

      Tell me you don't have root access to your workstation... If you do, then are you login as root at all time?

      Regular users and developers don't usually need admin access to their workstations.

      You can design the workstation in a way that lets a regular user install software, but still keeps the rest of the system protected. They can install software to their home directory, or you can create a special partition named '/devel', with /devel/bin /devel/etc, etc. and give them full access.

      That way, they can install software without interfering with the critical utilities in /bin or /etc.

      This works in most cases.

    2. Re:Comedy... by Stile+65 · · Score: 2, Informative

      Check out (in the Group Policy editor) "Software Settings." You can set software up to either be available for the user to install through Control Panel|Add/Remove Software, or to push it so it installs for the user automatically.

      --
      I claim first use of "Error No. 0B" - or "No. 0B error." It'll be the new ID 10T!
    3. Re:Comedy... by FirstTimeCaller · · Score: 2, Funny

      users are the admins of their machines.

      But are they masters of their domain?

      I suspect not.

      --
      Wanted: witty unique signature. Must be willing to relocate.
    4. Re:Comedy... by omicronish · · Score: 2, Insightful

      I know it's a joke, but when you need to do stuff like kernel debugging, testing stuff with GDI, yes, you need Admin privileges. It's unavoidable. However (I worked there as an intern this past summer), they do emphasize non-admin accounts when possible, and certainly for application-level work it's doable. I did it at work, and I do it at home.

      A lot of people complain about Microsoft making Windows unusable with non-admin privileges, but I honestly am using it fine with such privileges. Sure, every once in a while I need to install an application, in which case I right-click the installer and select Run As (I think press Shift if you don't see that menuitem), and games are notoriously bad for requiring admin privileges to do CD checking, but stuff like running Word, coding in VS.NET, and surfing are entire doable without admin privileges.

      As an aside, I've found that with games, cracking the game and making their entire directory world writable works almost all the time if you want to run as non-admin. Although it's even nicer when they don't require CD checking such as *ducks* Steam HL2 and UT2004.

  7. No surprise here by poot_rootbeer · · Score: 2, Funny


    Of COURSE they allow users to admin their own machines at Microsoft. Half of their software won't run correctly in XP unless the user has Administrator privileges.

    1. Re:No surprise here by wibskey · · Score: 2, Insightful

      Here I am, as an admin, trying to make sure all of our applications work on XP with regular user ID's, and it's so frustrating.

      I get so pissed when I hear that some third party application requires admin to run... now I find out the people writing the OS are running it as admins. So much for these bugs coming out in the wash... then again, for MS, the end user is considered "the wash".

      For someone who has to deal with these problems all the time, reading something like this is very discouraging.

  8. Admins of their own machines by enkafan · · Score: 4, Informative

    If you follow blogs.msdn.com, you'll find that while many people are admins of their own machine, they rarely actually run as admin. I think all they are saying is that they don't take away the power of the user to be able to install their own hardware or software. But the vast majority of people working at MS seem to understand the risk involved as running as an admin at all time.

    1. Re:Admins of their own machines by LurkerXXX · · Score: 3, Interesting
      Apparently you can't read. He didn't say they were Administrator if their DOMAIN. He said they were the admin of their own machine. HUGE difference. Apparently you have no clue how MS domain/security works.

      And as far as for being an admin of your machine, it does not mean you are running as admin all the time. Locally most folks here have an admin username they can log into to install software on their machines when needed. They also have a regular normal username they use to log in as a normal user to do their work.

  9. Common by over_exposed · · Score: 2, Interesting

    Our 800+ users all have local admin rights on their machine. Why? We run some software that doesn't work otherwise. It's an AS400 client that needs admin rights to install updates to the client.

    Now, in all fairness, there is a way around it (and we're exploring it). The problem is, that while revoking local admin rights for our users would save us lots of time and effort in combatting spyware, etc, we'll use that time manually updating the AS400 client software.

    --
    "The object of war is not to die for your country, but to make the other bastard die for his." - Patton
  10. No, that one is obvious too by PhysicsGenius · · Score: 5, Insightful
    Our users are the admins of their machines. They can load whatever software they want...

    That's the only way to run a network of computer-savvy users. Imagine a metalworking shop that wouldn't let the machinists adjust their own wrenches. You'd have to put a call-ticket in to "Tool Technology Support" and after a few hours (if you are lucky) or days (if you aren't) some kid comes over who doesn't know anything and tries to adjust your hammer.

    1. Re:No, that one is obvious too by COMON$ · · Score: 2, Insightful

      How many networks are full of network savvy users. And even if you did have some people who Think they are network Savvy would you want them screwing with the settings? I believe that most people who are not network admins do not understand the implications of making everyone an Admin on their box. Major rule of networking....NEVER give someone more privelages than they need to do their job. That rule goes across the board, microsoft or non-microsoft.

      --
      CS: It is all sink or swim...oh and did I mention there are sharks in that water?
    2. Re:No, that one is obvious too by Doctor+Crumb · · Score: 3, Insightful

      Most programmers are not sysadmins. A better analogy would be a metalworking shop that wouldn't let the truck driver adjust the wrenches. He may or may not be qualified to do it, but it's not his job.

      If you are one of those rare programmers with sysadmin skills, get a job as a sysadmin and you will quickly learn that most users should not be let anywhere near a computer, let alone given admin.

    3. Re:No, that one is obvious too by IceFox · · Score: 3, Insightful

      It all make sense!

      So this is why users in the real world need admin! Until internally they force their developers to only use user account there will always be problems. As a developer I can bet you that if I always have admin I will take the shortcut and not bother making sure it works 100% if I run it as a user that has no admin right. I always wondered why so many of their apps (MS Word needs write access to win32/ ???) require that you let them touch (not just read) files outside of your home directory. Know I know.

      Well I am happy. With this knowledge I know that Longhorn wont force users to only write to home directories like in Unix/Linux and virus's/bugs/spyware will continue to exists and they will only cause their Microsoft own downfall. This was the only feature that I figured would save Microsoft.

      -Benjamin Meyer

      --
      Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
    4. Re:No, that one is obvious too by Stradivarius · · Score: 3, Insightful

      A closer analogy would be that the machinist has a better wrench out in his truck but isn't allowed to just bring it in the building and use it. First he must put in a call-ticket, then hope that the helpdesk is willing to send somebody out to his truck, carry the new wrench inside, and put it in his working area. Because "it's not the machinist's job" to do that stuff.

      The point is that centralizing common and simple tasks wastes everyone's time - the support guy and machinist alike.

      Helpdesk is probably understaffed, and almost certainly has (at least from their perspective) more important things to do. Meanwhile, the machinist is stuck with an inferior tool until he can work the bureaucracy to get the new wrench in.

      The company loses too because it's using inferior tools, simply because the guys who use them aren't empowered to change their work environment.

      And not only is it extraordinarily difficult to bring in new but known-to-be-better tools (sometimes even free ones!), but forget trying to experiment with a tool to find out if it's better. Try convincing an overworked support guy that you really need this application installed because you want to try it out. You'll see snowballs in hell before that tool gets installed. Not through any fault of the support guy - he's just being rational and allocating his limited time to higher priorities. But the system is clearly flawed.

      In contrast, if the developer could admin his own machine, he could install something, try it out, and if it's helpful other developers could start using it too.

      Now is it possible that the developer could accidentally install malware if he has admin? Sure. But that's why Microsoft monitors their network - they can catch and correct mistakes that happen. They no longer handicap the developers, and IT doesn't have to babysit on simple things like application installs. The company reaps the productivity awards accordingly.

      Car manufacturers and other corporations learned years ago that giving the person closest to the problem the power to solve it lets them avoid bottlenecks and reap massive productivity gains. Somehow, the conventional wisdom on IT management hasn't quite caught up yet with the rest of the management world.

    5. Re:No, that one is obvious too by Lodragandraoidh · · Score: 2, Insightful

      I've been a sysadmin and a developer and project manager (as well as tech support etc...).

      Your assumption, 'that sysadmins know what they are doing and programmers do not' is a fallacy.

      Just as there are inept users, there are inept sysadmins - and even good sysadmins can have their moments. I have seen sysadmins do really boneheaded things - primarily because they are focussed on the OS, as opposed to understanding how that OS interacts with applications and services running on the machine.

      The real answer is for people to become acutely aware of how their actions can effect how a system works, or doesn't work holistically - and know what you are doing before you do it. This is particularly important for mission critical servers where one slip of the mouse can put clients offline for hours.

      If a user or a sysadmin for that matter consistently screws things up - then you need to start questioning their access to the system to begin with; maybe they are in the wrong line of work?

      --

      Lodragan Draoidh
      The more you explain it, the more I don't understand it. - Mark Twain
    6. Re:No, that one is obvious too by Grishnakh · · Score: 2

      This just shows how screwed up Windows is.

      In a Unix environment, a developer does NOT need the ability to install software. "Installing" software in Unix means putting it in a central place where all users can access it. As a developer, you don't need to do this; you just need to put it in your local directory and develop and test it there. If other people want to try it out, they can go there and try it as well (assuming you gave them read permission). When you're ready to deploy it to the entire company, then you get the sysadm to install it in one of the company's main directories (like /usr/company/bin, usr/toolname, etc). If you're just working on a tool for your workgroup, you don't even need this; you'll probably have an area set aside for your workgroup where all the members of that group have read and write permissions. Then you can manage yourselves within that directory. But because your group doesn't have permissions to other groups' areas, you can't screw up their stuff.

      The only time a Unix developer needs system-level permissions is if he's actually working on the OS itself. And in this case, he shouldn't be on a normal workstation connected to the network; he should be on a special standalone system, perhaps connected to a dedicated network for testing.

      The fact that Windows doesn't work this way, and requires that normal users be given system-level priveleges for things which really don't need access to them, shows how flawed its design is, and why it has so many problems with security. If you're in a workgroup, and all the developers are screwing around with their OS's internal settings, how are you supposed to be able to remotely login to their machines and expect the same environment you have on yours. In my work, I constantly rlogin to multiple machines in order to execute jobs. These machines absolutely must behave the same. If one of them has a configuration problem that prevents it from running a job properly, that machine has to be taken down by IT and diagnosed and repaired, which removes one compute resource from our pool. A significant number of these would affect our schedule.

    7. Re:No, that one is obvious too by Anne+Thwacks · · Score: 2, Interesting
      Tool Technology Support

      Actually, he is called a tool setter, and that IS how its done.

      --
      Sent from my ASR33 using ASCII
  11. Software Audits? by EdwinBoyd · · Score: 5, Funny

    "Well Johnson, we found the latest build of Firefox on your machine and a copy of OpenOffice. Clear out your desk by noon"

  12. Nice Knee-Jerk by FortKnox · · Score: 4, Informative

    They can load whatever software they want on their machines, but we do audit the network continuously.') I wonder how much time is spent combatting spyware?

    I am a software consultant. The first thing I usually need when I go to a new client is to have local admin to run various coding tools (app servers, for example).
    Do those clients have spyware running rampant? No, because the people that have local admin aren't idiots. I'm sure MS spends time educating non-techies on what to d/l and what not to. Its not surprising nor do I necessarily think its a bad thing for people to have local admin on their machines.

    Of course, if this wasn't about MS, I'm sure no one would care... but some people simply need someway to stick it to MS....

    --
    Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
  13. Don't run unix, eh? by TheGrayArea · · Score: 4, Interesting

    I guess that means they finally upgraded the phone system. Back when I worked there in Developer Suppport (98-03) the phone system for our incoming customer calls ran on a Unix system. To run the phone monitoring application and see the various queues you had to run an X-desktop emulator (Hummingbird I think) to run the monitoring app. I always thought that was funny at the time.
    We were allowed to pretty much install anything we wanted to. I had tons of command line tools, perl and other stuff installed along the way.
    Oh, and lots of guys had Linux boxes running at their desks along the way as well.

    --

    This space for rent.
  14. We don't run Unix. We don't run Linux. by Zocalo · · Score: 4, Insightful

    So, if "We don't run Unix. We don't run Linux.", then WTF did Microsoft feel the need to pay SCO all those millions of dollars for UNIX licenses? Unless, of course, the money actually came out of the "Marketing/FUD" budget instead the "Software Licenses" budget...

    --
    UNIX? They're not even circumcised! Savages!
    1. Re:We don't run Unix. We don't run Linux. by justins · · Score: 3, Informative

      http://www.microsoft.com/windows/sfu/

      Of course Interix or whoever MS bought the thing from probably paid the piper already, but knowing SCO's proclivity for lawsuits, I don't blame MS for doing it again.

      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    2. Re:We don't run Unix. We don't run Linux. by Keeper · · Score: 2, Funny

      For their SFU (Services for Unix) product. I'm sure the irony or the acronym wasn't lost on the person who came up with the name...

  15. There's definite pockets of non-Microsoft use... by argent · · Score: 3, Informative

    If you read MSDN blogs you occasionally come across references to people using non-Microsoft software, including Firefox, Apache, and *nix. Hotmail uses UNIX tools running on Interix... which includes the "viral" GCC.

  16. Pain by Icarus1919 · · Score: 2, Funny

    We start with the product group that developed the product, so they feel the pain first. Man, truer words have never been spoken (at least by an MS executive.)

  17. combatting spyware by mgpeter · · Score: 2, Insightful

    Some of the spyware that is out there will utilize known security vulnerabilities to install itself on the machine WITHOUT the user being an Administrator.

    Also, quite a bit of spyware will simply install itself to the user profile (hotbar, etc.), the only way to combat these types of spyware is to utilize Mandatory Profiles.

    Spyware is an ongoing problem with ANY Windows machine, whether it is "secured" or not.

  18. Software company, not bozos by dazedNconfuzed · · Score: 5, Insightful
    ('Our users are the admins of their machines. They can load whatever software they want on their machines, but we do audit the network continuously.') I wonder how much time is spent combatting spyware?"


    Pardon me for standing up for them, but ... it's MICROSOFT. They have a lot of smart talented software engineers who are just as capable of administrating their own computers as those writing for /. - and whatever is missed, like some spyware, gets picked up by the continuous network audit.


    Peeves me off when the people writing the software are not trusted to administrate their own computer which they are writing software for (or some equivalent thereto). What's with this growing American sentiment that nobody should be trusted with tools, that only someone special should be (without noting the perversity that if nobody can be trusted, then nobody can be trusted)?

    --
    Can we get a "-1 Wrong" moderation option?
    1. Re:Software company, not bozos by jedidiah · · Score: 2, Insightful

      There's quite a difference between having a key to the gun cabinet and constantly having a double action 357 magnum pointed at your foot. This is the primary difference beween Unix and DOS culture. Unix users and admins realize thier own limitations and would rather not have the constant ability to screw themselves over.

      If you run as root when you don't need to then either you are an idiot or those that built your system software are.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Software company, not bozos by jellomizer · · Score: 2, Interesting

      Being a Smart and talented software engineer doesn't make you capable of administrating their own system. Sure a large percentage are but there are still an other large percentage that arn't. Many good Software Engineers take what they are doing for granted and assume themselves as computer gods. Thus being sloppy in there computer safety skills. Running as administrator when they don't have to. Installing conflicting libraries, or just the fact that they are Software Engineers they might just want to poke around in the OS a little to much. Hey what does this do, then the next day their computer wont boot. I have seen some very talented software engineers who don't know about a lot of basic System Administration skills such as proper removal of software they will just go and delete the folder leaving all the bits and peaces all around. For home they can have all the access they want but when they are at work thy should have access to what the need to be efficient and nothing more.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:Software company, not bozos by gad_zuki! · · Score: 2, Interesting

      root and administrator really can't be compared. root in UNIX exists because of the legacy system of multi-user time-sharing mini-computers. Admin/user in windows exists almost purely for sys administration tasks. So in the UNIX world its very easy to get software that runs with its permissions system, in windows you'll be surprised how many apps try to write to system32/temp or windows/temp instead of the local profile.

      Sure, they are similiar concepts but in practice they're very different. Windows is for the PC desktop/everyone owns one revolution, UNIX was for the "holy crap we can have accounts on computers" revolution.

  19. No *nix? by anderiv · · Score: 4, Insightful

    We don't run Unix. We don't run Linux. We don't run Oracle. We're 100 percent Windows, SQL Server.

    That makes for a great testing environment for Windows Services for UNIX, huh?

    1. Re:No *nix? by sg3000 · · Score: 2, Interesting

      > I don't run anything that competes with Microsoft. My goal is
      > to make sure Microsoft products are the best products in the
      > world. It's an easy choice for me, in that sense--to run
      > Microsoft technology. We don't run Unix. We don't run Linux.
      > We don't run Oracle. We're 100 percent Windows, SQL Server.

      100% Windows? Wow, that must make the Macintosh BU's development efforts pretty hard.

      Although I agree that Microsoft should use their own products wherever possible, the interview with the CIO sounds like it was really written by the marketing department:

      > If I were to leave Microsoft, the first thing I would do is go to
      > Microsoft and say, "I want to be your first and best customer.
      > How do I get all of the products early?"

      That would be the first thing he'd do? Not, "I'm sick of the viruses! I'm ripping your stuff out unless you fix the security flaws in Outlook!"

      --
      Insert simplistic political, ideological, or personal proselytization here.
  20. Spyware... by WilliamGeorge · · Score: 2, Insightful

    I have a hunch that a really good way for MS to make sure it only has (reasonably) computer savvy employees would be to - ahem - "terminate" anybody who couldn't keep their computer clean. I mean, if a guy is coding MS security stuff, and can't keep a single desktop safe, he doesn't belong there...

    --
    William George
  21. Best practices by RealProgrammer · · Score: 3, Insightful

    With every user at MS an Administrator of their own machine, it's no wonder that it's so hard to implement any other security model using Windows.

    I hope some of those users are smart enough to give themselves a luser account and run under it ... but wait, that doesn't work well in an enterprise using Active Directory, does it?

    Maybe they have an enforced policy of using anti-spyware and anti-virus software ... but Microsoft doesn't make any.

    Maybe they have extensive training classes with stock options going to those who don't spread viruses (sort of like those "accident free days" campaigns you see at some companies). But wait, no one wants their stock any more ...

    Oh well, they're Microsoft -- they must know what they're doing.

    --
    sigs, as if you care.
  22. They STILL use some UNIX systems..to Compile Win.. by TheCeltic · · Score: 3, Interesting

    Is it not true that they use Suns to compile windows itself? Because they need the huge multiprocessor power of a real computer (130+ cpu's)? What about (noso)hotmail? There are still BSD systems running there. I guess the article is only talking about workstations?

    --
    =-=-=-=-=-=-=-= - The Celtic - =-=-=-=-=-=-=-=
  23. A Sound Knee-Jerk Reaction by EXTomar · · Score: 4, Insightful

    The people often bitten the worst by Spyware/Malware are very smart, very computer savy people. The problem is they don't realize all of the tricks that they will use to get onto your system. Besides, it can't happen to them! Many times people will recognize they've been bitten right away by an accident misclick but by then its too late.

    So while people might not be idiots, most should never be trusted with elevated privilages. But Windows does give you an option (or they are very painful) so load up the maintaince costs with all sorts of software and network monitoring because MS refuses to learn lessons painfully realized 20 years ago.

    For the love of all that is good and holy, I wish MS would abandon certain technologies (Active X hosting in application frameworks), I wish MS would stop requiring user level tasks with elevated privilages, and I wish people would stop making excuses for MS. Reinstalling from a backup image is not the proper way to fix problems on a platform that is supposed to be "enterprise enabled".

  24. Re:From the article by Twanfox · · Score: 4, Insightful

    One big thing I heard comes from Oracle. Oracle (the company) runs Oracle (the database). It was a mandate put down from on high and seems to make at least a modest amount of sense.

    Think of it this way. The biggest way that you figure out that something should be tweaked is if you are the user of the system. Those admins that never use the systems that they deploy and work on have quite a big harder a time trying to understand just what the program is trying to do, and what to do about it when it fails. To add to that, they never come across bad quirks that noone mentions because they're just that, quirks. It doesn't cause the system to fail or halt or mangle any data, but it sure is annoying when it does it.

    To live and die by your own software is not a bad thing. It gives you not only the developer's perspective of design and impliment a solution, but also allows you to see whether or not what you made is actually useful. Don't read too much into this post, like I support Microsoft totally (they can be quite an ass of a company), but the mentality is sound and used in more companies than just Microsoft.

  25. Famous last words by loren · · Score: 2

    Quoted from the article "I have no skills and no ability..." Yep, sounds like Microsoft to me.

    --

    Loren Osborn

    Software isn't software without source code. -- NASA
  26. No skills? by tchernobog · · Score: 2, Insightful

    We do [...] have an open-source client running--just for competitive analysis. As an IT organization, I have no skills and no ability and no purchasing of those products.

    So he's an IT manager with no skills in the IT industry other than MS-related? Someone could call this "to be blind and overconfident".

    Me, I call him a lucky guy that is probably paid >= 4000€ a month to say to the world "I don't know a thing about IT, but with MS my income has doubled". Heck, being on Bill's bill, McBride can say that too!

    --
    42.
  27. Totally Incoherent Answers by warriorpostman · · Score: 5, Interesting
    Obligatory rant here...how do they know it's the best product if they never run anything non-microsoft.
    As a policy, I don't run anything that competes with Microsoft. My goal is to make sure Microsoft products are the best products in the world. It's an easy choice for me, in that sense--to run Microsoft technology. We don't run Unix. We don't run Linux. We don't run Oracle. We're 100 percent Windows, SQL Server.
    What does the following mean? Other than an incoherent repetition of the above.
    We do, in areas on the client, have an open-source client running--just for competitive analysis. As an IT organization, I have no skills and no ability and no purchasing of those products. We don't even run J2EE. Everything is .Net.
    This guy really earned his title as Chief Information Officer. When I read this interview I got flashbacks of video clips of Iraq's Minister of Information making all those bizarre claims about the invasion.
    1. Re:Totally Incoherent Answers by hunterx11 · · Score: 4, Funny

      The Linux boxes are not here. They are not anywhere. They are segfaulting in the parking lot as we speak. I must now inform you that you are too far from reality.

      --
      English is easier said than done.
    2. Re:Totally Incoherent Answers by Jester99 · · Score: 4, Insightful

      Obligatory rant here...how do they know it's the best product if they never run anything non-microsoft.

      The point is they're eating their own dogfood. They may not have the absolute best product in the world, but it does everything they need it to do. If the only way to get feature X is to install Oracle WhizBangPro 5.0, they refuse to do it: they just write that feature into their own software. And thus, their software has all the features they need.

      Given that the IT needs of Microsoft probably rival or surpass almost any other organization, I'd say that probably qualifies their products as at the very least among the best.

  28. Who came up with this strategy? by Odin_Tiger · · Score: 2, Insightful

    "We're 100 percent Windows, SQL Server" Hold up a second, now. How the heck do they expect to know if their products are good or not, if they have nothing for comparison? You've got to be -very- familiar with both sides of an argument if you expect to win it.

    --
    Unpleasantries.
  29. Re:Hmm by Mundocani · · Score: 4, Interesting

    I'm a former MS developer/employee and we could install anything we wanted period. There were never any restrictions other than the stuff you'd expect such as no pirated software, etc. There were login scripts which ran every time you signed into corpnet and you were required to run anti-virus software (eTrust). Bridging to the public internet from corpnet was also prohibited for obvious reasons. Beyond that, it was a very trusting environment. Even WiFi was deployed many years ago on campus, something a friend at Oracle says they aren't allowed to have to this day.

    Neither our admin. assistants or QA people had any restrictions either, but I don't know about the receptionists. They sure seemed to play a lot of those boring built-in Windows games, so maybe they weren't allowed to install other software. I never asked them.

  30. Re:Well we already knew by danheskett · · Score: 2

    Yes, well, the gentlemen in question manages infrastructure. General purpose services. What you mention are products, and obviously, the development groups would handle those as appropriate.

  31. How can you compare without use? by SuperKendall · · Score: 3, Insightful

    I'll bet you anything that they have unix servers and oracles databases for comparison purposes though.

    Probably they do, but how mcuh real comparison can you do without running production systems? It could be just a small piece, but to ignore what it's like to maintain other products in production is short-sighted, I would say.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  32. The problem is that many savvy users aren't by Sycraft-fu · · Score: 5, Insightful

    I work for an Electrical and Computer Engineering department. Now one would think that the Computer Engineers at least would be competent. Well, not so much actually. Most of them are... how to put this... MORONS when it comes to computers.

    We have a Internet Technologies Lab. This is the lab where they study networking and so on. These are the engineers taht study this, they have degrees in this. However they have the most piss poor understanding of network fundimentals and security I've ever seen. They get boxes hacked all the time, they continually have problems with simple things like getting their subnet set correctly, and if their switch goes down plugging it in is too complecated a concept.

    Just because somone works ina computer related field, doesn't mean they are good at the support end of computers. I'd like to think that programmers and engineers ought to know enough to avoid spyware and such, but I know from experience that's not the case. Just because they can write good code doesn't mean they are good system administrators.

  33. they must be admins by multi+io · · Score: 2, Interesting
    the not-so-obvious ('Our users are the admins of their machines. They can load whatever software they want on their machines

    Note the subtle line of reasoning there -- what he implied to say is "Our users are the admins of their machines *so* they can load whatever software they want on their machines". Which is perfectly obvious, because it appears that on Windows, to do anything even slightly more advanced (like, say, installing new non-trivial software), you have to be an admin. Personally, I don't know of any Windows development shop where the programmers aren't admins and don't each have their own personal single-user PC...

  34. No shock by overshoot · · Score: 4, Funny

    Considering that "billg@microsoft.com" is hard-wired into quite a few tools for use with anonymous FTP ...

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
  35. Re:LIAR by fatwreckfan · · Score: 2, Informative

    None of those systems belong to Microsoft...you can see that clearly by looking at the Netblock column. Skip ahead until you get to systems that actually belong to MS and they are all running Windows variants.

  36. I like this question: by LilMikey · · Score: 2, Interesting

    Do you use any Linux?
    As a policy, I don't run anything that competes with Microsoft. My goal is to make sure Microsoft products are the best products in the world.


    Ah, the old 'bury your head in the sand' technique. It works well. Maybe if they actually *tried* linux they could see what pisses disenfranchised Windows users off or where these TCO numbers come from.

    --
    LilMikey.com... I'll stop doing it when you sto
  37. We don't run Unix? by Quixote · · Score: 2, Informative
    Here's a snippet from a Microsoft knowledgebase article about how they ensure virus-free software release:

    Disks are duplicated on a variety of industrial strength, quality focused systems. Most of these systems are UNIX-based. The UNIX-based duplication systems used in manufacturing are impervious to MS-DOS-based, Windows- based, and Macintosh-based viruses. The few MS-DOS-based and Windows-based standalone duplication systems do not allow MS-DOS-based operating systems to access the duplication system. Virus protection systems used by these MS-DOS-based and Windows-based duplication systems strictly govern the duplication process, even when they are not running.

    That KB article has since disappeared... smirk... ;-)

  38. Re:There's definite pockets of non-Microsoft use.. by KJKHyperion · · Score: 2, Insightful

    GCC is included in Interix because it's the only compiler that can make UNIX-style executables in PE/COFF format, and because most applications either explicitely require GCC or require shared objects. But Microsoft doesn't use GCC for the tools that weren't originally GNU (most aren't, they come from some BSD), and GCC and GNU are optional components, not included in a standard installation

    --

    Make a difference - use Windows! (open source clone of Windows NT)

  39. Re:WTF? CIO implies little talent here in USA? by Tet · · Score: 3, Insightful
    There are (supposedly) a gazillion out of work or underemployed computer scientists. The idea that they can't find what they want here in the states is just preposterous.

    A gazillion out of work and a gazillion that I'd want to employ are two very different things. I have a hard enough time recruiting for a department of 15, let alone trying to do it at the sort of scale he's talking about. The truth is that Sturgeon's Law holds just as well for IT staff as for anything else. In fact, if my experiences are anything to go by, he was being optimistic...

    --
    "The invisible and the non-existent look very much alike." -- Delos B. McKown
  40. Heh, this is a funny quote by phozz+bare · · Score: 2, Funny
    "We won't put all 90,000 mailboxes on Exchange beta. [...] We start with the product group that developed the product, so they feel the pain first."

    phozz

  41. Re:Weak by jd · · Score: 2, Insightful
    And that's fair enough. If they'd said exactly what you'd said, I'd have no complaints. (Actually, if they ever do have an opening for company spokesperson, you might want to apply, as you'd do a hell of a lot better than they do, currently.)


    I don't like Microsoft products, overall, but purely for technical reasons. There's no place for emotions or politics in solid-state circuitry. (I've heard that stressed silicon does better than regular, but I don't think that's the kind of stress they mean.)


    However, Windows is still a good system to use, for a lot of things. X is way behind on supersampling, anti-aliasing and other similar techniques for smoothing out graphics. It has improved, but Windows is the better of the two. For related reasons, it would be hard to develop a top-of-the-line GUI Desktop Publishing system for X. There are stacks of them for Windows and the Mac.


    Where Windows is strong is in presentation. Apple were there first, but since they keep reinventing the wheel, they don't get to build much on what they already have. I'd say Apple is still the best, there, in terms of absolute quality, but Microsoft is able to leverage their experience in a way Apple doesn't.


    There is no fundamental reason why Linux can't be good there, too. The hardware doesn't give a damn what OS is being used. Why should it? Although there is some work on improving X and developing better represenational systems, it remains essentially a stack of bitmaps on a pixel-based virtual screen.


    (I also hate the fact that X is horribly generic, with acceleration largely being done by high-end vendors for their own private distributions. Very few - if any - Linux distros have optimized X binaries for their platforms.)


    Berlin (now Fresco) offered the potential for busting out of a lot of the old, less useful, paradigms, but it's dead. Dead as a doornob.


    I use both Linux AND Windows. (And OpenBSD and Plan9.) There are technical things I resent about all of them, and there are personality quirks I dislike about proponents for each.


    Some people say all OS' suck. Well, if the OS developers stopped worrying about how much their rivals sucked, they might be able to learn from what they've done right.


    Evolution is asymtotic to perfection (ie: it tends to it, even though it'll never actually reach it). Learning from others will advance you along the line. Rejecting outright what others have learned, purely because they learned it first (the "Not Invented Here" syndrome) WILL push you further back.


    There's only one way to get closer to the goal, and it's not through excessive pride in one's achievements, or prejudices against those of others. Pride and Prejudice makes a great book title, but a really lousy corporate strategy.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  42. Apple and Cray by kanweg · · Score: 2, Interesting

    I once read that Apple were using a Cray to design a computer or something, and Seymore Cray was amused, because he used an Apple to design the next Cray.

    We foreigners can only laugh when we hear that a guy at Coca Cola was fired because his wife had bought him a Pepsi.

    Bert

    Who wonders how hard it would be for Slashdot to detect themselves that if a message doesn't contain HTML it is POT and should be formatted accordingly.

  43. Re:Hmm by TheAntiCrust · · Score: 2, Funny

    Thats such a pessimistic way of looking at it. You never know until you ask; some secretaries boxes might be much more readily available then you would first think.

    ;)

  44. That's bullshit, I worked there, I know by melted · · Score: 2, Informative

    You're allowed to run whatever the heck you want as long as there's a business reason to do so. In fact, at one time I had a RedHat box under my desk and ran MySQL on it, and I used MySQL quite extensively on Windows as well, until I figured out the architecture that allowed me to do bulk inserts into MS SQL backend. I know for a fact that lots of folks run unix command line tools, emacs, firefox, etc.

  45. Re:LIAR by kelnos · · Score: 2, Insightful

    I recall that MS used to use Akamai to mirror their website. If they still are, that would explain the non-Windows OSes in the list (which I can't see right now, as Netcraft isn't responding for some reason).

    --
    Xfce: Lighter than some, heavier than others. Just right.
  46. 10% Security by stuffduff · · Score: 2, Insightful
    Q: How much of your department's time, as an IT organization, is spent on security? We've heard the figure 10 percent thrown around.

    A: "It's hard to capture the overall time spent on security, but 10 percent is probably about right."

    This is exactly what is wrong with Microsoft Security. It needs to be the total responsibility of a few individuals who work closely with the larger security community, clearly when security is everyone's problem and they spend 10% of their time on it, then it is really nobody's problem. (Except that then it is everybodys problem! )

    Microsoft could save money and improve it by outsourcing security. Rather than trying again to fix a broken culture, why not just admit it's broken and realize that other companies use outside resources and it works fine for them. For example, would you but an extension cord without it first having been researched by Underwriters Labs? Would you go to a hospital that was not inspected by JCAHO?

    --
    "Can there be a Klein bottle that is an efficient and effective beer pitcher?"
  47. Re:However by Keeper · · Score: 2, Informative

    Obviously you don't spend 5 minutes with a customer and ask a customer, "hey, what do you want to do" and then go off and do exactly that. You figure out what problem it is they're trying to solve, and get an understanding of the core issues at play. Then you talk to more customers and repeat the process. From there you can organize that information to get an idea of how much need there is for a certain set of functionality. If one customer wants one feature, but 800 want another one, you start working on the solution to the problem 800 of your customers want.

    This is customer oriented/focused development.

    If you just go out and solve random problems that nobody has a need for, you risk losing focus on what really matters -- the people who buy your software. Nobody upgrades because a package does something new they don't care about -- they upgrade because it solves a problem they're having.

    This kind of development isn't "catchup" -- it isn't "bug fixing". It's identifying what people need, and then coming up with a solution for them that solves the problem they're having; this doesn't mean that it solves only that narrowly defined problem. The thing is, when you do this kind of work, you ARE solving problems people have before they encounter them (in addition to solving problems some of your customers already have).

    There is plenty of innovation that can occur by doing this, and I personally think you get a lot more useful innovation following this process. You'll certainly do better than copying the features in competing products.

  48. "We don't run Linux" by quigonn · · Score: 2, Interesting

    Ah, why have they then bought 200 (in words: two-hundred) boxes of Caldera's Linux distribution (forgot the name, it was before Caldera was the new SCO) a few years ago...?

    --
    A monkey is doing the real work for me.
  49. The death of administering by TheRealSlimShady · · Score: 2, Informative
    just as capable of administrating their own computers

    Is it just me, or is the word "administering" being slowly replaced by "administrating"? Administrating seems to be the wrong tense to me.

  50. I admin my own box by Pop69 · · Score: 3, Funny

    I'm an accountant for an insurance firm and I admin my own machine AND the dead rat mail/dns/webserver as well.

    That's because all our "technical" people only know how to admin Microsloth products. If a couple of reboots doesn't fix it they re-install from scratch.

  51. (JUST GUESSING) by pilsner.urquell · · Score: 2, Interesting

    root@urquell:/home/jwblack# nmap -vv -sS -O -P0 -T Insane microsoft.com

    Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2004-12-14 18:11 MST
    Initiating SYN Stealth Scan against cps.microsoft.com (207.46.130.108) [1660 ports] at 18:11
    Discovered open port 80/tcp on 207.46.130.108
    Discovered open port 443/tcp on 207.46.130.108
    The SYN Stealth Scan took 29.36s to scan 1660 total ports.
    Warning: OS detection will be MUCH less reliable because we did not find at least 1 open and 1 closed TCP port
    For OSScan assuming that port 80 is open and port 36502 is closed and neither are firewalled
    For OSScan assuming that port 80 is open and port 36846 is closed and neither are firewalled
    For OSScan assuming that port 80 is open and port 35462 is closed and neither are firewalled
    Host cps.microsoft.com (207.46.130.108) appears to be up ... good.
    Interesting ports on cps.microsoft.com (207.46.130.108):
    (The 1658 ports scanned but not shown below are in state: filtered)
    PORT STATE SERVICE
    80/tcp open http
    443/tcp open https
    Device type: general purpose|router|firewall
    Running (JUST GUESSING) : NetBSD (89%), Cisco IOS 11.X (88%), DEC IOS 10.X (88%), Microsoft Windows 95/98/ME (88%), Cabletron embedded (88%), HP HP-UX 11.X (85%), IBM AIX 4.X (85%), Secure Computing embedded (84%)
    Aggressive OS guesses: NetBSD 1.5_ALPHA i386 (89%), Cisco 4500 router running IOS 11.2(2) (88%), Cisco 1601 (IOS 11.0) or DECbrouter90T1 (Runs Cisco IOS 10.2(5)) (88%), Microsoft Windows 98SE + IE5.5sp1 (88%), Cabletron Smart Switch Router 8600 (88%), HP-UX B11.00 U 9000/839 (85%), IBM AIX 4.3.2.0-4.3.3.0 on an IBM RS/* (85%), Secure Computing SECUREZone Firewall Version 2.0 (84%)
    No exact OS matches for host (test conditions non-ideal).
    TCP/IP fingerprint:
    SInfo(V=3.70%P=i686-pc-linux-gnu%D=1 2/14%Time=41BF 8F81%O=80%C=-1)
    TSeq(Class=TR%IPID=RD%TS=0)
    T1(R esp=Y%DF=N%W=4000%ACK=S++%Flags=AS%Ops=MNWNNT)
    T2(Resp=Y%DF=N%W=0%ACK=S%Flags=AR%Ops=)
    T3(Resp =N)
    T4(Resp=Y%DF=N%W=0%ACK=O%Flags=R%Ops=)
    T5(Re sp=N)
    T6(Resp=N)
    T7(Resp=N)
    PU(Resp=N)

    TCP Sequence Prediction: Class=truly random
    Difficulty=9999999 (Good luck!)
    TCP ISN Seq. Numbers: C39D59C2 61104197 94FC38E7 8CA9A951 6EF250A1 CBBC3177
    IPID Sequence Generation: Randomized

    Nmap run completed -- 1 IP address (1 host up) scanned in 69.782 seconds
    root@urquell:/home/jwblack#

    I personally consider 89% a good bet.