My IT Blog

You can install the virtual SCSI controller driver during the installation of the guest operating system by performing the following steps: Description and screenshots where made while installing Windows Server 2008 on Virtual Server 2005 R2 SP1, however the same instructions apply to the installation of Windows Vista. For Windows 2000/2003/XP you will need to press the F6 key during the text phase of the installation process, then press “S” to specify additional drivers, and then provide the driver floppy image. 1. Begin the installation by inserting the appropriate Windows Server 2008 installation media into your DVD drive. 2. Continue with the installation process, until you reach the point where you’re prompted for the location of the system partition. Click on the Load Driver link. 3. Now you need to load the driver files as a virtual floppy image. The image’s name is “SCSI Shunt Driver.vfd”, and it is located in the C:\Program Files\Microsoft Virtual Server\Virtual Ma

tkrnlpa.exe is a process that runs on Windows NT, Windows XP, and the AT&T Assistant. It runs the kernel and other essential components of these operating systems. A kernel is a section of a partition that maintains an operating system’s most basic functions. By running the kernel and similar components, Ntkrnlpa.exe can run many programming-based tools that the user is not even aware of. Because of this, Ntkrnlpa.exe is a critical system process and should not be removed. The file itself can be found in the primary hard drive’s System32 and Windows folders. How Ntkrnlpa.exe Works Ntkrnlpa.exe runs kernel-based system services in order to perform a variety of background tasks. It contains several individual programs that work together to support the kernel of the Windows NT and XP operating systems. Ntkrnlpa.exe includes the Memory Manager, the Scheduler, the Security Reference Monitor, the Cache Manager, the Executive, and the Kernel itself. By running all of these differe

Ntoskrnl.exe (Windows boot up kernel) is a vital component utilized in the boot process for NT based Microsoft operating systems. It is also responsible for a host of system services such as process and memory management, security management, object management, hardware virtualization and so on. It holds several sub systems: Cache Manager, I/O Manager, Configuration Manager, Local Procedure Call, Memory Manager, Process Structure,Object Manager and Security Reference Monitor. Collectively, they form part of Executive services and System Services. As a result of such critical responsibilities, ntoskrnl.exe is a fundamental constituent of the Windows operating system. Ntoskrnl.exe in the Kernel mode In NT based Windows operating systems, ntoskrnl.exe is part of the Kernel mode. The kernel mode has complete access to the hardware and software components of the system. It acts as an intermediary between user mode services and applications and system critical modules. User mode service

Ntoskrnl.exe (Windows boot up kernel) is a vital component utilized in the boot process for NT based Microsoft operating systems. It is also responsible for a host of system services such as process and memory management, security management, object management, hardware virtualization and so on. It holds several sub systems: Cache Manager, I/O Manager, Configuration Manager, Local Procedure Call, Memory Manager, Process Structure, Object Manager and Security Reference Monitor. Collectively, they form part of Executive services and System Services. As a result of such critical responsibilities, ntoskrnl.exe is a fundamental constituent of the Windows operating system. NTOSKRNL.EXE is missing or corrupt The NTOSKRNL.EXE is missing or corrupt error message is usually encountered during the boot process of NT based Windows operating systems. It can also be classified as a blue screen error, which is a colloquial term coined by users to describe error screens displayed by Windows. Thes

NTLDR stands for New Technology Loader, and it is a program that is usually loaded from the hard drive boot sector. It is used to display the Microsoft Windows NT startup menu, and it helps load Microsoft Windows NT. "NTLDR is missing" is an error that prevents Windows from starting up, and a number of factors can cause this error. The procedure to fix this error depends on its cause. Here are some of the known causes and their solutions: Computer is booting from a nonbootable source – One of the common reasons for this error is using a nonbootable floppy disk or CD-ROM to boot the computer. You can prevent this error by ensuring that no diskette is in the computer unless you want the computer to boot from it. If you want the computer to boot from the diskette and you’re getting this error, then the diskette may not have all the required files. Also, you may receive this error while installing Windows XP or Windows Server 2000. This error can be prevented by ensuring tha

The BOOTMGR (Windows Boot Manager) is part of Microsoft Windows Vista, Windows Server 2008, and Windows 7. It finalizes the steps in booting the computer and loading the Operating System by looking for the active partition in which Boot Configuration Data is stored. BOOTMGR runs the “winload.exe” process in order to do this. This process is essentially the operating system boot loader that loads the operating system kernel and device drivers that are in the boot-class.Small changes can easily corrupt the BOOTMGR configuration on Vista, Server 2008, and Windows 7. When this occurs an error from the Boot Manager appears during the machine’s startup sequence. The message displayed is “BOOTMGR is missing, Ctrl+Alt+Delete to restart” along with a blinking cursor. The problem with the simple instructions to restart the computer with Ctrl+Alt+Delete is that it will not fix the problem. It simply makes the computer reboot and go through the boot sequence until it meets the BOOTMGR requiremen

The Boot Manager (BOOTMGR) is the bootloader of the Windows 7, Windows Vista, and Windows Server 2008 operating systems (OS). The computer's BIOS loads the program upon startup and will start the bootloader for the OS and other required programs. The NTLDRpreceded it on older versions of the Windows OS. What Problems Can Occur with BOOTMGR? Unfortunately, the BOOTMGR may display a number of errors due to varying circumstances. Some of the common BOOTMGR errors are a result of operating system upgrade errors, corrupt hard drive sectors, a damaged IDE cable, and an outdated BIOS. Another common cause of BOOTMGR errors is a computer trying to startup from a flash/disk drive that is not configured to be a boot disk. How to Fix BOOTMGR Errors Step 1 – Check the CD/DVD drive for a disk, as it could be triggering the error when the computer starts up. If a disk is found, remove it. Step 2 – If there was no disk in the drive, insert the Windows repair CD/DVD into the computer'

Auditing Overview Auditing enables you to determine which activities are occurring on your system and allows you to track access to objects, files and folders; and modifications made to the objects, files and folders. Auditing also enables you to collect information associated with resource access and usage on your system by allowing you to audit system logon, file access, and object access. Security auditing events are written to the Security log of the system and can be accessed from the Event Viewer tool. Because event logs grow over time and typically consume valuable disk space, you have to regularly delete event log entries contained in the Security log. The types of events which you should audit are listed below: Computer logons and computer logoffs Access to objects, and files and folders System events. Performance of user and computer account management activities. To prevent auditing from consuming valuable system resources, you should only audit events which are necessa