You may be wondering why you would bother upgrading your existing Windows XP and Vista machines to Windows 7, when Windows 8 has just been released.
Whether you are a home user or a large company there are great benefits to be had from upgrading and using your new Windows 7 PC as a stepping stone to Microsoft’s latest and greatest.
Windows XP recently celebrated its 10th birthday, a major achievement for it to keep such a stronghold but also a major issue when it becomes time to change to something new. The are always scare stories when Microsoft releases a new OS. The fact of the matter is, change often creates such fear-mongering when really its an opportunity waiting to be taken advantage of.
Businesses stayed away from Windows 7 for 2 major reasons
- Windows Vista had a terrible launch, fraught with bad reviews and needing an extra expense of upgrading hardware
- Due to people sticking with XP, business software wasn’t upgraded and smaller bespoke software would cost a fortune to redevelop for a new OS
Nowadays, this isn’t as much of an issue. Windows 7 runs easily on hardware over 4 years old and really flies on the latest kit. All major applications have been updated or can be delivered via modern methods like application virtualisation or by using tools like Microsoft’s free application compatibility toolkit or XP Mode. OS deployment technologies have moved on too, meaning you can upgrade people from XP to 7 in a couple of hours.
Windows Update (a.k.a. Microsoft Update) is normally pretty reliable in terms of keeping your computer up to date and secure. Unfortunately, there are times when an update crashes your PC (usually due to a conflicting OEM driver) or the update process just stops working. Since Windows Vista, Microsoft moved away from using the update.microsoft.com website and now has a dedicated app in the Control Panel. However, the underlying technologies are still the same. Even if you have the Windows Software Update Services (WSUS) server, controlling 100s or 1000s of computers in a corporate network, you are still going to come across the same kind of problems. You would hope that WSUS had some easy troubleshooting/rollback tools built in but unfortunately that is not the case.
I thought it would be a good idea to gather all the various methods and tools I use when troubleshooting Windows/Microsoft Update to help both Home and Enterprise users alike
Each Service that runs in Windows features a Recovery tab in the Services.msc management console. Normally I only ever set this up to restart the service after 5 minutes in case something had conflicted with it’s initial start-up attempt. However, we recently had a problem with an IBM service that caused our Windows 2003 R2 x64 Server to reboot if it crashed. I thought it would be very handy if we could get an email sent to the IT department if the service was failing. I had dabbled with using BLAT in the past but seeing as all of our servers already have PowerShell installed I thought that would be a more efficient option.
I recently had an issue with the latest version of Firefox (v3.6.15). Normally, when we install Firefox on our network, we have to change the proxy settings from the default “No Proxy” to “Auto-detect proxy settings for this network”. This doesn’t normally cause much of an issue as we only use Firefox on a few select machines and can be changed by the individual user. However, it seems the default install behaviour has slightly changed to add a new option that seems to muddy the water. There is now a “Use system proxy settings” option (similar to Google’s Chrome) that seems to be selected by default for new users. Although this may seem to make sense, on our network this causes terribly slow page load times, e.g. 10 minutes to load google.co.uk. Luckily I found a way to set the “Auto-detect” option for all users.
WARNING: This seems to have changed again since Firefox 4 was released. If anyone knows how to change it please add a comment.
Just a quick article here for a late Friday afternoon article.
If you managed Microsoft Windows Active Directory based domains you should be very familiar with the management console Active Directory Users and Computers (ADUC). When you have a sprawling OU design it can be difficult to find the user, computer or group that needs your attention. I set up a few saved queries to give me an easy to read list view of certain object types. If you can’t figure out how to create a new saved query then you may be in the wrong job but the is a comprehensive guide over at the Petri IT Knowledgebase. The 3 I use most often are set up as follows
- All Devices
- A simple query where just the computer object must have a value to display
- All Users
- Same as above, just make sure you are focussing on Users not Computers
- Locked accounts
- My most useful time saver. This one is only slightly more tricky as you need to enter a custom search string. Credit goes to an article on WinodwsNetworking.com for this one. By using the string below, when somebody calls to say they have been locked out, I can quickly bring up this saved query and unlock them in a matter of seconds
You can really go to town on these queries and there is a great list already created for you, back over on the Petri IT Knowledgebase
Sometimes you have a day when you think, “Why did I ever get into IT?”. Just when everything seems to be running smoothly an unexpected “blip” happens that seems to have no logical explanation. Then you remember that you sadistically enjoy solving these ambiguous problems and you start to dig.
I had such a problem this morning when I get an email from our overseas office telling me that they can’t log in. No problem, I thought, just a simple password reset and all should be fine. I fired up remote desktop to get to the Domain Controller but it wouldn’t let me log in under my admin account. Suddenly my server-spider-sense started to tingle. I knew this wasn’t going to be a quick fix. Oh, and I should say the DC is a virtual machine hosted in Microsoft’s Hyper-V (2008 R2 edition).
read more after the jump