Been keeping myself bussy at work with stuff that is reasonably interesting.
Oke, first the technical stuff, then the customary ranting.
Windows Update still wont work properly. Yesterday I came across some log entries that seemed to indicate hosts where having trouble finding the SUS server. I went back to my group policy and noticed that I had used wrong slashes, again, for the windowsupdate server, that we call .. http://windowsupdate
I am a little worried that there might be some host confusion at this name, as its also the DNS host name of Microsofts own update servers.
Just in case, I then changed the same to a FQDN.
Anyhow, the reason clients are not able to resolve the Netbios name seems to be major problems with the browsing service on the local subnet. Somehow the PDC was not properly updating its browse list, and since the PDC is also the domain master browser, everyone elses list was pretty short. Only computers that had booted that morning where in the list, the rest, like my own, where absent. I am still looking into this, at least how it occured, using resources like the MS Windows NT Browser White Paper, and a very cool little tool I discovered here, called the NetBIOS Browsing Console (Browcon.exe), written by Brian Schafer and Tim Rains. And of course Browstat.exe. I would have used Browmon if I had the Windows NT4 resource Kit tools here, but I only have the 2003 version which I downloaded. Also the Windows 2000 Resource Kit TCP/IP Core Networking Guide has agreally good appendix on the browsing service.
That kinda pisses me off, because I had expected the Resource Kit tools to be commulative. Also, Microsoft doesn't offer the older tool sets for download, or not completly. This is their marketing machine at work, trying to get you to buy the books, which I do, which include the 'complete set' of tools, while offering only a subset of the tools for download. Means in future I will have to keep the NT4, 2K, and 2K3 tools all seperatly on my laptop. I have also discovered that I need to do the same with other tools, like the support tools or deployment tools, because sometimes certain switch functionality ,or downlevel support for older enviroments, is lost in later releases. I remember a similair issue with the old NT4 regedit I think.
Anyhow, I moved about the domain browser role untill the problem was fixed. Then the domain browser service on the PDC resets, it sends out a DomainAnnouncement datagram to all hosts, and then builds up the list again from hosts sending hosts announcement messages, and they send these every 12 minutes by default. What I dont understand is why the domain master browser lost so many entries in the list, and why the list wasnt being filled up again. the eventlogs on hosts didnt give any details about netbios problems. I hope simply restarting the browsing service on the PCD helps to solve this problem in the future!
Oke. Rant time.
I am here only 2 weeks, and yet I find enough reasons to have installed the support tools, the Windows deployment tools, the Resource kit tooks, the adminpak, the Office 2000 Resource Kit tools, and various other small tools like the Process Explorer and Browcon.
Now why do I never ever see any other admin doing this? I find these tools indispesive! They are always the first things I am installing on any new pc that I will be using for administrative purposes! Why do other admins never seems to be creating distribution points for Office? Time and time again I see people dicking around with CD keys; its so unnessesary! Any new server I install, gets the support tools and resouce kit tools by default, aswell as the network monitor components. I build these installations into every unnatended install I do, so you dont have to worry about them anymore! Yet I have never ever come across a server installation at a customers, that had this stuff installed on it!
Oke.. lets think about this.
Do admins simply not know about what these tools have to offer? I am convinced this is the case, because everytime I show them these tools, they are obviously suprised!
So why then do they not know of these tools? Why is it that I do know of then? Because these tools are mentioned time again time again online, on support page, and Microsofts support sites, in documentation, etc.
That must mean that most of these admins I meet dont read or browse this kind of matieral often. Why not?
I come across this material all the time, for 2 reasons:
A. I use these resources in troubleshooting problems that I encounter.
B. I am genuinly interested in the material, so I buy a lot of books on this stuff, read a lot about it online, follow lots of Microsoft blogs, read a lot of technet stuff.
Now, I can well imagine most admins not spending their time reading technet or MSpress books. Fine. But I cannot imagine them not coming across this stuff when troubleshooting problems.
But perhaps that is the whole point. Often, these admins dont seem to be troubleshooting problems! Like they didn't even notice the lack of NETLOGON replication on both office domains, or the fact that nothing was up to date with Windows patches.
Now the reason they dont notice these thigns , at least here, is because their allerting software, in this case Sitescope, doesnt seem to alert them. This is perhaps something I can fix in these last 2 days if me being here.
The second reason, is that they are simply not interested enough in their office network, to even care to check manually. Their main business is their digital tv channel stuff, for which they have seperate domains and subnets, and they are bussy with that all day. They have left their office network to decay to the point of being a massive security and functionality hole, and their support persion, who has become their defacto sysadmin for the office network, simply doesnt know enough.
Unfortunatly, this is a scenario that seems to repeat itself over and over and over, and I come across it at almost every customer I am placed at. No wonder IT is so untrustworthy, with investment like this, or lack thereoff, and i am talking mental investment, not even financial, IT enviroments will never improve in reliability or managebility, and the way IT is practices will only ever be second rate. God how I long to work for a company that has their shit together in this.