Just more proof, as if it's needed, that users need to keep bang up to date and that defense in depth is a useful strategy. I suspect a lot of home users will get stung by this, and won't even know how it happened.
Thomas Lee's collection of random interesting items, views on things, mainly IT related, as well as the occasional rant
Monday, March 22, 2004
Witty Worm Targets Black Ice users
Sunday, March 21, 2004
ISO Recorder Power Toy for XP
Sadly, this tool does not work on Windows Server 2003, which has updated the CD burning facility. The tool only works on Windows XP.
Thursday, March 11, 2004
InfoWorld says Microsoft is to delay SQL Server, Visual Studio upgrades
Tuesday, February 03, 2004
Virtual PC 2004 vs. VMWare 4.0 Performance
Friday, January 30, 2004
MyDoom.b - even smart people do dumb things
Basically, what is clear by this virus/worm is that even smart people can do dumb things at times. With that in mind, I have no hesitation in passing on the advice I got from MS. If it helps just one person, its worth.
So why not take a quick peek at http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/alerts/mydoom.asp.
Tuesday, January 20, 2004
MBSA 1.2
This new version provides better language (ie non-American!) support, plus support for Exchange 2003, MS Office, Microsft Java Virtual Machine, B iztalk, Commerced Server, Contene Management Ser ver and Host Integration Server, MSXML, MDAC. MBSA solves a number of other problems too!
A useful upgrade, but where's SUS 2, MSI 3, etc??
Wednesday, January 14, 2004
Using Adminpak.msi to Install a Specific Server Administration Tool
The format is not overly friendly. For example, to install the DNS console, you'd type:
msiexec /i adminpak.msi ADDLOCAL=FeDNSConsole /qb
Cool .NET Linking Tool
The tool links MSIL code on demand putting together only the required classes and methods. The tool then builds a minimum set of the Microsoft .NET runtime to ship with your application. This usually results in installation size substantically smaller and faster then traditional .NET apps.
And by linking them this way, it's easier to obfuscate the code. A neat tool!
Wednesday, January 07, 2004
NetMon 2.1 - Part of SMS 2003
Monday, January 05, 2004
Microsoft TechNet Events
I was able to give some of these events in 2003 (and will be giving more in 2004). In December, I gave a talk on patch management and SUS. You can get a recording of this session athttp://www.placeware.com/cc/emea/view?id=msft0912cs&pw=RMG9GT. This uses PlaceWare, so to see the full webcast, you will need to load some software (you will get prompted for it).
The overall UK technet site is http://www.microsoft.com/uk/technet/learning/ - enjoy!
Thomas
Wednesday, December 17, 2003
Details on XP SP2 Emerge
Most of this document describes details of what has previously been disclosed. The details are nevertheless interesting reading!!
Saturday, December 13, 2003
Making the AU client run a little more often
The client is hard coded to go to a server every 22 hours (less a random amount of up to 20%). Thus in 'steady state' each clinet will ask for updates every 17.6 to 22 hours. But what if you want to push out an update a bit faster how can you do it? Turns out there are 2 ways - neither of them very pretty. GPO Workaround
1. Assign a temporary GPO to the appropriate part of the Organizational Unit structure and use security filtering to ensure it applies to the appropriate computers.� Note that this temporary SUS GPO should be of a higher priority then the SUS GPO which is normally in use.�
2. The policy settings within this GPO should be configured to disable the AU client and change the default Group Policy refresh interval for computers to 5 minutes.
3. Force DC replication to occur so that all domain controllers have a copy of the new group policy object.
4. Wait up to 120 minutes for all clients within the OU to refresh Group Policy (default GPO refresh time for domain members is 120 minutes).
5. Amend the policy settings within the new GPO policy so that the automatic updates client is enabled and set to automatic download and automatic installation. Automatic installation should be set to occur 1 hour from the current time.
6. Force DC replication to occur so that all domain controllers have a copy of the changed group policy object.
7. Wait for all the SUS clients to refresh the updated SUS GPO settings (which is now happening 5 minutes).� Once the GPO takes effect, the automatic update clients should begin to download the new update from the SUS server. Installation will begin once the specified time is reached.
8. Once the update has been successfully installed on all target computers, delete the temporary GPO used to make all these changes. Servers will fall back to the existing AU download and installation options once they refresh their Group Policy settings.
----------- Net Stop/Start method
1. From the cmd.exe prompt: net stop "Automatic Updates"
2. Delete HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\LastWaitTimeout (if it exists)
3. Delete HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\DetectionStartTime (if it exists)
4. Make sure that HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\AUState=0x2
5. Net Start "Automatic Updates"
Lindows.com Ordered to Change Name in Europe
Wednesday, December 10, 2003
Another Internet Explorer Vulnerability
While most folks reading this will not be likely to get hit by such tricks, the average user may well be. Let's get the patch for this, and get it applied quickly!
Monday, December 01, 2003
The Annotated XML Specification
Many fine hours of reading ahead!
Thursday, November 27, 2003
Windows SharePoint Services - Installation is Interesting
The problem occurs if you install Microsoft Windows SharePoint Services (STS as it used to be called), which from 3 days ago, fails with a fairly obscure error message. You also get this problem if you try to provision a new virtual server or you try to create a new content database when you are running Windows SharePoint Services by using MSDE (the KB appears to be inaccurate on this point).
The error is caused by a bug in the code that verifies the signatures of DLLS installed with SPS. All installations of Windows SharePoint Services experience this behavior after November 24, 2003. And guess which product installs this component by default? Small Business Server. Ouch!
Problems hapen. But the workaround is interesting: Set the date in the Date and Time Properties dialog box to a date that is between May 24, 2002 and November 23, 2003. That's right, lie to the OS. Trustworthy computing, maybe not, but it works. OH, be careful to not set it too far adrift, or you might trigger product activation.
My view of WPA is further diminished.
And here I thought Linux was secure!
This attack comes close on the heels of both an attempt to hack the Linux kernel, and and an attack at the Free Software Foundation. These hacks show two things: First that security is everyone's problem (not just for customers of Microsoft) - attackers do not play by any rules and will attack pretty much anything that is not totally locked down. Second, it proves, yet again, that any OS can be installed insecurely.
What the Linux bigots often fail to remember is that security requires three things: people, processes, and technology. Even the most secure technology can be defeated by poor processes or by people not doing the right things. This is not a Microsoft vs Linux thing, but more a simple recognition that security of your systems is only as strong as the weakest link.
Wednesday, November 26, 2003
Dell Ditch India - and not before time
Both techs I talked to were cheerful, but the responses bore no relationship to my questions. They had a script and totally had to follow it - any deviation was met with a refusal to go further. It took forever, and in the end, they were unable to help in time - so I go another hard drive from another source and made do with that. Next week, when I settle down a bit, I'll call again and get the disk replaced. See CNN.com for full details of this story
I couldn't make this stuff up if I tried!
Thursday, November 20, 2003
Microsoft Announces Availability of Open and Royalty-Free License For Office 2003 XML Reference Schemas
As it turns out, MS also formally used Copenhagen and IT forum to announce the availability of Open and Royalty-Free License For Office 2003 XML Reference Schemas.
This is a good step forward!