www.geekybob.com

When Microsoft NetMeeting Saved the Day

09 February 2026 • by Bob • Microsoft, Technology

In the late 1990s, I was delivering training for a large group of external business leaders in downtown Dallas that was organized by Microsoft's marketing team, and my presentation was supposed to be broadcast to remote Microsoft learning centers across the country using Cisco's video teleconferencing hardware.

As the time for the training to begin drew near, it was clear that the Cisco hardware was failing completely, and techs were scrambling to fix the problem, lest the expensive training session be canceled.

While the Cisco techs worked feverishly, I placed a Polycom conference phone on the speaker podium and used it to call the other learning centers. I told the people running the show at each location that I was firing up Microsoft's NetMeeting, then I gave them all my IP address and asked them to connect to me. I shared my desktop through NetMeeting, then I suspended a microphone over the Polycom phone so that everyone in the Dallas location could hear anything that was said at the remote locations. After a quick sound and video check with all the remote locations, we were in business.

As soon as I had everything ready-to-go through my unorthodox workaround, I turned to the Dallas audience and said, "You've just witnessed the successful deployment of a Microsoft software solution for a third-party hardware failure in real time." The audience erupted with applause, and the marketing folks at the back of the room who had organized the event were beaming with pride.

The rest of my presentation went off without a hitch, although the Cisco techs never got their hardware to work.

Of course, Microsoft NetMeeting is long gone, but in it's day - it was a handy, little piece of software that did amazing things.

Troubleshooting Tales: Rebooting Microsoft Surface Takes Several Hours

30 January 2026 • by Bob • Windows, Troubleshooting, Microsoft

I ran into an interesting troubleshooting situation that I felt was worth sharing, because it serves as another example of why original assumptions when troubleshooting a misbehaving computer might not be accurate.

Here's the problem description: I had a Microsoft Surface laptop from my employer that worked fine for a while, but over time it began to take anywhere between 3 to 12 hours to cold boot or reboot, which made powering off the computer or installing Windows Updates an extremely painful experience. (Note that the boot times were approximate as I never tried to time a reboot or shutdown/restart.) Whenever the Surface started, the screen would be black, but if I touched the touchpad or pressed a key on the keyboard, the keyboard would light up to show that the computer was running, but nothing would happen for several hours. Then without warning the machine suddenly would wake up and everything would be fine.

Of course, trying to troubleshoot what might be wrong was an extremely unproductive experience, because anything I tried would always take several hours to check. I'll spare everyone the sordid details, but in my efforts to troubleshoot the issue, I tried all sorts of things like configuring several Windows services for delayed start and various performance-related settings, and all with no success. To workaround the slow startup behavior, I never rebooted this laptop for anything other than Windows Updates - I would always hibernate the computer instead of shutting it down. In the meantime, I had an HP desktop computer that worked great - it always rebooted with no problems.

I eventually decided that my Microsoft Surface was unreliable (and often unusable), so I requested a replacement from my employer, and I was sent another Microsoft Surface laptop. However, shortly after I received the new computer, the same behavior started happening. I spent a lot of time searching for users who had experienced similar behaviors with a Microsoft Surface, and I compared dozens of settings between my HP desktop and Microsoft Surface, and lots of other things that I won't bother boring you with. And all the while my HP desktop computer continued to reboot as expected.

Though I should mention that as a troubleshooting step, I reinstalled Windows from scratch on one of the Microsoft Surface laptops. My employer uses Microsoft Entra ID for federated user authentication and group policy, but I didn't initially rejoin this computer to Entra ID after reinstalling Windows, and the reboot problem went away - until I rejoined it to Entra ID. The problem returned after I rejoined the Microsoft Surface laptop to Entra ID, although I wasn't having any problems with my HP desktop computer that was also joined to Entra ID, so I theorized that the underlying issue might be something in Group Policy that was causing problems only with Microsoft Surface laptops, and this theory became yet another avenue for troubleshooting.

However, one day I had an epiphany: what if the issue that I was experiencing didn't have anything to do Microsoft Surface laptops? With that thought in mind, I abandoned the train of thought that I had been pursuing and - to make a long story short - I soon discovered the article Microsoft Entra joined computers experience a three hours delay during boot, which contained the fix that resolved the problem, and I'll explain the details:

What was going on was that even though all my computers were joined to the Entra ID domain, the network settings on my Microsoft Surface laptops were configured to use the NETBIOS name for the Entra ID domain as the "WORKGROUP" name instead of something else. When this happens, Windows will enter a wait state for 10,000 seconds, which is 2 hours and 47 minutes, and in my observation I witnessed Windows re-entering that wait state for two, three or four times, which would respectively be 5.5 hours, 8.3 hours, or 11.1 hours, which explained the "anywhere between 3 to 12 hours" symptom that I described earlier.

As soon as I updated the workgroup name to something else, my Microsoft Surface laptop rebooted in a matter of seconds like it was supposed to.

I'd like to say that I managed to resolve this issue over the short span of a few weeks, but... no. Since this only happened with my Microsoft Surface computers and not my HP desktop computer, I spent over a year thinking that this was some sort of problem that was specific to Microsoft Surface computers and attempting to troubleshoot the issue from that perspective, when that was never the case.

Darn.

30 Years at Microsoft

18 December 2025 • by Bob • Microsoft

Ok, sure - I freely admit this post is 100% self-aggrandizing, but today is my official 30-year anniversary with the company. It seems like only yesterday when I was hired as a tech support engineer for Microsoft Access 95.

These past 30 years have been a great ride, and I hope I have more years to come.

(There was a time when employees who were celebrating their 10, 20, and 30-year anniversaries could look forward to a celebratory dinner hosted by the company in Redmond, but those days have long-since passed. C'est la vie.)

POSTSCRIPT:

I will admit that this post, much like my 25 Years at Microsoft post, is somewhat brief. But if you're curious, I wrote a detailed summary of my earlier history with the company in my Some Thoughts About My 20th Anniversary At Microsoft post. (Wow. I wrote that ten years ago. Where has time gone?)

Office Moves on Microsoft's Main Campus

11 July 2025 • by Bob • Microsoft

Office moves at Microsoft's Redmond campus are as ubiquitous as overcast skies and traffic on the 405, and several years ago I took an overhead photo of the old main campus and highlighted all the buildings where I'd had a physical office at one time or other.

Bear in mind, however, that this photo only has buildings 1 through 44, and I worked in some of the 50-59 buildings, too.

Not All Marginalization is Misogyny

10 July 2022 • by Bob • Computers, Apple, Microsoft, Technology, Rants

Every few years, the following photograph of Margaret Hamilton makes the rounds in social media. This particular image's popularity is not surprising; it's a great shot of Hamilton, who was NASA's lead developer for Apollo program, standing next to the stack of computer printouts for the software that told the Apollo Guidance Computer what to do and when to do it, which eventually helped astronauts land on the moon.

A friend recently posted this image to social media, and upon seeing it, someone else responded, "That is incredible. Why haven't I ever heard of her before?"

My friend's reply was simple: "Because men."

I completely understood my friend's point. There are far too many times when women are overlooked in their respective fields. But I was annoyed and frustrated by my friend's two-word reply, because there are times when gender has nothing to do with whether someone's accomplishments are publicly recognized. In this specific instance, Hamilton's relative obscurity wasn't due to misogyny. Developers like Margaret Hamilton, Grace Hopper, Jean E. Sammet, and Frances Allen are pioneers in their respective contributions to computer science and software engineering, but the real reason why people haven't heard of them is because: they're computer scientists, and no one cares about computer scientists, except for other computer scientists.

In some fields, men are easy targets for a good round of bashing where "popularity" or "fame" are concerned, but when an entire career field isn't "popular," then EVERYONE who works in that field remains obscure. As history shows, Hamilton (and Hopper, and Sammet, and Allen) earned a host of accolades, but most people haven't heard of them because we use their work without giving a second thought where it came from. (Which, by the way, is true of all engineering fields, but I digress.) I challenge anyone to name a single engineer - man or woman - who helped to produce the iPhone, which is (for better or worse) one of the most civilization-altering inventions in history. Oh, sure - everyone can name Steve Jobs, because he owned the company. But Steve Jobs never "made" anything; millions of unnamed engineers - both men and women - are responsible for the iPhone, the iMac, Windows, Google, Microsoft Office, etc.

Here's another example: I just watched the new "Thor" movie, and Taika Waititi's name is everywhere during the credits because he co-wrote and directed the movie; but most people probably haven't heard of his co-writer, Jennifer Kaytin Robinson, because "men." (Hollywood has always been and continues to remain misogynistic, but once again I digress.) However, did anyone bother to pay attention when the credits listed hundreds of people who worked on SFX/CGI for the movie? Nope - we enjoyed their work, but the computer scientists and digital artists who contributed to every scene in that movie remain unknown to anyone outside of their field.

Looping this back to the original subject of NASA and whether they slighted Margaret Hamilton, can anyone name any of the other members of her software development team? If the entire reason some people haven't heard of her was "because men," then I would assume that people could name some of the men who were on her team because they would have received credit for her work. But no, people can't name any of them, either. And why is that? Because - engineers.

How about any of the men and women who designed the Apollo space capsule? Or the Lunar Rover? Or the space suits? Or the propulsion systems? Or the communication systems? Or anyone involved in Skylab? Or the Space Shuttle? Or the Mars probes? Once again, people can't name a single one of those people. And why is that? Because "engineers."

NASA isn't slighting anyone. On the contrary, NASA hires brilliant minds - both men and women - who remain unknown to the general public because they chose extremely technical career fields that lead to obscurity within the community, and societal anonymity doesn't care about gender when it comes to scientific ignorance...

The Day I was a Sports Legend

22 October 2021 • by Bob • Humor, Microsoft

Back in my early days as a Technical Support Engineer at Microsoft, my boss had a dartboard outside her office, and several of our fellow team members would play darts on their breaks. I suck at darts, so I never joined them.

One day I happened to be walking by, and one of the guys asked, "Why don't you ever play with us?" I replied, "You wanna see why?," then I grabbed one of the darts and threw it with barely a look in the direction of the dartboard.

I fully expected to miss the board by several feet, and thereby demonstrate to everyone my complete lack of skills. However, by some miracle the dart landed dead center in the bull's-eye. Rather than show everyone my expression of dumbfounded surprise, I quickly collected myself, then I turned to the people gathered around and asked with a feigned air of superiority, "Do you REALLY want a piece of me?"

Then I walked off, leaving my stunned coworkers in awe while I basked in the glow of a victory that I could never have achieved if I had tried, and like any great athlete - I left the sport at the top of my game.

25 Years at Microsoft

19 December 2020 • by Bob • Microsoft

Today marks my official 25-year anniversary with Microsoft. I've had a blast, and I've had the privilege to take part in some pretty amazing projects. I can honestly say that several of the products that I helped design are running on millions of systems around the globe, and I worked with some amazing people to bring those ideas to life.

These past years have been great, and I hope that I have many more to come.

POSTSCRIPT:

If you'd like to see some of my personal history with the company, here are several videos that I recorded for Microsoft over the years.

NOTE: These videos were originally on Microsoft's Channel 9 website, which has been retired. As such, these videos are coming from the Internet Archive, so they make take longer to load than expected.

Flight Simulator 2020: First Impressions

27 November 2020 • by Bob • Reviews, Gaming, Microsoft, Troubleshooting

I've been a fan of Microsoft Flight Simulator (MSFS) since it was first introduced. (Or even earlier if you count SubLogic Flight Simulator that preceded it.) I have owned every version of MSFS, and I usually rushed out to buy each version when it hit the stores.

I would have to say, though, that my favorite version had been Flight Simulator X (FSX), which was released in 2006 - the levels of detail and realism were amazing. Unfortunately, FSX was the final version of MSFS. Microsoft chose to unceremoniously kill off MSFS in 2009, and like every other MSFS fanboy, I was quite upset to see it fade into the sunset. There were a few failed attempts to breathe life into the franchise via Microsoft's Flight and Steam's rerelease of Flight Simulator for their gaming platform, but each offering fell far short of the goal.

Needless to say, I was thrilled when I heard the news that Microsoft was reviving the series with Flight Simulator 2020, which promised unbelievable video quality and unparalleled realism. As I had done with every previous version of MSFS, I bought FS2020 on the day of its release and installed it immediately. As soon as the installation was done, I launched the application to see - nothing. MSFS displayed a message to inform me that my GeForce 9800 GTX video card was not powerful enough to run FS2020.

This was disappointing, to say the least, but I wasn't too worried - because I had already purchased an NVIDIA GeForce GTX 1070 video adapter for my computer. However, I had too many tasks competing for my limited time, so I had to delay the installation of my new video card. That being said - today was the day! I powered down my system, swapped out the old video card for the new card, and rebooted. As soon as the operating system was up and running, I launched FS2020 and was excited to see - nothing. Well, not exactly nothing; what I saw were two error messages:

Unfortunately, those error messages sent me into an endless loop that always resulted in my seeing these same messages again and again; and since there was no other way to exit the application, I had to hard kill FS2020 using the Windows Task Manager. I followed the advice from the error messages and I checked the forums, where I found the following two threads that described my exact situation:

I tried everything that was suggested in both of those threads (as well as suggestions from several other forum threads and blog posts), but so far - no luck. I still have yet to see anything from MSFS2020, but I'll keep looking.

With that in mind, here are my first impressions of Microsoft Flight Simulator 2020:

• Game Experience = I have no idea. I have yet to see the actual game.
• Installation Experience = terrible. The minimum requirements are excessive, and when an end user can't get a game to run as soon as they're done installing it, that's a catastrophic failure for which the game designer is solely responsible.
• Troubleshooting Experience = terrible. End users are pretty much on their own when something fails. Microsoft's single troubleshooting recommendation is for users to check the forums, which is way below par for a major software product from a major software company.

On a related side note, I installed MSFS2020 using the Microsoft Store application for Windows 10. That app is relatively easy to use, but it could be a lot better in my opinion; I often find myself highly annoyed at how difficult it is to find apps that I know have been released and install them.

This Scammer Picked the Wrong Geek to Mess With

08 December 2016 • by Bob • Microsoft, Support, Windows

What a great way to start my day. I just received a call on my work phone from an anonymous number where a guy with a thick accent on the other end of the line began his pitch by claiming, "This is Windows Technical Support. I am calling you today because we have been receiving a bunch of messages from your computer which are telling us that..."

Hehe... seriously? This clueless dude had no idea he was dealing with a Microsoft employee. But then again, I had a busy day planned, so I had no time for squabbling.

I quickly cut him off and said, "Look, I can save us both a bunch of time. Do you know who I work for?"

The would-be con man was immediately taken aback and momentarily at a loss for words, but he managed to eke out a hesitant "No" as a reply.

I continued by saying, "I work for Microsoft."

The scammer attempted to regain his composure and started to reply with, "Oh, then you must know..."

I cut him off again and I asserted, "Yes, I do know. I have worked for Microsoft for over 20 years, and I know that Microsoft does not call customers like you are doing. You are a liar. And what you're doing is illegal."

Predator had turned to prey, and the hapless dolt on the opposite end of the phone began to mumble, "Honestly, sir, I... uh..."

And then I heard nothing but dial tone.

Yup, that was a great way to start my day.

Some Thoughts About My 20th Anniversary At Microsoft

18 December 2015 • by Bob • Microsoft, Random Thoughts, Windows, IIS

At the risk of gratuitous self-aggrandizement - today is my actual 20th anniversary. My 20th anniversary crystal arrived the other day, so I added to the collection on a bookcase in my office. (Although to be honest, they didn't hand out anniversary crystals when I reached my 5th and 10th anniversaries, so I had to buy those after the fact.)

Things I'm Most-Proud Of...

Disclaimer: Yeah, I realize that I'm definitely bragging here; hence why I labeled this section "Things I'm Most-Proud Of."

• IIS Express - I came up with the idea for IIS Express one afternoon after writing an SDK sample where I showed that it was possible to create a mini version of IIS that could be used for self-hosting applications and debugging. After I proved that it could work, I faced a huge uphill battle trying to sell the idea for a miniature version of IIS to my bosses, (e.g. ThomasD, VijayS, Mai-lanB, BillS, etc.) Once I had convinced all of them, then I had to convince the Visual Studio team to dump Cassini in favor of IIS Express. (That was no small task, believe me.) Shortly after I had everyone on board, Vijay took over the project while I changed teams for the next year, and Vijay grew my rather simple idea into a full-fledged application. (Kudos to Vijay - I had more modest plans originally.) A few years later I changed teams again and I took over IIS Express, where I added some more cool features to it. Now IIS Express ships everywhere, so it's pretty cool to see how far you can take an SDK sample.
• Being a PM on the IIS team - This was a dream come true for me. Oh sure, that dream was more of a nightmare in the days before shipping a product, but being a PM for IIS was pretty much everything I thought it would be. By way of nostalgia, here's what the IIS Product team looked like in 2009. (Note: I took the picture, so I'm not in the picture. I prefer it that way.)
  
• RFC 7151 - It took me eight years to get this Internet Standard published, and I wrote most of it as part of my IIS PM work. As I have mentioned before, I get to honestly say that I helped create part of the Internet. (It's a very small part of the Internet, but I still get bragging rights.)
• Technical Writing - Between my ten years in product support and my years as a writer in this organization, I have written thousands of how-to articles, samples, walkthroughs, blogs, reference topics, and KB articles. It has never ceased to amaze me how much of what I have written has been used by customers; I love seeing code that I wrote in an article show up in customers' blogs or forum posts. It's especially amusing to me when they're passing it off as their code even though it's 100% copied from my samples. (Hey, I always can tell.) If I combined every article that I have written during my tenure at Microsoft, I could create a whole series of books. (Although that would be a really boring books series.)
• FTP Service for IIS 7 & IIS 8 - There's lots of good stuff in there; our feature team discarded the old FTP service (which no one wanted to use) and we created a first-class service from scratch, for which we received a lot of positive feedback.
• Being a Customer Advocate - I started in technical support, where I spent 10 years speaking with customers, and I have always hosted my own websites and run my own servers so that I could face many of their same frustrations. For instance, I run a full Windows domain in my house, where family members have individual accounts, and all Internet access goes through my proxy server, and I could use group policy to set restrictions for my kids when they were younger, etc. By using Microsoft's products as a customer, I made countless discoveries from a customer-point-of-view. But that being said, some of the people with whom I have had to work still don't understand their customers; I ran into that situation a lot when I was a PM. For example, when you make something easier for you that is harder for the customer, you have just failed your customer. (Sigh.)
• WebDAV for IIS 7 & IIS 8 - I loved this technology and I was a huge advocate for it. I hated the old version of WebDAV on IIS 6 and earlier, so when I was a PM on the IIS team I helped create a version from scratch that customers would like. Most people don't realize that Windows ships both a WebDAV service and WebDAV client, so you can map dives and share files over HTTP thanks to WebDAV.
• MetaEdit - This utility was like Regedit for IIS settings and shipped with the Windows Resource Kits. This was a very popular tool in its day, and it was cool to see classes being taught at ATECs for something that I had created. Eventually MetaEdit was replaced by another tool, and IIS 7 made both tools obsolete, but in its day MetaEdit reigned supreme.
• FrontPage Server Extensions (FPSE) - Customers both loved and hated FPSE, and I knew FPSE inside and out from my days in technical support; for years I was arguably the most-knowledgeable person about FPSE the company. (No exaggeration.) So when I became a PM for IIS, I was able to get them to work in all sorts of scenarios where they weren't designed to work, which helped to create new versions of FPSE that resolved thousands of customer problems for Visual Studio and other Enterprise-level customers. (Seriously - the lack of FPSE was an adoption blocker for thousands of Windows Server 2008 customers.) Then a few years later I got to be the PM who finally killed FPSE as far as Microsoft was concerned. (Or as one customer gratefully remarked as he reached to shake my hand, "So you're the guy who's driving the stake through the heart of FPSE!")

Embarrassing Microsoft Moments...

Here is a collection of amusing stories with which I have been involved over the years:

• Due to a simple programming error, (which wasn't my error - I swear), one of my servers managed to register "localhost" in the company's name servers, and it started responding to all TCP/IP requests for "localhost" across the entire network. Within a few hours, this mishap had taken down several mission-critical services across the company, so my office was kicked off the network and I received a call from a corporate president asking me to never turn my server back on. (Note - I found the error and fixed it. But I swear it was in someone else's code. Really. Why would I lie about something like that? )
• I mentioned MetaEdit earlier, and one of my greatest embarrassments was when I famously messed up the version checking dialog box.
• When I designed the extensibility APIs for the IIS 7 FTP service, I realized later that should have added an extra parameter to one of the method prototypes. I couldn't get approval to change the method in subsequent versions of the FTP service, so I have to live with that for the rest of my life. (Darn. Darn. Darn.)
• I didn't cause this error, but I helped diagnose it back in my technical support days: Windows has several built-in reserved filenames that all go back to the DOS days, such as PRN, CON, NUL, LPT1, COM2, etc. Back in the earliest days of IIS, most companies only had one server for everything - domain, web server, proxy server, file shares, print sharing, etc. So you could connect to the FTP service and start uploading a text file filled with nothing but page feed commands while using a destination filename of LPT1; if the company had a printer attached to their server, it would spit out all the paper and then pop up a dialog message asking the user to reload the printer. However, this was a modal dialog box, so IIS would hang until the user had completed the task. We called this the "Denial of Paper" attack.

Weird Microsoft Traditions...

We have done some silly things over the years at Microsoft; some of these traditions are still in practice, while others are long-gone. For example:

• Togas - Believe it or not, employees used to wear togas to work whenever our stock split. (Yeah, it's been years since that happened. )
• "Fire Me" Emails - Locking one's workstation used to be policed by the community, so if you found someone's desktop computer unlocked, you were supposed to send an email to the team that contained the words "FIRE MY LAME @$$!!!" (Eventually this practice was heavily frowned upon.)
• April Fool's Websites - Okay, this is mostly just me, but over the years I have created several internal-only websites for April Fool's Day - for example:
  • People for the Ethical Treatment of Software (PETS) - this was a take off on PETA that was advocating for the abolition of the cruel conditions under which software is tested
  • Buugle - It looked and acted like Google, but it wasn't...
  • Technical Support Trading Cards - this website looked like baseball cards, but listed off all the stats for technical support employees, (e.g. SDFC = "Solution Delivered First Contact," MPI = "Minutes Per Incident," etc.)
  • Virtual Tech Lead - I created Virtual Tech Lead back when I was a Tech Lead in technical support, and I populated it with a bunch of innocuous statements that most Tech Leads often said. I sent it out to my team on April Fool's Day with the caveat that it was "90% as effective as a real Tech Lead," and it took off across the company's tech support divisions like wildfire. Pretty soon my poor internal-only webserver couldn't keep up with the web traffic so it rolled over and died; I had caused a denial-of-service on myself.
• Office Pranks - We used to trash people's offices when they went on vacation. I realize that open space offices have put a dent in certain gags like filling an office with balloons, but how hard is it to wrap someone's desk in saran wrap?
• Anniversary Goodies - Usually people bring in one pound of M&M's for each year on their anniversary. Once I hit my 10-year anniversary I decided that 10 (or more) pounds of M&M's were simply too many for any team to eat, so I started bringing in rum cakes from the Caribbean. Since I work remotely I don't do that now, but my wife surprised me with 20 rum cakes on my desk this morning:
  

A Few of the Hardest Things for Me at 20 Years...

• The Demise of IIS - It has been difficult for me to watch IIS slowly get killed off as a product in an effort to encourage customers to host their websites on Azure. I started working with IIS in early 1996, so it's sad for me to see a product wither away and perish ignominiously after I have I spent thousands of hours designing, developing, and documenting it. But time and tide wait for no man, so the wheels of progress soldier on. However, if you want to see what IIS looked like way back in 1996, see /iis-legacy-screenshots/.
• Kenny King - I was hired at Microsoft on the same day as Kenny; we were hired within the same hour, to be exact. We quickly became friends and we worked together for years; we bought houses down the street from each other in Texas where our kids grew up together and our wives were like sisters. Kenny was always a rock star with everything he did at Microsoft, and he should be here celebrating his 20th anniversary along with me, but sadly he passed away from cancer shortly before our 19th anniversary with the company.

A Few Manager Anecdotes...

I worked with some great first-level managers at Microsoft - too many to recall - and I worked with some great skip-level managers, too. That being said, here is a list with some of my all-time favorite first-level managers (many of whom are no longer with the company): NancyL, SibhonO, MicheleP, JayV, StaceyC, TerryM, SharonM, BillS, Mai-lanB, EricD, ThomasD, AndrewL, TomW, WonY, and of course - WadeP.

Here are a few small managerial anecdotes - I don't have stories about everyone, so anyone left off the list is not meant as a slight:

• NancyL was my first manager at Microsoft, and she was on my interview loop when I was originally hired in Arizona. There had been 8,000 job applicants for 100 jobs, so after I was hired I naively asked Nancy why she wanted to hire me when there were so many great people to choose from, to which she replied, "You scared me; I was afraid that someone else would hire you and we would have to compete against you."
• JayV was one of the best "Big Picture" managers with whom I ever worked; Jay could take a scenario and see how it applied to the company at every level. Yet Jay never lost touch with his individual team members; he would always grab two or three team members and head out to lunch where we'd talk about how things were going. Whenever I have been in a position of leadership during my time at Microsoft, I have actively tried to emulate several of Jay's great qualities.
• StaceyC was one of my all-time favorite managers; I worked for Stacey on two different teams for a total of six years. Stacey was one of the best "people-persons" with whom I have worked. Even in the hardest of time she had a great attitude, and I watched her successfully manage several teams through some extremely traumatic times.
• EricD had not had many direct reports when he became my manager, so he called me into his office one day and said, "Look, I'm the guy who makes sure that IIS ships, so I'm usually pretty difficult to work with. So I want you to be my guinea pig - I want to try not to be jerk for you." Despite the ominous sound of that proposal, Eric turned out to be a great manager.
• JeffH was a really good guy who was in a really difficult position when I worked for him in Technical Support; I had pitched an idea for creating a specialty team of escalation engineers to several managers, and they liked my idea. However, once the team was created my original idea was quickly transformed into something that was entirely different than what I had proposed, so I no longer wanted to work on the team that I had just helped to create. Nevertheless, Jeff really needed the headcount, so he asked me to please stay on the team for six months in order to help get the team started - so I reluctantly agreed. In the end I worked on the team for a year and a half; I hated every minute of it, but I stayed because of Jeff. That was some good leadership on his part.
• Mai-lanB doubled as my mentor at times; she gave me a lot of great advice on how to manage my career as a PM during our 1:1 meetings, which were often over lunch somewhere off campus. However, Mai-lan's primary weakness was that she was a workaholic like me, so she worried some of her direct reports because she would email them at any time during the day or night with a question. Many people thought they had to have an answer right then, so a lot of her reports spent some restless nights until they figured out that it was okay to answer the next day. But that being said, I also had an unpredictable schedule, so Mai-lan was amazed that I seemed to answer all of her emails 24 hours a day. She eventually asked if I ever slept, to which I replied, "Only when you're on vacation." (Perhaps it takes a workaholic to understand a workaholic.) When Mai-lan's position was unexpectedly cut from the IIS team, she and I had found out immediately before we were scheduled to attend a team meeting, and when I sat next to her, I risked an HR violation by hugging her and saying, "I'm so sorry - I really liked working for you, and you will be sorely missed." Mai-lan simply cried as a response.
• I reported to WonY when I was an IIS PM, and he sat down the hall from me. Won had a laugh that was infectious; you could always tell whenever he had a meeting with someone because sooner or later something would make him laugh, and you could hear it everywhere in the building.
• It would seem inappropriate to expound upon WadeP's great qualities since I currently report to him and we have a review meeting coming up soon. So I'll just say that I have probably worked for Wade longer than any other manager, and the same can be said about most of Wade's reports. Any manager with a team of faithful, long-term employees and a zero attrition rate must be doing something right.

Windows Versions during my Tenure...

I thought it would be fun to take a look back at all the version of Windows that have existed during my time at Microsoft, with a few of my thoughts about each version. (Note: you should also see Windows turns 30: a visual history, which is a pretty amusing look back at the history of Windows.)

• Windows 3.1 - Believe it or not, this OS was still widely-used when I was hired, and I had to take tech support calls for it. (How many of you ever knew that there was a 32-bit version of Win31? I did - and I talked customers through getting it up and working.) Win31 wasn't bad, and I knew all sorts of really cool tweaks for customizing ProgMan that were soon to be obsolete. But in its day it was great.
• Windows NT 3.51 - This was the only viable Windows client and server product at the time that I was hired. Before I started at Microsoft, I was working in the IT department of a small college, and we had used WinNT351 for one of our servers. After I was hired by Microsoft I had to take tech support calls for WinNT351, which were an adventure. In terms of productivity, WinNT351 beat the crap out of Novell, which was far-too-cumbersome for most people, and that is why WinNT eventually took over the server market from Novell.
• Windows 95 - This was released shortly before I was hired, and Win95 quickly dominated the home PC market. That said, I had a love/hate relationship with Win95; some things were great, others weren't quite where they needed to be. But the built-in networking was great, and it eventually supplanted every other PC-based peer-to-peer networking technology. (Anyone remember LANtastic? ARCnet? Of course not.)
• Windows NT 4.0 - This was released shortly after I was hired - it was a great OS, and it had lots of stability (unlike its predecessor); both the client and server versions were fantastic. I earned my first MCSE certification on this OS.
• Windows 98 - I loved this OS, and believe it or not I still run the Win98 core OS (non-GUI) on a legacy machine where I need pure DOS-level functionality for some old MIDI stuff that needs unrestricted physical access to drive hardware.
• Windows NT Option Pack - This wasn't really a separate OS, but NTOP added amazing Internet-hosting features to Windows NT 4.0.
• Windows ME - A lot of people hated this OS; I only put it on one computer, and I didn't have any problems with it, so I never understood what the griping was all about.
• Windows 2000 - This was a good OS, both the client and server versions. That said, I never liked using Win2000 Pro for a desktop machine because it had crappy support for audio/video/MIDI processing, which was an intentional decision from the Windows product team. (Their argument was, "This is a business machine; watch videos and create music on your home PC." Of course, that decision alienated anyone who wanted to use Win2000 Pro as the OS on their home PC. It also helped Apple to take over the recording industry. I earned my second MCSE on this OS.
• Windows XP - As everyone is well-aware, WinXP was a fantastic product; in many ways it was too amazing for its own good so millions of people still refuse to upgrade from it. WinXP was clearly one of the greatest operating systems ever created, although there is some funny irony here: Microsoft received a lot of bad press about WinXP when it was first released - some people didn't like having to upgrade their systems for a few of the new product requirements. (Of course, Apple users had always forced to do that for years.) In any event, when Vista and Win7 came along a few years later, they also received bad press from people who didn't like having to upgrade, which made me start ignoring early reviews of operating systems.
• Windows Server 2003/R2 - This OS had some amazing security features, and certainly the best "Old School" version of IIS.
• Windows Vista - This wasn't a bad OS, although it got lots of bad press because it required more video/memory resources than were typical for many legacy systems, so millions of users were forced to upgrade their systems if they wanted to use it. It never worked correctly on my wife's laptop, which was cause for many unhappy conversations in our house. (e.g. My Wife: "Why did you upgrade my computer to this OS? I hate Vista!")
• Windows Server 2008/R2 - These were great server operating systems; lots of killer features, and amazing versions of a completely-redesigned IIS.
• Windows 7 - This is still my favorite OS of all time; it was so amazing that during the beta time frame I reformatted every machine that I had (including my home PCs) and installed the Win7 beta. It was pretty, it was fast, and it did everything right (or so it seemed). Microsoft hit an amazing home run with this OS. One of the least-actualized features of Windows 7 was Windows Media Center (WMC), which should have taken off and dominated the home theater and HTPC markets, but whoever was in charge of that product did not follow through with the right people in the right places to make that happen. WMC on a Windows 7 computer is still the centerpiece of our home entertainment system; it's our DVR, video library, music player, etc.
• Windows Server 2012/R2 - Once again, these were two great server operating systems, with amazing versions of IIS.
• Windows 8 - I am almost embarrassed to admit this publicly, but I really wasn't fond of this OS, even though I tried very, very hard to like it. I could wax poetic about my reasons for this decision, but I'll just leave this as it stands.
• Windows 8.1 - This OS fixed a few of the clunkers in Win8, but unfortunately Microsoft showed off additional fixes (like a replacement Start Menu) that were promised for a Win8.1 update, and that update never happened. The Windows product team decided to hold off and ship those features in Windows 10, and this was a seriously bad decision, for which I heard a great deal of end-user grumbling at Microsoft's expense. (Which may have been was well-deserved.)
• Windows 10 - I upgraded a couple of computers to Win10 during the beta: one physical computer (which stayed on a particular stable build) and one virtual computer (which I updated when new customer previews were available). I've continued to run Win10 on a few computers since its release, and so far it's much better than the Windows 8 versions. Of course, we completely killed Windows Media Center in Win10, so I'm unhappy about that. (Time to look into running XBMC on a Raspberry Pi? )

That about wraps it up for me. So if anyone is still reading by now, here is my statement that I have always used to summarize how I feel about working at Microsoft: "To me, working for Microsoft is like working for Santa Claus; we make all the coolest toys, and we get to play with them before anyone else."

With that in mind, who wouldn't want to spend 20 years working for Microsoft?

Blog Navigation

You are on page 1 of 2 pages.

Tag Cloud