Archive

Posts Tagged ‘windows’

Microsoft Windows 7 sneak highlights

November 16th, 2008 Dave W No comments

Microsoft are releasing more snippets of information about the forthcoming Window 7 edition. Here are a few of the promised highlights that relate to IT professionals:

Manageability

  • Windows 7 will extend the reach of what Group Policy can manage, and how settings are applied to specific users or computers, including non-GP aware components.
  • Windows 7 will introduce DirectAccess, a capability that allows IT to manage and update internet-connected remote PCs, even when they are off the corporate network, while giving mobile users seamless secure connectivity while on the road without having to open a VPN connection.
  • The new Powershell v2 and its graphical editor will help automate repetitive tasks with minimal scripting expertise required.

Security and Compliance

  • Windows 7 will provide customisable User Account Control (UAC) that allows IT to “tune” the UAC feature based on their environment.
  • For data protection, Windows 7 introduces BitLocker To Go, extending encryption to removable drives. This feature gives greater control over information leaving the corporation, as well as protecting lost or stolen USB drives.
  • Windows 7 will also allow greater control of access to specific applications by specific users

Deployment

In Windows 7, system image creation and deployment is enhanced with advances such as Dynamic Driver provisioning, the Deployment Image Service and Management tool, Multicast Multiple Stream Transfer, and improvements to user state migration. 
 

Vista Rollout – why it was bumpy

September 11th, 2008 Dave W No comments

An interesting post on MaximumPC sheds some light on the reasons why the Microsoft Vista rollout process was flawed. It includes some benchmarks testing between XP, Vista and Vista SP1, plus some feedback from Microsoft staff giving an insight into how the problems arose and what’s being done.

Of course, it basically boils down to an underdone release, made too early with inadequate co-operation between Microsoft and driver manufacturers. The article lists 7 major areas where the release really failed: 

Instability

At launch, Vista was much less stable than XP, and the problems weren’t limited to high-end hardware - users with low-end & standard setups also reported instability. Considering that improved stability was one of the biggest promises Microsoft made for Vista, users were understandably upset.

Incompatibility

If a desktop application didn’t follow Vista’s rules for behavior, Vista wouldn’t let it run. The program would fail to load, crash on use, or eat the user’s data, depending on the development infraction. This even affected such mainsrteam programs as Acrobat Reader, iTunes, Trillian, and dozens of others.

Hardware incompatibilities could be just as challenging, and Vista also shipped without support from major VPN manufacturers, including Cisco.

The sheer number and range of compatibility problems meant that every user would be affected in some way.

Performance

New OS releases can suffer from performance issues – but Vista showed dramatic degradation in performance on release. This poor performance affected even the most common of tasks.

User Account Control

Vista brought  improvements in the overall security of Windows, but one of the mechanisms that helps enable that security comes at a high cost – it’s incredibly annoying.

User Account Control, or UAC. Even if you don’t know what it’s called, if you’ve used Vista, you’ve used UAC. It prompts you whenever an app tries to write to an area of your hard disk or registry that Windows finds suspicious. This seems like a good thing but UAC prompts every time the installer does something suspicious. A problem compounded by the fact that each prompt looks and behaves differently, even though they’re all asking for basically the same thing.

To make matters worse, none of the UAC prompts tell users what the application is trying to do. When you click that Allow button, you still don’t know what it is you’re agreeing to.

Activation

Activation was introduced with Windows XP, and Vista activation includes the Windows Genuine Advantage software, which periodically checks in with Microsoft to ensure that the copy of Windows you’ve already activated remains genuine. WGA isn’t foolproof though, and it can be easily confused by something like a BIOS reset.

Version Overload

In the good old days, there were two distinct versions of Windows: one for home users and one for corporate users. For home, you bought Windows 98; IT departments bought Windows NT. With Windows XP, this trend continued, despite the fact that both the home and enterprise versions used the same core.

With Vista, Microsoft added three more versions of Windows, removing crucial features from the low-end release and forcing power users who want access to both work-related and enthusiast features to shell out for the $400 Ultimate edition.  The upgrade path from XP was also inflexible and expensive.

‘One More Thing’

To put it bluntly – Vista didn’t come with any ‘killer’ apps or new features.
 

The full article can be read  here

Common BSOD messages and causes

August 21st, 2008 Dave W No comments

The infamous Microsoft “Blue Screen Of Death”, or BSOD, can of course have many causes, some of which can be fixed up with a reboot. Other BSOD errors may signify a more serious issue related to Drivers, memory or other factors.

Listed below are a few of the most common Error messages that accompany a BSOD, together with explanations of what they may mean.

The error messages take the form of an 8-character hexidecimal code (the last eight characters in the ‘STOP’ message code).

 
STOP: 0×0000000A
IRQL_NOT_LESS_OR_EQUAL

Indicates that a kernel-mode process or driver attempted to access a memory location it did not have permission to access, or a memory location that exists at a kernel interrupt request level (IRQL) that was too high (a kernel-mode process can only access other processes that have an IRQL that’s equal to or lower than its own).

 
STOP: 0×0000001E
KMODE_EXCEPTION_NOT_HANDLED
The Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause this error can be either software or hardware related and result from invalid memory and access violations, which are intercepted by the Windows default error handler if error-handling routines are not present in the code  itself.

 
STOP: 0×00000024
NTFS_FILE_SYSTEM

Indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0×00000023, exists for the file allocation table [FAT16 or FAT32)] file systems).

 
STOP: 0×00000050
PAGE_FAULT_IN_NONPAGED_AREA
The requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software may cause this error.

 
STOP: 0×0000007B
INACCESSIBLE_BOOT_DEVICE

Windows XP has lost access to the system partition or boot volume during the startup process. Incorrect device drivers typically cause this error although it can also indicate a possible virus infection.

 
STOP: 0×0000007F
UNEXPECTED_KERNEL_MODE_TRAP

A hardware problem e.g. resulting from mismatched or defective memory, a malfunctioning CPU, or a fan failure that’s causing overheating.

 
STOP: 0×0000009F
DRIVER_POWER_STATE_FAILURE

Indicates that a driver is in an inconsistent or invalid power state. This error typically occurs during events that involve power state transitions, such as shutting down or moving in or out of standby or hibernate mode.

 
STOP: 0×000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access pageable memory using a kernel process IRQL that was too high. Typical cause is a bad device driver (one that uses improper addresses) although it can also be caused by faulty or mismatched RAM or a damaged pagefile.

 
STOP: 0×000000EA
THREAD_STUCK_IN_DEVICE_DRIVER

A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might point to a hardware problem with the video adapter or a faulty video driver.

 
STOP: 0xC0000218
UNKNOWN_HARD_ERROR

A required registry hive file could not be loaded. The file may be corrupt or missing. The registry file may have been corrupted due to hard disk corruption or some other hardware problem. A driver may have corrupted the registry data while loading into memory or the memory where the registry is loading may have a parity error.

 
STOP: 0xC0000221
STATUS_IMAGE_CHECKSUM_MISMATCH

Driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this message to appear.

 

Vista Security exploit – without the hype

August 18th, 2008 Dave W No comments

There’s been some wild and panicky stuff in some of the Tech press lately about a potential exploit that could bypass Vista’s security model. It all sounds pretty drastic but please bear in mind that most reports have been pretty sensationalist about it.

A ZDNet blog post contains a bit more ‘measured’ information about it along with responses from one of the guys who reported the exploit.

 

Microsoft officially ends sales of XP

June 30th, 2008 Dave W No comments

Microsoft is proceeding with plans to stop selling the Windows XP operating system to retailers and major computer as from June 30th.

Once major manufacturers such as Dell and HP have cleared their stocks of machines loaded with XP, then new machines will only be issued with Vista, and anyone wishing to revert to XP will have to buy Vista Ultimate or Vista Business and then legally “downgrade” to XP.

Smaller PC makers will be allowed to buys XP for resale through til January 2009. Cut down versions of XP will also remain available for use on machines such as the Asus Eee PC.

The decision comes despite vociferous protests from large numbers of people unhappy with Vista and amid calls for XP to be kept on-line until the release of the next Windows version 7, pencilled in for sometime in 2009.

Last week, Microsoft said it would provide full technical support for Windows XP through 2009, and limited support through 2014.