The Case of the Slooooow System

Mert egy rendes családban minden gépen ott figyel a Process Explorer, Process Monitor és társai.

Egyébként ezt a nyomkövetési technikát!

A few weeks ago my wife complained that her Vista desktop was not responding to her typing or mouse clicks. Given the importance of the customer, I immediately sat down at the system to troubleshoot.  It wasn’t completely hung, but extremely sluggish. For example, the mouse moved and when I clicked on the start button the start menu opened after about 30 seconds. I suspected that something was hogging the CPU and likely could have resolved the problem simply by logging off or rebooting, but knew that if I didn’t determine the root cause and address it, she’d likely be calling on my technical support services again in the near future. In any case, stooping to that kind of troubleshooting hack is beneath my dignity. I therefore set out to investigate.

My first step was to run Process Explorer to see which process was using the CPU.

The Case of the Slooooow System

Windows 2003 SP2 is now a RC (Release Candidate)

A Windows Server 2003 & Windows XP x64 Service Pack 2 Technical Overview-ból:

In addition to the all previously released Security Bulletin Updates, Service Pack 2 installs all individual hotfixes released since Windows Server 2003 RTM and several key customer requested features and enhancements.

New Features:
  • Scalable Networking Pack (SNP)
  • XMLLite
Enhancements to Existing Features

The enhancements to Windows Server 2003 Service Pack 2 include:

  • Windows Deployment Services (WDS)
  • Enabling ‘Firewall Per Port’ Authentication
  • Microsoft Management Console 3.0 (MMC 3.0)
  • Wireless Protected Access 2 (WPA2)
  • iCACLS tool
  • Expanded Windows Server 2003 Datacenter SKUs
  • Release of MUI Packs to insure greater compatibility between base and MUI language
  • Performance Improvements for SQL Servers
  • Enhanced discoverability options in MSConfig
  • Improved IPsec filter management
  • Performance Improvements under Windows Virtualization
  • Increased default storage for Message Queuing
  • Improvements to DCDIAG Domain Name Service tests
  • New Events for Cluster Service Accounts

Source: Windows Server 2003 & Windows XP x64 Service Pack 2 Technical Overview ,

Dear Santa Bill and Santa Ozzie

Felőlem hozhatná Bill Haley (vagy Ozzy Osbourne) is, csak a -ról legyen letölthető minden decemberben az összes lokalizált változaté tárgyévi összes patch-e egy ISO file-ban.
We'll even leave cookies and milk (and Cherry Coke) under the tree for you. Cherry Coke is lesz egy kartonnal.


I have just installed WXP Pro SP2 on my newly rebuilt machine.  Do you have any words of wisdom with regard to how I can make sure that I have all of the critical patches up to date without going through everything that has been released over the past 3 or 4 years?  I don’t want to spend two weeks of work time installing patches.

Dear Santa Bill (or Ozzie):

I know what you’d like me to answer that with… “Buy Vista!” but the reality is that Vista isn’t out for the retail marketplace yet. Now hopefully the inlaws will be over during Christmas so it will give this person an excuse to be in their home office and take the eons of time to go from XP sp2 to final patched up versions.  The reality is that you haven’t made it easy for the home user to take a XP sp2 machine up to full patch status for one machines.  Oh sure, you’ve given us admins things like WSUS and what not..but for the one machines that we have to deal with, or that hopefully you’ll have to deal with over your Christmas vacations with your families….. how about reconsidering once again a roll up cdrom. While that gives us some idea…. What I’d really like from Santa Bill or Santa Ozzie is an official Microsoft ISO available in December of each year of “fill in the blank” supported consumer operating systems so that we as sons and daughters of folks that use us a tech support at home can do it easily, or, as in the case of the person who asked, someone trying to get one business system up to full patch state quickly.

P.S.  I’ll even leave cookies and milk under the tree for you.


Source: Dear Santa Bill and Santa Ozzie

Microsoft Update

No meglepett, hogy megjelent a választható update-ek között:

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)

Download size: 1.5 MB , less than 1 minute
Remote Desktop Connection (Terminal Services Client 6.0) provides a way to use any new Terminal Services features introduced in Microsoft Windows Vista and Microsoft Windows Server Code Name “Longhorn” from a computer running Microsoft Windows XP with Service Pack 2 or Microsoft Windows Server 2003 with Service Pack 1.  Details…

Solution – Microsoft’s AntiSpyware Tool Removes Internet Explorer (Fix for Spanish IE7 problem (WSUS))

Tegnap írtam erről a gondról, most itt van a megoldás Sandi értesítőjében – Bobbie Harder (PM, WSUS) postja alapján:

Bobbie Harder has posted to advising that MS have confirmed the problem and have a fix, and advice for those affected.  You will need to access Bobbie’s post using NNTP to access the batch file.

Hi Folks –
We have verified a problem in the metadata for the latest  IE7.0 update
rollup package which impacts the installation behavior for all locales, and
results in an Spanish error dialog after installation as reported..

To immediately address the spread of this issue, the IE7.0 update package
has been expired effective 5:00PM PST, Wednesday, 11/22/06.  Synchronizing
WSUS servers after 5:00PM PST will ensure the expiration status is applied
to the latest IE7.0 update rollup package, released 11/21/06.

Clients which are currently displaying a Spanish error dialog, or are
rechecking for this update package, can be stopped from doing so via the
following steps:
If the update was approved for a scheduled installation:
1.       Stop the AU service.
2.       Kill the following processes –
a.       Iesetup.exe
b.      Ie7-WindowsXP-x86-esn.exe
3.       Start the AU service after you have synchronized the WSUS server to
expire the IE7 update.
4.       Run the command wuauclt.exe /detectnow.  We have to do this to
reset the IE 7 status on the client.  In my test, it offered the IE7 update
again, so it did not check back with the WSUS server where it had been
changed to detect only status.
If it is a manual kick off with the AU icon from systray, then clicking okay
to the error message, clears the IE setup executables, so we can just do the
following –
1.       Stop the AU service
2.       Start the AU service after you have synchronized the WSUS server to
expire the IE7 update.
3.       Run the command wuauclt.exe /detectnow.  We have to do this to
reset the IE 7 status on the client.  In my test, it offered the IE7 update
again, so it did not check back with the WSUS server where it had been
changed to detect only status.

If other updates were installed at the same time, a reboot will be required
to finish off the updates that did install for both scenarios above.

Attached is a sample batch file Before running a similar batch file you will
have had to either synchronize to ensure the update is expired , or have had
changed the update approval  to Not Approved or Dectect Only.  The batch
file sample can be run on the client system either from a logon script or
running it manually on the client.
A new update rollup package for this IE 7.0 release will be available for
synchronization early next week.  We regret the inconvenience and confusion
this issue may have caused WSUS customers.  Thank you for your reports and
enabling us to get this issue headed off so quickly.

– Bobbie Harder


Source: Fix for Spanish IE7 problem (WSUS)


Microsoft IT Showcase – Microsoft IT Early Adopter Experiences & Best Practices

El kell olvasni, persze. 
A “best experiences” körébe tartozik Susan Bradley tegnapi megjegyzése:

Sometimes I think we get too caught up in “best practices” to remember that the folks that set “best practices” are sitting on a committee and not building and running servers for small businesses.

Get ready to deploy by leveraging Microsoft IT’s experience!

Find here Microsoft IT’s early adopter experiences, best experiences, and lessons learned from our own deployments of Windows Vista, the 2007 Office system, and Exchange Server 2007. By leveraging our best practices, you can make decisions about how best to plan for, deploy, and manage Microsoft solutions in your own environment.

On This Page

Window Vista
Window Vista

2007 Office System
2007 Office System

Exchange Server 2007
Exchange Server 2007

Source: Microsoft IT Showcase – Microsoft IT Early Adopter Experiences & Best Practices

Microsoft Host Integration Server 2006 Management Pack for Microsoft Operations Manager 2005

Árukapcsolásnak, vagy jelentős funkcionális bővítésnek fogjam fel? Tényleg kellett ez a funkció. Most már csak egy olyan alkalmazásra várok, amelyik megmutatja, hogyan változik a host hatékonysága a HIS alkalmazásával. Elméletileg igazolható, de online mérést még nem láttam.


The Microsoft Host Integration Server 2006 Management Pack provides monitoring functionality for Host Integration Server 2006 computers running on Microsoft Windows Server 2000 and Windows Server 2003, and is supported for use only with Microsoft Operations Manager 2005 (MOM). This management pack provides monitoring of key Host Integration Server components, including SNA Connections and TN3270, TN5250, Print, Session Integrator, and host transaction resynchronization services.
Feature Bullet Summary:
• Host Integration Server 2006 Alert Monitoring
• Host Integration Server 2006 Health Indication and Monitoring
• Host Integration Server 2006 Performance Monitoring
• Automated configuration discovery and role-based assignment of monitoring rules
• An easy-to-understand and navigable processing rule group hierarchy
• Public views of Host Integration Server 2006 servers, alerts, and groups
• Operator tasks for use in response to common situations
Release History:
11/13/2006 MP published 

File Name:
     Microsoft Host Integration Server 2006 MOM 2005 MP.msi


Date Published:


Download Size:
     314 KB

Source: Microsoft Host Integration Server 2006 Management Pack for Microsoft Operations Manager 2005

Outlook 2007 Doesn’t Work with Exchange 5.5


Not that I’m really very surprised but Outlook 2007 will not connect to Exchange 5.5. I found a note about this on the TechNet Forums:

“Microsoft continuously strives to provide a consistent and predictable end-of-life-cycle experience for all of its products.  In accordance with standard Microsoft life-cycle policies Exchange 5.5 ended extended life-cycle support on January 10, 2006.  As a result, Outlook 2007 will not support Exchange 5.5.  Because neither the Outlook or Exchange team is supporting this combination we will not discover and/or fix issues that crop up as the result of innovations in both products .  Rather than subjecting customers to potential serious issues like data loss or frequent server downtime we choose to prevent Outlook from connecting to these older and now unsupported servers.  Our research has shown that there is a relatively small set of customers who want to upgrade their desktops to the latest and greatest versions of Office and run server technology as old as Exchange 5.5.  There are clearly exceptions but they don’t seem to be the norm.”

Something to keep in mind if, like me, you need to connect to an Exchange 5.5 email server.

Share this post: Email it! | bookmark it! | digg it! | reddit!

Source: Outlook 2007 Doesn’t Work with Exchange 5.5

Sun Never Sets on Java Security Updates

Tapasztalatomat az itt olvasottak megerősítik. Ilyen kuplerejisztikus “automatikus”  update eljárást, bánásmódot mióta kétágú vagyok, még nem tapasztaltam. Valóban horrorisztikus, követhetetlen, nem dokumentált és mondjuk nagyvállalati környezetben sem végrehajtható “biztonsági” javításokat produkál a Sun, amivel pont az ellenkezőjét – a nem megbízható rendszerek megteremtését – éri el.

Csatlakozom az anonymous hozzászólóhoz:
My current response to this has been to stick with Java 1.4.2.x, which has been stable longer and has far fewer updates. It handles most current Java code, and has not been EOL-ed yet by Sun. Of course, if all of us do that it hurts the spread of Java 1.5 development, but perhaps if enough people did that, it would send a clear message to Sun that they need to make changes.”

When it comes to security, Sun tends to be subject to much less criticism than some other system software vendors we could mention. But one reader thinks that a little more scrutiny of Sun would be a good thing, particularly in terms of how it handles Java security updates….

Source: Sun Never Sets on Java Security Updates

User support

Ahhoz, hogy ügyfeleim gépeit folyamatosan felügyelhessem (most mindegy, milyen software-rel), továbbá, ha nem vagyok a felügyeleti gépnél, vagy maguk az ügyfelek futtatnak e gépről (mint Terminal Server-ről) bizonyos keretek között alkalmazásokat és nincs lehetőségem erre a célra egy servert és server software-t használni (értelmét sem látom), szükségem van:

– az egyidejűleg lehetséges TCP kapcsolatok számának megnövelésére,
– az XPSP2-őt futtató gépen lehetővé kell tenni több egyidejű RDP kapcsolatot (minél többet, de legalább hármat a konzollal együtt)
– egyidejűleg több VNC servert is kell tudni látni.

Ezekre a dolgokra az alábbiakat használom (úgy tűnik, nem ütközik egyik sem sw jogi akadályba):

  • LvlLord: Event ID 4226 Patcher (4226 fix)

    What’s this all about?
    After almost everybody knows the <<EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts>>, I used a day to create for educational purpose a fix for this argumentative feature.

    Unfortunately there exists no REG-key which could easily be set (would be so nice and easy, right? *smile*). The file TCPIP.SYS in the directory C:\WINDOWS\SYSTEM32\DRIVERS and C:\WINDOWS\SERVICEPACKFILES\I386 has to be changed (system dependend eventually in C:\WINDOWS\SYSTEM32\DLLCACHE, too).

    Needed things:
    – Windows XP SP2 (from RC2 upwards) or Windows 2003 Server SP1 beta
    – a small amount of time

    What’s been done:
    To say it easy: the before 10 half-open connections are beeing increased to 50 (can be changed during runtime and with the parameter /L) and the CRC is been corrected. And that’s it!

    The method described here, should only be used by users, who know how to handle all the described. With the download of the here published program the user know, that changes are made on third party files. For damages in every kind I cannot be hold responsible for. Indeed, tests worked fine here. However, nothing is impossible.
    Info: When error occurs, the patcher can change the TCPIP.SYS back to the original! 

     Just download the patcher and execute it. It will automatically find the windows directory and ask, if it should increase/decrease. For higher values, please check the help with parameter /?.
    After a successful patch, the new TCPIP.SYS will be automatically installed. After that, the computer should be restarted.

    Ez a saját gépemen így néz ki:

    Jól látható, hogy itt már 50 “half open” kapcsolat lehetséges.

  • sala: Terminal Server Patch

    The beta 2055 release of XP PRO SP2 let you run two or more sessions (one local console and one or more remote desktop) concurrently. But this functionality was removed in the Final release. This patch will enable two or more concurrent sessions in Windows XP PRO Service Pack 2 (SP2) or later if you have FAST USER SWITCHING enabled, and your windows is NOT in a domain.

    Uninstaller is also included and can be found at windows Control Panel -> Add or Remove Programs.

    Download Latest Binary

  • IntelliNavigator Inc: VNC Navigator

    This program allows you to easily manage your VNC servers. It supports RealVNC, TightVNC, and UltraVNC. Connect to servers with just a double click. It keeps your passwords safe in a 256 Bit encrypted database.
    (Free version limited to 3 connections)

J’accuse: a kép négyzetalakú lett a kíváló .NET Paint alkalmazása miatt, direkt hagytam így.