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

508 comments

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

      I wonder what they did with all of their Xenix boxes? That's what DOS and Windows (up to 3.0) were written on, I hear. (Some Windows development on Suns, too?)

    4. Re:No wonder they're laggin behind... by JaffaKREE · · Score: 1

      The other thing on the security side is governance: Sarbanes-Oxley and regulatory compliance. I think a lot more time right now is being spent on compliance and the regulation. It probably is competing with the amount of time spent on traditional security.

      He's not kidding about this shit. Sarbanes-Oxley compliance at my last position essentially stopped productivity for months. The documentation requirements are insane - I'm talking pages of request forms to run a select statement against a non-production database. Everything IT touched needed "Compliance documentation", no matter how insignificant or silly it seemed. Need to install Ad-aware on a CLIENT station ? 14 pages of forms and a meeting at the (NON-technical) review board. You can imagine how much work was getting done following those processes.

    5. 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
    6. Re:No wonder they're laggin behind... by cowbutt · · Score: 1
      Eh, this is talking about their IT infrastructure. It would look pretty bad if it was based on unix servers and oracle databases.

      Not only would it look, it would be bad for the future development of Microsoft's products; if they were inadequate for even internal use, how could they hope to compete on the open market? Not even Microsoft is that dumb.

      --

    7. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      This has more to do with an overreaction on the part of your company and very little to do with SOX regulation. The regulation itself is extremely vague on what is actually required. Some companies are going way overboard in the name of SOX compliance.

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

    9. Re:No wonder they're laggin behind... by JaffaKREE · · Score: 1

      Interesting, I will have to email them and tell them they've wasted months of company time. I will enjoy it, I assume they will not.

    10. Re:No wonder they're laggin behind... by banzai51 · · Score: 1

      It's MS's "eat-your-own-dogfood" policy. And it doesn't supprise me that internal MS desktop users run in admin mode. Most would be devs who would require it.

    11. Re:No wonder they're laggin behind... by mopslik · · Score: 1

      I thought that it was normal corporate behaviour to look at their competitors.

      Good gods. I'm not picking on you specifically, but since many other have posted the same comment in this thread, it's probably best to reiterate this guy's full quote.

      As a policy, I don't run anything that competes with Microsoft... We do, in areas on the client, have an open-source client running--just for competitive analysis.

      Hope that clears things up a wee bit.

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

    13. Re:No wonder they're laggin behind... by daniil · · Score: 1
      and so that Novell employees would experience what their customers experience.

      Same difference, except that Microsoft is developing apps only for their own platform. Think of Microsoft employees running "Microsoft products only" as an incentive for them to make better (and more usable) software :7

      --
      Man is a slave because freedom is difficult, whereas slavery is easy.
    14. 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"?
    15. 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.

    16. Re:No wonder they're laggin behind... by RazzleFrog · · Score: 1

      Spoken like a true techie. There is no such thing as going overboard with something like this. It is a one-time cost sink that can save some huge headaches (and fines) down the road. Most companies are completely lax in their internal controls and ripe for employee fraud and financial mistatement. This is something that never should have needed legislation to be done in the first place.

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

    19. Re:No wonder they're laggin behind... by legirons · · Score: 1

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

      Surely not the same IE developer who left to work on Firefox, and whose article is on slashdot's front page at this very moment???

    20. Re:No wonder they're laggin behind... by abandonment · · Score: 1

      exactly - this whole 'eating your own dogfood' idea is fine and dandy, but completely unrealistic in the real-world of IT.

      You can also understand why MS products all require 15 other MS products to really work properly - if you buy one you find out you actually need licenses for a ton of other crap that otherwise you'd be able to do with out - and suddenly your IT server bank becomes a monstrosity with all of the servers that they expect you to run (back orifice type) ...

      Running MS servers when you aren't paying for them might be nice, but when you rack up the license fees, upgrade fees, 'per-processor' fees etc microsoft software just does not add up.

      we can run our entire IT network off of a 300 mhz pentium running bsd...zero licensing costs, zero 'maintenance' costs - it just works.

      it's pretty easy to see why microsoft completely misses the SMB market

    21. Re:No wonder they're laggin behind... by sphealey · · Score: 1
      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.
      Not sure what your reasoning is there dude as I just said exactly the opposite.

      Most of the networks I have used/built/operated over the last 18 years have been heterogenous. The one I happen to have right now is Microsoft, Solaris, and Linux. The one before that was Novell, Microsoft, and Linux. That is real life, unless you have totally abandoned your fiduciary duty and given your entire business information system to one vendor.

      Given that most networks I have worked with are multi-vendor, and IMHO they should be, why would I criticize Microsoft for testing in that environment?

      sPh

    22. 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!
    23. 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

    24. Re:No wonder they're laggin behind... by schwanerhill · · Score: 1

      The entire paragraph in question, from the article:

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

      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.

    25. Re:No wonder they're laggin behind... by bdcrazy · · Score: 1

      From what i recall, they don't want you publishing benchmarking info. However, you would actually attempt to run your software on systems before you actually buy them right... right? erm well, i'll go back over here and continue working...

      --
      Tonights forecast: Dark. Continued dark throughout most of the evening, with some widely-scattered light towards morning
    26. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      Unless I'm mistaken, Hotmail is still run on a non-MS platform. Who else remembers the Hotmail crash when they tried to move it to Windows 2000? Now all the front-end stuff is Windows, the back-end is not. Unless that changed and nobody told me...

    27. 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."

    28. Re:No wonder they're laggin behind... by HardwareLust · · Score: 0

      Lagging behind what exactly? I don't see any *nix companies with BILLIONS in cash reserve. I don't see any *nix companies selling millions of pieces of software (and hardware) every day.

      Exactly what or who are they lagging behind?

      --
      ...not that I'm a pirate.. Hell I've never even fired a cannon. - oldwolf13
    29. 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 :)

    30. Re:No wonder they're laggin behind... by Fulcrum+of+Evil · · Score: 1

      The UNIX-based duplication systems used in manufacturing are impervious to MS-DOS-based, Windows- based, and Macintosh-based viruses.

      It would appear that they chose Unix so that they wouldn't have to deal with viruses infecting the distribution media.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    31. 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.

    32. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      I invite you to RTFA. "We do, in areas on the client, have an open-source client running--just for competitive analysis."

    33. Re:No wonder they're laggin behind... by dingfelder · · Score: 1

      maybe you missed my main point...

      FreeBSD was (as you correctly pointed out) used as the "front end" mail processing part of the service. Sun's Solaris is still 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.

    34. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      With some experience from Microsoft, I can say that there are plenty of people using Mac, Linux, or some other breed of *nix for some specific purpose. But when commercial software is free (as in soft drink) and the latest version is always conveniently at hand, even a hard-core Linux enthusiast will eventually convert to the easy life.

    35. Re:No wonder they're laggin behind... by Spoing · · Score: 1
      1. 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.

      In general, I agree -- though I can't speak for the person you're replying to. This article is on Microsoft's IT department and they should 'eat thier own dog food'. If nobody, anywhere, in Microsoft has Linux, Solaris, HPUX, and *BSD networks and an IBM mainframe or two that would be very short sighted of them. I'm betting that they have these and others as well.

      That said, they do make Mac products, so the Mac group in MS should be running on nearly all Apple gear and OS up to the routers. The IT department for that part of MS would support a non-MS network...and they should.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    36. Re:No wonder they're laggin behind... by mini+me · · Score: 1

      I've heard that's also not true anymore. But I don't work at Microsoft so I cannot confirm or deny.

    37. Re:No wonder they're laggin behind... by SIGALRM · · Score: 1
      That's what DOS and Windows (up to 3.0) were written on, I hear
      Not exactly. I was on some related projects around that time; and it's worth noting that Microsoft never sold Xenix directly to end users, nor did they use it as a dev platform for DOS/Windows.

      Microsoft's intent was to license the software to OEMs such as Intel, Tandy, Altos and SCO who then provided a finished version of their own Xenix to the end-users or other customers.

      SCO introduced its first version of Xenix named SCO Xenix System V for the Intel 8086 and 8088 in 1983. Today SCO Xenix is one of the more commonly used and found versions of Xenix.
      --
      Sigs cause cancer.
    38. Re:No wonder they're laggin behind... by pompous+windbag · · Score: 1

      I can tell you from personal experience that lots of MS personnel run competitor OSes -- it's just not the official company line (for obvious reasons). Hell, they even have employees that talk/act like regular Linux disciples.
      As for using Windows under an account with reduced permissions: if you've ever tried it, you'd understand why nobody really does it. A columnist at winnetmag.com tried it for a few weeks, and entitled his first column "Oh, The Pain..."
      That should tell you something.

    39. Re:No wonder they're laggin behind... by YU+Nicks+NE+Way · · Score: 1

      The Solaris back end was also retired about two years ago. It's true that the back end hasn't migrated to Exchange, and possibly never will, but that has nothing to do with whether the back end database runs on Windows.

    40. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      /posted anonymously to protect the guilty (me)/

      Last year, MS acquired PlaceWare and re-branded it as LiveMeeting. Until just before the MS buyout, PlaceWare was a java client and solaris back-end. They've got a new Win32 client piece, but the back end is still Solaris.

      I used to work there and people tell me it's still Solaris becaus they haven't been able to reliably make it work on Server 2k3.

      BTW, as far as MS's IT practices go:
      Holy Crap! I stayed on through the merger period and saw things that would make you cringe. Yes, all users are local admins. The IT policies sort of walk a weird line between being very secure (smart-card authentication, requiring anti-virus for remote access) to insanely lax (users can have internet connections both proxied/firewalled and direct "D-Tap" unprotected connectinos at the same desk).

      As is the case with many big companies, there are different sub-units within MS IT that make conflicting rules and policies. They image laptops with copies of XP that have already passed their activation date, so users or support people have to reinstall everything from scratch anyway.

      Really, when you look at how screwed up the rest of their corporate structure is you can understand why IT has such a hard time. It's truly astonishing that they can even ship products anymore.

      And yes, I left angry. But I left voluntarily because I find it hard to work in the Dilbert zone.

    41. Re:No wonder they're laggin behind... by Lanoitarus · · Score: 0

      Well, if Win2k and NT4.0 werent powerful enough to serve up the files, why didnt they serve hotmail on Windows ME instead? It *was* "designed for the new digital age", after all....

    42. Re:No wonder they're laggin behind... by dingfelder · · Score: 1

      Netcraft has a tool to show all the current front end servers for any url.

      interestingly enough, netcraft says this about hotmail: http://uptime.netcraft.com/up/graph?site=http://ww w.hotmail.com&probe=1

      lol, one of their loadballanced servers is BSD :)

    43. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      There are *nix servers in Building 11 on the Redmond campus. They don't like to talk about them, and the NT sysadmins aren't supposed to touch them. A reilable source...

    44. Re:No wonder they're laggin behind... by eealex · · Score: 1

      They don't run *nix, Oracle, Mozilla and therefore they think they are the best.

    45. Re:No wonder they're laggin behind... by YU+Nicks+NE+Way · · Score: 1

      You mean the one that Netcraft claims is running IIS 5.0 on FreeBSD (at IP address 207.68.172.239)? You don't suppose that the problem could be with netcraft's algorithms, maybe?

    46. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      I can verify that Microsoft is a Sun customer and holds a Sun support contract.

      (Obviously this needs to be stated anonymously)

    47. Re:No wonder they're laggin behind... by monkey_jam · · Score: 1

      .... they're still practicing :P

    48. Re:No wonder they're laggin behind... by fataugie · · Score: 1

      Who said they *run* in admin mode? The comment at the top says they have admin rights...that they can install any software they want. Nothing about how they run day to day.

      --

      WTF? Over?

    49. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      This has been discussed before, they use Akamai for load balancing, hence the BSD appearing....

    50. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      Remember that story from that guy who worked at Microsoft Print(er?) dept, who made a picture of a bunch of Apple G5 who just came fresh out of a truck? He photographed it, put it on his blog, and got fired for that.

    51. Re:No wonder they're laggin behind... by bedessen · · Score: 1

      There's nothing that MS can do that would please the slashbots. Use MS technology exclusively and they're derided because they would never pick up on interoperability/standards issues (at least not until they got to the costly QA stage.) Use a mixed technology platform for in-house systems and they're derided for not eating their own dog food.

    52. Re:No wonder they're laggin behind... by Darkangael · · Score: 0

      Not tell people that you don't use your own products?

    53. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      Or maybe you're a fool and didn't realize that the original poster knew exactly what he was talking about.

      See Netcrafts own explanation of impossible operating system/server combinations which basically explain that it's obvious in this case that the Load Balancer (machine directly attached to the Internet) is running FreeBSD, while the webserver (in this case a Windows box behind the load balancer) is running IIS.

    54. Re:No wonder they're laggin behind... by Anonymous Coward · · Score: 0

      in the not-too-distant past the Hotmail servers were run on *nix systems (they needed the stability).

  2. Of course they're all admin by Anonymous Coward · · Score: 0

    Have you ever tried to run in non-Admin mode? A lot of programs don't work.

    1. Re:Of course they're all admin by stupidfoo · · Score: 1

      No kidding. Try installing some older adobe software on Windows 2000. I'm getting tired of having to make more and more of the registry accessible to non-admins.

    2. Re:Of course they're all admin by superpulpsicle · · Score: 1

      I can't freaking tell where MS technology is anymore. It used to be simple Windows NT4 Server + NT4 Workstation.

      Thin Client
      Server Client
      Client Workstations
      Serverside only
      Mixed mode
      Native mode

      Can someone tell me what Active Directory is trying to be. It gets worse every year.

    3. Re:Of course they're all admin by Zonnald · · Score: 0

      Older adobe software is the problem - not W2K.
      If software is written which needs to access the registry and *writes* to the registry, then it is the software that is requiring accessibility to non-admins.

    4. Re:Of course they're all admin by bloodhawk · · Score: 0

      This post tends you either don't have much AD skills or work in a place that has no idea. AD is one of the better technologies MS has implemented. It centralises management and simplifies policy and software administration. However if you don't know what your doing then it is a great way to get yourself into a mess. When properly configured it kicks ass over anything in the market.

  3. adware by hipbase · · Score: 0

    That means everyone is able to run adware and spybot. They should audit that!

  4. 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 Tibor+the+Hun · · Score: 1

      Pfft, don't be a Dummy Dave!
      The reason why longhorn is taking so many years to write is because they had to abandon their next gen filesystem, and use the, I dunno, the 6 year old one.

      --
      If you don't know what AltaVista is (was), get off my lawn.
    2. 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.

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

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

    4. Re:Longhorn? by nbvb · · Score: 1

      Right, and NTFS itself is an offshoot of HPFS, which was introduced with OS/2 in 1990.

      http://www.smartcomputing.com/editorial/dictiona ry /detail.asp?guid=&searchtype=1&DicID=17610&RefType =Encyclopedia

    5. Re:Longhorn? by Anonymous Coward · · Score: 0

      well that... and it's taking them much longer than anticipated to assimilate the evolving Linux kernel.

    6. Re:Longhorn? by bradkittenbrink · · Score: 1

      also, they don't want something like this happening again...

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

  6. In light by Prince+Vegeta+SSJ4 · · Score: 1

    Microsoft's internal IT practices. of all of their software security/bug/virus problems, I'd say that they show up to play without any practice.

  7. 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.
    1. Re:Spam by donutz · · Score: 1

      And according to this article, almost half of that incoming spam is for Bill Gates.

  8. Re:Hammer Revolution! by Anonymous Coward · · Score: 0

    Awww... It's a brand-new baby troll... How cute.

  9. 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.
    1. Re:Misquoted by Anonymous Coward · · Score: 0

      that reminds me - I finally found out what Windows means.

      "Windows Is NOT a Disk Operating Windowing System"

      So THAT's why it crashes so often!

  10. I wonder... by Vvornth · · Score: 1, Funny

    I bet Microsoft has a panic button on all their computers sporting Firefox, *nix and BSD that immediately displays a WinXP desktop.

  11. Well we already knew by rokzy · · Score: 1

    they use macs to make their "MS is the best" PDFs

    1. Re:Well we already knew by WJMoore · · Score: 1

      Yeah and they may well not run Linux but they must run FreeBSD in order to develop and hopefully test things like Rotor... does that count as UNIX? And what about Windows services for UNIX?

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

  12. Hmm by Heem · · Score: 1

    I wonder if that means they can install any Microsoft software they want, or anything anything - I mean, Microsoft sucks, but at least it doesnt have trojans and such in it - if they are installing just anything, They better at least know how to fix it - and I wonder if that applies to the office assistants and the girl at the front desk, and other non-techies.

    --
    Don't Tread on Me
    1. Re:Hmm by drakaan · · Score: 0, Flamebait

      Heem...I'm sure the girl at the front desk has had a trojan or two in her...

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    2. Re:Hmm by Heem · · Score: 1

      You forgot to add.. "If you know what I mean.."

      --
      Don't Tread on Me
    3. 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.

    4. Re:Hmm by TheGrayArea · · Score: 1

      I used to work at the Charlotte DS site. All the secretaries were contracted out there so I'm pretty sure their boxes were locked down tight.

      --

      This space for rent.
    5. 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.

      ;)

    6. Re:Hmm by no+soup+for+you · · Score: 1

      This brings to light SEVERAL things. I've struggled with how to bring our Microsoft environment out of the "users are local admins" for a long time. And if Microsoft can't (or more specifically, won't), how can we? There are so many times that you need Admin priveledges.... it seems like if you are going to have any users who know what they're doing with computers (withing reason: software customer support reps), they need admin rights or a separate admin login. And the reason I don't have a separate login is that they would just use that login 100% of the time. You feel my pain, admit it.

      --
      If you blog it...
    7. Re:Hmm by rbochan · · Score: 1

      I'm a former MS developer/employee and we could install anything we wanted period...

      And your browser could install anything it wanted period too ;o)

      Thanks! I'll be here all week!
      try the veal...

      --
      ...Rob
      The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.
    8. Re:Hmm by Kazoo+the+Clown · · Score: 1

      Bridging to the public internet from corpnet was also prohibited for obvious reasons.

      I presume you mean the obvious reason that Windows is simply too insecure...

      And as one other poster said-- if Microsoft can't make their systems secure enough when they're bridged to the internet, how can they expect us to?

      That reason has also become all too obvious to me-- the MS04-011 security fix that came out which then caused the followup 841382 on W2kPro, followed by McAfee claiming that the W32/RBOT-FP worm that hit some systems at work which wasn't caught by their program was "not a virus" but "a Windows upgrade issue" were the last straws for me-- I now boot Linux when I want to surf the web, and only boot Windows when I'm not on the web (and make sure my modem is turned OFF). It's taken a lot of stress out of life...

    9. Re:Hmm by jaseuk · · Score: 1

      If they _need_ local admin rights then charge them 3 to 5 times their usual per-desktop costs on the basis that having local admin rights means that you'll be rebuilding the machine more frequently when they fuck it up.

      Otherwise consider installing something like deepfreeze so that can screw around with their machine all the like, but gets fully restored when the machine is rebooted.

    10. Re:Hmm by emjoi_gently · · Score: 1

      It makes sense to me.
      The IT folks need to be able to mess heavily with their machines. And heck your PC is the tool of your trade... you should know how it operates and what processes are running on it.
      (Nothing more pathetic that a Programmer who doesn't understand his computer. "How do you install a printer?" *slap* *slap*)

      But the Admin, the PR guys, the mere users, they get more restrictions.

    11. Re:Hmm by nosfucious · · Score: 1

      Actually, horses for courses.

      Older software typically needs admin rights. Newer software 'designed for xp' or '2k' or whatever integrates a lot better. 99% of your headaches gone with the logo software.

      Of course, some of this is just documentation. If suppliers specified which parts of the registry or file system an unpriviliged user needed access to, it could all be scripted.

      Newer, logo'd software typically needs only Admin rights to install, which can be taken care of nicely by Group Policy. User settings go in HKEY\CurrentUser where it belongs.

      Of course, with Unix and unix-likes, everything was installed as root and you'd typeically have a .myapp/config folder in your home folder. Much better way of working.

      --
      Q:I was listening to a CD in Grip and it sounded horrible! What's up? A:Perhaps you are listening to country music
    12. Re:Hmm by alpha_foobar · · Score: 1

      I have worked on sites where people that can install whatever they like, still play those boring windows games... ...I offered them something more interesting to play, but they felt playing something more interesting would look less professional and they actually seemed to like playing solitaire! ...I guess it does look more professional than playing doom or quake or halflife or whatever else... but developers are expected to have a healthy interest any such games anyway... other business employees aren't stereotyped as big geeky kids i guess?

    13. Re:Hmm by jaseuk · · Score: 1

      If your serious about revoking admin then I guess you'll have to go through app by app and set permissions on the registry etc. yourself.

      I can't imagine there are too many essential apps in use that are that old.

      I quite agree with your comments though, the unix way of doing this is far better, although recent releases of windows are now emulating this behavior with documents and settings and HKCU.

      We are not locking down our machines as such and we regularly pay the price for it. Thankfully we are slowly migrating over to terminal services which puts the control back over to us as oppose to the departmental IT guy.

    14. Re:Hmm by XMunkki · · Score: 1

      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.

      Well knowing receptionists, I don't think they're usually that "into" computers (even at MS) to start tweaking them to their liking. I could be wrong. But how would they do their job then? "Hello sir, do you have an appointment or would you like to nibble on my control panel?"

    15. Re:Hmm by bloodhawk · · Score: 0

      banning bridging to the internet doesn't mean you can't connect to the internet. all internal machines have full internet access (protected by ISA of course). bridging to the internet means you can't create your own tunnels to internet based machines and hence bridging external machines to give them corpnet access.

    16. Re:Hmm by Anonymous Coward · · Score: 0

      This is simply not true. When I worked at microsoft only windows machines could run their proprietary proxy software, so linux machines could not get onto the network (to my dismay).

      Furthermore, the fact that each person had to administer his own machine was terrible. All the shared network drives were publicly readable and I couldn't get a "home" directory anywhere but on my local machine. Why did I need to buy and setup my own backup system when there could have been a unix server somewhere that I could keep my files on and have them automatically backed up?

    17. Re:Hmm by Mundocani · · Score: 1

      I think any company who would expose their entire corporate network directly to the internet would be a very foolish company, regardless of what OS their machines are running. Windows has plenty of vulnerabilities, but so does MacOS, so does Linux and so does every other OS. Windows is just a very attractive and large target (as is Microsoft's corporate network). If you believe that your particular OS choice is inherently secure from attacks and can be safely exposed to the entire world without any sort of protection then you are a fool.

    18. Re:Hmm by LordSah · · Score: 1

      Everything except peer to peer software. I had installed BitTorrent to download some big movie trailers, and a couple days later, I got a nasty email from an automated network gnome telling me to uninstall it immediately, and pave my machine as soon as possible.

      I contacted helpdesk and asked them if that was really necessary, and they didn't budge.

    19. Re:Hmm by Anonymous Coward · · Score: 0

      No wonder Microsoft can't develop a holistic security model, they never used one themselves. I guess its another instance of "do as i say not as i do".

    20. Re:Hmm by drakaan · · Score: 1

      Yeah, but if I added that (or "nudge, nudge...wink, wink...say no more"), I would have missed all of the "flamebait" mods ;)

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  13. 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 Belsical · · Score: 1

      They didn't say that everyone runs as admin all the time (though I'd be surprised if they didn't); they said everyone has admin access for when they need it.

      --

      "There are no such things as mutual fantasies. Yours bore us and ours offend you."
      - Bill Maher
    2. Re:Comedy... by pasde · · Score: 1


      Mod Parent down: Flamebait.

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

    3. Re:Comedy... by Anonymous Coward · · Score: 0

      ...which is far too frequent. I mean, Jesus, if the machine was truly locked down you couldn't change a FILE ASSOCIATION without calling in an administrator.

      I think the point was not that the users have to run as admins all the time, but that if you have users who require even marginal flexibility on a Windows machine, they need admin permissions (I think it was also implied that other platforms are designed a little better in this respect).

    4. Re:Comedy... by pD-brane · · Score: 1

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

      Of course you cannot.
      Please, mod parent down, because it is meant sarcastic. It shouldn't be meant sarcastic. It only states the obvious.

    5. Re:Comedy... by EnronHaliburton2004 · · Score: 1

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

      I'm curious, is there a way in Windows to allow users to install only software which has been approved by the administrators? Can a Windows admin sign the software or something?

      I'm now the unwilling admin of a Windows network (my realm is Unix), and I'd love to say "Ok guys, the latest AIM is here. You can upgrade when you get the chance", without giving them the ability to install the spyware programs that they love to install...

      Every power user here has a dozen spyware programs on their system... I want a respositoy of approved software...

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

    7. 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!
    8. Re:Comedy... by Anonymous Coward · · Score: 1, Informative

      Yes - If your clients are windows 2000 of better, and on a domain, you can use group policies to assign software to computers or users; software will install automatically at startup or login. Or you can publish apps to the add/remove control panel app (where the user can install them at their leisure)

      or, on windows xp cliens, you can set group policies that restrict any software from running, except from locations that you specify (eg - c:\windows, c:\program files, and \\server\\withApprovedSoftware)

    9. Re:Comedy... by Aliencow · · Score: 1

      Yes, that is called "Publishing" an application.
      You can make it available in the start menu (Even though it is not installed) or in Add/Remove Under Add programs..

      The program needs to be an MSI installer though, or you need to make your own MSI package of it.

      Here, I do not publish applications, I assign them (Installed at boot), so I make my own UltraVNC, Firefox, Thunderbird MSIs..

    10. Re:Comedy... by Anonymous Coward · · Score: 0

      Is there a way in Windows to allow users to install only software which has been approved by the administrators?

      Public floggings are an effective way to convey which applications are approved and which are not.

    11. Re:Comedy... by Perl-Pusher · · Score: 1

      No I use sudo or su. Mac asks for a password (sudo) graphically, so does linux (kdesu). Windows makes you log in as administrator or have those priviledges all the time.

    12. Re:Comedy... by sexylicious · · Score: 1

      Yes there is. What you are describing is done where I work. I am not quite sure how it is done.

      I know that there are login scripts that are run when I log in. I also know that there are some scripts that are run from a central server after I log in. All of the machines are behind proxies that block anything beyond a strict G rating (I assume slashdot gets by because the IT folks look at it too). And most of the users have no admin privelidges where I am at, but in other buildings, the users do have admin priveledges.

      The way we install things like new programs, updates, or whatever, is that we go to a specific shared directory and get the program's install package. Then we run the installer, and we get access to the program just fine. For things not in the shared directory, we have to ask IT to do a remote install. I did notice that the programs in the install directory are the same ones that I can pull at home; they're the same ones that come from that program's company website.

      None of those programs in that shared directory ask for admin priveledges when they are installed.



      I am writing this from a Win2k machine, and several other machines in my cubicle have XP. We do use *nix machines, but only for heavy duty or mission-critical applications.

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

    14. Re:Comedy... by snorklewacker · · Score: 1

      No I use sudo or su. Mac asks for a password (sudo) graphically, so does linux (kdesu). Windows makes you log in as administrator or have those priviledges all the time.

      You're absolutely full of shit, as the existence of runas.exe can demonstrate. Windows also has the "run as a different user" checkbox on the properties menu of any shortcut.

      --
      I am no longer wasting my time with slashdot
    15. Re:Comedy... by parkrrrr · · Score: 1
      C:\>runas /?
      RUNAS USAGE:

      RUNAS [ [/noprofile | /profile] [/env] [/netonly] ]
      /user:<UserName> program

      RUNAS [ [/noprofile | /profile] [/env] [/netonly] ]
      /smartcard [/user:<UserName>] program

      /noprofile specifies that the user's profile should not be loaded.
      This causes the application to load more quickly, but
      can cause some applications to malfunction.
      /profile specifies that the user's profile should be loaded.
      This is the default.
      /env to use current environment instead of user's.
      /netonly use if the credentials specified are for remote
      access only.
      /savecred to use credentials previously saved by the user.
      This option is not available on Windows XP Home Edition
      and will be ignored.
      /smartcard use if the credentials are to be supplied from a
      smartcard.
      /user <UserName> should be in form USER@DOMAIN or DOMAIN\USER
      program command line for EXE. See below for examples

      Examples:
      > runas /noprofile /user:mymachine\administrator cmd
      > runas /profile /env /user:mydomain\admin "mmc %windir%\system32\dsa.msc"
      > runas /env /user:user@domain.microsoft.com "notepad \"my file.txt\""

      NOTE: Enter user's password only when prompted.
      NOTE: USER@DOMAIN is not compatible with /netonly.
      NOTE: /profile is not compatible with /netonly.
      There's also a GUI version, on the context menu in Explorer. Yeah, it doesn't always work perfectly (for example, the Flight Simulator 2004 installer locks up if you use Run As) but it is there.
    16. Re:Comedy... by Flamesplash · · Score: 1

      You're statement is flawed. MS employees are not the regular users of windows, it's a whole freaking shop of developers. Running in admin mode isn't 'bad' if you know what you're doing and need the added functionality, and presumably everyone, ie all the developers, do.

      This however opens perhaps an issue. With everyone being the sort of users that needs and should run with admin rights what is being done to account for those that don't?

      I've interned at MS three times though never in a windows group, always in an application or web side group so I really don't know.

      --
      "Not knowing when the dawn will come, I open every door." - Emily Dickinson
    17. Re:Comedy... by Ath · · Score: 1

      You definitely can do it with Novell's Zenworks.

    18. Re:Comedy... by Anonymous Coward · · Score: 0

      ranas sucks. Did I mention that it sucks?

      If I'm in the middle of doing something why should I have to start another copy of the application using runas to gain addition priviledges. This is not a command line environment. It shows a clear lack of integration in the system software.

      runas does not help in the case of registry keys. If the stupid application wants to screw around in the registry then that user account itself has to have administrative priviledges.

      runas is clearly a sidestep measure to true integration of priviledge management in the standard windows applications.

      Why should priviledges be tied directly to user accounts anyway? Using runas still means I have to go in and reassign priviledges in the filesystem for files or the registry for keys created by the runas app.

      Why can't I associate priviledges with special non-login accounts or such and have those priviledges temporarily added to my login account? The login cost in a GUI environment is to high otherwise. I can't transfer already running applications between logins, and I can only log in once.

      A further problem is all the damn software packages out there that want the user to be an administrator to run them. It shows another fundamental problem with the priviledge system: The programers are always using accounts with administrative privilidges and never test their user software with an account that is otherwise.

      No, runas is no where near su, sudo, or the application asking for a username and password.

    19. Re:Comedy... by valrus348 · · Score: 1

      No, he is not full of shit...
      Simply because runas and sudo are two very different beasts.
      True, with runas you can do *some* administration and installs, but a lot of your efforts will bite the dust. At least, that is my experience.
      One example for you... Login to W2K as user, and start cmd as Administrator through runas. Now try to run any program from that cmd. Tough luck - none of what you run from there will work as if you are an administrator! Is it retarded or what?
      Now have you ever tried running IE or Explorer with runas? They won't run. But IE is needed to run Windows Update... So tough luck here. Unless you have automatic updates enabled, you WILL need to login as a real administrator to install updates. And, yes, this is a real problem for me in one of my installations: a computer that is running an LC-MSD instrument. I cannot turn on autoupdates since the machine will reboot at will, and people's experiments will get screwed up. It has to be up and logged on as a certain user at all times. So I choose the lesser evil - I update it manually. Since I do not always have a chance to do so (instrument is always in use and software startup takes 30 minutes once it has been shut down), I frequently end up 0wned and screeching my teeth. This machine was one of the 3 other similar ones on campus hit by Blaster (yes, I knew about the vulnerability, but due to totally retarded and bastardized implementations of runas and Winblows Update I could not patch in time).

    20. Re:Comedy... by Chokolad · · Score: 1

      > One example for you... Login to W2K as user, and start cmd as Administrator through runas. Now try to run any program from that cmd. Tough luck - none of what you run from there will work as if you are an administrator! Is it retarded or what?
      Actually all the programs which start new process will run as administrator.

    21. Re:Comedy... by Foolhardy · · Score: 1

      In addition to publishing software mentioned by others, there are Software Restriction Policies on XP and later: create a whitelist of allowed programs by hash and directory and distribute it by Active Directory. It can be more work to make a list of all the allowed binaries, but it provides a good amount of lockdown.

    22. 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.
    23. Re:Comedy... by s_mencer · · Score: 1

      Actually, if you use SUS you don't have to worry about the computer restarting. With a simple change of a registry key you can have a pop-up ask the user if the system should restart or not.

      Amazing what you can accomplish with SUS...

      http://www.susserver.com/

    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:Comedy... by Sexy+Commando · · Score: 1

      Then what's the difference from giving the user admin access to his own machine? stuff in /bin or /etc are hardly critical compared to the data in your home directory, say, checked out source codes. IT people probably already have backup of those common directories but not user diretories.

    26. Re:Comedy... by 0racle · · Score: 1

      ever tried running IE or Explorer with runas
      If you can't run IE or explorer you and/or your system are screwed up. They will indeed run, I do it all the time for windows update.

      If you can't do it you might want to look into a new line of work, since there is nothing that has to be done to make it work. Of course its so much easier to blame MS then it is to realize that you screwed up, have fun with the next virus outbreak.

      --
      "I use a Mac because I'm just better than you are."
    27. Re:Comedy... by snorklewacker · · Score: 1

      One example for you... Login to W2K as user, and start cmd as Administrator through runas. Now try to run any program from that cmd. Tough luck - none of what you run from there will work as if you are an administrator! Is it retarded or what?

      I in fact use runas /user:administrator cmd.exe precisely for that purpose, and all the commands it spawns do in fact inherit those rights. I have no idea what's wrong with your setup.

      Now have you ever tried running IE or Explorer with runas? They won't run.

      Running IE was the second most common thing I would start with runas (to run windows update). They work just dandy.

      Nowadays though, I just run my (firewalled) XP Home box with an administrator account. I largely just play games on it anyway. The box that had win2k on it now runs debian. It's nice how I can make sudo fine-grained and not require a password, but it's a single user machine, so usually I just keep a root shell open.

      --
      I am no longer wasting my time with slashdot
    28. Re:Comedy... by snorklewacker · · Score: 1

      If I'm in the middle of doing something why should I have to start another copy of the application using runas to gain addition priviledges. This is not a command line environment. It shows a clear lack of integration in the system software.

      You're confusing sudo with setuid. Look up the manual for ReplaceProcessToken sometime. Incidentally, do tell me how you get emacs to switch accounts on the fly? Or your shell? Oh right, you start a new one

      runas does not help in the case of registry keys. If the stupid application wants to screw around in the registry then that user account itself has to have administrative priviledges.

      Or the application should stick to using HKCU and not HKLM, or the ACL's should be set on the registry key (which requires using the security configurator or the horrid old-style regedit). One could set the process to run with the owner permissions (ala setuid, and no I don't remember exactly how that's done). Or, one could use (smacks forehead) runas.exe.

      The rest of your arguments apply pretty much equally to su and sudo, or at least partially. I don't even have a MCSE, which the average poodle can get, but it seems the average slashdotter is ignorant and incurious enough to not even learn the platform when they start bashing specific functions of it.

      --
      I am no longer wasting my time with slashdot
    29. Re:Comedy... by sharkey · · Score: 1

      In addition to Group Policy (Intellimirror), you can use SMS as well. SMS doesn't require MSI files, so can support legacy installs without repackaging as an MSI. SMS 2003 can show it's programs in Add/Remove the same as Group Policy.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    30. Re:Comedy... by EnronHaliburton2004 · · Score: 1

      I guess it depends on the philosophy and needs of your developers.

      Personally, many Unix users that I know aren't smart about system administration-- I've had too many instances where the developer mucked up the /bin and /etc directories. This week I had to clean up a machine where the user ran 'chmod -R 777 *' in the /etc directory, creating a nice security hole. In other instances I've had developers replace the native /bin/* utilities with the GNU versions of those utilities, which will break many things.

      Yes, you can restore those files from an image, but why even let it get to that level? /devel/bin is is fine for this purpose . /usr/local/bin also works, but /usr/local/bin is usually needed by third party utilities that the sysadmins install.

    31. Re:Comedy... by AtOMiCNebula · · Score: 1

      UT2004 and HL2 don't need CD checks. I have the DVD edition of UT2004, and it's never asked for the disc, except to install it (heh). And Valve just updated HL2 so that you don't need to do a CD check since it was giving so many people trouble, and it was stupid in the first place.

    32. Re:Comedy... by Sepodati · · Score: 1

      Doom 3, what a good example. I actually only have the demo to see how it would run on my system, but it certainly requires you to be admin. I can't even use "run-as" which I normally do for most games because then the mouse won't work. Maybe it's just my setup, I dunno, but it actually requires me to log in as an admin user in order to run it. I doubt the full game would be any different.

      ---John Holmes...

    33. Re:Comedy... by Anonymous Coward · · Score: 0

      Although it's even nicer when they don't require CD checking such as *ducks* Steam HL2 and UT2004.
      ...
      UT2004 and HL2 don't need CD checks

      You moron, thats what he said.

    34. Re:Comedy... by Bert64 · · Score: 1

      I have also seen many tide*.microsoft.com hosts being components in spam or ddos drone networks..

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    35. Re:Comedy... by Bert64 · · Score: 1

      The linux version works perfectly as a user. Infact, for some reason on my system it runs much slower as root, something to do with more limited access to the X server and opengl that's running under my account i assume.. quake3 has the same problem.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    36. Re:Comedy... by Anonymous Coward · · Score: 0
      So even Microsoft has realized you can't do crap under a limited login in XP.

      If you cant get things to run under a limited logon, you just dont have skillz.

      Given that you can alter permissions to registry keys, all you need to do is find out which "unalterable" registry keys the program needs to function, and provide those permissions to said logon (or preferably group).

      Its quite easy, it just requires understanding how Windows works. Which you obviously dont.

  14. this post too by Anonymous Coward · · Score: 0
    in light of you forgetting to and the paragraph flag, I think you made this post without any practice either!

    P.V.SSJ4

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

    2. Re:No surprise here by PoseidonMS · · Score: 1

      Check out Aaron Margosis' blog at http://blogs.msdn.com/aaron_margosis - he's got some very interesting helpful bits for folks who want to start down the path of least-privilege access on Windows. It's not the "official" word, and it's not at all comprehensive, but it's part of a wave of folks inside MS who are putting these practices to good use right now.

    3. Re:No surprise here by Senzei · · Score: 1
      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.

      *Bolding added for emphasis.

      So....tell me again where the third party applications needing admin rights have anything to do with OS developers? Now if this story was about some major third party software developer that is notorious for apps needing admin rights working exclusively from admin-accounts at the workstation then I would understand the comparison. As it is you seem to be blaming the engineer because an end-user doesn't understand how the product should work.

      --
      Slashdot: Where anecdotes and generalizations can be freely substituted for facts, logic, or intelligence
    4. Re:No surprise here by Anonymous Coward · · Score: 0

      So....tell me again where the third party applications needing admin rights have anything to do with OS developers?

      When the OS developer considers it normal and ordinary for everyone to run as root, it isn't suprising that the OS they build is designed to run best that way.

    5. Re:No surprise here by Senzei · · Score: 1

      So where again does "users admin their own systems" imply "everyone runs as root"? One would hope that in a room full of programmers specialized in the design and implementation of operating systems at least a small majority would not run as root.

      --
      Slashdot: Where anecdotes and generalizations can be freely substituted for facts, logic, or intelligence
  16. Lesson Here by COMON$ · · Score: 1

    It is a good thing diversity is a bad thing in IT...right?

    --
    CS: It is all sink or swim...oh and did I mention there are sharks in that water?
    1. Re:Lesson Here by Enrico+Pulatzo · · Score: 1

      No, the lesson here is that Microsoft is committed to eating their own dogfood. This is a great trend for their company. Few things encourage developers to fix issues like having those issues affect them. Good for Microsoft. However, I'm not 100% convinced that they should be 100% dependent on their own stuff, but if they're willing to stand by it, more power to them.

    2. Re:Lesson Here by WhiplashII · · Score: 1

      Now we need to force them to really eat there own dog food - turn off admin access on their machines.

      I bet things would start working without admin rights REALLY fast!

      --
      while (sig==sig) sig=!sig;
  17. 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 Anonymous Coward · · Score: 0

      You don't think it's more likely that these "many people" you're referring to don't realize that not logging in as "Administrator" doesn't mean that they haven't logged as a member of the Administrators group?

      I can't believe MS users "rarely" run as admin. The latest version of XP Pro I have at home adds new users to the Admin group by default without a password. I don't think they know what the hell they're running as.

    2. Re:Admins of their own machines by Anonymous Coward · · Score: 0

      did you not pay attention?

      all users are in the ADMINISTRATOR group in the domain.

      i dont care if you log in as dave or administrator, with those settings EVERYONE is the same as running as administrator.

      and it is unbelieveably stupid for them to do that.

      power user is fine for 99% of the workers, the rest can be given the administrator password if they need it.

      only complete idiots put users in the administrator group.

      yet it does not supries me that this is corperate polict at MS.....

    3. Re:Admins of their own machines by Chokolad · · Score: 1

      > all users are in the ADMINISTRATOR group in the domain.
      This is bullshit. Devs are local machine administrators, but no way in hell they are DOMAIN administrators.

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

    5. Re:Admins of their own machines by Spoing · · Score: 1
      1. 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.

      Not to raise your ire any more...an honest observeration and question from another network admin.

      Most of the networks that I've managed had desktop systems that were about as powerful -- and sometimes more powerful -- than the servers in the back room. Except for the development and customer deployment systems (mostly for custom software), the servers are not heavy duity speed machines. Most are old and taxed to the limits we can push them. To me, this is as it should be as long as we can expand the backend as necessary.

      The main differences between desktop and server are the quality of the hardware, sometimes the disk array and memory, and the networking gear that ties it all together. Everything else is configuration and network design (router, physical cable, login authentication/scripts, ...).

      Having seen and delt with how most admins manage networks, that last step seems to be what suffers the most. There's this idea that a 'server' is something unique and special...thus, what the client systems do is not nearly as important. Yet, the client systems can and do cause most of the problems -- and are plenty capable of replacing the backend servers if folks were sneaky enough and the admins aren't doing a good job.

      In the case of malware and just dumb mistakes on the user level, why allow most people to admin the desktop machines?

      (Got bitten with allowing admin access to a server over the weekend, btw. Someone created and then deleted MySQL accounts on a *nix server...causing multiple problems. The person is knowledgeable enough to be dangerous, though I'm not going to yank any admin access from him yet. I think he learned not to be sloppy. [crosses fingers] I'm attempting to lead by example by documenting everything as I go along and asking for an OK before acting on larger changes. Even a minor thing such as shutting down/restarting a service for a few moments gets reported and logged before it happens.)

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    6. Re:Admins of their own machines by LurkerXXX · · Score: 1
      In the case of malware and just dumb mistakes on the user level, why allow most people to admin the desktop machines?

      It depends on a lot of variables. Expectations of the users, attitude of the big boss, frequency of need for install of new programs by some of the users, etc. As I said above 'most' users at our place have an admin account on their desktop as well as their regular domain account. Some have shown they can't handle the privledge, so they don't have it. At most other places, I'd agree with you and be all for locking the users down and not giving them any admin privledges.

      I don't consider the servers special because they have better hardware, but because that's where the data lives. No data lives on the workstations here. They just have applications for viewing manipulating the limited amount of data the user is specifically allowed access to. If someone screws up a machine it is simply ghosted back to the install image. If someone toasts the server all the important stuff, the data, is compromised.

      Also because configuration problems in the server affect everyone, not just the user of the single workstation. Yes, a workstation can cause problems for the whole network, but a compromised server immediately puts all the data/configs for the whole network in question.

    7. Re:Admins of their own machines by Spoing · · Score: 1
      1. ... At most other places, I'd agree with you and be all for locking the users down and not giving them any admin privledges.

      I've been there; mainly social/'business requirements' issues. (Horror story: One database for a 50K/day, $1M/day check processing system had the default admin account with no password -- and accessed through about a dozen non-integrated apps that way; everyone used the admin account. 6 months of pointing out carefully to key people that this was a really bad idea made no difference. Some got it. None that got it could change anything. It's probably still that way. The rest of the systems weren't much better. I wouldn't touch them as I was not the admin on that project or one of the development staff; not my place to make that unilateral decision. I keep within my role even if it makes me jump up and down in frustration. [def: Frustration; the repression of the need to choke the living $#!7 out of some poor bastard that desperately needs it.])

      1. I don't consider the servers special because they have better hardware, but because that's where the data lives. No data lives on the workstations here. ...

      Good. Servers no doubt have a few weeks of backups, right? :}

      1. Also because configuration problems in the server affect everyone, not just the user of the single workstation. Yes, a workstation can cause problems for the whole network, but a compromised server immediately puts all the data/configs for the whole network in question.

      True. With that environment, you probably do system isolation at the router and elsewhere. (Ex: DB server A is used by web app server B and web app server B is used by everyone: Expose B on port 80 to the intranet, and set a route between A & B but not A & the intranet. DB A is exposed by tunnel/login, other DBs and apps are exposed on a 'need to know' basis.)

      Not too restrictive, though, as you don't want folks to have a reason to sneak around and undo/workaround what you have spent time setting up. (Ex: Getting root and setting everything to 777 on your *nix box because of frequent premissions errors.)

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    8. Re:Admins of their own machines by Anonymous Coward · · Score: 0

      Obviously you've never worked there. While there is a local admin account, for those who "own" the machine, their domain creds are added to the local admin group.

      Otherwise, publicly they don't run other OSs. Realistically, they do. Either to test software against, to perform testing with (some apps just don't run on NT) and because they've acquired companies (hotmail being one) that weren't running NT at the time of purchase. Yes they try and migrate.

      For my best donald rumsfeld:
      Do they have problems with worms?
      Yes
      Do they have problems with security?
      Yes
      Are they that much worse (internally) than other places?
      Probably not
      Do they test their products to death before and after release by running them internally?
      Yes
      Is there a company which doesn't have software development issues or security problems?
      No

      Having done a lot of work there, they actually are much better than I thought they were when there. Looking at how other companies are doing the same tasks, MS really isn't that bad. There is room for improvement. Individual items may look really bad, but that's because much more of their dirty laundry is made public where other software or end user companies tend to keep the issues more private.

      I don't love the place, and to claim their employees understand the risks of installing software better than most is completely false. They haven't figured out how to weed out the idiots better than any other company and in some cases it is worse because things can get very isolated up there.

  18. 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
    1. Re:Common by me+at+werk · · Score: 1

      We give all users admin rights and use group policies to remove them. It works fine.

      --
      For context, click Parent.
    2. Re:Common by jd142 · · Score: 1

      There's a very simple work around for this, provided the updates can be done silently. Just schedule a task to run as system. There's a couple of ways you can push a scheduled task out to people.

      GPO to run a batch file on computer start up. The batch file has the line:

      schtasks /create /sc once /st YOURTIME /sd YOURDATE /ru System /tn "TASKNAME" /tr "TASKTORUN"

      Because it's run as a computer start up script, it runs as system, which let's it tell it the task should be run as system (or any other user; system is just easier). Then the update happens automatically and the users don't need to be admins.

    3. Re:Common by pnutjam · · Score: 1

      If you find out where the updates are installing, both in the file system and in the registry you can explicitly allow users access to those registry keys and folders. Then they will be able to isntall files. I find Sysinternals software invaluable for figuring out where software is trying to write.

    4. Re:Common by Chemical · · Score: 1
      Using Client Access (iSeries Access)? Just do what my company's IT department does. Never upgrade it. No service packs, and no version upgrades unless you get a new machine/re-imaged.

      Not that I agree with that, as CA service packs fix a lot of problems, but I think their mentality is that CA is little more than an overglorified Telnet program, and as long as you can get a green screen there is no need to upgrade. We still have machines using CA V3R4! My machine has V5R1, which is still 2 releases out of date.

  19. 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 cowbutt · · Score: 1
      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.

      Sure, but on the other hand, I suspect this is probably at the root of why Microsoft can't really grok why their products are so hard to use in typical enterprises. Very few of the non-technical workers in most enterprises are competent at managing their machines, so tools to make this easy and effective to do centrally are a must. Microsoft are beginning to understand this, but they're still way behind UNIX (probably even VMS!) in this respect.

    4. Re:No, that one is obvious too by yuri+benjamin · · Score: 1

      That is one insightful analogy. I'll use it next time I send a request through to our "IS Helldesk".

      Mind you, I work in a call centre where it doesn't really apply in the same way.

      --
      You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
    5. Re:No, that one is obvious too by Anonymous Coward · · Score: 1, Interesting

      I work as a senior J2EE technical architect for a cable tv / isp / telco company. a big part of my job is evaluating new technologies i.e installing software.

      I have an XP workstation and the powers that be won't give me local admin access, so I basically can't do my job.

      Today the upgrade of a production app server failed because some support monkey decided to reboot a firewall while it was happening. That's right, a support monkey is allowed to reboot a piece of production equipment whenever they feel like it without consulting anyone, but as a highly qualified and highly paid Java expert I am not trusted to install the Java Virtual Macine on my own workstation.

      My previous job was working in global equities at a large investment bank, we had to pass a full background and credit check before they let us in the building, but we had local admin access of our workstations because IT knew we needed it in order to work effectively.

      Somehow I don't think I will be here much longer...

    6. Re:No, that one is obvious too by Anonymous Coward · · Score: 0

      no it is not. it is stupid thing to do.

      developers need a seperate devloper pc on a developer network with a bridge server between the developer's domain and the main domain. all regualr corperate work is to be done on the corperate machines, the development machines have access to only their network and NOT EVEN NET ACCESS.

      that way the latest virus that the CTO unleashes on the network will not hurt the machines that make the money for the company.

      pc's are dirt cheap, giving developers 2 each is a non issue.

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

    8. Re:No, that one is obvious too by Anonymous Coward · · Score: 0
      Major rule of networking....NEVER give someone more privelages than they need to do their job.

      That's why you are such a success, and Microsoft never amounted to anything.
    9. Re:No, that one is obvious too by lifeblender · · Score: 1

      Since your sig is on-topic, I'll just say that there is no way that IE is that much fun. It would need to come with at least three free drunken frats/sorors to compete.

      --
      Playing pornographics games during the day is evil! Play at night!
    10. Re:No, that one is obvious too by kaustik · · Score: 1

      This is your "IS Helldesk"
      We've been monitoring you web traffic due to some, ummm...., [flip, flip] 'unconditioned loopback reflux'. It looks like you've been surfing a lot of Slashdot. Maybe that is why you've had no time to back up your home directory? Too bad...

    11. Re:No, that one is obvious too by Grishnakh · · Score: 1

      That's the only way to run a network of computer-savvy users.

      No, that's a terrible way to run a network. Only system administrators should have root access to computers. Giving people more privelege than they need for their job is a recipe for disaster.

      The machinist analogy is a bad one. If you're a software developer, you do not need admin access. I write and test software all day on a Linux workstation, and I've never had root access. The only thing that's needed for is installing large software products for multiple users. I can install copies in my home directory (space permitting) for testing purposes.

      The danger of giving everyone admin access is that they can not only screw up individual workstations, but can alter or destroy files on the network filesystems which everyone depends on.

    12. 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?
    13. Re:No, that one is obvious too by the0ther · · Score: 0

      Apparently it is NOT obvious. I'm a programmer who doesn't have the admin password for my own machine. It's bullsh1t.

    14. Re:No, that one is obvious too by Anonymous Coward · · Score: 0

      You don't network a lathe or a drill.
      A lathe is self contained system, not a possible zombie box, etc

    15. Re:No, that one is obvious too by Frostalicious · · Score: 1

      Installing development related tools onto a developer machine needn't be a sysadmin task. If I am forced to call the help desk because I want to install some SDK documentation, I won't be able to do my job. Insisting that I do so would make you a network operator from hell.

      Request...DENIED!

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

    17. Re:No, that one is obvious too by FuzzyBad-Mofo · · Score: 1

      You are right, when one is using a decent environment. I think you'll agree that a developer needs the ability to install software. For those of us stuck using Windows at work, it's essential to have system-level permissions, since most software just can't be installed in the user account..

    18. 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
    19. Re:No, that one is obvious too by QuestorTapes · · Score: 1

      While -most- developers should not need root access to their machines, there are very definitely cases where some -need- it. If the developers are designing software that needs to run on a server, and need to test features common users do not have access to, they have to have admin access on their own boxes in order to unit test. They should not be running as admin most of the time, but it is needed sometimes. Other common reasons are to test server-side install processes, test automated upgrade features, and test agressive failure scenarios (mimic attacks, that sort of thing). Additionally, in about 50% of the shops I've been in, I needed to set up PCs for developers. In-house tech support couldn't handle it; they only know how to install a few user applications. Also, local admin access in Windows just gives them total control of their PC. If they log on as local admin, they have no special rights on servers or network filesystems.

    20. Re:No, that one is obvious too by slapout · · Score: 1

      NEVER give someone more privelages than they need to do their job

      Problem is, a lot of shops just go with default privelages. Which in some cases don't allow you to do your job.

      I had a coworker who wasn't allowed to delete an icon off his desktop because he wasn't the user that created it (it was a shortcut to word or something). It's one thing to limit users who don't know what they're doing. It's another thing to insult compenent computer professionals.

      --
      Coder's Stone: The programming language quick ref for iPad
    21. Re:No, that one is obvious too by slapout · · Score: 1

      Why not give any IT person who wants it admin access to there own machine? But with this condition: They screw it up, they have to fix it. They will get no support whatsoever from the help desk or system admin. If they fill it with spyware, they have to get it off. Give them a restore disk and let them start over any time they need to. If they do something that screws up the network, cut them off the network.

      --
      Coder's Stone: The programming language quick ref for iPad
    22. Re:No, that one is obvious too by WhiplashII · · Score: 1

      However forcing Microsoft developers to do that would ensure that the rest of us wouldn't have to!

      Who do we contact to get admin rights revoked for all Microsoft developers?

      --
      while (sig==sig) sig=!sig;
    23. 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.

    24. Re:No, that one is obvious too by Grishnakh · · Score: 1

      Because in an environment where compute resources are shared, all machines must work the same and must work properly. I can't do my work on just one machine; I need access to lots of them to run compute jobs. I have to be able to remotely login to lots of computers at once and run jobs on them, and have them all run properly. If people are screwing with their machines like this, this whole system of sharing resources will not work.

      Not only that, but the idea of making people responsible for their own machines is silly. It may sound good, but in reality, you'll end up with half your department not getting any work done because they don't know how to deal with their computer problems, and then your whole department will be in serious trouble. What are you going to do, fire them all? We already have enough trouble finding employees with the required engineering skills for this job. Everyone I work with is an engineer, and most of these people are not savvy about how to keep machines running well. When something happens with one of their Windows machines (we use both Windows and Unix), they take it to IT to fix it.

    25. Re:No, that one is obvious too by CynicalGeek · · Score: 0

      I think a better analogy would be truck mechanic=programmer and truck driver=sysadmin. Most truck mechanics can drive trucks, but most truck drivers can't fix them. The calibre of programmers you get in any decent shrinkwrap shop are perfectly capable of doing most sysadmin work.

    26. 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
    27. Re:No, that one is obvious too by gnuLNX · · Score: 1

      "If you are one of those rare programmers with sysadmin skills, "

      This statement certainly holds in reverse...but many (most) programers are quite competent when it comes to administering their own machines...or they are probably not very good programers.

      Sorry to burst your bubble there buddy but basic sys admin stuff is well...trivial...Note I said most...and basic...not all. Programming is a much harder skill to master for most people.

      --
      what?
    28. Re:No, that one is obvious too by COMON$ · · Score: 1

      I think what a lot of you are missing here is that many end users carry a lot of arrogance around with them. In my experience it hasnt been the ignorant user who screws up their PC or the Network. It is the Self Proclaimed Guru who installes the "free" tools or useful software on their PC for the betterment of their job. Then the system crashes because they did not understand the vulnerablilies in the software, or forgot to read the license agreement with the spyware disclaimer in it. Or For that point they put a file share program on the PC that Clogs the Network and shuts down an entire subnet. Not to mention the people who just HAVE to check their home e-mail importing the latest worm, now we have several infected servers, an overworked router and many users who cannot get their Job done. How many of you replying to this post would allow an unknown person to sit at their home PC with admin rights? Or just allow me to sit on your network with an Admin box. Yea, I am pretty sure I know what your answer to that question is. Problem is, in a Microsoft environment there are so many unknowns that any real-time Sys Admin knows that the best solution is to give users what rights they need to work. Dont make them Gods in an environment so they can have Webshots or that rare unecessary upgrade. I am guessing most of you complaining about these problems have never been put in charge of a real network and therefore do not understand the implications of giving users admin rights. I think you are just complaining because someone is limiting you and you cant stand having someone who has more power than yourself. I have a network of over 750+ users and their are 9 admins 3 sys admins. We cover an entire State for support and we get along pretty well without any user admins.

      --
      CS: It is all sink or swim...oh and did I mention there are sharks in that water?
    29. Re:No, that one is obvious too by Spoing · · Score: 1
        1. 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.

      Not really. There are different levels of dangerous;

      1. Total novice: Harmless and they admit ignorance. (Assumes you've configured the machine moderately first!)
      2. Moderately experienced: Typically cautious, though not always. Usually will not go out and do anything dumb.
      3. Begining experts: Tend to think they are experts in all software. Cocky and will assume they know what they don't and will argue that something they don't know is broken (sometimes it is...not usually!).
      4. Experts: Have gotten burned and will be extra cautious. This group assumes they are about to make a big mistake and will plot ways of undoing the dammage before they create it. Humble but knowledgable; this group knows what they don't know.

      If you put in controls and make people responsible when they screw up, you'll reduce the dammage caused by the beginning expert group. Some things should be handled by the IT department, even if it's a Jr. IT monkey.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    30. Re:No, that one is obvious too by Spoing · · Score: 1
      1. Sorry to burst your bubble there buddy but basic sys admin stuff is well...trivial...Note I said most...and basic...not all. Programming is a much harder skill to master for most people.

      Being an expert in one field doesn't make you knowledgeable in another. If you really believe what you say, guess where you'd end up on my list?

      I've worked with some top-notch programmers, and others that didn't know that there were things such as diff or that installing malware was a bad thing. I'd be a poor programmer...and there are plenty of poor programmers out there, just as there are plenty of admins that shouldn't be allowd on the systems they 'manage'.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    31. Re:No, that one is obvious too by Spoing · · Score: 1
      1. 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.

      BSEG! Yep, I assume every person using a system and every system connected to the network is about to cause problems with every other system it can see. It's so much easier to be nice to people when things can't be destroyed or -- at a minimum -- can be recovered.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    32. Re:No, that one is obvious too by Sexy+Commando · · Score: 1

      The environment you described is a situation where many people share a few machine. But in Microsoft people are given multiple machines to just play around. Nothing is really shared except files on file servers.
      You also ignored the fact that Those are local admins, not DOMAIN admins. People cannot screw with other people's files no matter what if the admin rights are only local to users' own machines.
      Why would you want other people to
      At the end you also give an invalid example on how those rlogin machines have to be locked down. It has nothing to do with people's desktops. Do you rlogin to reception desk's computer to build a project? Think not.

    33. Re:No, that one is obvious too by Anonymous Coward · · Score: 0

      You have never worked in a union shop. I can tell.

    34. Re:No, that one is obvious too by Anonymous Coward · · Score: 0
      If you are one of those rare programmers with sysadmin skills



      WOOHOO! Finally someone recognizes my skills!

    35. Re:No, that one is obvious too by MrTufty · · Score: 1

      Windows itself is not flawed for this reason. You're far too much into Unix to understand, but 90% of the reason you need Administrator rights to use much of Windows effectively is because of bad programming practices in other, third-party companies. Games companies in particular, with CD checks and protection that REQUIRE Admin rights because of the way they are accessing the hardware, or because they insist on trying to write to the program directory - which under XP Home is NOT allowed unless you have Admin rights. This should be considered a VERY VERY bad thing in my opinion, but is unavoidable (at least in the case of copy protection) because of the nature of the checks. The only thing that will fix this is a major re-education of developers.

      For reference, I'm not against Unix per se. I have used it, as I have Linux, and BeOS, and QNX also. Of them all, I've found Windows consistently more useful and easy to operate. After all, just because I am a geek with knowledge of development and command lines and system/network administration doesn't mean I want to or should have to use that knowledge just to perform simple tasks, like play games or even just install drivers for my hardware.

      And, as other people have pointed out - the Admin accounts that the guys and gals at Microsoft are being given access to are just for their own machines, not for the network....

    36. Re:No, that one is obvious too by Grishnakh · · Score: 1

      At the end you also give an invalid example on how those rlogin machines have to be locked down. It has nothing to do with people's desktops. Do you rlogin to reception desk's computer to build a project? Think not.

      If you're in a shared compute environment, yes. We even have utilities that let us automatically rlogin to the machine with the most resources available where I work.

      Of course, secretaries aren't using Unix machines here, but all engineers have them, and they're all used for compute jobs.

      How would Microsoft do work like this? Give every person their own compute farm? When I submit 500 jobs to be run, it'd take a week to do that on my own machine alone.

      Is this concept really so difficult for Windows users to understand?

    37. Re:No, that one is obvious too by Sexy+Commando · · Score: 1

      So you are basically saying that lack of sandboxing limits the users control to their own machines. Seti@home runs perfectly fine in a heterogenius envirnment. distcc runs fine given that you have the right version of cc or cross compiler on that machine. you can even rlogin to usermode linux or vmware or something. It's your implementation that force you to put a DRM on each machine and take away users' power to do whatever they like to their own machine.

    38. Re:No, that one is obvious too by Foolhardy · · Score: 1

      Good insight. There is no reason that (well designed) apps can't be run cross-platform natively or otherwise by virtulization. Forcing all users to have the same environment, in fact one out of the user's control, is an evil goal for DRM.

      Although in this case, I'd say that since the computers at work are owned by the company, it isn't really your computer.
      Still, the "let's assume all the employees are incompetent: we must protect them" attitude sucks. They should get admin until they actually break their computer; either for themselves or as a node in the cluster. As long as they can keep it working properly, give it to them: company admin can have the last word, as the company owns the machines, but give delegation a chance.

    39. Re:No, that one is obvious too by stephenbooth · · Score: 1
      It's your implementation that force you to put a DRM on each machine and take away users' power to do whatever they like to their own machine.

      I missed the bit where it was suggested about putting Digital Rights Management software on peoples machines. I know Microsoft do that in Windows (try ripping an audio CD in Windows Media Player on one Windows PC and then copying the files onto another Windows PC, odds are (unless the PCs are cloned copies) that you'll have to export the licenses from the first machine and import them onto the second PC to play them) whether you want it or not.

      Also, what's this "their own machine" business? If it's their work machine then (except in certain very rare situations) it's not their machine, it's their employer's machine. If I'm employing someone and providing them with desk space and equipment then I have a right (even duty) to control what they do with that equipment and what they can install on it.

      Stephen

      --
      "Don't write down to your readers, the only people less intelligent than you can't read" - Sign on Newspaper Office Wall
    40. Re:No, that one is obvious too by julesh · · Score: 1

      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

      I've never had a problem with an MS app. I'm currently running Win2K using a user with no admin priveleges, and other than installing updates all the MS apps I have on my system are able to work just fine. MS Word does _not_ need write access to any specific directory. I'm not sure what exactly you mean by "win32/" as there's no such directory, maybe you mean %windir% (aka "c:\winnt" on most installations) or possibly %windir%\system32, but whichever you mean, Word does not need to be able to write to it.

      That's not to say I have no problems at all. I need to run several programs as administrator to make them work. CD writing software seems to be the main culprit (and yes, I do have the local policy set that's supposed to allow that, it didn't work). I also have a parallel port scanner that won't work properly from a user account (it needs to write to "%windir%\twain32" for some reason). But all of these problems involve non-MS software, so I'm not sure whether I can blame MS for them or not.

    41. Re:No, that one is obvious too by Grishnakh · · Score: 1

      Who said anything about DRM? Do you even have any concept of what a Unix environment is like? This has nothing to do with sandboxing.

      These machines belong to the company, not the employees. If employees don't like that they can't install spyware on them, then they should find another job.

      The idea here is not that machines must all be identical, per se (they do run different Linux versions, kernel versions, etc.), but that they must be kept in a properly running state at all times. This means no unauthorized software hogging CPU time, no crap filling up the disks, and no idiots rebooting the machines for no good reason. It's a real setback when I rlogin to some other machine, run an 8-hour simulation on it, and then before it finishes some idiot reboots the machine.

    42. Re:No, that one is obvious too by Sexy+Commando · · Score: 1

      At where I work we are given at least two machines and can install whatever we want, including dual boot to other OS's. We are also allowed to listen to mp3 all the time while coding. Guess it's different culture.

    43. Re:No, that one is obvious too by Grishnakh · · Score: 1

      Obviously, CPU time is not a limited resource where you work. Try doing something that involves running 8-hour-long simulations in batches of 500 jobs at a time, where all this must be complete in one day.

      It's not a different culture, it's a question of possibility. How are you going to run 500 8-hour jobs on two machines in one day? Or are you going to give each person 500 machines? Or, do you take the sensible solution and set up a system where 500 people can all share their machines? This is the only thing that makes sense, and it simply isn't feasible with Windows, or worse an environment where everyone is dual-booting who knows what OS, doesn't have the correct setup for NFS which involves 100 different NFS filesystems, etc.

      In short, you're not working in an enterprise, where a lot of computing work has be done by a limited number of machines, which are all networked together with a very complex system requiring full-time 24-hour support by an entire corporate department.

    44. Re:No, that one is obvious too by Stradivarius · · Score: 1

      I think the key sentence in your reply was:

      "any real-time Sys Admin knows that the best solution is to give users what rights they need to work."

      That's exactly my point - being able to try and use new tools on your own is a fundamental aspect of the "rights they need to work". Particularly in the field of software development, where the available tools are continuously changing and improving.

      Dont make them Gods in an environment so they can have Webshots or that rare unecessary upgrade.

      I'm not arguing developers should be made Gods on their machine. As a developer, I don't care about or want privileges to upgrade the OS, install new hardware, change firewall settings, or any of a million other sysadmin tasks that need "God" privileges to perform. I'm asking for the ability to install and use the application software of my choice so I can be as productive as possible at my job. In a reasonable environment, that should not require "God" privileges.

      I would also argue that useful upgrades are neither unnecessary nor always rare, and that in any case, the developer is the person who is in the best position to determine what is "necessary" to his or her job.

      Finally, with regard to the Self Proclaimed Guru screwing up their PC or network: can it happen? Sure. It's a risk that needs to be managed. But risk avoidance isn't the same as risk management. One way to manage that risk in a software development shop: give the developers a mandatory training session on Dos & Don'ts for installing software, and monitor their machines. If they ignored the training and screwed stuff up, you have a policy in which they get educated on their mistake, and in which repeated violations lead to a revokation of privileges.

  20. From the article by grub · · Score: 0, Redundant


    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.

    If you don't run anything other than Microsoft products how can you "make sure Microsoft products are the best"? It's easy to compete with a field you get to choose.

    --
    Trolling is a art,
    1. Re:From the article by Anonymous Coward · · Score: 0

      Of course, the next paragraph states:
      We do, in areas on the client, have an open-source client running--just for competitive analysis

    2. Re:From the article by Anonymous Coward · · Score: 0

      If you don't run anything other than Microsoft products how can you "make sure Microsoft products are the best"? It's easy to compete with a field you get to choose.

      Well, they're the best products in his world.

      By definition.

    3. Re:From the article by spac3manspiff · · Score: 1

      Sollog told him that ignorance is bliss :/

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

    5. Re: From the article by Alwin+Henseler · · Score: 1
      Another lovely quote: "The drawbacks? You do find issues. We're testing at alpha stage and beta stage, so you are going to find issues."

      Hmmm... I thought it was: alpha stage, beta stage, release, service pack 1, service pack 2, some more updates, and still you are going to find issues.

    6. Re:From the article by JustNiz · · Score: 1

      >> My goal is to make sure Microsoft products are the best products in the world.

      Bwahahahaha

      The only way that is going to happen is if Linux, OSX, Solaris and just about every other real OS dissapear first, therefore his goal is unachieveable.

    7. Re: From the article by Anonymous Coward · · Score: 0

      As opposed to Linux ...

      Beta stage, beta stage, beta stage, release, advisory, patch, advisory, patch, advisory, patch, advisory, patch ... ... And it's still slow and a hackjob.

    8. Re:From the article by TheOriginalRevdoc · · Score: 1

      I have no doubt that Oracle run their own software, but I doubt very much that they run their production business systems on alpha or beta DBMS releases, as MS do.

    9. Re:From the article by SvendTofte · · Score: 1

      It's called "eating your own dog-food", and it's something Microsoft is famous for. And it's of course a good strategy (in most ways). Don't RMS run GCC/Emacs himself perhaps?

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

    1. Re:Software Audits? by Anonymous Coward · · Score: 1, Informative

      Disclaimer: I'm a Microsoft employee.

      I'm running FireFox right now on my dev box at MS. I use the google desktop search (though I'm thoroughly impressed with the MSN one and am migrating). I can't contribute to open source, nor have I looked at any OSS code since I started working here...I only run binaries. At Microsoft, you're more than welcome to call it as you see it. It's no secret that many of us use other browsers and state openly that the company's fallen way behind with IE. I'm not asked not to use the software, and I'm certainly not being fired.

    2. Re:Software Audits? by Anonymous Coward · · Score: 0

      It's no secret that many of us use other browsers and state openly that the company's fallen way behind with IE.

      Says the A. Coward.

    3. Re:Software Audits? by Spy+der+Mann · · Score: 1

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

      The name wasn't Johnson. It was "Mr. Anderson".

    4. Re:Software Audits? by Procyon101 · · Score: 1

      Non Coward here. Sql Server Team Bldg 35 representing!

      Running Firefox.

      I use Firefox for all my browsing except intranet sites, as many of the intranet sites use really weird IE only stuff that firefox chokes on.

  22. Our users are the admins of their machines by Dynedain · · Score: 1

    Well, that clearly explains why the OS and applications are designed for the end user being an admin. Explains why all the non-admin accounts are such a pain to setup and get working with the permissions you want.

    --
    I'm out of my mind right now, but feel free to leave a message.....
    1. Re:Our users are the admins of their machines by jacksonj04 · · Score: 1

      I personally think this isn't Microsoft's fault - it's a throwback to the days of 95 when you had 'Users'. Not users with permissions, just users.

      Many companies haven't yet worked out that Windows is tightening up security.

      --
      How many people can read hex if only you and dead people can read hex?
  23. 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!
    1. Re:Nice Knee-Jerk by BrianHursey · · Score: 1

      I work at a university in the IT department, and I see that the majority of users are not competent enough to be their own local root. You would be amazed at the kinds of things that they do to their system. 75%+ of problems with systems on campus are user created errors from either improper management of the system or lack of update practices by the user.

      --
      Linux is like a teepee. It has no windows, no gates, and there's an Apache inside.
    2. Re:Nice Knee-Jerk by Anonymous Coward · · Score: 1, Interesting

      Seems kinda crappy that those tools you use need root access to run...

    3. Re:Nice Knee-Jerk by Lord+Kano · · Score: 1

      I nearly got fired from a job once because "IT" locked the machines down too tight.

      I needed to be able to see and change file extensions. Our accounts didn't allow this. I went to my my supervisors and asked for our accounts to be allowed to do these things. My requests were ignored.

      I had to find a creative way to get around the idiotic limitations that were imposed by "IT". The assumption that no one had any experience with DOS were my way. I would get a DOS prompt and manually change file extensions as I needed to.

      While plumbing around in DOS I found some things that "IT" didn't think we would. For example, all of the machines were running file servers, but we weren't supposed to share any files.

      I shared this with the supervisors and as a result my employment was threatened for using "unauthorized functions".

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
    4. Re:Nice Knee-Jerk by fermion · · Score: 1
      So MS should tell customers to limit MS Windows machines to those people that can be educated and will not download stuff just because they think it is funny to screw thier boss. (When the 900 numbers first came out, I was in a sales office where the sales people would call the number just to run up the phone bill).

      If the cost of education and monitoring is too great, then MS should suggest the customer buy non-MS solutions.

      Problem solved.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    5. Re:Nice Knee-Jerk by swb · · Score: 1

      I'll take a small step up to bat for IT here...

      We run into self-styled "developers" and "civilian sysadmins" from time to time who insist on doing something, despite our policies dictating otherwise.

      The problem is that even well-managed IT is a house of cards and it only takes a couple of instances of someone doing "the right thing" for their 5 person workgroup for the entire thing to become and unmanageable jungle.

      Even then, you're often the target of their myopia -- they're pushing X because it's good for their career or some other one-off situation and they could actually care less that whole other 100-plus person departments get degraded service. I've had mangers asking about client upgrades tell me, point-black, when told that upgrades were being done "as needed based on PC age" that they "didn't give a shit about other people, they only cared about their people" -- and this was from someone who managed about 8 people.

      Even when we've largely agreed with them and let them push the big red buttons, we find a lot of abandoned projects that didn't work well or caused (localized) havoc because they ignored our advice and policies.

      IT policies aren't always great, but they're usually a delicate compromise between someone else's financial and accountability goals and technical viability. The result is admittedly not always pretty or rational on the surface, and such are compromises.

      I'd be curious as to how many companies structure their IT in such a way that if a department or workgroup wants to call all the shots they can, but they have to either pay for it (new computers ahead of schedule? Sure, explain your loss in profitability) or lose access to other parts of the network or support.

      My guess would be that the trend is consolidation and centralization, not individual choice and opportunity, since the former at least promises cost savings based on economies of scale and standard "best practices". Not calling it always the right answer, mind you.

    6. Re:Nice Knee-Jerk by Lord+Kano · · Score: 1

      There is a difference between maintaining the integrity of the infrastructure and just making their own jobs easier.

      The example I was referring to earlier came about because one of the programs that we used didn't always properly assign file extensions. For example, PDFs would be DOC or TIFs would be BMP, things like that. They made it exceedingly difficult for us to make the changes as needed. I was the only person below the rank of supervisor who had the access(because of my own creativity) to make the changes and the only person including "IT" who knew what the problem was.

      LK

      --
      "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  24. 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.

  25. 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.
    1. Re:Don't run unix, eh? by urbaneassault · · Score: 1

      My guess is that's not the case anymore.

  26. why he does what he does by Kipsaysso · · Score: 1

    As an IT organization, I have no skills and no ability and no purchasing of those (Linux) products.

    I would Work for microsoft too if I had no Linux skill.

    --
    This is another way of starting a sig with this and ending it with that.
  27. I wonder by spac3manspiff · · Score: 1

    , but we do audit the network continuously

    Then I wonder if they allow users to use firefox and Linux.

    1. Re:I wonder by TheGrayArea · · Score: 1

      We had more than one linux box running in my group. We actually had cases where we needed to test against pulling files off a samba share to see what happened. Firefox wasn't there yet when I was there, but I did know guys running various mozilla flavors.

      --

      This space for rent.
  28. Curious aint it? by Baron+von+Blapp · · Score: 0

    So if the end-users are the admins (something I let the programming dept at my last job do) that means they can install *n*x or Opera... Hehe, even Solaris :D

    --
    "It's too bad she won't live, but then again who does?" - Gaff
  29. Social Reinforcement within MS by 8tim8 · · Score: 1
    I wonder how much time is spent combatting spyware?

    Because MS is such a geek culture, I'd be interested in finding out if what the social reprecussions are for someone finding malware on their system. If you consider yourself to be an alpha geek, are you really going to be calling the helpdesk about a computer issue that you brought on yourself?

    1. Re:Social Reinforcement within MS by TiggertheMad · · Score: 1

      Because MS is such a geek culture...

      Having worked there, there are a lot of really smart people there. However, it is a large corp, so I'd say 90% of the employess are not the 'uber geeks' that you picture them as. Most people that work there are only slightly more techno-savy than the average white collar workers.

      Several years ago while working there, I had to explain what an .ASP page was to my boss. He wasn't stupid or anything, just not a coder. I'm not sure that he really fully got the idea.

      --

      HA! I just wasted some of your bandwidth with a frivolous sig!
    2. Re:Social Reinforcement within MS by TheGrayArea · · Score: 1

      You rarely called the helpdesk. Most folks fixed their own problems other than hardware and network lockouts. I've seen many a net tap disabled because someone's machine caught the latest worm/virus going around, so it did happen. You'd make fun of them and then go on with things. It really wasn't that hard core socially when those things happened.

      --

      This space for rent.
  30. 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 yamla · · Score: 1

      SCO claimed that Windows interferes with the SCO intellectual property. Furthermore, SCO claimed that the money they got from Microsoft did NOT prevent SCO going after Microsoft's customers for violation.

      So why did Microsoft pay all that money? Officially, to protect Microsoft (but not Microsoft's customers) against claims from SCO.

      --

      Oceania has always been at war with Eastasia.
    2. 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
    3. Re:We don't run Unix. We don't run Linux. by happyfrogcow · · Score: 1

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

      too bad it's not http://www.microsoft.com/windows/stfu/

    4. Re:We don't run Unix. We don't run Linux. by justins · · Score: 1
      http://www.microsoft.com/windows/sfu/

      too bad it's not http://www.microsoft.com/windows/stfu/

      The t is silent, you ignoramus.
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    5. Re:We don't run Unix. We don't run Linux. by Anonymous Coward · · Score: 0

      Bollocks. There are a lot of Mac OSX Powerbooks being used in the Microsoft production studio. I've seen them firsthand.

    6. Re:We don't run Unix. We don't run Linux. by Anonymous Coward · · Score: 0

      I think microsoft made SCO in order to have someone else as "The Bad Company" and distract the crowds. Seriously. Darl McBride was bribed. He took the money man. He took it. Directly and indirectly.

    7. Re:We don't run Unix. We don't run Linux. by Anonymous Coward · · Score: 0

      They don't run Linux for their internal IT infrastructure. They still run Linux for other purposes, such as product comparison testing.

      How many times are people going to have to post this to people in this article discussion? I've seen it five times already. THIS IS TALKING ABOUT THEIR IT INFRASTRUCTURE. Geez. When did the majority of Slashdot's readership become illiterates? I miss the late 90s when everyone didn't randomly reference SCO all the time to score mod points.

    8. Re:We don't run Unix. We don't run Linux. by Flamesplash · · Score: 1

      MS made a version of IE for solaris a while back, say 98ish. While they may use *nix in some groups, it is in no way prominante there, maybe .1% (50) of people there . I worked there for 3 different summers and never ran across anyone using *nix for a project.

      --
      "Not knowing when the dawn will come, I open every door." - Emily Dickinson
    9. 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...

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

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

    1. Re:Pain by twiddlingbits · · Score: 1

      That's not funny..Should be modded insightful. The concept of "eating your own dog food" is actually a very good way of testing products prior to external release. Cisco does exactly this same thing. The QUALITY of the iternal testing must be lacking at MS (or the exec you mention was full of crap) since to many bugs seem to make it into the final product. The theory is fine, the application of it seems weak in Micrsoft's case.

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

  34. 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 JustNiz · · Score: 1

      > They have a lot of smart talented software engineers who are just as capable of administrating their own computers..

      Bullshit. If that was true, Windows wouldn't be full of security holes and wouldn't suck.

      Microsoft perfer hiring new grads with no real world experience because they can get away with paying them shit and they work long hours. (a.k.a. 'the EA mentality' ).

      Thats one of the reasons why Windows (still) sucks and is (still) full of security holes.

    3. 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.
    4. Re:Software company, not bozos by Holdstrong · · Score: 1

      That's some twisted logic there. Just because you are writting software for a computer does not in anyway mean you are a capabale or trustable administrator of that computer.

    5. Re:Software company, not bozos by tclark · · Score: 1

      I'd guess they also have a large number of general purpose office pogues perfectly capable of rendering a brand new machine unbootable before lunchtime.

    6. Re:Software company, not bozos by Dynedain · · Score: 1

      On the other hand, he's the biggest beta tester MS has. If the betatest environment assumes that all users have local admin of their machines, development for the contrary will be lacking (as we can readily see).

      --
      I'm out of my mind right now, but feel free to leave a message.....
    7. Re:Software company, not bozos by abertoll · · Score: 1

      I agree. A lot of people out there in the working world consider what they do a job, and leave it at work. Sure they might love software "engineering" but a lot of them don't go home to do more programming, or have even bothered with system administration.

      Only the people who are really interested in doing it for themselves are going to go above and beyond the call of duty to learn something that work isn't asking them to do.

      --
      "he drew his sword Ringil that glittered like ice... and he wounded Morgoth with seven wounds..."
    8. 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.

    9. Re:Software company, not bozos by Anonymous Coward · · Score: 0

      so true.. I know one software developer who can't admin a Windows box worth a shit. He's always got spyware/adware and always reinstalling. He's also too stupid to use a firewall at home, even after being warned to do so many times. He's not a great developer either, but he can code software that works.. You'd think he'd have enough sense to keep a Windows machine clean.

    10. Re:Software company, not bozos by armer · · Score: 1

      Ah but don't forget, not all of them are software engineers, you also have bean counters, lawyers and secretaries as well. Just because they work for M$, does not mean the are smart and/or talented...

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

    12. Re:Software company, not bozos by Anonymous Coward · · Score: 0

      Pardon me for urinating all over them, but... it's MICROSOFT. They can go fuck themselves.

      Peeves me off when someone gets peeved off about a growing American sentiment that nobody should be trusted with tools, when billy bathgates protection services, Inc. is the prime instigator of that mistrust. Witness palladium.

    13. Re:Software company, not bozos by Anonymous Coward · · Score: 0

      You forgot the "and we can login multiple times" and the "we can login remotely multiple times" and the "we don't have to be logged in for something to run", etc.

      Windows is still in the backwaters of system priviledges. Priviledges are still not truly integrated into the core system. The system still shows lots of single-user per machine mentality.

      Priviledges are still associated with accounts per login basis. Priviledge elevation of logged in accounts does not exist. etc.

      Nope, windows is still one step foward and one step back.

    14. Re:Software company, not bozos by Foolhardy · · Score: 1

      You can log in as many times as you want, remote or local. This has been true since the very first version of NT; NT has always been multi-user. See AT, telnet, any one of the many SSH servers, etc. Oh, you meant GUI sessions? Does UNIX require X to be multi-user?

      One of the core kernel subsystems is the Object Manager. It handles all kernel objects accessible from user mode, handles to them and security on them; everything from files to events to mutexes to processes to memory sections. It has existed since the first version of NT and provides object security integrated in the system.
      A token object represents a process or thread's security identity and priviliges. TCB components can add whatever privilieges they want to them; elevate them to whatever level. Perhaps you just don't know how.

    15. Re:Software company, not bozos by praxis · · Score: 1

      Microsoft applications, much more so than third-party applications, behave well when installed and run as a non-Administrator account. In fact, in the last three years, every problem I've had with using software on my machine due to it being written with poor assumptions (like access to every registry key, folder, etc) has been with non-Microsoft software. I don't run as Administrator and have no problem with it.

    16. Re:Software company, not bozos by MrTufty · · Score: 1

      But who decides what they need to be efficient? As a programmer myself, I know already that my working methods are different from other programmers. The end result might be the same, or similar, but the way in which I get there is different. So how could you say, "this is what you need to be efficient" in a situation like this? The result of that is forcing everyone to work in the same way, turning your staff, whose creative abilities you RELY on, to act as clones, stifling those talents in the interests of Efficiency. Sorry, doesn't work.

    17. Re:Software company, not bozos by jellomizer · · Score: 1

      Well if you ask your administrator to install a free tool. They normally will do it just as long as you can justify why you need it. But even in the OSS community there is a lot of programs that are written with the programmer with root access. (Hense Dependancy Hell), oh Ill install this library and this one. Sure that may make them efficient in there program but you end up with a program that only the programmer can install.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    18. Re:Software company, not bozos by thegoofeedude · · Score: 0
      root and administrator really can't be compared.
      Yeah, root is way cooler.
    19. Re:Software company, not bozos by drsmithy · · Score: 1
      On the other hand, he's the biggest beta tester MS has. If the betatest environment assumes that all users have local admin of their machines, development for the contrary will be lacking (as we can readily see).

      Note that there's a difference between "having local admin" and running as an Administrator user _all the time_.

    20. Re:Software company, not bozos by Anonymous Coward · · Score: 0

      IT's MICROSOFT! Read NIMDA, CODE RED, ILOVEYOU, and 3800 friends this year, 3500 friends last year, tens of thousands of other security flaws over the years. Then there is the performance of the product. Very frequent reboots. Shockingly shoddy memory management --I worked for a company who put more memory into peoples computers so that the machine would not crash before the end of the day--, shockingly poor performance, obtuse system design (who was the fscking lightbulb that designed the system registry, --it is at once a prime target for the malicious, a zoo for the administrator, a single point of failure for the entire system, insane from a maintenance perspective (making it so that you can only use only highly specialised tools to edit it provides what exactly?) making it an overly hierarchial design instead of a more object oriented one where software and their settings are grouped logically was supposed to do what exactly? Was the point obfuscation for it's own sake? The clown show that stuck the browser and the window manager into the operating system was in your opinion brilliant? What are you, drunk? Breaking the rule of making software out of small modular verifiable logically verifiable blocks was a good idea in your opinion? When they steal code from other people, they are talented? No, I believe you are (quite) mistaken. Microsoft is loaded (overloaded?) with bozos. Either that, or whoever is in charge has not clue 1 about how things should be built, no idea of sound software design, no idea of planning, no idea of performance. I would suggest that the place is run by a clown from marketing who believes that everyone should wear a tie as that 'makes the software better', that software should be made fast and simple, that software design should be an afterthought, and that "no one will notice the bugs, and we have to ship tomorrow, ready or not here we come!" They *ARE* bozos. Their glory days are done. All they ever did is make a few of their founders very rich. They screwed a lot of people to do it (maybe even you). Bill Gates said "I dare ya to beat me", and the software community took him up on the challenge. Now he's whineing that they did. Their product is shit! Pretty much anything else out there is better than theirs. I've seen and used over 30 "different" systems. Have you ever seen any more than one? What is your basis for comparison if you've never seen another? The truth is that a computer should normally run (hard all day, all night for years) without ever needing to be rebooted or reset. Unix systems have an uptime command, why not Microsoft? Unix based computers never come with a 'reboot' button, not so with Microsoft. Microsoft is a blight on the computer industry. They tarnish the reputation of real computer professionals. They are a joke, and a laughing stock at the best, and a wretching hoare at the worst. They bought out most of DOS from ABC computer of Seattle, IBM took their 'product' and pulled the bugs out (of 8000 lines of assembly, there were 3000 lines of bugs). They tried to steal doublespace from Stac electronics, their version sucked so hard they got sued, and they got sued from Stac, they they bought out Stac. They stole OS/2 code from IBM and called it NT, and that is why you still get OS2 compaitbility layers right up to NT5 (they call it XP). NTFS still is 90% of HPFS. Their own networking layer --winsock-- sucked so hard and worked so badly that they dropped it, and 'lifted' the TCP/IP stack out of BSD unix and put it into NT --now they say they 'rewrote' their TCP/IP stack so that all the BSD code is gone, uh huh. There is the entire window manager that they 'lifted' from apple --and to give proper credit, apple got it from Xerox, whose foundry was at XEROX/Parc and Alan Kay and Doug Englebart should get a lot of credit. So their system isn't as 'pristine' as you suggest. Their 'EXPERTS' are better at 'Modifying' code others wrote, rather than anything original, and by the way, their software lookes 'hacked' rather than crafted, but that's what you get when you shove pieces together rather than properly writing software to work and an integrated whole. I hate to rant, but you really don't know what you are talking about.

    21. Re:Software company, not bozos by julesh · · Score: 1

      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.

      There's quite a difference between "being the administrator of your own machine" and "being logged in as Administrator all the time rather than using a regular user account". While the latter implies the former, the former does _not_ imply the latter.

    22. Re:Software company, not bozos by jedidiah · · Score: 1

      Sure it does. Certain operating systems, that need not be named, require anyone to have what would be at least a subset of root-style priveledges just to be usable.

      No amount of Wizardry can make up for pisspoor tools.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    23. Re:Software company, not bozos by cortana · · Score: 1

      > Admin/user in windows exists almost purely for sys administration tasks

      And to run most third party software.

    24. Re:Software company, not bozos by julesh · · Score: 1

      Sure it does. Certain operating systems, that need not be named, require anyone to have what would be at least a subset of root-style priveledges just to be usable.

      No amount of Wizardry can make up for pisspoor tools.


      Well, I'm sitting here using Windows 2000 from a non-administrator account, and haven't needed to log in as administator for over 6 months. And I consider myself a power user. So obviously that isn't the system that you're talking about?

  35. 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 Anonymous Coward · · Score: 0

      How about Hotmail? Does it still run on *BSD?

    2. Re:No *nix? by nutbar · · Score: 1

      He's talking about in their IT infrastructure, bozo. Not their test beds. RTFA. Properly.

    3. 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.
    4. Re:No *nix? by Keeper · · Score: 1

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

      Just because the IT ifrastructure is all Microsoft all the time, it doesn't mean that his comments translate to every other department in the company.

    5. Re:No *nix? by kylef · · Score: 1
      100% Windows? Wow, that must make the Macintosh BU's development efforts pretty hard.

      No, it doesn't. Macs run fine in a 100% Windows infrastructure environment.

      100% Windows in the IT department doesn't mean Microsoft the company only runs Windows.

  36. So, do they run Great Plains or Axapta? by winkydink · · Score: 1
    As both of these are MS ERP products?

    100% Microsoft my foot.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:So, do they run Great Plains or Axapta? by Nino+the+Mind+Boggle · · Score: 1

      Other than the fact that these are both MS ERP products, do you know anything else about them? Like the size of the companies and which industries they're targeted at? ERP solutions aren't one size fits all.

      Would you be just as snarky if you found out that Intuit doesn't run Quickbooks and that SAP doesn't market to the coffee shop on the corner?

      --
      ------ "Darn floor. Big bite." (Koko the gorilla's best attempt at explaining the experience of an earthquake.)
    2. Re:So, do they run Great Plains or Axapta? by winkydink · · Score: 1

      No, I'm snarky because their CIO said, "we don't use competitors products". I don't recall Intuit's CIO making a similar claim and my coffee shop on the corner fired their CIO when the dot-com bubble burst, so I can't ask them.

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    3. Re:So, do they run Great Plains or Axapta? by drsmithy · · Score: 1
      No, I'm snarky because their CIO said, "we don't use competitors products".

      Note that a non-Microsoft product in a market segment they don't compete in *isn't* "a competitor's product".

  37. Anyone have Weblogs with MS IP Ranges? by Proudrooster · · Score: 1

    I no longer have access to ISP weblogs, but I seem to remember taking a browser census and noting that vistors from MS were indeed running Mozilla under Linux.

    This makes sense and is consistent with the CIO's statement. Since each user is their own administrator, they are allowed to wipeout windows and run any Linux distro they want. They probably use use VMWARE or VirtualPC to host their Windows OS and quickly switch to full screen whenever a manager is around.

  38. 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
  39. Hmm... by which+way+is+up · · Score: 1
    We don't run Unix. We don't run Linux. We don't run Oracle. We're 100 percent Windows, SQL Server.

    Notice he didn't say 'Mac'. The mac business unit runs macs as well as the people doing the graphic design and print work. Unless of course he was only referring to the server OS's

  40. >We don't run Unix. We don't run Linux. We don't run
    >Oracle.

    And our TCO sucks! By giving our users Admin access, we don't have to support them ALL THE TIME, they support themselves. Heck, would you want to? So our TCO numbers are not as bad as they might be at least.

    - MS CIO

  41. I'm sure they run *nix on Virtual Server 2005 by vision33r · · Score: 1

    They have to in order to insure the product works as advertised.

    1. Re:I'm sure they run *nix on Virtual Server 2005 by alc6379 · · Score: 1

      Why do they have to do that? From one of their whitepapers on the topic:

      Virtual Server 2005 optimizes Windows guests for computing, storage, and networking performance, and provides support for:

      Windows Server 2003, Standard Edition
      Windows Server 2003, Enterprise Edition
      Windows Server 2003, Web Edition
      Windows Small Business Server 2003
      Windows 2000 Server
      Windows 2000 Advanced Server
      Windows NT Server 4.0 with Service Pack 6a

      I'm quite sure that it could run *nix (my personal experiences have shown you can run *nix well enough on Virtual PC 2004, the technology behind VS2005), but that's not the target deployment, from the docs I've found. They only support their products under VS2005, and it's just a possible added benefit that you could run other x86 OSes on that platform, too.

      --
      I don't moderate anymore. Karma penalty for 90% fair mods? Can I mod that unfair?
  42. That explains everything! by StLawrence · · Score: 0

    Now I understand why Microsoft is having such a difficult time
    making reliable & secure software... They spend most of their
    time dialing with viruses & other assorted malware.

  43. Are they even allowed to ... by Anonymous Coward · · Score: 1, Interesting

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

    Could that be why they don't run Linux or Unix? It would be interesting to know if they reprimand those who want to run linux, unix or solaris? Policy with regard to people choosing to run open source products, on their machine, would also be interesting.

    1. Re:Are they even allowed to ... by Anonymous Coward · · Score: 0

      He also said thay can run anything on desktops. Maybe that includes Linux.

      And maybe they do the same as linux guys: they have a normal user account jdoe and use 'Fast User Switching' or 'runas' to do admin-level tasks. We don't know, actually.

  44. RTFA by Anonymous Coward · · Score: 0

    We do, in areas on the client, have an open-source client running--just for competitive analysis

    That's in the paragraph about not running other OS's and stuff. HE doesn't run Linux, but there are people checking it out for competitive analysis.

  45. 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.
    1. Re:Best practices by Anonymous Coward · · Score: 0

      "I hope some of those users are smart enough to give themselves a luser account and run under it" - Yes, this is the case.

      "Maybe they have an enforced policy of using anti-spyware and anti-virus software" - Yes, they use 3rd party software.

      "Maybe they have extensive training classes with stock options going to those who don't spread viruses" - if your computers spews out too many packets, they shut down your network access; this is to prevent slammer-type viruses from spreading.

    2. Re:Best practices by Anonymous Coward · · Score: 0

      Or, instead of making a bunch of karma-whoring, M$-bashing assumptions, you could read the MSDN blogs and see that most of them run under accounts with limited privileges and bitch when an app requires otherwise.

      All this article said is they're allowed admin privileges for their machines. Since they're Microsoft devs, what is wrong with that? I'm sorry, continue drawing a bunch of completely random conclusions based on your own negative opinions of Microsoft.

    3. Re:Best practices by LurkerXXX · · Score: 1
      If they are doing it they way I'd assume, they have a regular Active Directory username they normally log in to do their work. The users aren't assigning themselves these normal 'working' username. That would all be handled by the Domain admins.

      In addition, they probably also have a separate username on that individual machine that is the admin group on that individual machine. Just for installing software specific to the user.

    4. Re:Best practices by Anonymous Coward · · Score: 0

      you can make a domain user admin of a single box locally if you are admin on that box (as a local user or whatever)

    5. Re:Best practices by KJKHyperion · · Score: 1

      Yeah, that must be why all of Microsoft's software can install and run under any account (their packages even default to My Documents as the destination of single-user installs). Since you mention ActiveDirectory, you can use AD to publish your applications to groups or OUs - as soon as anyone tries to run a published program that isn't installed on their workstation, it gets installed automatically, for the whole workstation and whatever the kind of user that started the program in the first place

      --

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

    6. Re:Best practices by LurkerXXX · · Score: 1

      Right. But folks are probably normally going to do their work as the domain user. And running as admin all the time is DUMB, so it's not a good idea to make the domain user account the admin. Make a separate admin account for doing the software installs, not the domain account you normally work as.

    7. Re:Best practices by bmajik · · Score: 1

      1. AV software is mandatory on all managed computers

      2. AD does nothing to prevent you from creating user accounts on a workstation you have local admin rights on. What is usually done is your AD network credentials are NOT given admin rights on your local workstation, and you create a local admin account instead (with no network rights). Note you can, using your normal user account (i.e. network rights), get local admin privs without revoking your network privs if you use "runas" properly

      I've worked at MS for almost 5 years. I've never run across an employee infected with spyware on a work machine. It may happen, but I suspect the employee responsible wipes their box quietly pretty shortly after contraction of the malware.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    8. Re:Best practices by drsmithy · · Score: 1
      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?

      Works fine.

  46. 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 - =-=-=-=-=-=-=-=
  47. ok, comedy gold, but! by ross_winn · · Score: 1

    since when did Hotmail start running on Windows Advanced Server? I think this may be a bit of a lie.

    --
    Ross Winn "not just another ugly face..."
  48. 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".

    1. Re:A Sound Knee-Jerk Reaction by chigun · · Score: 1

      I have to disagree with this one. I run a complete/updated virus/spyware scan about once a month. I usually have zero virii and probably about 1-6 spyware apps running, but nothing too bad. usually just a few cookies I didn't want and something like alexa toolbar my girlfriend probably let through by accident. I consider my myself tech savvy and my machine is pretty well locked down from the outside world unless I explicitly let something through.

      On the other hand, whenever a friend or family member asks me to "fix" their computer, I usually find out their computer is nigh-unusable due to the LITERALLY thousands of spyware apps running on their computers. Totally infested with any number of virii and trojan is par for the course as well. When I say unusable, I mean it too.

      Broadband for the masses has not been an altogether good thing. Much of my family/friends don't actually need it, because all they do is check their email once a day and surf sites like nytimes.com anyway, but they have it anyway and now claim not be able to live without it. These same users are completely unaware of windowsupdate.com and have only the vaguest (if any) understanding of what a firewall is.

      It's these users that spyware and virii target. It's not even tech savvy anymore. These people just click through things without paying attention to what it says/does. These users are much less "tech-savvy" than they are "observationally ignorant."

      --
      swanker than you
    2. Re:A Sound Knee-Jerk Reaction by rizzo420 · · Score: 1

      i beg to differ. while yes, i admit that i know some computer savvy, techie people who are smart and still haev spyware on their machines, it's not anywhere near as bad as the less savvy people i see. i do this stuff for a living. i see a lot of computers each week. the biggest problem is spyware/adware stuff. some have viruses, but when we give out managed virus software, it limits them. the people who come in who seem to know what they're doing don't have anywhere near the number of infections that those who have no clue have. i hear things like "oh, i thought that away message that said "OMG!! LOOK AT THESE PICS!" was a real link to pics (if you don't know that one, it's an AIM hijacker, links to a .scr file). or how about "the page said i was infected so i clicked the link to clean my computer, it hasn't been the same since." right... yeah, people who know anything don't click those.

      i'm not making excuses for MS, but you should realize that the worst infections, sometimes nearly beyond cleanup are not the savvy people. i haven't had an infection on my personal machine ever if i think about it. i probably wouldn't even run virus software if i wasn't receiving viruses in emails from members of discussion lists i belong to. for the record, i do run anti-virus, i run win2k, and i use firefox (IE for windows updates and IE-specific pages only).

      i don't blame it entirely on MS though. it's possible to combat it, it's possible to avoid it, it's possible that other operating systems would have similar issues if they were as mainstream as windows.

      --
      please me, have no regrets.
  49. 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.

  50. Bad poster! by StLawrence · · Score: 0

    You said "girl." That's gonna hurt your karma...

  51. whoops, read as... by claussenvenable · · Score: 1

    "Good article over at CNet regarding Microsoft's infernal IT practices. Some intriguing "

    nothing to see here...

  52. Re:Nice Knee-Jerk (but accurate) by gosand · · Score: 1
    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.

    You think a company, ANY company, doesn't have its share of non-techno-savvy idiots installing spyware? I work with people who are somewhat tech savvy, yet they still get spyware. Do you actually think that a company the size of Microsoft is any better, if not worse? They have marketing people, they have sales people, they have non-tech related people. In fact, I would venture a guess that they are proportionally LESS tech-savvy than most small companies. They brought us Clippy for crying out loud!

    I don't think that this is an unfair assessment of Microsoft at all, it shows their attitude towards software perfectly.

    --

    My beliefs do not require that you agree with them.

  53. It's a Viral mess by Anonymous Coward · · Score: 0

    There was a time when I worked for Microsoft. It was kinda annoying..... You couldn't build a machine on the Lan without it getting a virus. Be it from lack of a password, or from putting an unpatched machine on the LAN just to download the service packs and patches. You couldn't build a computer on their Lan.

  54. Re:They STILL use some UNIX systems..to Compile Wi by Anonymous Coward · · Score: 0

    Don't konw if it's true but a guy at Sun told me that hotmail.com runs on Sun gear.

  55. Dell by mushupork · · Score: 1, Interesting

    Dell spent millions trying to migrate off Compaq Tandem and onto Windows Servers for their core manufacturing database. They were going to use 100% Dell hardware damnit! Millions of dollars later, Tandem was alive and well.

    Can anyone at Dell confirm Tandem is still the heart of the mighty beast?

    --
    Currently bidding on sig
  56. 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
  57. The question I want to see answered... by which+way+is+up · · Score: 1

    The question I want to see answered is "How do you deal with the same day to day annoyances that plague other companies running your OS, such as spyware/malware?

  58. 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.
  59. 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 JesseT · · Score: 1

      So what about all of those GNU/Linux savvy developers who refuse to try out what Microsoft offers? Too many times have I seen people saying that emacs or vi/vim are excellent source code editors, and then they say that the latest versions of MS Visual Studio suck. When asked if they have ever used it, the reply is "no, why would ever use micro$hlop products?" Naturally, I have hard time holding back my laughter. The fact of the matter is that this dogheaded policy of ignoring competitors products is practiced by both camps. And besides, do you think that the CTI and his department is responsible for deciding what direction that Microsoft products are going to take? Probably not as much as the development and technology/research departments.

    3. Re:Totally Incoherent Answers by Dracolytch · · Score: 1

      What is so incoherant about it? The first is a statement of their infrastructure: Meaning that they don't run their internal applications off of Oracle, they use their own products. When they're developing a new project, and are choosing a platform, his choice is Microsoft.

      The second statement ties into this: They have some open source stuff to get an idea of what the competition is doing, but the organization itself operates on Microsoft software.

      Thus: While they occasionally RUN other programs, the only software they USE is Microsoft products.

      ~D

      --
      This sig has been enciphered with a one-time pad. It could say almost anything.
    4. 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.

    5. Re:Totally Incoherent Answers by Anonymous Coward · · Score: 0

      So MS Visual Studio runs on *nix now does it? I always go back to using vim and I've tried many editors and IDE's, I'm not alone and that should be telling you something!

    6. Re:Totally Incoherent Answers by warriorpostman · · Score: 1

      I somewhat agree with that. Ignorance definitely travels both ways between the two camps. Still, most of the UNIX/Linux-heads that I've worked with are a little more understanding of MSWindows, in comparison to MS-developers being knowledgeable of Linux. There are a lot of 100% homogenous MS shops, but companies that are using Unix/Linux are typically more heterogenous in their tools and OS's, as a group. My only point is that, I can't believe anyone is in the slightest interested in what this guy (CIO?) has to say about anything, since his job title is really just a fancy term for cheerleader.

    7. Re:Totally Incoherent Answers by kupci · · Score: 1
      And thus, their software has all the features they need.

      That hardly means it has the features other organizations 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.

      Interesting logic, but wrong. MSFT has marketshare more because of how it shrewdly uses it's monopoloy postion coupled with good leadership and understanding of the market.

      IBM requires everybody to use Lotus Smartsuite, and IBM is far far bigger than MSFT and has far more "IT Needs", so Lotus should be awesome, right? Further, there are great open source products such as Apache, Struts, Linux, Firebird, MySql, Snort, that rival and/or surpass the best MSFT has to offer. These aren't built by a giant monolithic corp. eating it's dogfood at all.

      For some interesting reading, read this blog and the comments, about MSFT culture and software bugs. Also see ESR's paper.

    8. Re:Totally Incoherent Answers by Anonymous Coward · · Score: 0

      just because you eat your own dog food doesn't mean it tastes good. And when I worked for microsoft (a few months ago), I couldn't get a "home" account anywhere besides my own machine. All the shared network drives were publicly readable, which meant that if I wanted privacy and backup I needed to buy and setup my own backup system. Where I work now, my home directory is automatically backed up, saving me time, saving the company money for the backup system, and saving us both from lost data due to me not knowing how to correctly setup a backup system. And yes, I've looked at the windows RAID drivers and they are miserable. When I first arrived my windows box was useless without cygwin and gnu emacs, which is why microsoft officially supports both of them for their research division (but not the corporate division). The worst microsoft product is probably their version control stuff, which just made life miserable.

      While I agree that microsoft products are "at the very least among the best," the fact that they don't want you to use anything but microsoft products doesn't meant that it does everything you might want. It only means that their employees are forced to do things the microsoft way, for better or for worse.

    9. Re:Totally Incoherent Answers by digitalcowboy · · Score: 1

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

      I very well could be mistaken, but I rather doubt the accuracy of that statement. I've personally worked inside a couple of Fortune 500 companies that were certainly smaller than MS in market cap and I cannot imagine what MS would be doing that would rival either of them in terms of constant data processing.

      One is a large clothing retailer that is grabbing EVERY SINGLE cash register transaction from 10,000+ stores every single night and doing absurdly complex analysis on what items are purchased with what and which promotional displays are causing which other items to sell, etc. They are doing it daily, 360+ days a year.

      The other is a massive consumer packaged goods company that is processing millions of transactions from tens of thousands of route sales reps on a daily basis. Again, it is at a micro-granular level and done every single day. That is just the sales side. They are at least as obsessed with analyzing their manufacturing plants and supply chain and they also maintain maintenance and repair data on the largest fleet of corporately owned trucks in the United States, among other IT tasks.

      I can't even fathom what kind of data crunching Target and Wal-Mart must be doing. Then there's Fed-Ex, UPS, etc. with the real-time shipment tracking. I would imagine that a moderately sized regional chain of grocery stores is crunching more data on a daily basis than Microsoft.

      Maybe I'm naive, but I seriously doubt that in the kind of business Microsoft is engaged, their data processing needs are anywhere near the 30th percentile.

    10. Re:Totally Incoherent Answers by advocate_one · · Score: 1

      waves hand... "These are not the Linux boxes you are looking for..."

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  60. 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.
    1. Re:Who came up with this strategy? by Keeper · · Score: 1

      Using a product and finding what doesn't work or what it doesn't do is the easiest way to improve it. When was the last time you compared two pieces of software side by side? I'd be willing to bet that you used one piece of software, got frusted at something it didn't do that you wanted to do, THEN tried the other piece of software.

      Besides, this is the IT department for crying out loud; ie: not a product development group. If their IT department can't use the software they create, they can't very well go out and tell other companies that it'll solve their problems now can they?

    2. Re:Who came up with this strategy? by Odin_Tiger · · Score: 1

      "If their IT department can't use the software they create, they can't very well go out and tell other companies that it'll solve their problems now can they?" Not that that's gonna stop them from trying anyways... :P

      --
      Unpleasantries.
  61. Microsoft Sun by justins · · Score: 1

    At least in the "eating your own dogfood" department:
    http://news.netcraft.com/archives/2004/12/11/wwwge orgewbushcom_switches_to_selfhosted_freebsd_server _wwwsuncom_upgrades_to_solaris_9_not_10.html

    Of course if the Sun admins are going by what the www.sun.com webpage says, they're probably just as confused as I am about when the real version of Solaris 10 is coming, why they had a "release event" without releasing the actual product, why all those "Solaris 10" links go to Solaris Express beta downloads, and so on.

    --
    Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  62. uh, try 4 years ago. by MelloDawg · · Score: 1

    See http://www.microsoft.com/technet/interopmigration/ case/hotmail/default.mspx. Of course there were reports that some of the DNS servers were still running FreeBSD: http://www.windowsitpro.com/Windows/Article/Articl eID/22474/22474.html. But that was *3* years ago.

    --
    /. is irrelevant.
  63. Time spent combatting spyware? by erroneus · · Score: 1

    Likely little to none... oh wait, they probably use MSIE... strike that.

    While I service a lot of Windows machines, my own WinXP box remains free of such contamination due in part to my own browse habits (I don't click "yes" to everything and I don't visit a lot of weird sites all of the time.) as well as the browser that I use.

    My users are a different story... I keep fairly busy with it.

    1. Re:Time spent combatting spyware? by Random+Guru+42 · · Score: 1

      Actually, it seems that at least some of the developers at MSFT use browsers other than IE (some even use Firefox). Anyway, most developers are pretty concious of what's on their machines, so at least among the programmers, I doubt that there's much need to fight spyware.

      Of course, among the marketing department, it's probably a totally different story. :D

      --
      Christopher S. 'coldacid' Charabaruk -- coldacid.net
  64. Re:Microsoft Sun by justins · · Score: 1

    Ha. I had Microsoft > Sun in the subject but slashcode nerfed it. I'm sure there's a good reason why.

    --
    Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  65. That was a lame interview. by ARRRLovin · · Score: 1

    I like how the interviewer skirted all the Windows vs. Other questions and went right for the latest IT alarmist buzzword "OUTSOURCING". Who cares if MS outsources? I would rather see them turn IE into something useful than I would see them "bring the jobs back". To me, that's a more pressing issue.

    --
    -Randy
  66. Alot of people with iTunes at MS these days... by OldManCoyote · · Score: 0, Offtopic

    No dog good here. :)

  67. Hotmail servers by Tribbin · · Score: 0

    I'm not trying to start a fight here, but what was the thing about the hotmail servers again?

    I heard it ran on some not-windows OS and was mapped through a windows computer so it seems like it ran on windows, or something...

    Could be all bullshit; enlighten me.

    --
    If you mod this up, your slashdot background will turn into a beautiful sunset!
  68. 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
    1. Re:How can you compare without use? by Keeper · · Score: 1

      You don't have to compare your offering side by side with your competitors if you listen to what your customers want.

    2. Re:How can you compare without use? by Surt · · Score: 1

      Well, you do if you want to be competitive. You can't trust your customers to know or express everything that they want. Better to know what your competitors are up to than to be blindsided by a superior product your customers didn't know to demand.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    3. Re:How can you compare without use? by Keeper · · Score: 1

      Chicken and the egg scenario. If the competitor is better, and the only thing they did was copy your product, then how is it a superior product? They obviously did something else other than clone the competition.

    4. Re:How can you compare without use? by RailGunner · · Score: 1
      They probably keep up by asking potential customers who curently use Oracle what they like / dislike about it.

      I'm sure they also know that the TPC benchmark record was set by Oracle... running on Red Hat Enterprise Linux, and so they probably know how much faster they need to make SQL Server in order to compete.

      I'm also sure they read the same benchmarks that show ReiserFS kicking NTFS's ass in (hence the upcoming WinFS).

    5. Re:How can you compare without use? by sproketboy · · Score: 1

      >>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. Does that matter? Microsoft has the marketing money to sell anyone anything. What does technological excellence have to do with it?

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

    1. Re:The problem is that many savvy users aren't by Anonymous Coward · · Score: 0

      You sound like you work at Clemson!

      We just hired five Comp Eng graduates from Clemson, and not a one knows a damn thing about computers. The best one (and that statement is relative) just took five weeks to write a web page with a form that generates an e-mail message. I could have done it in 20 minutes. All five claimed to have extensive experience with Linux, writing HTML, and some experience with PHP, but they knew almost nothing about any of those things. Two even claimed to have worked on video drivers for Linux for a VR lab, but together they couldn't figure-out how to get out of single user mode in Linux (hint: fsck / then exit the shell to reboot, just like the instructions told you to do). Swapping an AT power supply stumped two of the others.

      Things have changed there since I graduated in Comp E in 1989 from Clemson. When I went there, the students actually knew something about computers. Over half of the students in that program were what I would consider smart. They were smarter on average than the guys I went to grad school at Michigan with. Now apparently they're just idiots.

    2. Re:The problem is that many savvy users aren't by dhart · · Score: 1

      The same can be said for most regular Software Engineers.

      While 80% of them would be okay admining their own boxes (generally just leaving things alone, as the smart ones recognize that they should spend their time working rather than tinkering), the remaining 20% who are overly stupid or stubborn would wreak havoc for the rest. Yes, I've seen it happen!

    3. Re:The problem is that many savvy users aren't by Saeger · · Score: 1

      Well, you don't have to reboot if the fsck is clean. Just 'init 3' or 5 to get up and running sooner.

      --
      Power to the Peaceful
    4. Re:The problem is that many savvy users aren't by Anonymous Coward · · Score: 0

      Cause he's Nick Burns, your company's computer guy!

    5. Re:The problem is that many savvy users aren't by dohcvtec · · Score: 1

      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

      The thing I've never understood is why Electrical Engineering and Computer Science are so often lumped together. In reality (take a few classes and you'll see) they have very little to do with each other, except the math. Usually it's the association of EE with CS, that Electrical Engineering people are highly knowledgeable with computing, but in practice EEs tend to be no more or less knowledgeable than Mechanical or other Engineering folks.

      --
      -- Never hit a man with glasses. Hit him with a baseball bat.
  70. Very honest of him by mav[LAG] · · Score: 0, Redundant

    From the article:

    As an IT organization, I have no skills and no ability

    OK, OK, it's from the middle of a sentence but my eye was still arrested by it :)

    --
    --- Hot Shot City is particularly good.
  71. Re:They STILL use some UNIX systems..to Compile Wi by Anonymous Coward · · Score: 0

    Can you give sources please on that quip about using Suns to compile Windows? To my knowledge, they use their own compilers (the command line Visual C compilers) to build windows. For example, Windows Server 2003 was built using VC's /GZ (I think) option.

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

    1. Re:they must be admins by spruce · · Score: 1

      Well that's becuase the writers of the non trivial application require admin access for their poorly coded applications. That's not MS's fault.

    2. Re:they must be admins by multi+io · · Score: 1

      So you can install MS Office, MSSQL, or Visual Studio as a normal user? Several versions of those in parallel? Several instances of the same version, each with a seperate configuration? Last time I checked, that didn't seem to be possible.

  73. MOD PARENT WESTWARDS, HO! by daniil · · Score: 1

    With colour schemes like these, it's no wonder Microsoft is winning!

    --
    Man is a slave because freedom is difficult, whereas slavery is easy.
  74. From TFA (Re:No wonder they're laggin behind...) by Lesson+No.+25 · · Score: 1
    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?

    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.

    Indeed. From TFA, 2nd paragraph under "Do you use any Linux?":

    We do, in areas on the client, have an open-source client running--just for competitive analysis.
  75. Apple IT by tehJR · · Score: 1

    Apple does something similar. Their employees all have issued PowerBooks and are theirs to use. Everyone has Admin rights and can install what they want. Not that they have as much to worry about in regards to spyware and viruses.

  76. OT: Coffee by Anonymous Coward · · Score: 0
    I like my women like I like my coffee... existing for the sole purpose of making me happy.

    s/making me happy/getting me up/

  77. WTF? CIO implies little talent here in USA? by 192939495969798999 · · Score: 1

    (interviewer) So if there were enough talent here, (offshoring) probably isn't something you would be looking at?
    (CIO) It's an alternative for me when I can't find the talent in the United States.

    WTF???
    If this guy can't find talented programmers/etc. in the US, he has no business being CIO of Microsoft. 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.

    --
    stuff |
  78. LIAR by Doc+Ruby · · Score: 1

    Maybe Microsoft properties like Hotmail.com don't run Linux on their public webservers ANYMORE. But check NetCraft for ".microsoft.com"; the first hundred or so hosts are *all* Linux, possibly lab machines judging from their hostname. And many more throughout those records are Linux, including those at partners plugged directly into Microsoft IT. Then there are all the hosts NetCraft reports as "unknown" - Windows doesn't report as "unknown". And we're just looking at the public hosts that NetCraft can see, not the many thousands of hosts actually run by Microsoft.

    Maybe Markezich doesn't know about NetCraft. Maybe he just doesn't care that geeks can easily find out he's telling the big lie. A CNet News article that gets the meaning of "alpha tester" wrong isn't pointed at geeks, but at PHBs who just envy Markezich's salary, and the insider releases his job includes. That there's any Linux around Microsoft at all shows just how important is Linux to any large organization's IT. Especially when they're taking the risk of lying about Linux not existing: it all makes Windows triply bad. Another Open Source advantage over proprietary software: no lying CIO to get caught, discrediting the rest of the organization - there's always "the other" distro, where the truth is at home.

    --

    --
    make install -not war

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

    2. 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.
    3. Re:LIAR by Anonymous Coward · · Score: 0

      Netcraft confirms: Netcraft is dying.

  79. Clerks by sykt · · Score: 1

    If Dante and Randle worked at QuickStop and Microsoft respectively.

    Randle: Hey let me borrow your DSL line.

    Dante: I don't want to talk to you.

    Randle: Fine, just let me borrow your DSL.

    Dante: Why should I loan you my DSL?

    Randle: I want to download Linux.

    Dante: You want to download Linux?

    Randle: I want to download Linux!

    Dante: Sighs...

    Randle: What's that for?

    Dante: You work at Microsoft!

    Randle: I work at a shitty Microsoft! I want to go to (insert name of favorite distro) for a good operating system!

    Dante: (Writes some e-mail)

    Randal: Eventhough I work at Microsoft I choose to download Linux, Agreed?

    Dante: You are a danger to the dead and the living.

    Randal: I like to think I'm the master of my own destiny.

    Dante: Get the hell out of here.

    Randal: You know I'm your hero!

  80. Whatever they want? by corngrower · · Score: 0, Redundant
    They can load whatever software they want on their machines,

    I wonder how many of them have loaded Linux on their machines.

  81. this just in by MasterOfUniverse · · Score: 1

    IBM employees only use thinkpad as thier laptops!

    --
    "There is no flag large enough to cover the shame of killing innocent people."--Howard Zinn
  82. Re:Nice Knee-Jerk (but accurate) by westlake · · Score: 1
    They brought us Clippy for crying out loud!

    If Links draws users into the Help systen and adds a welcome touch of color and animation on the desktop then she has done her job and done it well. The only ones still cracking jokes about Clippy are Geeks.

  83. Microsoft? laggin behind? by RadioActiveLamb · · Score: 1

    Seems to me Microsoft has a very successful business model. How can you say they are lagging behind?

    --
    Tag line, copyright 2004 RadioActiveLamb
  84. 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."
  85. It's Lake Wobegone by gelfling · · Score: 1

    Where all the men are strong, all the women are good looking and all the children are above average.

  86. 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
  87. Re:Nice Knee-Jerk (but accurate) by Anonymous Coward · · Score: 0

    Oh come on, you know even non-geeks complain about clippy. The problem is UI design. You don't want something to pop up over what you're doing EVERY TIME something happens. Take note of your web browser with the check box that says "show this message next time." Why can't we just have those instead? The only ones who know how to disable clippy are the very people who say are the only ones complaining ;)

  88. funniest part of the article by bongoras · · Score: 1

    "So since taking over as CIO last spring, Markezich has had a busy time of it. First, he moved Microsoft's entire network to Windows XP Service Pack 2. Nowadays, he's in the midst of testing out new versions of SQL Server and Visual Studio."

    Yeah.... SURE "he" is in the midst of that... I can see it now... Markezich, holding a cup of coffee, leaning over his employee's cubical... "Hey Peter, what's happening? We need to test the new versions of SQL Server and Visual Studio ASAP. So if you could just go ahead and work on that over the weekend that would be greeaaattt."

    1. Re:funniest part of the article by praxis · · Score: 1

      Microsoft employees get private offices.

  89. College Kids and Jimmy Hoffa by Corellon+Larethian · · Score: 1

    It's one of the things that come up when I talk to college students and they ask, "Is IT a good career?" It's a wonderful career for someone in the United States coming out of college.

    Absolutely.

    I myself am surprised at the things companies get away with, hiring college kids straight out of their diploma. The kind of stuff that the Teamsters would send The Boys down to...discuss the issue with management.

    What EA, Microsoft, and Walmart need are a couple good Jimmy Hoffa's in there.

  90. Re:Microsoft Sun by Profane+MuthaFucka · · Score: 1

    More like "eating your own dog's shit" department. At least that's how I view running Microsoft products.

    --
    Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
  91. They use(d) unix in their network operations dept. by Anonymous Coward · · Score: 1, Interesting

    That's funny.

    A year ago I applied for a Unix operations position in their network management department.

    (I have a family to support; fortunately I didn't have to take the job.)

    In the last year they axed all the Unix boxes?

    Doubt it.

  92. Re:They STILL use some UNIX systems..to Compile Wi by isometrick · · Score: 1

    Used to. They ported it to a Windows environment ... "not developed here", you know.

  93. Well, they're lying for a start. by jd · · Score: 1
    • Microsoft is well-known to have labs that run Linux. There was a story, albeit a while ago, of a Linux webserver running on someone's desktop at Microsoft. They are also believed to be the mysterious bulk-purchaser of a large number of Red Hat 9 CD-ROMs in that specific part of Redmond.
    • Microsoft owns Hotmail, and although some Hotmail machines are Windows, they also use FreeBSD.
    • There have been Unix and Linux versions of Windows products, in the past, though they never got much past beta. What did they write these on? Tin foil?
    • What about the Microsoft Office suite for Apple? MacOS ain't Windows, either.
    • Netcraft reports that a LARGE number of .MSN.COM machines run an "unknown OS", which certainly isn't Windows.


    In short, they aren't even willing to be honest about what they use, even though it's public knowledge and easily verifiable. Hey, this isn't just about Microsoft. I get pissed off when ANY distributor or software developer blatantly lies. Especially when the lie has zero value, because nobody would have cared anyway. It simply isn't important.


    There's a story that one generation of Apples was designed on a Cray... ...but at the same time, Cray was desgining his computers on an Apple. Does it make them bad for not using their own products? Of course not. Why would it?


    So why go to all these lengths to persuade us that Microsoft is a Microsoft-only shop, when they clearly aren't? Sure, they're 99.99% Microsoft, but why the vehement denial that the other 0.01% exists? Are they becoming so paranoid that even that tiny intrusion is simply too much for them to stomach?

    --
    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)
    1. Re:Well, they're lying for a start. by Keeper · · Score: 1

      Microsoft is well-known to have labs that run Linux. There was a story, albeit a while ago, of a Linux webserver running on someone's desktop at Microsoft. They are also believed to be the mysterious bulk-purchaser of a large number of Red Hat 9 CD-ROMs in that specific part of Redmond.

      How much do you want to bet those labs are not run/managed by their IT department?

      Microsoft owns Hotmail, and although some Hotmail machines are Windows, they also use FreeBSD.

      Hotmail isn't run by their IT department.

      There have been Unix and Linux versions of Windows products, in the past, though they never got much past beta. What did they write these on? Tin foil?

      Product development groups are not run by their IT department.

      What about the Microsoft Office suite for Apple? MacOS ain't Windows, either.

      The Mac BU isn't run by the IT department.

      Netcraft reports that a LARGE number of .MSN.COM machines run an "unknown OS", which certainly isn't Windows.

      MSN is not run by the IT department.

  94. Never got any spywhere by Anonymous Coward · · Score: 0

    I work at MS and am in the net every day for over 3 years now. Never got any spyware. Of course I only surf to slashdot, anything they reference, cnn, a bunch of blogs.

    My machine(s) at home now, which sees the ocasionally porn site, and the kids run all kinds of games (neopets mostly), and god only know what my wife surfs, now that gets spyware all the time. Have to clean everything once a week.

    I'd lose all my karma if I didn't check that lil' PA box :)

    Sigs are for wimps.

  95. Not much time at all... by Anonymous Coward · · Score: 0

    "I wonder how much time they spend combating spyware?"

    HAHAHAHAHA HA heh...

    not funny. If you weren't so busy getting ass raped by Slashfud admins, you would have read the article, and seen that they know what their users are doing, and undoubtedly their users are slightly smarter than the average user (say, you, for instance.

  96. I want to see this for RedHat by Anonymous Coward · · Score: 0

    I'd like to know how RedHat does it.
    How do they handle laptop users, single sign-on, updates, etc.

  97. Irrelevant by xant · · Score: 1

    It doesn't matter much if the user has root access. You may want to keep the user from tinkering with the computer in an unapproved way, but hell, it's a computer, if you have physical access you can ultimately do whatever you want. The point is that not every process on the computer needs admin access to run.

    If you give a user a normal login, and rights in sudoers to do whatever they want provided they type in their password first, you've prevented 90% or more of the damage that can be caused simply because (1) the user has to think before doing and (2) software the user runs can't make changes to access-controlled resources secretly. (Oops, Windows doesn't have sudo. Sucks to be Windows.)

    --
    It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
    1. Re:Irrelevant by hobo2k · · Score: 1

      No sudo... but runas comes pretty close to satisfying the same need.

  98. Weak by Anonymous Coward · · Score: 0

    The point is that MS doesn't rely on Unix/Linux for anything (although Hotmail might..but their status was always dubious).

    It is true. I know.

    However a large percentage of competent people (a good 60% I would say) have Linux boxes at home, and even at work, just to keep up with the what is happening out there. And that is another reason why MS is in no danger of losing its grip.

    Linux is cool. But Windows is too, for a lot of the same reasons.

    1. 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)
  99. And they do mean ANY software... by lullabud · · Score: 1

    "They can load whatever software they want on their machines"

    Point in case: Radium's release of SoundForge

  100. Re:WTF? CIO implies little talent here in USA? by Anonymous Coward · · Score: 0

    Quantity != Quality.

  101. Re:WTF? CIO implies little talent here in USA? by Anonymous Coward · · Score: 0

    Supposedly is right. All the ones that were any good are already employed, and have been for 2 years now. The rest of the "IT for Dummies" programmers who jumped on the bandwagon are the vocal minority...

  102. Some answers by Anonymous Coward · · Score: 0

    I spent a year there (before I got outsourced) so here are a few answers to some questions/rants others posed (no particular order):

    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

    Most don't actually run as an admin. I think you are confusing poorly written third party applications with MS apps. MS apps all run fine on XP as a user. Nice troll though.

    I wonder how much time is spent combatting spyware?

    Little, if any, IT effort is needed to combat spyware. Individuals are more than capable of preventing or removing spyware without IT help. Our grandmothers don't work at MS you know.

    I wonder if that means they can install any Microsoft software they want..

    Yep. Generally it's all published in your control panel under add/remove programs. For OSs you just visit a website to get a key.

    Because MS is such a geek culture, I'd be interested in finding out if what the social reprecussions are for someone finding malware on their system.

    It's painful. There are a number of behaviors that will get your network port swiftly shut down including: spyware, viruses, rogue dhcp servers, network/port probes, unpatched software or operating systems etc.. If you manage to get yourself "ratholed" off the network expect your peers to find out and absolutely clown you relentlessly for weeks after the incident.

    And our TCO sucks! By giving our users Admin access, we don't have to support them ALL THE TIME, they support themselves. Heck, would you want to? So our TCO numbers are not as bad as they might be at least.

    The TCO there is unbelievable low. All IT has to do is drop off a PC at your desk and they are done. You PXE boot off the NIC, choose your OS, reboot, all security updates and antivirus are done automatically and you pick your own apps off of Active Directory. Basically the whole company IS an IT department if you think about it. The IT dept. at MS just provides the tools and gets out of the way.

    Could that be why they don't run Linux or Unix? It would be interesting to know if they reprimand those who want to run linux, unix or solaris? Policy with regard to people choosing to run open source products, on their machine, would also be interesting.

    No, they don't reprimand anyone who runs *nix, but it doesn't happen. You may be surprised to know that when given a choice of any software they want, people will choose MS (*gasp*) over *nix. People will run *nix for testing in virtual machines and whatnot; it's fairly common.

    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?

    I think you may be confused. Every day users do not have admin access to any portion of AD beyond the ability to add workstations. As for local admin privileges, everyone creates a local user account for day to day use.

    :P

  103. MS can't use an unpatched machine internally by InnerParty · · Score: 1

    Actually I have heard from a reliable source inside MS that an unpatched machine will have a virus on it within minutes when connected to their own internal network. the network "Ops" do monitor the network and will shut off your port if you do just that. Also, since their users are admins of their own machines, I have heard of at least one guy who uses Linux because it better suited to a certain task, but overall what the CIO said is true unsurprisingly. I also have seen an inflatable Tux punch toy in one of their labs before. I desired to save Tux from the evil MS Server people, but alas, I had to exude professionalism and not let emotion overwhelm me....:P

    1. Re:MS can't use an unpatched machine internally by shadowsurfr1 · · Score: 1

      "unpatched machine will have a virus on it within minutes when connected to their own internal network"

      What a surprise. They're using M$ products, most likely without spyware scanners at all. Not to mention IE.

      I like the guy who uses linux in that M$ lab.

      Then tux is in there? What's next?!

  104. Decreasing cost? by Anonymous Coward · · Score: 0

    "When I look at my IT spend as a percent of revenue, it's decreased every year over the last five years for the IT organization--even though head count has grown every year for the company"

    That's nice - how much would anyone care to bet that MS IT is not charged for any of the software they run?

    If they had to shell out for every server & client license - it would be a different story - they would probably be screaming in pain like the rest of us.

  105. All animals are equal, by gwayne · · Score: 1

    but some animals are more equal than others...

  106. Grain of Salt by Anonymous Coward · · Score: 0

    MS is a big company. This guy knows only his (little) corner (sounds big, but it isn't really). Most people don't pay him any attention at all (I never heard of him).

    For example MCS (Microsoft Consulting Services) uses a Java based PSA product because their own offering in the arena (Project) is too weak (at the moment anyway).

    And the MBS people do whatever they want (but they had better start making a profit soon or they might be toast).

    Anyway this is all a tempest in a teapot. The big question is: When will the Office Group be allowed to support Linux?

    That is the 30 billion dollar question.

  107. It makes sense... by Anonymous Coward · · Score: 0

    Windows is still subscribing to the 'Personal' computer, one user one box idea. NT and XP covers the aberrant idea of more than one person using a computer, although simultaneous use is still a clusterfsck for the average family or small business.

  108. 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... ;-)

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

  110. Other companys do it. by BenTheDewpendent · · Score: 1

    I currently work for a good sized international company. Everyone here also has admin access to their machines. Most of us know what we are doing the ones who don't ask the people who do or IT

    They do audit for "forbidden" software and use a 3rd party patch system to push updates for windows and other software.

    If users are breaking their boxes frequently they need more todo.

  111. Eat your own dog food by Yankel · · Score: 1

    Twanfox does have a strong point. IBM and Novell are hailed for running their own distributions of Linux in-house as well.

    Yes, they'll need to know the enemy -- so run an extra box under your desk for testing purposes. But your day-to-day work better be hacked out using your own tools.

    Heck, I do the same at home. If I'm trying to sell the idea of open source software and Linux to friends and relatives I need to walk the talk.

    I sure as heck miss FrontPage 2000 -- Nvu isn't quite as polished for bulk dumps of text and tables into HTML pages. I just keep smiling.

    --
    --- Dan
  112. That's GNU/Microsoft Windows Services for UNIX by NZheretic · · Score: 1
    Many Microsoft users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is more often known as 'Microsoft Windows Services for UNIX 3.0' or SFU , and many users are not aware of the extent of its connection with the GNU Project.

    There really is a SFU; it is a subsystem, and these people are using it. But you can't use a subsystem by itself; a subsystem is useful only as part of a whole operating system. SFU now inludes Interix which is normally used in a combination with the GNU development toolchain and libraries : the system is basically GNU, with SFU functioning as the compatibility DDL Library layer.

    Many users are not fully aware of the distinction between the compiler toolset, which is SFU, and the whole system, which they also call `SFU''. The ambiguous use of the name doesn't promote understanding.

    Programmers generally know that is a Subsystem. But since they have generally heard the whole system called `Interix' as well, they often envisage a history which fits that name. For example, many believe that once Softway Systems finished writing the posix compatibility DDL Libraries, they looked around for other free software, and for no particular reason most everything necessary to port a Unix-like system was already available.

    What they found was no accident--it was the GNU system. The available free software added up to a complete system because the GNU Project had been working since 1984 to make one. The GNU Manifesto had set forth the goal of developing a free Unix-like system, called GNU. The Initial Announcement of the GNU Project also outlines some of the original plans for the GNU system. By the time Interix was written, the system was almost finished.

    Most software projects have the goal of developing a particular program for a particular job. For example, Softway Systems set out to build an environment to allow UNIX apps to be ported directly to NT. Donald Knuth set out to write a text formatter (TeX); Bob Scheifler set out to develop a window system (X Windows). It's natural to measure the contribution of this kind of project by specific programs that came from the project.

    If we tried to measure the GNU Project's contribution in this way, what would we conclude? If you had access to the full source code of SFU with Interix, you might find found that, GNU software was the largest single contingent, around 60% of the total source code, and this included some of the essential major components without which there could be no compatable subsystem. SFU by without Interix itself could be about 20%. So if you were going to pick a name for the system based on who wrote the programs in the system, the most appropriate single choice would be `GNU''.

    But we don't think that is the right way to consider the question. The GNU Project was not, is not, a project to develop specific software packages. It was not a project to develop a C compiler, although we did. It was not a project to develop a text editor, although we developed one. The GNU Project's aim was to develop a complete free Unix-like system: GNU.

    Many people have made major contributions to the free software in the system, and they all deserve credit. But the reason it is a system--and not just a collection of useful programs--is because the GNU Project set out to make it one. We made a list of the programs needed to make a complete free system, and we systematically found, wrote, or found people to write everything on the list. We wrote essential but unexciting major components, such as the assembler and linker, because you can't have a system without them. A complete system needs

  113. 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
  114. Better to anticipate though by SuperKendall · · Score: 1

    I would say it's always better to try and anticipate what they would want, to have really useful features ahead of time. Listening to your customers is also good but sometimes it can be even more invaluable to have the same kind of problems they will ahead of time and have prepared solutions.

    That they work without having any of the integration issues that every other company on the planet has leads to a certain degree of blindness on their part, and to some degree a certain amount of skeptisim that they know what they are talking about when the advertise product interoperability.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Better to anticipate though by Keeper · · Score: 1

      Given a choice between problems your customers currently have, and problems that you think your customers might have in the future, it is generally better to solve the former. And believe me, there is never a shortage of problems your customers want you to solve.

  115. he's lying, too by SuperBanana · · Score: 1
    We don't run Unix.

    Funny. Someone should tell him about all those unix machines with apple logos.

    (the advertising/marketing divisions have them, the Mac product group obviously has them, etc).

  116. Re:They STILL use some UNIX systems..to Compile Wi by quamaretto · · Score: 1
    command line Visual C
    QFE
    --
    *is run over by rotten tomatoes*
  117. 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

    1. Re:Heh, this is a funny quote by TiggsPanther · · Score: 1

      I just think that idea is asking for trouble.

      "Hey Kyle, last Tuesday I reported an issue with Exchange inboxes in the current beta randomly dropping new messages. I distinctly remember emailing about it."
      "Aah. Jim migrated the bugtest account to the new beta last Monday. I thought the number of bug reports was down recently."

      OK, so maybe that exact scenario won't happen but surely you keep your active devs on the most stable system you have going? Granted this way they're more likely to get first-hand experience of any major bugs but surely it would eat into actual bugfix time if their system got hosed by a particularly severe glitch.

      --
      Tiggs
      "120 chars should be enough for everyone..."
  118. Eat your own dog food... by Anonymous Coward · · Score: 0

    ...analogies come to mind. We do this sort of thing all the time in terms of the IT group being the first ones who get to live and die by "dot zero" releases of NOS's, desktop OS's and applications. MS are doing the correct thing here, although the interviewee is beating his chest a bit about it (for the wrong reasons).

  119. Makes Sense by Momoru · · Score: 1

    I agree with alot of the above comments, if this guy said something like "We use oracle and apache for our web servers, because its more secure and has better performance", you guys would be going nuts...."LOOK EVEN MS DOESNT USE THEIR STUFF!!!!". Its the same reason the parking lot at GM looks like a Chevy/Cadillac dealership.

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

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

  122. Local Admin, so what? by rayd75 · · Score: 1

    It's not like Microsoft is the only shop where a bunch of programmers and engineers are local admins. Hell, if it were I suspect that I'd spend a lot less time troubleshooting apps that want to write user preferences to HKEY_LOCAL_MACHINE or insist on storing temporary data in %windir%. My job would be much simpler if the typical programmer had to use a non-admin account for his or her regular work.

  123. Funny facts by Anonymous Coward · · Score: 0

    They are reducing the field of the "operating system" term, to Microsoft windows, as in the next quotation:

    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.

  124. However by SuperKendall · · Score: 1

    It's all too easy to get bogged down in one-offs that customers have issues with, rather than trying to adress the big picture and winning out in the long term.

    It's the difference between playing catch-up all the time and being an innovator in a space, which will net you customers because they know you'll solve some problems ahead of time instead of THEM having to tell YOU what to build all the time.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. 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.

  125. www.microsoft.com by Omniscientist · · Score: 1
    'It's an easy choice for me--to run Microsoft technology. We don't run Unix. We don't run Linux.'

    From what I remember from nmapping www.microsoft.com years ago was that they were running that on OpenBSD. As it has been said before in previous comments, that quote is a wee bit inaccurate.

    1. Re:www.microsoft.com by marcushnk · · Score: 1

      not its not inaccurate.. Microsoft don't run their own major web servers.. its outsourced to another company.. therefore MS don't run linux..

      But I do remember reading about 4 years ago that they did use Unix in the Dev area of Windows..

      --
      "Consider how lucky you are that life has been good to you so far. Alternatively, if life hasn't been good to you so far
  126. MOD PARENT UP!!! +5 Funny by Anonymous Coward · · Score: 0
  127. 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?"
    1. Re:10% Security by rrhal · · Score: 1

      They have a corporate security group. The IT folks spend about 10% of their time responding to mandates from this group.

      --
      All generalizations are false, including this one. Mark Twain
  128. Sure, I bet he sleeps well ... by Anonymous Coward · · Score: 0

    after all, there's just nuthin like denial, is there!

    The richer get richer ...

  129. Go with that thought. by khasim · · Score: 1
    Your assumption, 'that sysadmins know what they are doing and programmers do not' is a fallacy.
    Okay, I can see that.
    Just as there are inept users, there are inept sysadmins - and even good sysadmins can have their moments.
    I'm still with you.
    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.
    Nope. You lost me.

    While that is a good theory, it fails in practice.

    That's because it requires every developer to also learn the skills of a good sysadmin.
    This is particularly important for mission critical servers where one slip of the mouse can put clients offline for hours.
    I look at it the opposite way.

    I cannot trust those people to have the sysadmin skills so I cannot trust them with the rights to damage that server.
    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?
    While I look at it as maybe you have the wrong access policy.

    They might be a really good developer, and a crappy sysadmin. Which means they would do very well in a place with a different access policy.

    Why do I want to base the access rights on an individual rather than a group?
    1. Re:Go with that thought. by Spoing · · Score: 1

      Great reply. Agreed with all parts of it.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    2. Re:Go with that thought. by Lodragandraoidh · · Score: 1

      The problem with your rebuttal is that while it agrees that there is the possibility of bad sysadmins, it then blithely ignores the same.

      The assumption that locking out your end-users will solve all your problems is ignoring the biggest problem - the system administrator. Assuming the system administrator has more knowledge about how a system functions is a fallacy.

      The fact of the matter is both developers and system administrators fall woefully short on understanding how their actions can effect operational systems.

      The system admin who patches a system without validating what files will be touched - thus crashing a mission critical application (seen it happen) and driving calls into the technical support center - I would argue are more damaging than what most developers do to systems they have admin rights on.

      In both cases, a more holistic knowledge - say that of a computer scientist/system integrator - would avoid such calamities. This goes back to how we train our IT professionals, which imho is lacking. There is a strict demarcation between hardware people (site managers/system admins) and software people (developers/dbas) - that is artificial and unnecessary.

      Developing better communications and training is the key to fixing this. Slapping a bandaid on a problem and calling it fixed is not the solution.

      --

      Lodragan Draoidh
      The more you explain it, the more I don't understand it. - Mark Twain
  130. Re:They STILL use some UNIX systems..to Compile Wi by alc6379 · · Score: 1

    I think Markezich's statement was pretty clear:

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

    I mean, it doesn't get much clearer than that. I don't think the guy's talking about the development side of things (of course developers would have Unix boxes set up to test Interix or Windows Services for UNIX), or that certain development folks would be running competing products in a testbed environment. He's saying, all of our desktops and production servers are Windows, and by right, that would include the machines that actually do the compilation of Windows itself.

    Besides, with the way Server 2003 Datacenter scales, it probably would be safe to assume these days that through some combination of clustering and SMP systems, Microsoft should be able to pull off compiling Windows on its own platform some way or another.

    --
    I don't moderate anymore. Karma penalty for 90% fair mods? Can I mod that unfair?
  131. Windows and Firefox plugins by Spy+der+Mann · · Score: 1

    "Firefox requires a plugin to view this webpage. Click to install".

    Click...
    installing Sun Java runtime environment...

    what? Not enough privileges? =-/

    OK I try again. This time, I use RUNAS /user:admin.

    Same error! >:(

    Seriously, who invented this Windows crap?

  132. I prefer SU or SUDO by Seng · · Score: 1

    That's a helluva lot quicker than logging completely out of the system to install something.

    1. Re:I prefer SU or SUDO by LurkerXXX · · Score: 1

      I use that on my BSD box as well. But for the windows environment, you can always just do 'runas'.

    2. Re:I prefer SU or SUDO by Anonymous Coward · · Score: 0

      Runas doesn't always work. It'll work for MSI packages most of the time, but "runas explorer.exe" (which is what you have to do to get the functionality you need to do something substantial) will at best give you a half-functioning Explorer window (on XP). Ditto "runas control.exe". "runas cmd.exe" works, sure, but Windows cannot be effectively administered from the command line because Microsoft wants us to click-and-drool.

    3. Re:I prefer SU or SUDO by hobo2k · · Score: 1
      Yes I know I'm responding to an AC, but wtf.

      "runas explorer.exe no work" - try runas iexplore.exe instead (with explorer you must disable the single process mode)
      "runas control.exe no work" - Either use the IE trick above, or even better, hold down the shift key while right-clicking the control panel item. Click runas. (possibly not available on all XP versions)
      Also note that regedit does the single process thing too. So if you runas regedit, make sure it isn't already running.

      Any more questions?

  133. Why not lock them down? by khasim · · Score: 1
    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.
    I think you put too much faith in the mere words of a CIO.
    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).
    Why?

    Programming knowledge is not the same as networking knowledge or sysadmin knowledge.
    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)?
    Nope. The idea is to have the people who are specially trained work with the tools they're specially trained on.

    Ideally, all programmers would FIRST be required to work as sysadmins for 2 years and then netadmins for 2 years before being allowed to write their first line of code.

    They aren't.

    So why do you believe that learning programming automatically gives you the knowledge of a sysadmin and netadmin?
    1. Re:Why not lock them down? by gnuLNX · · Score: 1

      Speaking for myself here.

      I would say the being a programmer qualifies me (in a very small way) bacuase I had to install linux, learn it all own my own....and then once I was able to install and keep the box running I was able to develop software...I guess that doesn't really hold up in a windows world.

      I am certainly no uber admin, but I do run my own web server, mail server, and a few other things...why? Well because I can, and I am interested enough to learn how.

      --
      what?
  134. Ummm, no. by khasim · · Score: 1
    You can log in as many times as you want, remote or local. This has been true since the very first version of NT; NT has always been multi-user. See AT, telnet, any one of the many SSH servers, etc. Oh, you meant GUI sessions? Does UNIX require X to be multi-user?
    Telnet, SSH, etc are all connections.

    Even old MS-DOS could run a telnet server and handle multiple connections.

    That didn't make DOS "multi-user".

    Unix does not require X to be multi-user. Being multi-user requires the ability to run X if the user so desires (and it is installed).
    1. Re:Ummm, no. by Foolhardy · · Score: 1

      Multi-user. As in multiple users logged on at the same time with different identities and privileges where normal users can't interfere with others or the system. Telnet, SSH, SMB, at and the like are services that take advantage of multi-user capabilities; I meant them as examples of things you could use to exploit NT's multiuser capabilities.

      There are fully functional X servers and clients for Windows.

      What does Windows NT lack in the first version (3.1), or any subsequent version that prevents it from being multi-user?

  135. Interseting Quotes... by Anonymous Coward · · Score: 0

    It doesn't matter!

    I tried cutting and pasting from Mozilla to IE. It didn't work!

    Nothing else needs to be said! If cutting and pasting from another vanilla app to IE doesn't work, then what else do we need to say about Microsoft!

    Fuck 'em! Just fuck 'em!

    1. Re:Interseting Quotes... by Anonymous Coward · · Score: 0

      Mod this down if you must, but, damnit, this is the basic problem with Micro$oft... if they cannot succeed any other way (and they can't, NOT on technical excellence, anyway) then they will succeed on shear bullshit, by making the competition look bad, when it is really M$ that is bad on technical reasons.

      Fuck 'em, just fuck 'em!

    2. Re:Interseting Quotes... by shadowsurfr1 · · Score: 1

      I'd go with just fuck 'em. I've always liked linux more.

  136. Re:From TFA (Re:No wonder they're laggin behind... by cyberformer · · Score: 1

    Indeed. We already knew that Microsoft ran a few Linux PCs, as they made a lot of noise about purchaseing licenses from SCO.

    In the past, MS has also sold (or given away, free-as-in-beer) some software for Linux. There used to be an SDK that let sites running Apache on Linux use MS Passport for authentication, but I think that went away with the demise of the whole Passport plan.

  137. are you kidding? by tacokill · · Score: 1

    "But wait, no one wants their stock any more ..."

    Pardon me, sir, but I am very happy with my 14% gain this year in MSFT. I'll take 14% year over year forever if I could.

    Reality and your emotions are NOT the same thing. MSFT regularly trades around 100mil shares a day. SOMEBODY wants it and for those who have had it, it's been a VERY profitable invesment

    1. Re:are you kidding? by RealProgrammer · · Score: 1

      >14% gain Wow, nice.

      --
      sigs, as if you care.
  138. People aren't as simple as we'd like to think. by Crag · · Score: 1

    "Maybe if they actually *tried* linux they could see..."

    I doubt it.

    With a few exceptions, the people who genuinely like Windows, Linux, or MacOS like them based on some fundamental principle. Linux users like that nothing is held back from them. Windows users like that they aren't subjected to any of the gritty details. Mac users like the pretty colors and "it just works". (Appologees for the gross over-generalizations.)

    Your assertion is a little like saying, "if Republicans would just spend some time at a homeless shelter dishing out soup they'd understand welfare.", or "if Democrats spent some time with crack babies they'd understand drug prohibition."

    Sure, there are people who are ignorant, but that's not the real problem. The real problem is that People Are Different. Even if the people on the various sides of the various fences COULD agree on The Facts and The Rules Of The Universe, they STILL wouldn't agree on What We Should Do.

    Because People Are Different.

  139. "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.
  140. 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.

  141. Unix in MS Environment by ebooher · · Score: 1

    I once worked for a company that had this desktop mentality. If it was a desktop PC it ran NT, authenticated and connected to an NT server and stored files on an NT controlled file server. Now, as I was hired into the company as a Junior UNIX Admin for all the *outside* boxes (which not a one happened to be MS) I was a little interested in the fact that the other Junior as well as the Senior admins (who focused primarily on the large Cisco gear) never once even raised a stink about it. Just went on with it, not wanting to step on toes, since the *internal* administrator was MS centric.

    So, I decided to take myself out of the loop. Formatted my machine, installed Red Hat (still say I should have used SuSE - but we had a couple Red Hat boxes and could get support so *shrugs*) tweaked it up a little to look a little more like NT (not perfect mind you, but it was hard to tell that it wasn't NT with a theme on top to the untrained eye) Plus I was in an office so my machine faced away from the door, so it was hard to see what I was doing anyway.

    So when the LAN Admin finally finds out (who was actually a pretty cool guy, but had several hundred desktops he had to deal with on the network) he comes to me and says "So .... you obviously know what you're doing with UNIX, you can authenticate against NT? You have access to files? You can print? ..... I don't have to support you?"

    He walked out of my office and I never heard word one about it again. Makes me wonder if there are any *NIX friendly people that got sucked into MS that are still running a *NIX but not telling anyone about it.

    Any way, that was my rant, I now return you to your regularly scheduled /.

    --
    "Genius may shine aloof and alone, like a star, but goodness is social, and it takes two men and God to make a Brother."
  142. Re:There's definite pockets of non-Microsoft use.. by argent · · Score: 1

    None of which changes the fact that they ship it, and use it internally at Hotmail.

  143. scoop from the inside by rich42 · · Score: 1
    when I last worked there (about 2 years ago) - things were a bit of a mess.

    some of their internal systems were well maintained / patched - but a lot of others weren't (like all the desktops).

    When the SQL Slammer worm hit -everything- went down. the internal network itself was so saturated with traffic - nothing worked whether it was running SQL or not.

    never heard how it got inside - but on a network that size with all the different VPN's / etc - it's not hard to imagine.

    People were running around with floppy disks trying to patch everything - truly comic.

  144. Piracy by Anonymous Coward · · Score: 0

    It would be interesting to see how much pirated software is loaded on the desktops of developers at Microsoft. I bet they're a bunch of hypocrites.

  145. Non-Windows servers at MS by Anonymous Coward · · Score: 0

    Elsewhere on this thread somebody quoted a great article pointing out BSD use for Hotmail. I can't find an "official" quote just now but I remember reading in multiple places that for years Microsoft has used IBM AS/400 (now iSeries) servers to run many of their business processes.

    So much for Windows-only technology...

  146. If you were a horse breeder... by Goonie · · Score: 1
    and you asked farmers in the 17th century what they wanted out of their horses, all of them would want a horse that could pull a bit bigger plough, had a bit better endurance, and ate a little less. None of them would have said "Hey, what if we could replace the horse with a tractor".

    I think the key point is that merely listening to your customers is not enough. You have to show some creativity in figuring out how to meet their requirements if you really want to innovate.

    --

    Any sufficiently advanced technology is indistinguishable from a rigged demo
    --Andy Finkel (J. Klass?)
    1. Re:If you were a horse breeder... by Keeper · · Score: 1

      and you asked farmers in the 17th century what they wanted out of their horses, all of them would want a horse that could pull a bit bigger plough, had a bit better endurance, and ate a little less. None of them would have said "Hey, what if we could replace the horse with a tractor".

      And if you were doing your job right, you would analyze the farmer's problem. In this particular case, the farmer may be asking for specific attributes in a horse, but what they really want to do is plow more land faster at a lower cost.

      If the only way you can solve that problem is breeding a better horse, so be it. But that analasis does not prevent you from coming up with a solution that does not involve a horse.

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

  148. Programing by CoolSilver · · Score: 1

    All there equiptment is Microsoft based, except all the macs they program on.

  149. Don't run Unix or Linux, but they do use Macs... by Shag · · Score: 1

    And I'm not just referring to people in the Mac Business Unit, either. Remember that load of G5's that showed up for the XBox 2 developers? :)

    (Of course, depending who you ask, those Macs may actually have wound up running some PPC64 port of Windows XP. *shudders*)

    --
    Village idiot in some extremely smart villages.
  150. His picture... by runamok1 · · Score: 1

    scares the living HELL out of me!

    picture o' doom

    He looks all tweaked out OR has a computer chip installed in his brain!

  151. Microsoft a new brand of diapers? by Anonymous Coward · · Score: 0

    I thought Microsoft was some brand of diapers but I guess they did some other kinds of shady business including raketeering and anti-trust violations in the past. Perhaps they would be better off making diapers...

  152. I dont know about all by loconet · · Score: 1

    Maybe most of their staff uses Microsoft only products but I know I've gotten a few hits from the .microsoft domain on my website from people using Firefox/Mozilla on XP. They are most likely those in charge of researching the competition products or just simply employees with a clue.

    --
    [alk]
  153. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  154. Spending by mattyrobinson69 · · Score: 1
    When I look at my IT spend as a percent of revenue, it's decreased every year over the last five years for the IT organization--even though head count has grown every year for the company

    So theyre hiring more mexicans than ever before.
  155. (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.

  156. What Spyware? by Anonymous Coward · · Score: 0
    I wonder how much time is spent combatting spyware?

    Probably very little. I would imagine they, unlike the majority of people here, have very competant people doing their firewalls (which, since it is a 'chokepoint', can be used to totally control what goes in and out of the company, and thus, the computers themselves).

    Show me a company having trouble with spyware, and I'll show you a company with incompetant fools running a firewall.

  157. What's the big deal by trolman · · Score: 1

    I thought all windoze boxen users were admin by default???

  158. Ummm, no, again. by khasim · · Score: 1
    Multi-user. As in multiple users logged on at the same time with different identities and privileges where normal users can't interfere with others or the system. Telnet, SSH, SMB, at and the like are services that take advantage of multi-user capabilities; I meant them as examples of things you could use to exploit NT's multiuser capabilities.
    By that definition, MS-DOS was "multi-user".
    What does Windows NT lack in the first version (3.1), or any subsequent version that prevents it from being multi-user?
    Actual multi-user functionality. That was added later by Citrix and eventually by Microsoft as "terminal services".
    1. Re:Ummm, no, again. by Foolhardy · · Score: 1
      By that definition, MS-DOS was "multi-user".
      Really? MS-DOS provided preemptive multitasking? No.
      MS-DOS provided and enforced object security? No.
      MS-DOS prevented processes from interfering with each other? It doesn't even HAVE processes.
      MS-DOS had privilages? No.
      MS-DOS had a user database and a protected component that authenticated users? No.

      What's your definition of multi-user?
      Actual multi-user functionality. That was added later by Citrix and eventually by Microsoft as "terminal services".
      Specifics. I want names of services that UNIX provides that NT doesn't required for multi-user capibility.
      Name one multi-user thing that NT3.1 can't do that a UNIX server can.

      The ONLY thing that Terminal Services provides is multiple graphical sessions through Win32. Multiple users logged on by the network with text sessions has always been suported.
  159. Licence Fees by Anonymous Coward · · Score: 0

    It may also worth considering that Microsoft probably gives itself a bit of a price break on its licence fees.

  160. IT Practices at Microsoft by Anonymous Coward · · Score: 0

    I think their CIO needs to qualify his comments to say "We don't Blah Blah Blah, ANYMORE".
    I heard rumors from very reliable sources that in the NT4 days, M$ engineers did at least some of their development work on Solaris workstations. I also heard that Hotmail was run on Unix mailservers up until just 3 or 4 years ago (because Exchange sucked so bad!). I also heard that MS used UNIX exclusively in the embrionic days, and that Bad Billie originally wanted to make NT based on a nearly pure Unix kernel. Can anyone confirm any of this?

  161. They don't run Linux? by RollingThunder · · Score: 1

    Not according to a guy I know who worked there during the permatemping era.

    He described it as a bunch of feifdoms. Have the right liege lord, and you ran whatever you wanted.

  162. What is the Retail Cost of All Windows Licenses?.. by was_ms_now_linux · · Score: 1

    ...in use within MS? Windows would be very compelling for universal usage if it didn't cost so much. The issue isn't whether it's solid (it's still the best desktop and the server is pretty full-featured), it's the relatively high cost. This is especially true when you have more than a small number of servers and/or desktops. I bet the retail value (or even the discounted corporate price valuation) of all the Windows licenses being used would be mind-boggling.

    --
    http://www.softwareobjectz.com
  163. Perl and Vi by Saint+Stephen · · Score: 1

    Windows build system is heavily built on Perl; a lot of the devs use vi and emacs; and SourceForge is a fork of a commercial CVS-like system.

    I could probably think of a few more.

  164. I worked there for a little bit by Stonent1 · · Score: 1

    They had a decent password policy, better than most. Getting admin rights was just as simple as calling the local IT guy to hook you up. Since I was at MS, they had pretty much the entire MS product catalog available from add/remove programs. (When selecting add, a list of apps would show up.) They also hosted a site for just software that you could find older stuff if needed. (Win3.1 was still available if needed). One site was just called http://linux and it had all the "talking points" needed to host a decent anti-linux conversation with a customer. There were a few iMacs and G5 Macs on the floor but I never saw anyone using them since we shared floorspace with the graveyard shift. Critical updates were sent down pretty much every week or every other week. You had X number of days to install them before your network jack was shut off remotely. Then you had to call the internal helpdesk (staffed by HP employees) to get them to unlock your port just long enough for you to get your update loaded. Basically they were probing the systems constantly to make sure you had all of the critical updates loaded. We used all the standard stuff like MS Office Pro, (we usually got the "Gold" versions forced on to the computers a few weeks before they went retail). I forget the helpdesk software we used... Compass something I think. If you ever make it inside the Irving, Texas office, stop by the Starbucks inside the cafeteria in the morning, say hi to Manuel (the free breakroom coffee is horridly undrinkable for some reason). And for lunch grab a burger from the grill, they are to die for. (Seriously)

  165. Whatever. by khasim · · Score: 1
    Really? MS-DOS provided preemptive multitasking? No.
    MS-DOS provided and enforced object security? No.
    MS-DOS prevented processes from interfering with each other? It doesn't even HAVE processes.
    MS-DOS had privilages? No.
    MS-DOS had a user database and a protected component that authenticated users? No.
    Okay, this might take a while. It seems you don't know anything about multi-user.

    #1. "MS-DOS provided preemptive multitasking? No."
    That's right. But that only means that DOS was not a pre-emptive, multi-tasking OS.

    You may note that this is the first time you've brought that up. Prior to this you've been going on about telnet and ssh.

    Windows95 was pre-emptive and multi-tasking with Win32 apps. Yet Win95 was not a multi-user OS.

    Yet I could get a telnet login to a Win95 box.

    #2. "MS-DOS prevented processes from interfering with each other? It doesn't even HAVE processes."

    See above re: Win95

    #3. "MS-DOS had privilages? No."

    same

    #4. "MS-DOS had a user database and a protected component that authenticated users? No."

    and so on.
    Specifics. I want names of services that UNIX provides that NT doesn't required for multi-user capibility.
    Name one multi-user thing that NT3.1 can't do that a UNIX server can.
    I'll let Microsoft answer that one. http://www.microsoft.com/ntserver/ProductInfo/term inal/WhyUpgrade.asp

    Look for the phrase "More than a million users run Windows® based applications today using Citrix WinFrame*, which is a multiuser version of Microsoft Windows NT Server 3.51 platform."
    The ONLY thing that Terminal Services provides is multiple graphical sessions through Win32. Multiple users logged on by the network with text sessions has always been suported.
    Again, getting a telnet prompt is not the same as being multi-user.

    Even Microsoft's web page admits it.
    1. Re:Whatever. by Foolhardy · · Score: 1
      In order for an OS to be multiuser, it must have those things. I still may not be multiuser, but before it can be, it must have those things; it's a prerequisite.
      You claimed that under my definition, DOS was multiuser too. I clairified my definition to include some prerequisites that DOS does not satisfy.

      Win95 does not have privilages or users or access-controlled objects or full memory protection, but NT does. Are these things not needed for a multi-user system?
      Sure you can telnet to a 95 box, but normal user A on the system can kill user B's programs without permission; i.e. interfere. This would not be possible on a multiuser system like UNIX or NT.
      Even Microsoft's web page admits it.
      Microsoft said that as a marketing gimmic to get people to buy the product. It is the only way to get multiple GUI sessions via Win32, but graphical sessions are not a requirement of being multiuser. Just because marketing says it doesn't make it true. The article lies by omitting the fact that remote Win32 sessions are the only feature added by TS.
      You can have multiuser sessions through telnet on NT without TS, just like you can have multiuser sessions through telnet on UNIX without X-Windows.
      Again, getting a telnet prompt is not the same as being multi-user.
      I've yet to hear YOUR definition of multi-user, broken into explicit requirements. Tell me in your own words what you consider a multi-user system and specifically how NT does not meet those requirements.
  166. what does Bill use? by has2k1 · · Score: 1

    Bill is a geek. If he is not using unix, BSD or linux what is using?

  167. Re:They STILL use some UNIX systems..to Compile Wi by beerman2k · · Score: 1
    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?
    That's a pattently false. Windows is built on Windows using VC++; as is nearly every piece of software made by Microsoft. There's no "huge multiprocessor power" needed to build the Windows OS either. More processors of course is alwasy better, but it's more like 2 and 4 processor machines not 120+. I don't know where you heard this rumor, but trust me, it's absurd.
  168. Re:They STILL use some UNIX systems..to Compile Wi by beerman2k · · Score: 1

    I think you mean the /GS compiler switch. This adds buffer overun protection as well as other secuirity enhancements. Windows XP and beyond have been and will be compiled with that switch. In fact starting with VS 8.0 it is no longer an "option", its the default.

  169. false by bmajik · · Score: 1

    Windows is not compiled on sun boxes. The windows build is completely self hosted, i.e. people working on longhorn are running longhorn and building private drops from their own longhorn machines. The official windows builds also happen on wintel hardware.

    Sun has not made any kind of hardware in the last 10 years that has been price/performance competitive with wintel, especially for compiling (which is dominated by specint, which SPARC chips are awful at).

    There are also few (if any) BSD boxes remaining at hotmail, and it has been that way for a number of years.

    Obviously the statement "there are no unix machines anywhere it microsoft" is false. I had an SGI and a linux box in my last office; the linux box i ran certain things on because it was just easier (tcpdump, samba), the SGI machine i brought to work because it broke and there are fantastic resources available to me at work.

    Furhtermore, word gets around amongst the UNIX people at MS and before you know it someone with a legitimate need for a unix machine is asking about yours. In my case, we wanted to test that visual studio could consume WSDL files hosted on unix webservers. Best way to do that ? Well, i already had apache 1.3 on redhat running in my office..

    On my workstations i also install SFU, as i find real commandline utilities to be extremely helpful for working with code and solving certain problems.

    The point of this article is that Microsoft _runs_ on its own software. We don't depend on oracle, we depend on SQL server. We don't depend on NDS, we depend on Active Directory. We don't depend on sendmail, we use exchange. (You would cry if you saw the amount of hardware we've thrown at exchange to handle our userbase of 60k power users with multi-hundred megabyte mailboxes :)

    The MS server products got to where they are today (as opposed to 10 years ago) because MS, the company, runs on them, even before they're released. Microsoft.com is one of the worlds largest web sites. The MS corporate network has one of the highest counts of attached managed PC's of any known organization. The geographical diversity of our AD rivals uh... pretty much everything.

    You can't get your products to ever be good enough if you don't bet your business on them. Don't read this article and read "microsoft never looks at unix, they have no idea that firefox exists". Read it and understand that "if there is something MS needs that a competing product seems to do better, MS works at fixing it's own offering until it can solve MS's needs."

    As an aside, my team develops in a version of visual studio not yet released, on a version of .net not yet released, using a messaging framework not yet released. Domain controllers in my building are running pre-released versions of upcoming Server 2003 products. Patches that get sent out to WU are deployed via all of the different patch deployment technologies we support internally first (well, usually :)

    The point of all of this is - if it's not good enough to meet the needs of MS, how can it be good enough to meet the needs of other customers?

    (this is why we got so much flak about hotmail historically, btw, and why there has always been pressure to convert hotmail to windows, even in the case of the USTOREs, where it made awful financial sense, but needed to happen eventually for a number of reasons)

    I'm glad to report that most of the negativity about hotmail not being on windows is just incorrect and recycled bits at this point.

    --
    My opinions are my own, and do not necessarily represent those of my employer.
  170. NT based systems force user admin status... by samdu · · Score: 1

    My first job in an IT department was at a local software development company with around 500 employees and on the order of 750 workstations. All the desktops were running NT4. Everyone had local administrator access to their machines. Every time I've set up a machine based on NT since then, for clients or family, etc..., I've given them admin access to their machine. I tried to impliment a more sane security model but it just doesn't fly with NT based systems. Too many applications require that the user has some measure of administrative access. I gave up even trying. The Linux model for user rights is far more sane and real-world usable. NT basically plays at being a multi-user system. But that's all it does, play.

  171. stupid easy, actually... by akamoe · · Score: 1

    True, with runas you can do *some* administration and installs, but a lot of your efforts will bite the dust. At least, that is my experience. One example for you... Login to W2K as user, and start cmd as Administrator through runas. Now try to run any program from that cmd. Tough luck - none of what you run from there will work as if you are an administrator! Is it retarded or what? Now have you ever tried running IE or Explorer with runas? They won't run. But IE is needed to run Windows Update...

    Just make a shortcut to IE, then right-click on it, and choose `Run as'. I'm doing it to update this workstation right now.

    -a-

    1. Re:stupid easy, actually... by Perl-Pusher · · Score: 1

      How many windows users are aware of this? On a mac when you execute it makes you use a password. With runas you have to know what to do and want to do it that way. If I give a user the administrative password to allow him to do simple tasks with runas, he will invariably use it to become an administrator and it's spyware city. On a Mac it's not that simple you cannot login normally as root, this can be changed but not easily.

  172. Which brings us full circle. by khasim · · Score: 1
    Multi-user means that every user has access to all features and functions as every other user at the same time.

    Therefore, if only the console user has a GUI, the OS is not multi-user.

    That is why Citrix and Terminal Services make NT multi-user. Each user has the same access to features and functionality as the console user.
    Microsoft said that as a marketing gimmic to get people to buy the product. It is the only way to get multiple GUI sessions via Win32, but graphical sessions are not a requirement of being multiuser.
    GUI sessions are not a requirement for multi-user, as long as none of the users have a GUI. Once that functionality is available to the console user, a multi-user OS would provide it to all users.
    In order for an OS to be multiuser, it must have those things. I still may not be multiuser, but before it can be, it must have those things; it's a prerequisite.
    Like I said, "Whatever".
    You claimed that under my definition, DOS was multiuser too. I clairified my definition to include some prerequisites that DOS does not satisfy.
    No. What you are doing is attempting to add requirements every time I show that your definition is flawed because you want NT to be multi-user even when Microsoft admits that it was not.
    You can have multiuser sessions through telnet on NT without TS, just like you can have multiuser sessions through telnet on UNIX without X-Windows.
    Which brings us back to MS-DOS being multi-user under your definition.

    Full circle.

    Buh bye now.
    1. Re:Which brings us full circle. by Foolhardy · · Score: 1
      Multi-user means that every user has access to all features and functions as every other user at the same time.
      Under that definition, a UNIX machine that is multiuser in every way except that the console has sound support and there is no remote sound support, becomes not-multiuser until I remove the sound card? It's a feature that not all clients have access to.

      If only the local user has access to the removable drives physically on the system, does that also prevent the system from being multiuser?
      Therefore, if only the console user has a GUI, the OS is not multi-user.
      What if I disable the local Win32 GUI so no one can have it? What if I take the video card right out; unplug the keyboard and mouse so there is no console, only the network? (like an AS/400) You can have remote GUI sessions on NT 3.1 by running X-Windows client apps; is it multiuser then? Even if it's the only option available to all clients? These are normal and supported scenarios for Windows.
  173. Re:There's definite pockets of non-Microsoft use.. by julesh · · Score: 1

    GCC is included in Interix because it's the only compiler that can make UNIX-style executables in PE/COFF format

    Bollocks. I used to be a regular use of a compiler called LCC which can target any platform supported by the NASM assembler, which does support PE as its output format.

  174. Re:There's definite pockets of non-Microsoft use.. by julesh · · Score: 1

    which includes the "viral" GCC.

    What, exactly, about GCC is "viral"?

  175. Yeah sure. by jotaeleemeese · · Score: 1

    System Administrators have to deal every day with people that thought they were "smart" that do not see the forest because they hav a damn bonsai in front of them.

    There are system administrators for a reason, one of them is that they have global view of the systems, security, audit issues, etc. while many other IT people, brillant as they may be, have a more limited view normally circumscribed to one machine or a reduced set of them.

    The cavalier attitude of MS in regards to security (and on assuming that MS tools are always the best for the job) is completely didiculous (if true, which I pretty mudh doub it) and should not be taken as an example of how to set up IT infrastructure correctly.

    I wish some histories of how they are getting infected by nasty virii should be out there to probe my point.

    --
    IANAL but write like a drunk one.
  176. sigh by bmajik · · Score: 1

    Microsoft does not run microsoft.com on their "own" linux machines.

    Microsoft has a content hosting agreement with akamai, and akamai DOES use linux to host lots of things. Netcraft doesn't make any distinction between something inside the microsoft owned ip space and the netcraft content mirrors. The result is that people with a conclusion ("microsoft needs linux in order to run its website") find data to support it ("netcraft says microsoft.com content comes from linux boxes!")

    In the URL you pasted, look at the "Netblock" column. Akamai, Energis, etc. HOSTING partners.

    Note also that once you get into the "interesting" machines, it's all W2k or W2k3. (and when the Netblock value changes to "Microsoft").

    --
    My opinions are my own, and do not necessarily represent those of my employer.
  177. Security not allows thought out by slapout · · Score: 1

    I always thought it was funny at my old job. I didn't have admin rights to my own machine. But I had full db access. So while I wasn't allowed to defrag my own hard drive, I could delete all the tables in the database and bring the company to it's knees.

    --
    Coder's Stone: The programming language quick ref for iPad
  178. Re:There's definite pockets of non-Microsoft use.. by argent · · Score: 1

    What, exactly, about GCC is "viral"?

    You doubt Microsoft's honest word that free software is a "virus"? Would they fib? How could you even IMPLY such a thing?

    [in other words, I put "viral" in quotes because I found it ironic that Microsoft would ship GPLed code after claiming that you shouldn't use it because it'd infect your intellectual properties with commie cooties or something...]

  179. Again, you're wrong. by khasim · · Score: 1
    Under that definition, a UNIX machine that is multiuser in every way except that the console has sound support and there is no remote sound support, becomes not-multiuser until I remove the sound card? It's a feature that not all clients have access to.
    Okay, I'm going to guess that you're pretty young.

    The reason I'm going to guess that is because you're thinking in terms of telnet and such.

    Telnet is a service that runs on a server. Telnet can run on a single-user system.

    With Linux, you can hook up multiple terminals via the serial ports. They have ALL of the functionality that the console has.

    They can ALL be use concurrently.

    A Linux box without ssh or telnet running or ANY OTHER SERVICE LIKE THAT is STILL a multi-user operating system.

    Even if they cannot hear the sound card, they can still access it.
    What if I disable the local Win32 GUI so no one can have it?
    Okay, what if? The console can still re-enable it and use it. That functionality is not available to others.
    What if I take the video card right out; unplug the keyboard and mouse so there is no console, only the network? (like an AS/400)
    The AS/400 is a multi-user operating system.
    You can have remote GUI sessions on NT 3.1 by running X-Windows client apps; is it multiuser then? Even if it's the only option available to all clients?
    Answer that yourself. The key was not a GUI, but whether every other user had access to all the features and functions that the console user has.

    You're flailing.
    These are normal and supported scenarios for Windows.
    Right. Sure they are.
    1. Re:Again, you're wrong. by Foolhardy · · Score: 1
      The reason I'm going to guess that is because you're thinking in terms of telnet and such.
      Services like a GUI? Both are a communications channel that applications use to commnicate with users.
      I'm bringing up services because you said that NT without TS wasn't multiuser becuase only the console got a GUI. That is the ONLY specific reason you have provided that NT isn't multiuser and it isn't valid because services do not make the system multiuser, as you said yourself.
      They have ALL of the functionality that the console has.
      A text terminal on a serial port does not provide the GUI that the console can have, which is the exact reason you said NT wasn't multiuser:
      Therefore, if only the console user has a GUI, the OS is not multi-user.
      A text console from the network provides the same functionaility as a text console from a serial port or a text console in a local window or local fullscreen text, and you can have as many as you want concurrently, owned and operated by different users, Windows or Linux. You don't need TS to have as many concurrent text consoles of equal and full functionaility as you want.
      A Linux box without ssh or telnet running or ANY OTHER SERVICE LIKE THAT is STILL a multi-user operating system.
      If no remote services are required for a multiuser system then a NT box without SSH or telnet or RDP or any other service is still a multi-user operating system.
      Even if they cannot hear the sound card, they can still access it.
      Ok then, even if remote users can't see the console GUI, they can still access it. Any process can get a handle to the local interactive desktop and create or manipluate windows there given the required permission, even if that process is owned by a user connected remotely.
      Okay, what if? The console can still re-enable it and use it. That functionality is not available to others.
      If the console is disabled, you can't use it to re-enable itself. When the OS starts, you get a black screen; all input from the keybard, mouse and USB HID devices are ignored. That's why it's called disabled. It must be re-enabled remotely by any user that has permission.
      The AS/400 is a multi-user operating system.
      And it has no console. All access must be done remotely, just like a NT box with the console disabled or a Linux box with the console disabled, or one of those with the console hardware removed.
      Answer that yourself. The key was not a GUI, but whether every other user had access to all the features and functions that the console user has.
      And if there IS no console, what then?
  180. Of COURSE They Run Windows... by Anonymous Coward · · Score: 0

    It's their internal enterprise net, for chrissakes. Why would you run Oracle on the corporate leg? Why would you NEED to run anything else on an internal LAN/VLAN? It's not a test/dev environment, it's not an integration environment, it's a work domain used to join all these different legs together. Of course the users will be running Windows machines.

    Their front end is Windows. Just like if Linus set up his own company with an internal LAN, you might expect all Linux OS for their users on the corporate net. Big deal. If Linus wants to run OS/2 on his backbone, who the fuck cares? Shut up with the 'appeal to emotion' rants about how teh_evil_M$ ONLY uses their own product on an internal LAN. Holy fuckin' christ, Batman, you would think that was the hypocrisy to end all contrarian arguments. And you people vote?

  181. My final post. by khasim · · Score: 1

    Services like a GUI? Both are a communications channel that applications use to commnicate with users.
    I'm bringing up services because you said that NT without TS wasn't multiuser becuase only the console got a GUI. That is the ONLY specific reason you have provided that NT isn't multiuser and it isn't valid because services do not make the system multiuser, as you said yourself.

    No. I said that NT without Citrix/Terminal Services was not multi-user because every user did not have the same access to features and functionality. The console GUI was an example of one feature that the other users did not have access to.

    Services do not make a OS multi-user.

    The inability to provide all the services to all the users, concurrently means that the OS is NOT multi-user.

    A text terminal on a serial port does not provide the GUI that the console can have, which is the exact reason you said NT wasn't multiuser:

    But if the console has a GUI, I can get that on a different connection. At the same time as the console has it.

    A text console from the network provides the same functionaility as a text console from a serial port or a text console in a local window or local fullscreen text, and you can have as many as you want concurrently, owned and operated by different users, Windows or Linux. You don't need TS to have as many concurrent text consoles of equal and full functionaility as you want.

    But not the GUI on the console. As I've stated in the past.

    If no remote services are required for a multiuser system then a NT box without SSH or telnet or RDP or any other service is still a multi-user operating system.

    No it is not because there is no way for a 2nd user to be logged in, concurrently with the console user and have all the features and functionality that the console user has.

    Ok then, even if remote users can't see the console GUI, they can still access it. Any process can get a handle to the local interactive desktop and create or manipluate windows there given the required permission, even if that process is owned by a user connected remotely.

    "even if remote users can't see the console GUI, they can still access it". Riiiigggggghhhhhhhttttttt.

    It will be very interesting to watch you play minesweeper that way. What? You say you can't? You can just launch the game, move the window and kill the process?

    Yes, I thought as much.

    If the console is disabled, you can't use it to re-enable itself. When the OS starts, you get a black screen; all input from the keybard, mouse and USB HID devices are ignored. That's why it's called disabled. It must be re-enabled remotely by any user that has permission.

    And if telnet and ssh and so forth are not enabled? Well, that means that the machine needs to be rebooted with a recovery disk.

    And it has no console. All access must be done remotely, just like a NT box with the console disabled or a Linux box with the console disabled, or one of those with the console hardware removed.

    Actually, it does have a local console. I believe it is accessed via a 5250 connection. Look up "LCS" if you don't believe me.

    And if there IS no console, what then?

    Then it isn't Windows.

    Windows ships with a console. It is a GUI console.

    With Citrix (a multi-user version of Windows) it is possible to still get a console even after all the damage you're trying to do to the box.

    A multi-user system is a step UP from a single-user system.

    You are trying to REMOVE functionality in order to meet the definition.

    It doesn't work like that.

    Windows ships with a console. In order for Windows to be multi-user, it must provide that console to all concurrent users.

    You keep tryin

    1. Re:My final post. by Foolhardy · · Score: 1
      "even if remote users can't see the console GUI, they can still access it". Riiiigggggghhhhhhhttttttt.
      Hey, you suggested that "Even if they cannot hear the sound card, they can still access it." How is this any different?
      You can just launch the game, move the window and kill the process?
      You can stick the window on a non-console desktop and poll the window contents. VNC does the same thing, but doesn't look for desktops that aren't on the console out of the box.
      And if telnet and ssh and so forth are not enabled? Well, that means that the machine needs to be rebooted with a recovery disk.
      Any OS can be rendered unusable by making it deaf to all inputs. So what?
      Actually, it does have a local console. I believe it is accessed via a 5250 connection.
      The 5250 is a remote terminal. You can physically place it next to the box, but it's the same kind of terminal that every user uses. There is no special console connection.
      Then it isn't Windows.
      Then what is it? Do I have to have every service enabled or else it isn't an operating system anymore?
      FC2 ships with a console. A GUI console. If I disable X-Windows, does it cease to be Linux? No!
      You keep trying to focus on ways to REMOVE the console GUI. Whatever.
      It doesn't NEED a console GUI or any kind of GUI to be multiuser. If a GUI isn't needed to be multiuser, what's the problem with removing it?
      With Citrix (a multi-user version of Windows) it is possible to still get a console even after all the damage you're trying to do to the box.
      To disable the local console, change the Windows= part of the value "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows" from On to Off. I wasn't aware that a configuration change constituted "damage". No, there is no way to get the local console back from the local console.

      What about sound support? If only the console user's applications get sound support and remote users don't, wouldn't that prevent the system from being multiuser? Last time I checked, FC2 provided local sound support but didn't provide remote sound support. Under your definition, it can't be multiuser because the console has a function that isn't provided remotely.
      FC2 ships with local sound support. In order for FC2 to be multi-user, it must provide that console sound support (which it ships with) to all concurrent users; it can't to remote users.
      How about video framebuffer access? This is only meaningful to the console user.
      How about plugging in USB devices? Can I do that from a remote machine? Can I plug a device in a remote machine and access it from the server as if it were connected locally?
      Functionaility provided only to console users.