January 2010 ~ bench3

The Ant And The Grasshopper Moral Story | Importance Of Planning

Labels: Education , Management , Moral Story

Careful preparation and planning is a key step to any endeavor. When we were schooling, our teachers prepared for us a “study plan”. The college football tournament was not won by kicking the ball around, but by adhering to a “game plan”. When we had enough funds to build a house, we prepared through our architects a “building plan”. For our business to tick, we put in place “business plan”, “sales plan”, “marketing plan” and so on.

There is nothing like being prepared for every possible situation and the earlier we do it, the more assured we are of our success.

Story: The Ant and the Grasshopper

In a field one summer's day a Grasshopper was hopping about, chirping and singing to its heart's content. An Ant passed by, bearing along with great toil an ear of corn he was taking to the nest.

"Why not come and chat with me," said the Grasshopper, "instead of toiling and moiling in that way?"

"I am helping to lay up food for the winter," said the Ant, "and recommend you to do the same."

"Why bother about winter?" said the Grasshopper; we have got plenty of food at present." But the Ant went on its way and continued its toil. When the winter came the Grasshopper had no food and found itself dying of hunger, while it saw the ants distributing every day corn and grain from the stores they had collected in the summer. Then the Grasshopper knew: It is best to prepare for the days of necessity.

Moral:

It is best to prepare for the days of necessity.

Kidding me:

This is an edited version of the rather hilarious parody written by Jim Quinn:-

When winter comes, the shivering Grasshopper calls a press conference and demands to know why the Ant should be allowed to be warm and well fed while others are cold and starving. CBS, NBC, and ABC show up and provide pictures of the shivering Grasshopper next to a film of the Ant in his comfortable home with a table filled with food.

America is stunned by the sharp contrast. How can it be that, in a country of such wealth, this poor Grasshopper is allowed to suffer so?

Kermit the Frog appears on Oprah with the Grasshopper, and everybody cries when he sings It is Not Easy Being Green. Bill and Hillary Clinton make a special guest appearance on

the CBS Evening News and tell a concerned Dan Rather that they will do everything they can for the Grasshopper who has been denied the prosperity he deserves by those who benefited unfairly. Richard Gephardt exclaims in an interview with Peter Jennings that the Ant has gotten rich off the "back of the Grasshopper," and calls for an immediate tax hike on the Ant to make him pay his "fair share."

Hillary gets her old law firm to represent the Grasshopper in a defamation suit against the Ant. The Ant loses the case.

The story ends as we see the Grasshopper finishing up the last bits of the ant's food while he lives in a government house. The Ant has disappeared in the snow. And on the TV, which the Grasshopper bought by selling most of the Ant's food, they are showing Bill Clinton standing before a wildly applauding audience announcing a new era of "Fairness" has

dawned in America.

Lessons in life:

“If you fail to plan, you plan to fail”. This is one of the fundamental principles of good management.

Any company should always have short and long-term growth plans. At a strategic level, a business plan will enable the company to identify business objectives and opportunities.

At the operational level, planning leads to smooth and successful daily operational activities. For family businesses, succession planning is vital as we have seen examples of businesses folding up after the loss of their key leader. Plans should also not be cast in stone. They should be reviewed constantly, in line with the changing market conditions of the particular industry.

On a separate note, the fable does allude to the social dichotomy between the rich and the poor. There are the people who make a fortune through sheer hard work, and there are the loafers who blame everyone except themselves for the poverty they face. The strange thing, however, is that these loafers survive.

In certain welfare states, they are so well provided for by the government (with social insurance for old age, illness, and unemployment needs) that they are better off not working. Tax the rich to give to the poor. While this will bridge the income gap between the two classes, if overdone, it may force the country's wealthy citizens to migrate to countries with lower tax regime.

Not only that, it gives the poor no incentive to work hard, or to upgrade their skills. While the fable did not reveal much of the fate of the Grasshopper, we know that in real life, Grasshoppers will continue to hop about merrily and enjoy the fruits of labor of the Ants. They do it either via the legitimate social framework, or the thugs' method portrayed in the animated film “A Bug's Life.” Life is never fair.

Haja is currently working in a multi-disciplinary role that combines programming including, SAP Administration, Network Management, and System Administration. He is passionate about Technology and this blog is his platform for sharing his ideas. If you like this post, Please leave a comment. And if you have any queries, mail to help @ bench3 . com

How To Add Images Or Icons To Links In The Sidebar For Blogs Hosted In Blogger

Labels: Blogging Tips , Template , Web Design

Sidebars are sometimes crowded with lots of text. There are many ways to make some of the items stand out. You can add image to each link as what you see in most blogs (refer image) to differentiate links from normal text. And you can also draw a thin line after each link. To be consistent, the color of these lines shall be the border color. Well, we will see how to do it.

Note: Since each type of template has its unique margin, padding and style settings, this guide may not apply to few templates. You can try to adapt this to your template. Preview the change, and adjust the margins and paddings. Often, a bit of experiment with these values will do the trick. If they still don't look satisfactory, do not save the template.

First, scout around for a picture that you would like to use. In this site, I have used an arrow image. You can use any photo editing software to reduce the image size to about 9px x 9px; I used Google's Photo Editing Software Picasa.

After having an image, upload it onto a free server. You can use free hosts like Google Page Creator and Google Groups. There were also a rather comprehensive list of free Image Hosts and File Hosting Services available. Check out those sites and choose one that is fast, reliable and enables hotlinking to the uploaded files. Take note of the URL of the Image file.

Go back to “Template” tab and click “Edit HTML”. Scroll to look for the following lines:-

.sidebar ul {
list-style:none;
margin:0 0 0;
padding:0 0 0;
}
.sidebar li {
margin:0;
padding:0 0 .25em 15px;
text-indent:-15px;
line-height:1.5em;
}

Replace them with this:-

.sidebar ul {
list-style:none;
margin:0 0 1.25em;
padding:0 0px;
}

.sidebar ul li {
background:url("URL OF IMAGE FILE") no-repeat 2px .25em;
margin:0;
padding:0 0 3px 16px;
margin-bottom:3px;
border-bottom:1px dotted $bordercolor;
line-height:1.4em;
}

Remember to insert the URL OF IMAGE FILE into the code.

If you don't want the line at the bottom of every item, delete the border-bottom code (shown in green) or change the value to 0px.

Preview to see if you like the layout. If it is fine with you, Save the Template.

Problem With Text overlapping In Your Blog?

Follow this trick if you find any overlapping in your blog. Find the following code in your template...

.sidebar li {
padding:0 0 .25em 15px;
text-indent:-15px;

Try removing the indent and adjusting the padding values. They vary depending on the size of your image.

Does Your Template Already Having An Link Image?

In any case, to see the icons, you can go to

#sidebar

and look for the image URL. If you want to replace the image, you can upload your new image onto a server, and then insert your new link.

How To Add A Navigation Link Bar To The Header In Blogger | Merging A Navigation Bar With Header Image In Blogger.

Labels: Blogging Tips , SEO , Web Design , Web Technology

Here we will see how to add a navigation bar to your blogger. The Navigation bar can be text links, image links, or both. Since they are navigation tools, they should be somewhere at the top of the page and easily noticeable. You may have a background image in the Header and after adding the Navigation bar, you find the Navigation bar sitting at the top or bottom of the Header.

Perhaps you want the Navigation bar somewhere in the middle of the image instead. In this article, we shall explore further customization tips on aligning the Navigation Bar and moving it to the exact position within the Header.

Header Image using Blogger feature

If you have inserted the background image into the Header using the 'Edit Header' method, and added the Navigation Bar, you will see the Header image and the Navbar as 2 separate items like this:-

Merging Of Header Image With Navigation Bar In Blogger:

This is because they are different widgets, i.e., the Header image is comprised in the Header widget whereas the Navbar is in the HTML widget. One comes after the other in the layout. To move the Navbar further up so that it is within the Header image, we can set the top and bottom margins of the Navbar widget. If you have inserted the Navbar through our tutorial, you would have remembered that we called the widget “newnavbar”. Go to Template - > Edit HTML and add another code:-

#newnavbar{
margin: -80px 0 80px 0;
}

There are four values in the margin setting. They are respectively the top margin, right margin, bottom margin and left margin. By indicating a negative top margin value, we are shifting the Navbar upwards, into the Header image. The result is the menu bar within the Header like this:-

If you want the Navbar further to the right, put a negative value to the right margin setting. Similarly, if you want to shift the Navbar to the left, indicate a negative left margin setting. Since image sizes and template styles differ, you would have to try out different margin values to find an optimum setting for your template. Preview the template to see the new layout.

Header Image by modifying stylesheet

The second way to insert the background image into the Header is the 'Modify Stylesheet' method. This is done by uploading the Header image onto a server and placing a link in the Header style:-

#header-wrapper {
background-image: url(URL of image);
}

Once you have added the Navigation Bar, you would notice that it is positioned immediately after the Blog Description, and it is within the Header image.

This seems to be what you want, as the Navbar is already a part of the Header image. However, there is still a need to fine-tune the position. For example, you can see that our picture in the center of the Header image is 'cut off'. Our image height is 400px but since the Title and Description do not take up much space, the Header image is not fully shown. If we want to show the entire Header image, we can insert a height specification into the header-wrapper definition like this:-

#header-wrapper {
background-image: url(URL of image);
height:400px;
}

Next, as we had mentioned, the menu bar is after the Description and within the Header. We want to move this downwards so that it is at the lower part of our Header image. Same as before, we insert another style definition for the “newnavbar”:-

#newnavbar{
margin: 400px 0 0 0;
}

This time, we want to shift it down, so we add a positive value to the top margin. There we have it, a full Header image, and the horizontal Navigation Bar at our desired position within the image.

Installing New Software In Windows Seven | Installation Difference Between Windows XP And Seven

Labels: Software Review , Windows 7 , Windows Vista

Compared to earlier releases of Windows, the processes of installing, configuring, and maintaining software and game programs work differently in Windows Vista and Windows 7. Primarily, this is because of changes to:

The way accounts are used
The way User Account Control (UAC) works
The removal of the Add/Remove Programs utility
The way application access tokens are used
The way applications write to the system locations

Unlike earlier releases of Windows (particularly windows XP), Windows Vista and Windows 7 has only standard user accounts and administrator accounts. When you log on to Windows Vista or Windows 7, you use one type of account or the other, removing the gray area between these two types of accounts that was previously available through the Power Users group. From Windows Vista, the Power Users group is included only for backward compatibility, and you should use it only when you need to resolve compatibility issues.

From the introduction of Windows Vista, software installation, configuration, and maintenance are processes that require elevated privileges. Because of this, only administrators can install, configure, and maintain software. Because of UAC, Windows Vista and Windows 7 is able to detect software installation. When Windows Seven or Vista detects a software-installation-related process, it prompts for permission or consent prior to allowing you to install, configure, or maintain software on your computer.

You know that the new Windows Seven and even Vista does not include an Add/Remove Programs utility. Instead, it relies completely on the software and game programs themselves to provide the necessary installation features through a related Setup or Autorun program.

Most programs created for Windows 95, Windows 98, Windows Me, Windows 2000, and Windows XP use setup.exe programs. Programs created for Windows Vista and later versions of Windows can use autorun.exe programs, particularly if those programs use current versions of Windows installers. For simplicity's sake, I'll refer to both Setup and Autorun programs as Setup programs.

Windows Seven and Vista also provides new architecture guidelines for software and game programs that fundamentally change the way software access tokens are used and the way software programs write to system locations. These changes are so far-reaching that software not specifically designed to support the new architecture guidelines is considered legacy software. This means there are two general categories of software that you can use with Windows Vista or Windows Seven:

Windows Vista-compliant applications
Legacy applications

Any software written specifically for Windows Seven or Vista's new architecture guidelines is considered a compliant application and can be certified as compliant with Microsoft. Applications certified as compliant have the Windows Vista-compliant logo or Windows Seven-compliant logo. Applications written for Windows Seven or Vista have access tokens that describe the privileges required to run and perform tasks. Windows Seven or Vista-compliant applications fall into two general categories:

Administrator user applications
Standard user applications

Administrator user applications

If an application requires elevated privileges to run and perform tasks, it is considered an administrator user application. Administrator user applications can write to system locations of the registry and filesystem.

Standard user applications

If an application does not require elevated privileges to run and perform tasks, it is considered a standard user application. Standard user applications should write only to non-system locations of the registry and filesystem.

Any application written for an earlier version of Windows is considered a legacy application. Legacy applications run as standard user applications and in a special compatibility mode that provides virtualized views of file and registry locations. When a legacy application attempts to write a system location, Windows Seven / Vista gives the application a private copy of the file or registry value. Any changes are then written to the private copy, and this private copy is in turn stored in the user's profile data. If the application attempts to read or write to this system location again, it is given the private copy from the user's profile.

New Group Policy Features In Windows 7 and Windows Server 2008 R2

Labels: GroupPolicy , Windows Server , Windows Server 2008

Windows 7 and Windows Server 2008 R2 build on the foundation of Group Policy improvements made in Windows Vista and Windows Server 2008. The key improvements to Group Policy in Windows 7 and Windows Server 2008 R2 are as follows:

New categories of policy settings Windows 7 and Windows Server 2008 R2 include new categories of Group Policy policy settings and also some additional policy settings for existing policy categories.

Default Starter GPOs Windows 7 and Windows Server 2008 R2 now include a number of default Starter GPOs that you can use to help ensure compliance with security best practices for enterprise environments. In Windows Vista and Windows Server 2008, you had to download these Starter GPOs separately before using them.

Windows PowerShell cmdlets for Group Policy In Windows 7 and Windows Server 2008 R2, you can now use Windows PowerShell to create, edit, and maintain GPOs using the new Windows PowerShell cmdlets for Group Policy available within the Windows Server 2008 R2 GPMC. This allows administrators to automate many common Understanding Group Policy in Group Policy management tasks and to perform such tasks from the command line.

Note: This feature does not work with Local Group Policy. Also, it only works with registry-based settings and not with security policies or other aspects of policy.

Enhancements to ADM Settings ADM policy settings (ADMX templates) are enhanced in Windows 7 and Windows Server 2008 R2 with an improved user interface that makes it easier to add comments to policy settings. Support for multi-string and QWORD registry value types is also now supported by ADMX templates for Windows 7.

The overall authoring experience is also improved with the new ADMX user interface as the windows are more integrated and dialog boxes are now resizable.

Enhancements to Group Policy Preferences Group Policy preferences has been enhanced in Windows 7 and Windows Server 2008 R2 with new capabilities for managing Power Plan settings in Windows Vista and later versions, creating scheduled tasks for Windows Vista and later versions, creating immediate tasks for Windows Vista and later versions that run immediately upon Group Policy refresh, and managing settings for Windows Internet Explorer 8. In addition, a new preference item called Immediate Tasks lets you create tasks.

Advanced Audit Policy Configuration Group Policy in Windows 7 and Windows Server 2008 R2 now includes more than fifty Advanced Audit Policy Configuration settings that can be used to provide detailed control over 10 different areas of audit policies, and they can be used to identify possible attacks on your network or to verify compliance with your organization’s security requirements. In Windows Vista and Windows Server 2008, these advanced audit policy categories can be managed from the command line using the Auditpol.exe utility. Starting in Windows 7 and Windows Server 2008, however, these advanced audit policy categories can be managed using Group Policy and are found under Computer Configuration\Policies\Windows Settings \Security Settings\Advanced Audit Policy Configuration.

Application Control Policies Group Policy in Windows 7 and Windows Server 2008 R2 now includes Windows AppLocker, which replaces the Software Restriction Policies feature of Windows Vista and Windows Server 2008. AppLocker is found under Computer Configuration\Policies\Windows Settings\Security Settings\Application Control Policies. AppLocker includes new capabilities and extensions that can help reduce administrative overhead and allow administrators to control how users access and use executable files, scripts, Windows Installer files (.msi and .msp files), and dynamic-link libraries (DLLs).

Name Resolution Policy Group Policy in Windows 7 and Windows Server 2008 R2 has been enhanced with support for Name Resolution Policy, which can be used to store configuration settings for Domain Name System security (DNSsec) and DirectAccess in a Name Resolution Policy Table (NRPT) on client computers. This new policy setting can be found under Computer Configuration\Policies\Windows Settings\Name Resolution Policy.

Logical Side And Physical Side Of Active Directory | The Two Sides Of Active Directory

Labels: ActiveDirectory , Windows Server , Windows Server 2008

Active Directory has both a logical side and a physical side, and each one plays a very important role. The physical side is made up of the domain controllers and physical locations where the domain controllers reside. When you promote a system to domain controller status, you will usually place that domain controller close to the user population that will use it for authentication and access.

Domain controllers need to communicate with one another to share the information they have. The logical side is a little more nebulous; as well as containing the objects that define how the resources are organized and accessed, the logical side contains objects within Active Directory that define how the domain controllers will communicate with one another. Active Directory sites and site links define which domain controllers will replicate directly with each other and which ones will have to communicate indirectly through other domain controllers.

Domains dictate the replication scope. When you create a domain, the domain partition is replicated only to domain controllers from the same domain. The domain partition is not copied to domain controllers outside of the domain. This allows you to partition your directory service and reduce the size of the database file that holds all of the forest’s objects. Forests and domains are discussed in greater detail in Chapter 3, “Active Directory Forest and Domain Design.”

Organizational units are used to organize objects for easy administration and to manage those objects easily using group policies. To have efficient administration of resources, you should design your Active Directory with administration in mind.

If you are in the process of rolling out Active Directory, be sure to develop a detailed plan for the rollout. Without a good design, Active Directory may not work efficiently for your environment. If your design does not meet the needs of your organization, you may be faced with either suffering through working with an inadequate design or rebuilding your Active Directory infrastructure from the ground up. Neither of these options will sit well with your user base or the management of the company.

How Indexing For Optimized Searches Works | Windows Active Directory

Labels: WIndows Search , Windows Server , Windows Server 2008

The directory data store can be indexed to improve the efficiency of searches. Indexing is specified as part of the schema definition of an attribute (such as Description or given- Name). When an attribute is indexed, all occurrences of that attribute will be included in the index.

Some attributes are indexed by default, and the administrator can configure additional attributes to be indexed. Multiple types of indexing are available, depending on how the attribute will be used in searches:

Basic indexing The value(s) of the attribute is indexed so that queries requesting objects with a specific value for that attribute will run quickly.
Containerized indexes Similar to basic indexing, but also indexes the objects by container. This enables a query to quickly evaluate all the child objects in a container to determine if any match the requested attribute value.
Tuple indexes Used on string attributes so that substring searches specifying that attribute will run quickly. For example, applying a tuple index to the Description attribute would allow queries such as “return all objects whose Description attribute contains the string ‘Fabrikam’ anywhere in it” to execute efficiently. Maintaining tuple indexes can consume a large amount of resources, so they should be enabled sparingly.
Subtree indexes Enables a special type of Active Directory search, known as virtual list view, to execute quickly. These are similar to containerized indexes but include not only the immediate children of the container but also all the grandchildren, great-grandchildren, and so on. Like tuple indexes, subtree indexes can be expensive to maintain.

Administrators can enable indexing on attributes that aren’t indexed by default, based on the needs of their organization. Basic and containerized indexes can be enabled using the Active Directory Schema snap-in. However, tuple and subtree indexes require you to manually set the value of the searchFlags attribute on the attributeSchema objects defining the attributes you want to index.

Step By Step Instruction On Installing Microsoft Office As Terminal Services In Windows Server

Labels: Microsoft , Office , Windows Server , Windows Server 2003

This step-by-step article describes how to install Microsoft Office 2003 or Microsoft Office XP on either of the following computers:

Microsoft Windows Server 2003-based computer with Terminal Services enabled
Microsoft Windows 2000 Server-based computer with Terminal Services enabled

Note Terminal Server installations are supported only on Enterprise versions of Office XP. However, in Office 2003 (I never tried in office 2007, but i expect this to work in that version of office also.) the Retail and Enterprise editions can be installed to a server that has Terminal Services enabled if a license exists for each user who will run any of the Office 2003 (hopefully in office 2007 also) programs. See the End User License Agreement for Office for more information.

Before you install Office to the Windows 2000 or Windows Server 2003 Terminal Services computer, the computer must be configured as follows:

Terminal Services is installed and enabled
Terminal Services is configured for application server mode for multiple terminal server clients to run Office

How to install Office on a computer that is running Windows 2000 or Windows Server 2003 with Terminal Services enabled

To install Office on a computer that is running Windows 2000 or Windows Server 2003 Server with Terminal Services enabled, follow these steps.

Note: In Windows Server 2003, the everyone user group has to have read rights at the root to successfully start Office programs. (Typically, the root is drive C.) By default, the everyone user group is not allowed to read the content of drive C.

Click Start, point to Settings, and then click Control Panel.
Double-click Add/Remove Programs, click Add New Programs, and then click CD or Floppy.
Click Next.
Click Browse.
Locate the root folder of the Office source location, click Setup.exe, and then click Open. Setup.exe is added to the command line that appears in the Open box of the Run Installation Program dialog box.
Click Finish to run Office Setup.
If requested, type your customer name and product key (CD key) information in the appropriate boxes, and then click Next. Note: The Next button is not available until you type a valid product key.
Accept the End User License Agreement, and then click Next.
Specify the location where you want to install Office, and then click Next.
On the Choose which applications for setup to install page, click Next.

If you click Choose detailed installation options for each application on the Choose which applications for setup to install page, and then click Next, the feature tree appears on the Choose installation options for all Office applications and tools page. Because Office Setup detects that you are using Terminal Services, the only installation states that are available are Not Available and Run from My Computer. By default, some features are set to Not Available. Do not change the installation states of these features to Run from My Computer, because you may experience problems with the Office programs that use these features.

Warning: By default, some features are set to Not Available to make sure that there is optimum performance in a Terminal Server environment, including the elimination of unexpected errors. Do not change the installation states of these features to Run from My Computer.

Note: If your Office source location is an administrative installation, Run from Network is also displayed as an installation state.

11. On the Begin installation page, click Install.

12. When you receive a message that the installation completed successfully, click OK,

13. click Next, and then click Finish.

Understanding Windows 7 Compatibility Issues | Using XP Mode In Windows 7 And Vista

Labels: Computer , Hardware , Microsoft , Softwares , Windows 7 , Windows Tips

Any discussion of PC compatibility, of course, encompasses two very different but related topics: hardware and software. In order for a given hardware device—a printer, graphics card, or whatever—to work correctly with Windows 7, it needs a working driver.

In many cases, drivers designed for older versions of Windows will actually work just fine in Windows 7. However, depending on the class (or type) of device, many hardware devices need a new Windows 7–specific driver to function properly on Microsoft’s latest operating system.

Software offers similar challenges. While Windows 7 is largely compatible with the 32-bit software applications that Windows users have enjoyed for over a decade, some applications— and indeed, entire application classes, such as security software—simply won’t work properly in Windows 7.

Some applications can be made to work using Windows 7’s built-in compatibility modes, as discussed below. Some can’t. Those that can’t—like legacy 16-bit software or custom software typically found in small businesses—might be able to find solace in the new XP Mode feature in Windows 7. Always remember that you can use Windows XP Mode for any software by righ clicking that application and choosing Properties And going to Compatibility. Please Refer The Screen Shots below.

A final compatibility issue that shouldn’t be overlooked is one raised by the ongoing migration to 64-bit (x64) computing. Virtually every single PC sold today does, in fact, include a 64-bit x64-compatible microprocessor, which means it is capable of running 64-bit versions of Windows 7. However, until Windows 7, virtually all copies of Windows sold were the more mainstream 32-bit versions of the system. The situation is now changing in favor of 64-bit with Windows 7.

From a functional standpoint, x64 and 32-bit versions of Windows 7 are almost identical. The biggest difference is RAM support: while 32-bit versions of Windows “support” up to 4GB of RAM, the truth is, they can’t access much more than 3.1GB or 3.2GB of RAM because of the underlying architecture of Windows.

64-bit versions of Windows 7, meanwhile, can access up to a whopping 192GB of RAM, depending on which version you get. Well, To know more about the difference between 64bit and 32bit, please refer my earlier article on Benefits Of Windows 7 64-bit Operating System

Refer: download windows 7 ultimate final english x86 and x64 dvd

Hardware Compatibility

One of the best things about Windows historically is that you could go into any electronics retailer, buy any hardware device in the store, bring it home, and know it would work. Conversely, one of the worst things about any new version of Windows is that the previous statement no longer applies. One of my friend (who, let’s face it, is old) often tells the story about the time he was wandering down the aisles of a Best Buy in Phoenix, Arizona, over a decade ago when Windows NT 4.0 first shipped, with a printed copy of the Windows NT Hardware Compatibility List (HCL) in his hand. He needed a network adapter but had to be sure he got one of the few models that worked in the then new NT 4.0 system.

Windows 7 users face a similar problem today, though there are some differences. First, there’s no HCL available anymore, at least not a public one, so you’re a bit more on your own when it comes to discovering what’s going to work. Second, Windows 7 is already far more compatible with existing hardware than NT was back in the mid 1990s. Indeed, thanks to a 3-year head start with Windows Vista—with which Windows 7 shares the same compatibility infrastructure—Microsoft claims that Windows 7 is actually far more compatible with today’s hardware than Windows XP was when it first shipped back in 2001.

Based on my extensive testing and evidence provided by Microsoft, this is clearly the case. But then, that was true with Windows Vista as well, though overblown tales of that system’s compatibility issues burned up the blogosphere during virtually its entire time in the market.

I’ve tested Windows 7 for over a year on a wide variety of systems, including several desktops (most of which use dual- and quad-core x64-compatible CPUs), Media Center PCs, notebook computers, Tablet PCs, TouchSmart PCs, netbooks, and even an aging Ultra-Mobile PC. Windows 7’s out-of-the-box (OOTB) compatibility with the built-in devices on each system we’ve tested has been stellar, even during the beta, and it only got better over time. (In this case, OOTB refers to both the drivers that actually ship on the Windows 7 DVD as well as the drivers that are automatically installed via Automatic Updating the first time you boot into your new Windows 7 desktop.)

On almost all of these systems, Windows 7 has found and installed drivers for every single device in or attached to the system. So much for all the compatibility nightmares. Myths about how the Windows Aero user interface requirements would require mass hardware upgrades also dissipated during the Vista time frame. And sure enough, by the time we got to Windows 7, we stopped seeing anything other than the Windows Aero UI on every single modern (2006 or newer) PC we’ve tested. (With the following exception: when you install Windows 7 Home Basic or Starter, you don’t gain access to Windows Aero—but this is due to limitations of the OS, not the hardware.)

As always, you could still run into hardware issues with older scanners, printers, and similar peripherals, especially if you’re coming from Windows XP. My Friend's network-attached Dell laser printer wasn’t supported by Windows 7–specific drivers at launch (though it was in Windows Vista with Service Pack 1 and newer). But because it’s really a Lexmark printer in disguise, he was able to get it up and running just fine using Lexmark drivers.

If you’re coming from Windows Vista, or are using Windows Vista-era hardware, you’re in much better shape. For the most part, everything should just work. TV-tuner hardware? Yep. Zune? Done. Apple’s iPods? They all work (even on x64 systems). Windows Media–compatible devices? Of course; they all connect seamlessly and even work with Windows 7’s Sync Center interface.

Download Windows 7: download windows 7 ultimate final english x86 and x64 dvd

Web Server Traffic Reporting With Webalizer In Linux | Running A WebServer In Linux Machine

Labels: Fedora , Linux , LinuxServer , Web Technology , WebHosting , WebServer

If you're running a Website, you're likely to be interested in the amount of traffic it receives, where it's coming from, and where it's going. The analysis of Web traffic enables developers to assess whether or not the Websites hosted on your server are being used as expected. It allows those developers to make the changes required to deal with unexpected loads, or to direct visitors towards particular Web pages of which they may not be aware.

Traffic reporting for Web pages is a two-stage process. First, there needs to be a log of each request made for each Web page; fortunately, that's exactly what Apache's /var/log/httpd/access_log log file contains. Second, the raw data in that log file needs to be turned into a useful report. This is where Webalizer, an open source Web server log analysis program, comes in handy. Webalizer periodically goes through Apache's access logs and produces an HTML report, complete with charts, so that we can quickly and easily identify any trends in site traffic.

If Webalizer is not installed, install it from the Package Management tool by selecting the Webalizer package from the Web Server package group, or by entering yum install webalizer at the command prompt.

Fedora's Webalizer package is already configured to read /var/log/httpd/access_log once daily to regenerate its reports, so there's no need to configure Webalizer. The default configuration writes its reports to the directory /var/www/usage, which can be accessed via the browser at http://localhost/usage/, as shown in Figure below.

Note that if Webalizer's cron job has not been run, nothing will be available at this address: you'll see an error message. To force Webalizer to generate reports, run webalizer from the command line as root.

The reports are very detailed, showing not only tables that indicate the "number of hits" the site has received, but graphs of changing hit counts over time, traffic statistics broken up by month, week, day, and hour, and details of which "user agents" (Web browsers) were used to access the sites.

There are many, many Web traffic analysis tools like Webalizer. You may already have experience with another and, if so, you may prefer to use that. I'd recommend Webalizer because it provides comprehensive statistics in a clearly understandable format, and requires no configuration to set up and get working.

Figure: A Webalizer report.

While Web traffic analysis reports are useful to Web application developers, they can also be useful to you, the system administrator. A traffic report can give you an idea of when site traffic typically spikes to higher levels, and which parts of your Website attract the greatest numbers of users, which will help you make decisions about network bandwidth .

For example, if you find that your server is serving a lot of images, and that, consequently, those requests are slowing down the other processes on the machine, you might think about setting up a second LAMP server purely to serve the images, thereby reducing the load on your first server. You might also decide to use traffic shaping tools to alter your network bandwidth to route more (or less) traffic to particular servers or services. This can be particularly handy if you're seeing bandwidth spikes to particular services, or at particular times.

The Myth of RAID Backups | RAID Is Not A Backup Function

Labels: Disk Backup , HardDisk , Hardware , RAID , Troubleshoot

RAID stands for Redundant Array of Inexpensive/Independent Disks. It's a set of hardware and/or software configuration(s) that grants you higher storage hardware availability (from failed disks), storage capacity, and/or gets you storage speed-nothing more. Some people are under the misconception that RAID can function as a backup for their system. This is simply not true.

RAID gets you hardware availability with respect to hardware failures (that is, it keeps things running after one of your hard drives die). Backups get you data availability with respect to time. RAID will NOT save your assets if you accidentally rm -rf /home (don't ever type that!), or if you accidentally rpm - Upgrade to the latest kernel instead of -installing it, nor will RAID help you get your data back if you get hacked, cracked, or rooted. When data is written to a RAID array, it gets written to ALL the disks. RAID will save you if one of your hard drives fails. That's all. Hardware availability with respect to, well, hardware!

Backups get you data availability for when your data fails (that is, rm - rf *, rpm - i kern*, or h4x0r3d). I've heard from many people who were baffled as to why they couldn't just recover their system from RAID. (These are likely the same unfortunate souls who thought that a firewall would protect them from the CodeRed or Nimda Internet Worms.) In short, if you want to protect your system from being down from blown drives, get RAID. If you want to protect your data and OS configuration from, well, yourself and others, get backups.

You may have heard of some newer forms of pseudo-RAID/backup-ish type technologies such as snapshots, LVM, and off line RAID-1 that do give some measure of "data availability" or backup type of functionality. But these are not very common, are beyond the scope of this chapter, and should not be confused with regular RAID-1 or RAID-5. Plus, these solutions do not get you all the security and flexibility of off-site rotated backup tapes.

What Is Media Access Control Or Burned In Address | MAC

Labels: Hardware , Networking , Troubleshoot

Just as each residence has a unique telephone number, your computer’s NIC also has a unique number. However, unlike a telephone, each NIC has a unique number built (or burned) into it at the factory; this is referred to as its burned-in address, or BIA.

This address is long enough so that trillions and trillions of addresses are possible. For convenience, the address has a compact form, represented by six hexadecimal bytes.

Some folks refer to the BIA as the MAC (media access control) address.

Hexadecimal sounds like a witch trial and a math contest rolled up into one. Really, though, it’s just a different method of counting—instead of having digits from 0–9 (decimal), you use digits 0–F (hex). Because you have more options for digits (16 rather than 10), you can express numbers more compactly. Don’t worry about it, though. All you really need to know is that a byte consists of two of these hex digits and that a MAC address is expressed using six bytes. Actually, 00-00-10-2b-5c-8d isn’t too much more tough than 1-800-555-1212, is it?

The IEEE hands out ranges of MAC addresses rather than the addresses themselves (for instance, Proteon Inc. has all numbers that start with 00-00-93). This means you can tell who made a network card by looking at the MAC address’s first three hex bytes. This is called the OUI (organizational unique identifier) and can be useful if you’re troubleshooting certain kinds of problems.

The Institute of Electronic and Electrical Engineers (or IEEE; pronounced eye triple-E) is the organization that, among other things, acts as a standards body for various electronic standards. One of the IEEE’s roles is to act as a clearinghouse for MAC addresses. Because so many network manufacturers exist, it’s really important that MAC addresses be tracked. Otherwise, two different manufacturers might accidentally make network cards with the same address, which will cause network problems if two of these network cards end up on the same network. This could happen even though there are many, many possible MAC addresses. A MAC address’s six-hex-digit format (or 48-bit address, if you want to sound geeky by talking in binary terms) turns into 281 trillion possible addresses—281,474,976,710,656 to be precise! That’s a heck of a lot of combinations. Compare this with the phone system in the United States, where only nine billion phone numbers are available.

OUI ou Non? : Knowing the OUI came in handy for me once when I was experiencing intermittent problems with a new application. The application vendor pointed the finger at one of my network card vendors, who, in turn, told me to get the “latest and greatest” drivers for its network cards to eliminate the problems I was experiencing with the application. Fortunately, I rolled out only a small set of those drivers, which turned out not to be the “greatest.” I started to have major network problems and noticed (from the OUIs listed by the network analyzer) that I was only experiencing problems with the cards I had just updated. I undid the update, the network problems went away, and I leaned on the application vendor to solve the original problem. The OUI can really be a useful concept to know.

The OUI only tells you who made the chip, not the manufacturer who put the board together. Creating a microchip is expensive, but putting these chips together on a circuit board that becomes a NIC is less expensive. Because of this cost differential, many vendors purchase other vendors’ chips to use on their brand of network cards. For example, although Emulex is on the OUI list as using 00-00-c9, Proteon, Inc. has released network boards with this OUI.

If a network configuration option ever asks you whether you want to override the MAC address of a NIC, say no! This option is intended only for experienced network administrators and can wreak havoc if not used correctly.

God Exists | Moral Story

Labels: Moral Story , Story

A man went to a barbershop to have his hair and his beard cut as always. He started to have a good conversation with the barber who attended him. They talked about so many things on various subjects.

Suddenly, they touched the subject of God. The barber said: “Look man, I don’t believe that God exists as you say so.”

“Why do you say that?” Asked the client. Well, it’s so easy; you just have to go out in the street to realize that God does not exist. Oh, tell me, if God existed, would there be so many sick people? Would there be abandoned children? If God existed, there would be neither suffering nor pain. “I can’t think of a God who permits all of these things.” The client stopped for a moment thinking but he didn’t want to respond so as to prevent an argument.

The barber finished his job and the client went out of the shop. Just after he left the barbershop, he saw a man in the street with a long hair and beard (it seems that it had been a long time since he had his cut and he looked so untidy). Then the client again entered the barbershop and he said to the barber: “know what? Barbers do not exist.”

“How come they don’t exist?” asked the barber. “Well I am here and I am a barber.” “No!” - the client exclaimed. “They don’t exist because if they did there would be no people with long hair and beard like that man who walks in the street.”

“Ah, barbers do exist, what happens is that people do not come to us.” “Exactly!” - Affirmed the client. “That’s the point. God does exist, what happens is people don’t go to Him and do not look for Him that’s why there’s so much pain and suffering in the world.”

Using Remote Server Administration Tools For Windows Server 2008 | Using RSAT

Labels: Administration , RemoteDesktop , Windows Server , Windows Server 2003 , Windows Server 2008

What if you want to manage our file server running Windows Server 2008 remotely from another machine? Once we have a Remote Desktop Connection session with the remote server, we can run tools such as Server Manager or File Server Resource Manager as if we were sitting at the remote machine’s console.

In Windows Server 2003, you can also manage remote servers this way. But you can also manage them another way by installing the Windows Server 2003 Administration Tools Pack (Adminpak.msi) on a different Windows Server 2003 machine, or even on an admin workstation running Windows XP Service Pack 2. And once the Tools Pack is installed, you can open any of these tools, connect to your remote server, and manage roles and features on the server (provided the roles and features are installed).

Is there an Adminpak for Windows Server 2008? Well, there’s an equivalent called the Remote Server Administration Tools (RSAT), which you can use to install selected management tools on your server even when the binaries for the roles/features those tools will manage are not installed on your server. In fact, the RSAT does Adminpak one better because Adminpak installs all the administrative tools, whereas the RSAT lets you install only those tools you need. (Actually, you can just install one tool from Adminpak if you want to, though it takes a bit of work to do this-see article 314978 in the Microsoft Knowledge Base for details.)

What features or roles can you manage using the RSAT? As of Beta 3, you can install management tools for the following roles and features using the RSAT:

Roles:

Active Directory Domain Services

Active Directory Certificate Services

Active Directory Lightweight Directory Services

Active Directory Rights Management Services

DNS Server

Fax Server

File Server

Network Policy and Access Services

Print Services

Terminal Services

Web Server (IIS)

Windows Deployment Services

Features:

BitLocker Drive Encryption

BITS Server Extensions

Failover Clustering

Network Load Balancing

Simple SAN Management

SMTP Server

Windows System Resource Management (WSRM)

WINS Server

How do you install individual management tools using the RSAT? With Windows Server 2008, it’s easy-just start the Add Feature Wizard, and select the RSAT management tools you want to install, such as the Terminal Services Gateway management tool. (See Figure below. Note that installing some RSAT management tools might require that you also install additional features. For example, if you choose to install the Web Server (IIS) management tool from the RSAT, you must also install the Configuration APIs component of the Windows Process Activation Service [WPAS] feature.)

Figure: Installing a management tool using the RSAT feature

The actual steps for installing features on Windows Server 2008 in production environment are even more. For now, just note that when you install an RSAT subfeature such as TS Gateway, what this does is add a new shortcut under Administrative Tools called TS Gateway. Then if you click Start, then Administrative Tools, then TS Gateway, the TS Gateway Manager console opens. In the console, you can right-click on the root node, select Connect To TS Gateway Server, and manage a remote Windows Server 2008 terminal server with the TS Gateway role service installed on it without having to enable Remote Desktop on the terminal server.

Finally, the Windows Server 2003 Adminpak can be installed on a Windows XP SP2 or SP3 workstation, which lets you administer your servers from a workstation. The RSAT can be installed on a Windows Vista or Windows 7 machines so that you can manage your Windows Server 2008 machines from there.

Managing Virtual Machines in Windows Server 2008 | Experts Talk About Windows Server Virtualization

Labels: Virtual , Virtual PC , Windows Server , Windows Server 2008

The MMC snap-in for managing virtual machines that is provided with Windows Server virtualization is evolving, And here, I wanted to give you a quick preview. Figure below shows the Windows Virtualization Management console of Windows Server 2008. The console tree on the left displays the name of the server, while the Details pane in the middle shows a number of virtual machines, most of them in an Off state and two in a Saved state. The Actions pane on the right lets you manage virtualization settings, import virtual machines, connect to a virtual machine, and perform other tasks.

Figure: Windows Virtualization Management console

So that’s a very brief preview of what’s in store for virtualization in Windows Server 2008 in terms of managing virtual machines. Fortunately we also have some experts on the product team at Microsoft who provide us with some more information concerning this feature and especially the planning issues surrounding implementing Windows Server virtualization in your environment.

First, here’s one of our experts talking about using Windows Server virtualization in conjunction with the Windows server core installation option of Windows Server 2008:

From the Experts: Windows Server Virtualization and a Windows Server Core Installation:

The Windows server core installation option of Windows Server 2008 and Windows Server virtualization are two new features of Windows Server 2008 that go hand in hand. The Windows server core installation option is a new minimal GUI shell-less installation option for Window Server 2008 Standard, Enterprise and Datacenter Editions that reduces the management and maintenance required by an administrator. The Windows server core installation option provides key advantages over a full installation of Windows Server 2008 and is the perfect complement to Windows Server virtualization. Here are a couple of reasons why.

Reduced attack surface A Windows server core installation provides a greatly reduced attack surface because it is tailored to provide only what a role requires. By providing a minimal parent partition, this reduces the need to patch the parent partition. In the past with one workload running per server, if you needed to reboot the server for a patch, it wasn’t ideal, but generally one workload was affected. With Windows Server virtualization, you’re not just running a single workload. You could be running dozens (even hundreds) of workloads in their own virtual machine. If the virtualization server requires a reboot for a patch (and you don’t have a high availability solution in place), the result could be significant downtime.
Reduced resource consumption With the parent partition requiring only a fraction of the memory resources for a Windows server core installation as opposed to a full installation of Windows Server 2008, you can use that memory to run more virtual machines.

In short, it is highly recommended that you use Windows Server virtualization in conjunction with a Windows server core installation.

-Jeffrey Woolsey [ Lead Program Manager, Windows Virtualization ]

Next, let’s hear another of our experts on the virtualization team at Microsoft share about how to identify what should be virtualized in your environment and what maybe shouldn’t:

From the Experts: Virtualization Sizing

It is very important to understand how to roll out virtualization in your organization and what makes the most sense for your environment and business conditions. So often, some enthusiastic users and organizations start either attempting to virtualize everything or start with their most complex middleware environments. There are no right or wrong first candidates for virtualization but you need to ensure that you have fully thought about the impact of using virtualization in your environment and for the workloads in question.

As you think about what to virtualize and how to go about picking the right workloads, the order of deployment, and what hardware capabilities you need, find a model or a set of models that help you conceptualize the end solution. The System Center family of products provides you a set of tools that help simplify some of these issues, and other solutions from vendors like HP provide you tools to help size the deployment environment once you have figured out the candidates and the rollout process.

The next few points help identify some of the best practices in sizing your virtualization environment. Think of the following as a set of steps that will help you identify what workloads to virtualize and what the deployment schedule should look like.

1. Assessment As with any project, the first step is to fully know about where you are today and what capabilities you already have in your environment. The last thing you want to do is to sit and re-create the wheel and invest in things you already have in your environment. As you think about assessment, think about assessing all the components you have in your infrastructure, the types of workloads, and interdependencies of the various workloads. Also evaluate all the management assets you already have in your infrastructure and identify the functions that these are performing, such as monitoring, deployment, data protection, security, and so on. These are the easier items to assess, but the more critical one to assess will be the overall process discipline that exists in your organization and how you deal with change in today’s world. While this is a hard factor to quantify, this is critical in evaluating what capacity you have to deploy virtualization. To help you make this assessment from a holistic perspective, there are tools available such as Microsoft’s Infrastructure Optimization Model or Gartner’s IT Maturity Model that you can choose to use. There is one thing a customer once told me that I will never forget–“If someone tells you they have a solution for your problems when you have not identified or told them what your problems are, most likely they are giving you something you already have in a different package–that is, if you are lucky.”

2. Solution Target Once you have identified and assessed your current environment, find out where you can use virtualization today. All server virtualization solutions today provide these usage scenarios:

Production Server Consolidation, which encompasses all forms of consolidation of systems in existing or new environments.
Test and Development Environments, which addresses the use of virtualization for optimizing the test and dev cycles and not only enables you to leverage the cost saving from hardware needs but also enables easy creation and modification of the environments.
Business Continuance, where your primary motivator is to leverage the fact that virtualization transforms your IT infrastructure to files (in Microsoft’s case a VHD file) to enable new and interesting continuance and disaster recovery solutions.
Dynamic Datacenter, which is a new set of capabilities unleashed by virtualization to now enable you to not only create and manage your environment more efficiently, but provide a new level of capability to be able to dynamically modify the characteristics of the environments for workloads based on usage. The dynamic resource manipulation enables you to take the consolidation benefits and translate it to now making your IT a more agile environment.

Branch Office, which while not being a core solution, is one usage scenario where virtualization helps change how IT systems are deployed, monitored, and managed and helps extend the capabilities of the branch environment to bring in legacy and new application environments under one common infrastructure umbrella.

As you are trying to decide which solution area or areas to target for your virtualization solution, do keep in mind the level of complexity of the solutions and the need for increasing levels of management tools and process discipline. Test and dev environments are the easiest to virtualize and usually can manage to take some downtime in case of hiccups–hence this is a natural start for everyone. Server Consolidation is another area that you can start using virtualization in today. The initial cost savings here are in the hardware consolidation benefits–but the true value of consolidation is seen only when you have figured out how to use a unified management infrastructure. Business continuance and branch scenarios need you to have a management infrastructure in place to help orchestrate these solutions and again to see the true value – you will need to have a certain level of processes outlined. Dynamic datacenter is a complex solution for most customers to fully deploy and this usually applies to a certain subset of the org’s infrastructure–select the workloads that need this type of solution more carefully as adding the SLAs to maintain such a solution should mean that the workload is really critical to the organization.

3. Consolidation Candidates Most users today are deploying virtualization to help consolidate workloads and bring in legacy systems into a unified management umbrella. In this light, it becomes important to identify which workloads are the most logical ones to consolidate today and what makes sense in the future. There are some workloads that sound attractive for virtualization, but might not be ideal at any stretch because of certain I/O characteristics or purely because they are so big and critical that they easily scale up to or beyond the capabilities of the hardware being thrown at them. Operations Manager or Virtual Machine Manager has a report that is generated called the virtualization candidates report that helps scan your entire IT org and tell you exactly what workloads are ideal for virtualization based on a number of thresholds such as CPU utilization, I/O intensity, network usage, size of the workload, and so on. Based on this report and knowing the interdependencies identified during the assessment phase, you can make intelligent decisions on what workloads to virtualization and when.

4. Infrastructure Planning This is where the rubber meets the road so to speak. Once you have identified the candidates to virtualize, you need a place to host the virtualized workloads. Tools from companies such as HP (HP Virtualization Sizing Guide) help you identify the type of servers you will need in your environment to host the virtualization solution that you have identified in the previous step. There is one fundamental rule to consider as you are selecting the infrastructure for virtualization–the two biggest limiting factors for virtualization are memory and I/O throughput–so always ensure that you select a x64 platform for your hardware to ensure a large memory access, and always try to get the best disk subsystem either into the system for DAS or good SAN devices.

5. Placement This is not so much an area that is going to affect the sizing of your environment, but has the potential to impact your sizing decisions in the long run. Here we are referring to the act of taking one of the virtualization candidates and actually deploying it to one of the selected virtualization host systems. The knowledge of interdependencies of the various workloads affects some of how this placement occurs but from a high level, this is more about optimizing the placement for a few selected variables. Virtual Machine Manager has an intelligent placement tool that helps you optimize either to a load balancing algorithm or to a maximizing utilization algorithm. You can alternatively also tweak individual parameters to help optimize your environment based on your business weights of the different parameters.

As you size your virtualization environment, also keep in mind the overall manageability factor and how you can scale your management apps to help cover the new environment. Now that you have seen how to size your virtualization environments, keep two things in mind–virtualization is a great technology that can help in multiple levels and scenarios but is still not the panacea for all problems so do take the time to identify your true problems and also remember that you need to look at deploying and managing virtualized environments over a long period of time and hence the need to think about virtualization as a 3-year solution at least.

Virtualization is primarily a consolidation technology that abstracts resources and aids aggregation of workloads, so think carefully about how this affects your environment and what steps you need to have in place to avoid disasters and plan for them early.

-Rajiv Arunkundram [ Senior Product Manager, Server Virtualization ]

Finally, an important planning item for any software deployment is licensing. Here’s one of our experts explaining the current licensing plan for Windows virtualization:

From the Experts: Virtualization Licensing

One of the most talked about and often most confused areas for virtualization is licensing. Some of this is primarily caused due to the lack of one industry standard way of dealing with licensing and the other cause is that virtualization is a disruptive technology in how companies operate and hence not clear to customers on what the various policies mean in this new world.

Microsoft’s licensing goals are to provide customers and partners cost-effective, flexible, and simplified licensing for our products that will be applicable across all server virtualization products, regardless of vendor. To this effect, several changes were put in place in late 2005 to help accelerate virtualization deployments across vendors:

Windows server licensing was changed from installation-based licensing to instance-based licensing for server products.
Microsoft changed licensing to allow customers to run up to 1 physical and 4 virtual instances with a single license of Windows Server 2003 Enterprise Edition on the licensed device; and 1 physical and unlimited virtual instances with Windows Server 2003 Datacenter Edition on the licensed device.
With the release of SQL Server 2005 SP2, Microsoft announced expanded virtualization use rights to allow unlimited virtual instances on servers that are fully licensed for SQL Server 2005 Enterprise Edition.

With all these changes, you can now easily acquire and license Windows Server and other technologies in a much more efficient process. Virtualization also adds another level of complexity for licensing with the ability to easily move the images or instances around between machines. This is where licensing from the old era makes it tricky. The simple way to remember and ensure that you are fully licensed is to look at the host systems as the primary license holders with the instances being the deployment front. So if you want to move a workload to a system that has Windows Server Enterprise Edition running and already has 4 instances running, you will need an additional license; if it is lower than 4, you will not need an additional license to make the move happen.

Do note that the licensing policies for these apply across virtualization products in the same manner across all server virtualization platforms.

The Ant And The Grasshopper Moral Story | Importance Of Planning

How To Add Images Or Icons To Links In The Sidebar For Blogs Hosted In Blogger

How To Add A Navigation Link Bar To The Header In Blogger | Merging A Navigation Bar With Header Image In Blogger.

Installing New Software In Windows Seven | Installation Difference Between Windows XP And Seven

New Group Policy Features In Windows 7 and Windows Server 2008 R2

Logical Side And Physical Side Of Active Directory | The Two Sides Of Active Directory

How Indexing For Optimized Searches Works | Windows Active Directory

Step By Step Instruction On Installing Microsoft Office As Terminal Services In Windows Server

Understanding Windows 7 Compatibility Issues | Using XP Mode In Windows 7 And Vista

Web Server Traffic Reporting With Webalizer In Linux | Running A WebServer In Linux Machine

The Myth of RAID Backups | RAID Is Not A Backup Function

What Is Media Access Control Or Burned In Address | MAC

God Exists | Moral Story

Using Remote Server Administration Tools For Windows Server 2008 | Using RSAT

Managing Virtual Machines in Windows Server 2008 | Experts Talk About Windows Server Virtualization

Translator

Popular Posts

Subscribe By Email

Choose By Category

Microsoft Press

Free Ebooks Download

Recent Posts