Tag: Windows 2008 server

How to find system up-time on Windows 7, 8 & 2008 Server

If you leave your computer on for extended periods of time, it’s usually a good idea to perform a reboot now and then. Furthermore, if you’re managing multiple computers, it’s difficult to remember when each received a reboot. That’s why Windows keeps track of your total up-time and the last time your computer booted for you. Here’s how to access those pieces of information:

To find total up-time:

Step 1: Launch the task manager. You can do this in one of three ways:

Choice 1: Press Ctrl+Alt+Delete. On the screen that appears, select Start Task Manager.

Choice 2: Right click on the taskbar and select Start Task Manager.

Choice 3: Press CtrlL+Shift+Esc to launch the task manager directly.

Step 2: In this window, click on the Performance tab.

Task Manager-1

Task Manager

Step 3:  Your system’s up-time is displayed next to Up Time (highlighted in the above picture) in the format of Days: Hours: Minutes: Seconds

To find last boot date:

Go to Start  –> Run –> cmd


In the command prompt, run the following commands: systeminfo | find /i “Boot Time”


systeminfo | find “Time:”


systeminfo | find “System Boot Time”



Happy Computing 🙂

source: cnet, superuser, serverfault

McAfee ePO Installation errors

McAfee ePO Installation errors:

I had encountered three problems when installing McAfee ePO 4.5, 4.6 & 4.6.6 on Windows 2008 server standard edition R2.

Problem 1: SQL2005 backward compatibility:
McAfee ePO comes with SQL 2005 express, however you will encounter a problem of unable to install the SQL 2005 backward compatibility on Windows 2008 server R2 standard edition. You have to install SQL 2008 otherwise ePO installation cannot be preceded.

Problem 2: 8.3 naming convention was disabled:

8.3 naming error

You need to modify the registry to enable the 8.3 convention. 8.3 naming is needed for the tomcat service.

computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation from 2 to 0


Another method which is easier – is to use fsutil.exe.


NOTE:  While installing McAfee ePO 5.0, it won’t throw 8.3 naming convention error.

Problem 3: Setup is unable to access UDP port 1434:

This problem will arise while installing all versions of McAfee ePO 4.5, 4.6. 4.6.6 and 5.0.

SQL error

To resolve above error, we have to start SQL server browser service. By default SQL server browser is disabled. SQL Server Network Configuration protocols TCP/IP to be enabled, this protocol also by default disabled.

Go to Start -> All programs -> MS SQL Server 2008R2 ->Configuration Tools ->click on Configuration Manager (for details see the image given below)

SQL server config Manager

SQL sever config Manager 2

SQL sever config Manager 3

Once  changes done we have to restart the SQL server service (see the below image)

SQL sever config Manager 4

That’s it, further click Next… Next finish the installation.

Happy computing….

From here forward, McAfee will be known as Intel Security.


Source: Microsoft, cyruslab, McAfee, McAfee community



UEFI: The acronym stands for Unified Extensible Firmware Interface and is designed to be more flexible than its venerable predecessor.

Wave goodbye to BIOS, say hello to UEFI, a new technology that will drastically reduce start-up times.

The next generation of home computers will be able to boot up in just a few seconds, as 25-year-old BIOS technology makes way for new start-up software known as UEFI.

BIOS technology, which has been used to boot up computers since 1979, was never designed to last as long as it has, and is one of the reasons modern computers take so long to get up and running.

By contrast, UEFI – which stands for Unified Extensible Firmware Interface – has been built to meet modern computing needs, and will soon be the pre-eminent technology in many new computers, enabling them to go from ‘off’ to ‘on’ in seconds.

Pronounced “bye-ose,” BIOS is an acronym for basic input/output system. The BIOS is built-in software that determines what a computer can do without accessing programs from a disk. On PCs, the BIOS contains all the code required to control the keyboard, display screen, disk drives, serial communications, and a number of miscellaneous functions.

The BIOS is typically placed on a ROM chip that comes with the computer (it is often called a ROM BIOS). This ensures that the BIOS will always be available and will not be damaged by disk failures. It also makes it possible for a computer to boot itself.

 Below are the major BIOS manufacturers:

When you turn on your computer, several events occur automatically:

  1. The CPU “wakes up” (has power) and reads the x86 code in the BIOS chip.
  2. The code in the BIOS chip runs a series of tests, called the POST for Power On Self-Test, to make sure the system devices are working correctly. In general, the BIOS:
    • Initializes system hardware and chipset registers
    • Initializes power management
    • Tests RAM (Random Access Memory)
    • Enables the keyboard
    • Tests serial and parallel ports
    • Initializes floppy disk drives and hard disk drive controllers
    • Displays system summary information
  3. During POST, the BIOS compares the system configuration data obtained from POST with the system information stored on a CMOS – Complementary Metal-Oxide Semiconductor – memory chip located on the motherboard. (This CMOS chip, which is updated whenever new system components are added, contains the latest information about system components.)
        4. After the POST tasks are completed, the BIOS looks for the boot program responsible for loading the operating                         system.  Usually, the BIOS looks on the floppy disk drive A: followed by drive C:
        5. After being loaded into memory, the boot program then loads the system configuration information (contained in                the registry in a Windows environment) and device drivers.
       6. Finally, the operating system is loaded, and, if this is a Windows environment, the programs in the Start Up folder                  are executed.

            The BIOS has two fundamental weaknesses. Firstly, it is based on 16-bit assembly code and cannot directly address          the latest 64-bit hardware, and secondly, there are no set standards for specifications, so manufacturers come up with            their own versions.

The participants of the UEFI Forum wanted to set this straight. From the outset, each process has been precisely defined. Thus, the boot process or platform initialization (PI) is clearly described in phases. Immediately after powering up the PC, the Pre-EFI Initialization (PEI) is executed, which initializes the CPU, memory and chipset. This is then followed by the Driver Execution Environment (DXE). At this point, the rest of the hardware is initialized. This process saves the time required for booting because UEFI can integrate various drivers that need not be reloaded during booting. Thanks to these drivers, the user already has access to network card, including features such as network booting and remote assistance at the early stage of the boot process. With the graphics processor enabled, a fancy user interface is also presented.

However, biggest time-saving feature of UEFI is the fact that not all the installed hard drives will be scanned for the boot loader, since the boot drive is set during the installation of the operating system in the UEFI. The default boot loader is run without consuming much time searching the drives.

The faster boot time is not the only advantage of UEFI; applications can be stored on virtually any non-volatile storage device installed on the PC. For example, programs and diagnostic tools such as antivirus or system management tools can be run from an EFI partition on the hard drive. This feature will be very useful to original equipment manufacturers (OEM), who can distribute systems with extra functions in addition to the standard EFI firmware stored on the motherboard’s ROM.

UEFI fully supports 3 TB hard drives

The classic BIOS can access only up to 232 sectors of 512 bytes in size, which  translates to a total of 2 TB. So the upcoming 3 TB variants of Western Digital Caviar Green and Seagate Barracuda XT won’t be fully compatible with the current BIOS. Seagate uses larger sectors to make the full capacity usable on Windows, but the BIOS cannot boot from this drive.

UEFI, on the other hand, works with GUID partition table (GPT) with 64-bit long addresses and can handle up to 264 sectors that address up to 9 Zettabyte (1 zettabyte equals 1 billion terabytes).

The GUID Partition Table (GPT) was introduced as part of the Unified Extensible Firmware Interface (UEFI) initiative. GPT provides a more flexible mechanism for partitioning disks than the older Master Boot Record (MBR) partitioning scheme that was common to PCs.

A partition is a contiguous space of storage on a physical or logical disk that functions as if it were a physically separate disk. Partitions are visible to the system firmware and the installed operating systems. Access to a partition is controlled by the system firmware before the system boots the operating system, and then by the operating system after it is started.

MBR disks support only four partition table entries. If more partitions are wanted, a secondary structure known as an extended partition is necessary. Extended partitions can then be subdivided into one or more logical disks.

GPT disks can grow to a very large size. The number of partitions on a GPT disk is not constrained by temporary schemes such as container partitions as defined by the MBR Extended Boot Record (EBR).

The GPT disk partition format is well defined and fully self-identifying. Data critical to platform operation is located in partitions and not in unpartitioned or “hidden” sectors. GPT disks use primary and backup partition tables for redundancy and CRC32 fields for improved partition data structure integrity. The GPT partition format uses version number and size fields for future expansion. Each GPT partition has a unique identification GUID and a partition content type, so no coordination is necessary to prevent partition identifier collision. Each GPT partition has a 36-character Unicode name. This means that any software can present a human-readable name for the partition without any additional understanding of the partition.

Below given Windows OS supports GPT:

  • Windows 7
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Vista
  • Windows Server 2003 SP1
  • Windows Server 2003 (64-bit)
  • Windows XP x64 edition
Source: wikipedia, chip, MSDN

How to Remotely Enable Remote Desktop (Terminal Services or RDP) via Registry in Windows 2000/XP/2000/Vista/2008

Remote Desktop or RDP service is a free yet useful tool to remotely log on to remote computer and gain full access and privileges as if user is in front of local console. Remote Desktop is also known as Terminal Services. It’s useful if the server, or PC, is located miles away in remote location and frequent trips to the site to troubleshoot, configure or manage the system is not a viable option.

Although most versions of Windows operating system such as Windows 2000, 2003, 2008, XP and Vista do come packaged with Remote Desktop, it’s disabled by default. Turning on and enabling the Remote Desktop via local console is easy, where Microsoft provides similar GUI (graphical user interface) in all editions of Windows.

However, if an off-site server needs to be accessed via Remote Desktop Connection (RDC) client immediately, when the Remote Desktop is not enabled on the server, then it will be a headache. Luckily it’s possible to remotely enable and turn on the Remote Desktop service on a remote PC or server by remotely editing its registry.

To remotely enable Remote Desktop on another computer, follow these steps:

  1. Login to theworkstationwith administrator credentials.
  2. Run Registry Editor (regedit).
  3. Click on File menu.
  4. Select the Connect Network Registry in the pull down menu (see Figure 1).
Figure 1

5.    A “Select Computer” dialog search box is opened. Type the host name of the remote computer in the text box, or browse Active Directory to locate the remote server, or click on “Advanced” button to search for the remote computer (see Figure 2).

Figure 2

6.   Click OK after the remote computer is selected. A node for the remote computer network registry will be displayed in the Registry Editor with HKEY_LOCAL_MACHINE (HKLM) and HKEY_USERS (HKU) hives (see Figure 3).

Figure 3

7.   Navigate to the following registry key for the remote computer:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server

8.   In the right pane, locate a REG_DWORD value named fDenyTSConnection. Double-click on fDenyTSConnection and change the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled) (see Figure 4 & Figure 5)

Figure 4
Figure 5

9.   Reboot the remote machine by issuing the following command in Command Prompt:

shutdown -m \\hostname -r

10 .  Replace host name with the actual computer name of the remote host.

Once host pc/server is restarted, you can connect through RDC.

Source: My digital life