Bob Muglia - Senior VP by day, IT Pro by night

Posted By: Adam Bomb | Jan 27th @ 11:59 PM

Bob Muglia is the Senior Vice President of our Server and Tools division - that makes him 'kind of a big deal' around here. A little while ago, I got to attend a meeting with Bob and one of the product teams he looks after, and he mentioned in passing some of the, let's say, 'challenges' he'd had getting certain things configured on his home network. A VP that does his own network administration? I was interested enough that I asked Bob if we could talk about that, and he found time in his busy schedule for us to meet.
In addition to the 9 server infrastructure that runs Bob's house, we talk about the various roles he's had in his 20 years at Microsoft, why he's excited about Server 2008, and how his team went about creating Windows Home Server - the solution for those who would rather leave their IT Pro activities at work.

Tags: ISA, IT Pro, Windows Home Server, Windows Server 2008

Rating:

Views (6,985)

Comments (8)

Downloads

System

Pingback from Neil Hutson - Windows Server 2008, Visual Studio 2008 and .NET 3.5 for developers : Bob Muglia - Senior VP by Day, ITPRO by night

System

Pingback from Bob Muglia - Senior VP by Day, ITPRO by night - Noticias externas

System

Pingback from VolkerW's WebLog : Bob Muglia - Senior VP and IT Professional

System

Pingback from Bob Muglia - Senior VP and IT Professional - Noticias externas

System

Pingback from Bob Muglia - Senior VP and IT Professional - News

PederVM

I think Bob needs to reconsider how he is going to consolidate his servers at home, he needs a physical DC. The DC should also run DHCP, DNS and WINS and probably NAP if Bob is planning on using that technology, of course it should run Server Core.

Why?

So he can use

- user accounts from AD for his service-accounts, a physical DC is faster to load than a virtual one in case of total loss of power.

- use DHCP to provide and secure IP-adresses for the machines (the servers IP-adresses should be reserved on the DHCP-server and setup manually locally on the servers). DHCP should be allowed to make and own DNS-records on behalf of the machines so a rogue machine on the network won't be able to spoof anything in the infrastructure and you can allow DHCP and DNS to make automatic cleanup.

- WINS is still nessesary because some products still try to do NetBIOS name resolution first and DNS second and it's annoying to wait for the timeout to happen.

By the way: The red Q on the shipping award behind Bob, what product is this for?

Does Bob use a Home Server?