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?"

38 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 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"?
    4. 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

  2. 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.
  3. 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 Opie812 · · Score: 1, Insightful

      Good point, however, I'd bet that there are a heck of a lot of people that work for microsoft that aren't computer savvy. *Some* people might say most, but I'm thinking of people in HR, secretaries, and others that aren't your typical Microsoft developer/engineer/computer guru. Imagine if an HR person were allowed to adjust the machinists wrenches.

      --
      I'm not a nerd. Nerds are smart.
    3. 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.

    4. 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?
    5. 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.

    6. 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
  4. I know why his users are admins by Anonymous Coward · · Score: 1, Insightful

    Because the various versions of Windows all reveal their bias as a single user operating system, and even it's creators despair at efficiently administering a Windows network.

  5. 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!
  6. 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.

  7. 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 Anonymous Coward · · Score: 1, Insightful

      I agree with local admins especially in a technology company.

      I did user and network administration in a smaller software development company and we gave all our users access to the Administrator account so they could install whatever tools they needed to perform the work needed. Sometimes our developers and software testers would elect to download freeware and shareware. Other times they may download and install some demo software that, in some cases, was found to be effective and licenses then purchased based on suitability to the tasks rather than a nice software advertisement and a friendly sales rep bearing gifts.

      It's just a more sane way to treat the people since they should know what they are doing. It also helps to compress timelines when a new build needs to get done and out the door.
      In case of problems though they could always request a system refresh that involves having the computer ghosted to a base reference install and then the developer would need to add any customizations as required.

      Frankly, while I always believed in what I was doing there was always a side of me that wasn't sure if I should be letting all people be admins. This Microsoft interview confirms the thought for me and I will encourage and promote such practices in any future admin position I may take.

  8. 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?

  9. 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
  10. 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.
  11. 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".

  12. Re:There's definite pockets of non-Microsoft use.. by Anonymous Coward · · Score: 1, Insightful

    but since the users admin their own machines, the CIO can deny any knowledge of it.

  13. 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.

  14. 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.
  15. 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.
  16. 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.

  17. 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
  18. 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.

  19. Re:Comedy... by Anonymous Coward · · Score: 1, Insightful

    Whose to blame for that?

    Microsoft has a publicly available set of guidelines for writing applications that run under limited privileges. If John Carmack didn't follow those specs and requires you to run Doom 3 as admin, is it Microsoft's fault?

  20. 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)

  21. 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
  22. 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.

  23. 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)
  24. 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.

  25. 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.
  26. 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?"