Back in July 2008 I blogged on viztaview.com about the Uniblue Process Scanner. In answering some questions about process lookup for one of the Windows 7 classes I teach online for HP, I discovered that Uniblue has completely reworked this still-excellent product.
Instead of plugging right into task manager as the previous version did, the latest version of Process Scanner spelunks your system, then opens a Web page to show you all the processes it finds running. The resulting (cropped) output looks like this:
Unlike Task Manager, however, you can click on any line in this display, and jump straight into Uniblue’s excellent Process Library to learn what they know about the entry in question. This provides information about the processes’s author, memory usage, security state, file version and even its MD5 hash value. The whole thing makes it easy to separate questionable and unknown stuff from know good working stuff, which is what spelunking processes is usually all about.
The previous version of this tool embedded itself into Task Manager. This offered the plus of simply clicking on an icon to the left of the process name to retrieve this data, offset by the minus of loading and running the lookup tool whether you use it or not. This way, although you must explicitly run the Process Scanner, and work from the Web page it generates, at least it creates no constant system ovehead when it’s not in use as the old version did. Definitely worth grabbing and using.
For those interested in the next generation of Windows development tools and platforms, related beta exams will be available from March 31 to April 20, 2010, as explained in this posting from the MS Beta Exams Blog. Here’s a list of what’s coming up during that time window:
- 70-511 TS: Windows Applications Development with Microsoft .NET Framework 4
- 70-513 TS: Windows Communication Foundation Development with Microsoft .NET Framework 4
- 70-515 TS: Web Applications Development with Microsoft .NET Framework 4
- 70-516 TS: Accessing Data with Microsoft .NET Framework 4
- 70-519 Pro: Designing and Developing Web Applications using Microsoft .NET Framework 4
In addition, the following beta exam will also become available a little bit later (probably in April, or perhaps April-May):
- 70-518 Pro: Designing and Devevloping Windows Applications using MIcrosoft .NET Framework 4.0.
Poster Gerry O’Brien is a Technical Product Planner for Developer Certifications at Microsoft, and he promises to post again to the Beta Exam blog when the final dates are determined, and a special no-cost promotional code is available for beta exam sign up at Prometric. With March just over a week away as I write this blog myself, I’m guessing we’ll be hearing further on this subject in the next 10 days to two weeks. Stay tuned!
Remember: while the number of seats for beta exams is limited, those who sign up quickly take them for free. And those who pass those exams get the same credit as if they had waited and paid for the final public versions. If you’re already working on the new platform, and with the Visual Studio 2010 environment, this could be a great opportunity to upgrade or add to your certifications at little or no cost.
By now, everybody’s aware of the speed and power consumption or battery life benefits that solid state drives (SSDs) can confer on desktop and notebook PCs, respectively — at least, for those prepared to cover their high costs of acquisition. Knowing that some IT professionals will no doubt be asked to retrofit such hardware into certain “high-value” users’ desktop or notebook machines, I’d like to share some potential pitfalls that might crop up for those potentially hapless staff members. Here, “high-value” often translates into “high visibility” for the results of such efforts and “high expectations” regarding their results.
I’ve just gone through the process of getting SSDs to work on several Windows 7 machines, and I can now attest that there’s a LOT more involved in getting an SSD working properly than simply imaging the old drive, copying that image to an SSD, and replacing the old drive with the new (SSD) one. And while Windows 7 is rightly touted as an “SSD-friendly” or “SSD-aware” operating system, that friendliness or awareness isn’t as likely to be helpful in cases where the OS is moved from an existing conventional hard disk to an SSD after the OS is installed. That said, if you can reinstall Windows 7 on a system with a new SSD in place, some of these observations won’t apply — enough of them, in fact, that you may want to consider this as an additional impetus to upgrade your users from 32- to 64-bit OS versions as an “excuse” to justify the reinstall (and make your life easier).
There are three major areas where you’ll have to proceed with some caution, and will probably have to experiment with the SSDs and systems you’re working with to understand what’s what:
1. Firmware Updates
Most SSDs packaged or sold before November/December 2009 (and I have to believe this still represents a substantial portion of the stock on resellers or distributors shelves, even at this very moment) include older firmware. Download CrystalDiskInfo (see this page at Crystal Dew World) so you can determine which version of firmware is installed on whatever SSDs you have on hand. For the kind of performance most users expect from SSDs, firmware that supports TRIM (a technique for managing SSD content that’s been written, then deleted, for improved re-use and disk writing performance) is absolutely essential. Be prepared to invest $35 on an eSATA drive caddy so you can easily update the firmware on these drives from a bench PC before installing them in their target machines. Investigate the SSD maker’s firmware update tools (Intel and Samsung make such hardware and software, and Intel also offers a pretty nifty SSD Toolbox as well) and learn how to use them.
2. Windows 7 Tweaking
There’s a lot of stuff that has to be turned off or tweaked on Windows 7 to make sure your users can make the most of the fairly high investment in switching to an SSD. Be sure to check out and use Ahsley Maple’s excellent SourceForge project called SSD Tweaker to help you understand all the many settings you must check (and often monkey with) to make sure Windows 7 and your user’s SSD will get along properly (and quickly enough).
3. BIOS Issues
You may have to reset the desktop or notebook PC’s BIOS to interact with SATA drives on those systems as AHCI (Advanced Host Controller Interface) devices rather than having them emulate IDE (which is how many SATA drives work on the systems into which they’re installed). Sometimes, you can simply force Windows 7 to load the msahci.sys driver through a registry hack, reset the BIOS, restart Windows and let it repair itself (using the capable and reasonably quick Startup Repair options built into Windows 7 itself). Sometimes, more forceful shenanigans become necessary, and may even require re-installing the OS as a last and mostly unwelcome resort. See if your users can live with IDE emulation first, if you find yourself facing the decision to reinstall the OS to achieve the right host controller capabilities on user hardware platforms.
Though SSDs are indeed fast, and do offer performance and power benefits, they can be irksome and tricky to get working properly. But with a little online research, and some preparation for the problems you may encounter, you can get through the tasks involved without losing too much time or sleep. Just don’t think of it as a simple remove-and-replace operation, and you’re already well on the way to accomplishing this task.
Yesterday, I had the pleasure of seeing a recent article I wrote for my colleague and co-worker’s Website “IT Expert Voice.” It’s entitled IP Toolkits: 6 Great Items for Your Networking Toolbox, and it covers a variety of free and commercial IP tools and tool sets that most Windows administrators are likely to find both useful and interesting. You can see some screencaps and read a summary on the review itself. Here, I’ll just give you a list of attractions with brief blurbs to explain what they can do for you.
- NetScanTools: I cover the collection of DNS, Whois, and Ping-related stuff readily available in that company’s free NetScanTools Basic Edition.
- SysInternals: Here you find pointers to Mark Russinovich’s excellent TCPView tool and his stalware command-line Whois implementation.
- Peter Kostas makes a snazzy revived and revised version of the old winipcfg.exe tool called Win IP Config: it provides a single GUI interface for stuff you normally do at the command line, or across a raft of Control Panel items in Vista or Win7.
- Solarwinds offers an expensive but amazing software bundle called the IT Pro Pack, which includes its well-known Engineer’s Toolset and LANSurveyor packages. You’ll find a plethora of dashboards, monitoring tools, management widgets, and reporting capabilities in this fully-stocked set of IP tools.
Head on over to ITExpertVoice and see what this Dell-sponsored enterprise oriented site has to offer, and read my article. I’ve also included links to all the tools mentioned therein above, for those who must simply cut to the chase. Enjoy!
If you’re in the market for an MSDN Subscription, as I was recently–I missed my “renewal date” while I was overseas for the last week of January and the first week of February, and found myself in a “grace period” upon my return as a consequence–don’t overlook the third-party channel. For years, I’d been buying my subscriptions direct from Microsoft, but when I ran into trouble renewing my subscription online this morning at the MS Partner site, I decided to go shopping and see what kinds of deals I could find on the outside, as it were.
Boy, am I glad I did: I found a 3-year subscription deal at Software International (www.software-intl.com) that cost less than two years’ worth of full-price MSDN but delivered three years worth of service at that price. And because the company’s in Colorado, and I’m in Texas, no sales tax on the purchase, either (an additional savings of around $100 as compared to direct purchase from Microsoft). I ended up paying $1,086 for three years for an annual rate of $362 per year. Compare that to a straight annual renewal at Microsoft for $699 plus tax (total $756) for the OS-only MSDN license and $1,099 plus tax (total $1,190) for the same package I just purchased — namely, the Visual Studio Professional with MSDN Professional license — and you’ll quickly get a sense for the kinds of savings available on the open market.
Like the old song goes “You better shop around.” There are deals out there, and they go all the way into Open License and other software arrangements with Microsoft, where the same kinds of discounts are available, even at the enterprise level. Let your purchasing folks know that there are some awesome deals to be found in the reseller channel, right now.
For the past two weeks, I’ve wandered wide away from my usual orbits. I’ve been in one the Benelux countries (hint: it’s the one with the best beer) assisting in the preparations needed to help bring IT operations back in-house from a third-party provider based here. The company itself is solidly global with major data centers in Belgium, Singapore, and New Jersey.
Aside from a contrarian (and to me, very welcome) switch from outsourcing to a kind of insourcing, the trip was absolutely fascinating for me because of the purpose of the meetings we held. The primary focus was to understand how the vendor is handling things now, particularly with regard to its tools, processes, and procedures. Though –as is invariably the case when a change of hands and control occurs – the company plans to make some changes when it accepts the handoff from the vendor, it knows it needs to understand how things work right now, to keep them working when they have to take over and keep doing what the vendor is doing for them right now, and what they must do themselves starting on the cutover date and thereafter.
Of course, the two organizations will work in parallel for a while (a period called “shadowing”) where the vendor will take the lead up to the transition point, as the company mounts and operates parallel operations in the background. After transition, the tables turn, and the company takes the lead role, but the vendor keeps on operating in parallel to make sure they can resume control if the company’s operations fail or run into difficulties.
What’s been both fascinating and educational to observe , and even to participate in, has been the back-and-forth between vendor and company as the handoff comes ever closer to the cutover date. The kinds of questions that come up have primarily to do with soliciting enough detail to ensure smooth operation as the current controlling entity (the vendor) passes control over to the future one (the company). Natually, both sides are concerned that the transition go smoothly, and be successful, but both sides have slightly different aims: the vendor wants to accomplish the handover without having to do too much extra work, while the company wants everything and anything they can lay hands or eyes onto to shed as much light on day-to-day problems, issues, procedures, and resource requirements as they possibly can.
Given a situation that could have been tense and fraught with animosity, relations were professional and mostly unemotional. Sometimes, they were downright cordial. To the company’s surprise and delight they discovered that the vendor’s well-described and documented procedures were not only numerous and well named and identified, but also chock-full of useful details and helpful information. As the person tasked with making up any gaps in those materials, and in customizing them to fit the company environment as closely as possible, I heaved a sigh of relief as I recognized that my own workload had dropped from outright Herculean to merely difficult and challenging.
I look forward to encountering and subduing those challenges in the weeks and months ahead, and in reporting here on how things go. For the moment, suffice it to say that surprisingly stable Windows runtime environments, including some vast Citrix server farms, have helped to make the transition process not only conceivable and technically feasible, but also seem fairly doable to those responsible for making it happen—including me!
Hello there! This is not a normal blog for me, nor will I count it as such. It’s a news update from yours truly to let you know that I’m flying off to Belgium on Satuday, January 23, and that I won’t be back until February 6, just in time for my son Gregory’s sixth birthday. I’m also out of town for the week of February 8 through12, testifying as an expert witness in a courtroom in Tyler, Texas. In the meantime, I’ll be taking time off from this blog. You may see an occasional post or two from me during this interval, but that will happen only if I find some time on my hands, or an unusually important topic about which to blog. So much for the hiatus part, which will last three weeks, starting today and lasting until February 15.
Upon my return to a more normal working schedule on February 15, I’ll be posting at half of my usual frequency (once or twice a week, instead of three times a week) until the end of May. I’m both saddened and delighted to report that this is because I’ve gotten so busy with work that I’m having to cut back a bit on my blogging activities.
Do please stay tuned, and keep your comments and questions coming. Nothing makes me happier than to be able to respond to a reader request or suggestion when it comes to choosing topics for future blogs.
I’m sitting here at Gate 78 in the Pittsburgh airport. It’s 4:40 AM, and I’m waiting for 5:15 to roll around so I can board a flight to Atlanta, and thence on home to Austin. In about 5.5 hours I should be climbing into my car, to drive another 35 miles to Round Rock and home. Especially while traveling, keeping track of time is important, particularly when trying to make connections, keep appointments, and catch planes.
That’s why I experienced some frustration in my hotel room last night when I ran the Windows Internet Time time synch in the Date and Time item in control panel. At first one, then another, and finally, all of the time servers iisted in the Internet Time Settings window came up with the uninformative error message “An error occurred while Windows was synchronizing with time.windows.com” (or whatever other servers I tried at NIST, bldroc.gov, and so forth).
Usually the time synch messages are a little more informative than that, and will add tidbits of information like “Unable to resolve peer” or “timeserver took too long to respond.” Thus, I found myself doubly stumped: I wasn’t able to communicate with any time servers, and I had no additional error info to help me figure out why. Fortunately, I did have a working Internet connection, and with a little digging I came across a utility called Atomic Clock Sync V3.0.
Not only was it able to synch with its own parent time server, but it also offered a handy-dandy repair service for my apparently failed local time service. Open this tab in the program and you encounter the steps depicted in this screenshot:
Anybody familiar with Windows services will recognize that these steps represent what’s required to halt a hung or failed service, unregister it from the services manager, and then reverse that process by re-registering it and finally starting it up again. Proof that it worked occured when I completed the final step and indeed found myself once again able to synchronize with whatever time server I chose in the Date and Time widget’s Internet Time Settings window.
This handy widget has now taken up residence in my toolbox. If you ever find yourself facing a Windows machine that can’t complete a time sync, you’ll want to add it to your toolbox, too.
I teach online courses for HP and other vendors, and really enjoy that work. I often learn as much or more from the students as I feel like they’re learning from me. Case in point: in one of my Windows classes, a student asked me if there was any graphical utility like the old winipcfg utility that came with Win95, Win98, Win ME (and another student claimed even Windows 2000, but I didn’t remember this being available). So I went off to check and sure enough there’s a program called Wntipcfg.exe that was available for Windows 2000 and that even worked on XP that supported the same graphical abilities to manage IP protocol stuff, DHCP leases, and so forth, that Winipcfg.exe did for the older Win9x versions. The trouble is, this old tool won’t work (I tried, no go) with Vista or Windows 7, which have experienced enough TCP/IP internals changes in their makeup to make that program fail.
I went poking around to see what I could find by way of replacement, and unearthed this little gem: it’s called Win IP Config, and it’s freeware created by independent programmer Peter Kostov. Here’s a screenshot that shows what it can tell you about your network adapters (this one shows the info for my current hotel room Wi-Fi connection, including a Class A private IP address with a Class C subnet mask! It also accurately indicates that my Bluetooth and GbE interfaces are currently not in use):
You can also use it for netstat info, to create and manage secondary IP address assignments, handle DHCP leases, and manage static IP routes. My only beef is that in an increasingly IPv6 world, this tool remains IPv4 only. But maybe Peter will stumble across this blog, and starting plugging away at what must surely be a nice enhancement to an already excellent tool. Here’s hoping!
I’ve been an online instructor for HP at their online Learning Center for over five years. There, the company offers free, short courses on a whole range of computing topics, including numerous items focused on Windows 7 (the following snippet is cut from the all courses listing there).
Of the items listed, I’m currently teaching the Windows 7 tune-up and migrating from XP to Win7 courses, with a very active bunch on the former, and a reasonably active bunch on the latter.
As you might imagine, the topic of 64-bit computing is one that comes up frequently in both venues. In answering student questions and concerns, and in researching the state of the current marketplace, I’m observing that except for lower end notebook, netbook, and desktop PCs (all-in-ones and under-$500 offerings) it appears to me that the bulk of commercial products come with 64-bit Windows 7 pre-installed. Any machine that can accommodate 4 or more GB of RAM is far more likely to ship with 64-bit Windows 7 Home Premium or Professional by default these days, and vendors like Dell, HP, Acer, Asus, Lenovo, and others are all touting their support for 64-bit Windows 7 operating systems.
When it comes to upgrading an existing 32-bit installation (Vista or XP, usually) to 64-bit Windows 7, a few important observations are in order. First, most experts recommend (and I concur, based on installing dozens of 32- and 64-bit Windows 7 systems) that you plan to perform a clean install of 64-bit Windows 7 versions, and to re-install Windows applications on the new platform. Even though products like Laplink’s PC Mover can take preferences, settings and even some applications from 32-bit XP or Vista to 64-bit Windows, and Windows Easy Transfer can do likewise with setting and preferences, you’re often better off starting from a clean slate (and registry) when making such a move.
Certainly, you’ll want to boot from a Win7 64-bit ISO and run Upgrade Advisor from a 64-bit perspective to see how target hardware fares in that analysis, too: 32-bit drivers remain more forgiving than 64-bit ones (all of the latter *MUST* be signed to work with Win7 64-bit editions) but that can also lead to trouble and/or ongoing instability issues.
I’ve learned to look for rock-solid hardware configurations with workable drivers for all components. For 64-bit Windows 7, this often appears to produce more stable and reliable systems. After fighting with Vista for over two years, that comes as a real relief! My HP students and the various forums I haunt to keep up with the current state of the art, all also appear to validate this perspective. Perhaps 64-bit Win7 can also work for you?