Most Damaging Malware

All malware is bad, but some types of malware do more damage than others. That damage can range from loss of files to total loss of security -- even outright identity theft. This list (in no particular order) provides an overview of the most damaging types of malware, including viruses, Trojans and more.

Overwriting Viruses

Some viruses have a malicious payload that causes certain types of files to be deleted - sometimes even the entire drive contents. But as bad as that sounds, if users act quickly the odds are good the deleted files can be recovered. Overwriting viruses, however, write over the original file with their own malicious code. Because the file has been modified/replaced, it can't be recovered. Fortunately, overwriting viruses tend to be rare - in effect their own damage is responsible for their shorter lifespan. Loveletter is one of the better known examples of malware that included an overwriting payload.

 

Ransomware Trojans

Ransomware trojans encrypt data files on the infected system, then demand money from the victims in exchange for the decryption key. This type of malware adds insult to injury - not only has the victim lost access to their own important files, they've also become victim to extortion. Pgpcoder is perhaps the best known example of a ransomware trojan.

Password Stealers

Password stealing trojans harvest login credentials for systems, networks, FTP, email, games, as well as banking and ecommerce sites. Many password stealers can be repeatedly custom configured by attackers after they've infected the system. For example, the same password stealing trojan infection could first harvest login details for email and FTP, then a new config file sent to the system which causes it to turn attention to harvesting login credentials from online banking sites. Password stealers that target online games are perhaps the most commonly talked about, but by no means are games the most common target.

Keyloggers

In its simplest form, a keylogger trojan is malicious, surreptitious software that monitors your keystrokes, logging them to a file and sending them off to remote attackers. Some keyloggers are sold as commercial software - the type a parent might use to record their children's online activities or a suspicious spouse might install to keep tabs on their partner.

Keyloggers may record all keystrokes, or they may be sophisticated enough to monitor for specific activity - like opening a web browser pointing to your online banking site. When the desired behavior is observed, the keylogger goes into record mode, capturing your login username and password.

Backdoors

Backdoor trojans provide remote, surreptitious access to infected systems. Put another way, it's the virtual equivalent to having the attacker sitting at your keyboard. A backdoor trojan can allow the attacker to take any action you - the logged in user - would normally be able to take. Via this backdoor, the attacker can also upload and install additional malware, including password stealers and keyloggers.

Rootkits

A rootkit gives attackers full access to the system (hence the term 'root') and typically hides the files, folders, registry edits, and other components it uses. In addition to hiding itself, a rootkit typically hides other malicious files that it may be bundled with. The Storm worm is one example of rootkit-enabled malware. (Note that not all Storm Trojans are rootkit-enabled).

Bootkits

While said to be more theory than practice, this form of hardware targeting malware is perhaps the most concerning. Bootkits infect flash BIOS, causing the malware to be loaded even prior to the OS. Combined with rootkit functionality, the hybrid bootkit can be near impossible for the casual observer to detect, much less to remove.

Tips for using device manager on virtual Windows Servers

By Rick Vanover (techrepublic.com)

August 24, 2011, 7:32 AM PDT

Takeaway: Even though virtual machines may be the de facto platform for new Windows Servers, the hardware management panel is still critical for troubleshooting issues on a system. Rick Vanover shares tips on using device manager for virtual machines.

When Windows Servers are running in a virtual machine, we rarely check into device manager. Given that systems built as a virtual machine have a much higher chance of being successful when the proper drivers are installed (such as VMware Tools), this issue is less of a problem for new builds. But some systems may have gone through a physical-to-virtual (P2V) conversion or a virtual-to-virtual (V2V) conversion. There’s a greater chance P2V systems will have some sort of carryover device in the device manager. Some devices (especially network interface controllers) might be inventoried in the server but not displayed. The goal of a device manager console is to be free of any issues, as shown in the virtual machine hardware inventory in Figure A.

Figure A

Click the image to enlarge.

For systems that have gone through a P2V conversion and had their virtualization drivers installed, there may be residual issues with previously enumerated hardware. One such issue is the “phantom” network interface; this is usually most visible when a single network adapter is visible, and it is called Local Area Network 2. Further, if a static IP address is assigned to the server that was the same when it was a physical server, a confusing warning message may appear before saving the changes. Removing the phantom network interfaces is an easy process.

The phantom network interface is one of the most common examples where a missing device may have a lingering configuration yet not be part of the device manager enumeration. Sometimes the option to show hidden devices in the device manager doesn’t show these either.

For all servers, Windows device manager is an important console that should be reviewed from time to time and not just after the server build. For virtual machines, this doesn’t change, and by making sure the device manager is accurate, it can ensure the virtual machine is performing as expected.

What do you do differently for support virtual hardware on Windows servers? Share your comments below.

Server Hardware Explained (Part 2)

• Published: Sep 15, 2011
• Author: Brien M. Posey

Introduction

In my first article in this series, I talked about the various form factors used by network servers. Although it might at first seem a bit odd, I want to turn my attention to server cases. My reason for doing so is that server cases often have a number of features that are designed to support the server’s overall wellbeing. Since my goal in writing this series is to educate novices on server hardware I wanted to start at the beginning.

 

Cooling Features

Computers must be kept cool in order to function properly. All kinds of bizarre errors can occur if a system's processor begins to overheat. Servers use devices such as heat sinks and CPU fans to keep components cool, but the case design also plays a vital role in regulating the server's overall temperature. Blade servers however, are the exception. The blade server chassis is responsible for cooling the individual blade servers. For rack mount and tower servers however, the case is specifically designed to keep the server cool.

The actual cooling features that are found in a server's case vary from one server to the next. At a minimum, a server typically has at least a couple of case fans. The fans are arranged in a way so that cool air is pulled into the server through vents. This cool air passes over the individual system components and is then exhausted from the system's case. The size of the fans and the number of fans used can vary considerably depending on the case design.

Some server cases rely solely on case fans that really aren’t much different from those found in PCs. Others use a more creative design. For example, I recently saw one server that was equipped with exhaust fans located between each expansion slot.

Servers are also typically equipped with temperature sensors. Sometimes these sensors are integrated into the system board or into individual components, but they may also be built into the case. If the temperature inside the case begins to rise then the fans will spin faster in an effort to keep the server operating at a safe temperature. The system BIOS usually also has a safety mechanism that can shut down the server before damage occurs if the temperature gets to be too high.

 

Filtering

Sometimes fans alone are not enough to keep a server cool. In industrial areas a server’s fans can suck in dust, dirt, soot, and other contaminants. These particles can clog air vents and may also prevent fans from operating efficiently. In order to prevent this type of contamination, some (but certainly not all) server cases are equipped with built in air filters.

Air filters do a good job of keeping stray particles of contaminants out of a server case, but they require routine maintenance. Air filters (which are usually washable) must be cleaned on a regular basis. A dirty air filter can actually restrict air flow just as badly as if the server’s vents were completely obstructed.

 

Physical Security

Physical security doesn’t seem to be a major priority when it comes to server case design. Many server manufacturers seem to assume that servers will be placed in physically secure datacenters, so there is little need for physically secure server cases. However, there are aftermarket server cases that are designed to provide good physically security. Such cases are usually key lockable and are often made of heavy gauge steel.

 

Status Indicators

Servers almost always have various forms of status indicators. The status indicators are typically LED lights. Status LEDs are not unique to servers. PCs also use status LEDs. For example, almost every PC has a power indicator and a hard drive activity indicator. Servers offer such indicators too, but often include additional indicators that are not usually found on PCs.

Each server manufacturer uses their own proprietary set of indicator lights. However, there is usually a global indicator light that can convey the server’s status through colors and / or flash patterns.

Some servers also have a locate light. The idea behind the locate light is that when you are managing a server in a large datacenter it can sometimes be difficult to figure out which physical machine you are connecting to. The locate light helps you to spot the machine that you are managing. For example, if you were to connect to a server using a management tool and then discovered that the server needed to have a hardware component replaced. You could illuminate the server’s locate light and use it to figure out which physical server needs to be repaired. Not all servers have locate lights, and on some servers the simple act of connecting to the server with a management tool causes the locate light to illuminate.

In addition to the status indicator LEDs, there are a few server cases that have integrated thermometers that visually display the temperature inside the case.

 

Ports

In most datacenters, servers are only accessed remotely. Even so, servers typically include keyboard, video, and mouse ports. These ports can be used during the initial setup or in those rare situations in which it is necessary to perform diagnostics locally.

In the case of blade servers, individual blade servers do not include keyboard, video, and mouse ports. These ports are provided through the blade server chassis.

In addition to the keyboard, video, and mouse ports, servers also typically include USB ports. It is becoming more common for servers to provide USB ports in place of keyboard and mouse ports since USB ports take up less space and can be used as a keyboard or mouse connection.

 

Drive Bays

Most servers contain at least one or two drive bays. The biggest determining factor in the number of drive bays that a server can accommodate is its form factor. For example, a 1U server might only have one or two drive bays, while some 4U servers offer dozens of drive bays.

Servers with smaller form factors often use local hard drives solely for the operating system and connect to remote storage (such as a SAN) for everything else.

 

Swing Out Bezels

Another set of features that are often found on rack mount servers are swing out bezels. To help you to understand what swing out bezels are and why they are important, imagine for a moment that you have a rack with half a dozen or so servers installed in it. Now, imagine that you need to add some memory to one of the servers that is located in the middle of the vertical stack. How do you do it? The top, bottom, and sides of the server are all blocked. You could remove the server from the rack, but that’s a lot of work for a simple memory upgrade.

This is where swing out bezels come into play. Swing out bezels allow you to slide the entire server forward so that you can open the server’s case without having to remove the server from the rack. The There are various designs for swing out bezels, but they are usually integrated into a server’s side rails.

Server Hardware Explained (Part 1)

Information shared from http://www.windowsnetworking.com

Author: Brien M. Posey

Introduction

A few years ago I wrote an article series for this site called Networking for Beginners. To date this series remains immensely popular and I routinely receive E-mail messages from readers asking me to continue the series. Unfortunately, continuing the Networking for Beginners series isn’t an option for various reasons, but I wanted to do the next best thing and write a series that is designed to introduce beginners to the basics of server hardware.

 

The Difference Between PCs and Servers

When I first started out as a network administrator one of the concepts that I had trouble grasping was the difference between a server and a PC (from a hardware standpoint). Don’t get me wrong, learning the differences between a PC and a server isn’t rocket science. It’s just that I didn’t have anyone who could explain it to me.

I got my first job as a network administrator almost twenty years ago during my first year of college. At the time I had a really strong working knowledge of PC hardware and of DOS (which was the desktop operating system of choice at the time). However, I had never been exposed to network servers before. My only background in networking at that point involved IBM mainframes.

Prior to interviewing for the position I memorized a book on Novell NetWare and managed to pass myself off as a networking expert. When I started my new position I didn’t have any trouble working with the network operating system, but I was a bit baffled by the server hardware. I could only assume (incorrectly) that the servers that we were using were highly specialized computers that were only capable of running server operating systems.

A couple of years later Microsoft released Windows NT and I decided to attend a training class to see if Windows NT would benefit our organization. The training center where I took the class provided each student with a PC and then proceeded to teach us how to install Windows NT Server onto it.

This really confused me. I just couldn’t understand why the company that I worked for was spending thirty thousand dollars for each server when a PC that cost a thousand dollars would run Windows NT just as well. Since our servers used exactly the same CPU architecture as our desktop PCs, my only conclusion was that our hardware vendor was ripping us off. After all, it seemed that from a hardware prospective there was absolutely no difference between a PC and a server other than the price.

Obviously I was wrong. I won’t bore you with the details of what the differences between our PCs and our servers were because all of that hardware is completely obsolete today. Even so, I wanted to share this story with you as a way of illustrating the point that there are major differences between PC hardware and server hardware. Sometimes those differences just aren’t immediately obvious to beginners.

In many ways server hardware really isn’t all that different from desktop PC hardware. Both use the same basic components such as memory, CPUs, and power supplies. In spite of these similarities however, server hardware can seem completely foreign to those who have previously only dealt with desktop hardware. The individual components tend to be more advanced than the components that are found in desktop computers. Servers may also make use of redundant and / or how swappable components. Occasionally PCs might have redundant or even hot swappable components, but such features are much more common on servers.

 

Server Form Factor

So now that I have talked a bit about some of the differences between PCs and servers, I want to turn my attention to server form factors. When it comes to computers, the term form factor describes the physical dimensions and standards used by various system components and by the computer as a whole. To give you a more concrete example, many PCs use a form factor called standard ATX. A standard ATX case can physically accommodate any standard ATX system board and power supply, even if they are made by a different vendor.

Another common PC standard is Micro ATX. Many standard ATX computer cases are designed to accept either standard ATX or Micro ATX system boards, but a Micro ATX case would not be able to accommodate a standard ATX system board because Micro ATX cases use a smaller form factor.

Form factors apply to server hardware as well, but servers typically adhere to different form factors than PCs (but not always). There are several different form factors used for network servers, but the three most common form factors are tower servers, rack servers and blade servers.

 

Tower Servers

Tower servers look a lot like PCs. Each tower server is a standalone machine that is built into an upright case.

Tower servers are used mostly in smaller datacenters. Larger datacenters typically avoid the use of tower servers because of the amount of physical space that they consume and because they tend to be noisy.

Another disadvantage to using tower servers is that the cabling can get messy. Server racks and blade server chassis usually have features that are designed to manage cables, but tower servers have no such features.

 

Rack Servers

As the name implies, rack servers are servers that are mounted within a rack. The rack is of a uniform width and servers are mounted to the rack using screws. Each rack can accommodate multiple servers and the servers are typically stacked on top of each other.

Because racks are designed to accommodate standard sized components, many hardware vendors offer rack mountable networking components other than servers. For example there are rack mountable network appliances (such as hardware firewalls) and rack mountable switches.

Rack mount components follow a form factor that is referred to as a rack unit. A standard rack mount server is referred to as a 1U server meaning that it is 1 rack unit in size. A 2U server consumes two rack units of space within the rack. Some vendors also offer 4U and ½U servers. The larger form factors are usually used when the server needs to be able to accommodate a large amount of storage.

 

Blade Servers

Like rack servers, blade servers also adhere to a standard size and mount inside a special “rack”. In the case of a blade server however, the rack is known as a chassis.

Blade servers tend to be vendor proprietary. You can’t for example insert a Dell blade server into an HP chassis.

The reason why blade server design is proprietary is because unlike a rack server, which is fully self-contained, blade servers lack some of the components that they need to function. For example, blade servers do not have power supplies.

The blade server chassis is designed to accept various modular components, including the blade servers themselves. For example, a chassis might contain a power supply unit, a cooling unit, and a blade server. The actual chassis design varies from one vendor to the next, but most blade server chassis are designed to accommodate multiple power supplies, multiple blade servers, and a variety of other components (such as network adapters, storage modules, and cooling modules). With the exception of the cooling components, individual blade servers are mapped to the individual modules or components.

All Windows Commercials (3.1 to 7)

12tb NAS Home Server Introduction Server 2008 R2

Migrating Exchange Server 2010 Organization into the Private Cloud

Cloud Definitions:

Today everybody is talking about clouds: what they are; how to use them and if using them is suitable for their organization. In general “cloud computing” can be defined as server based computing in virtual environments in decentralized datacenters. This means that these servers are accessible via WANs and do not exist in the local network.

In general there are three kinds of cloud technologies:

• Public Clouds
• Private Clouds
• Hybrid Clouds

Public Clouds are IT environments that are hosted at big providers (like Microsoft, Google or Amazon). These data centers are spread all over the world with high availability functionality. They are often called “Software as a Service” solutions, because the servers are not dedicated for your company because all data of all customers is hosted by these servers in parallel.

Private Clouds are IT environments that are hosted by your organization but the underlying technology is the same as in Public Cloud environments. This means you are prepared for the cloud but are running your own cloud, either in your data center or in a collocated data center of a big provider.

Hybrid Clouds are a mixture of public and private cloud designs based on the technology needs of your company.

This article will discuss how to migrate a dedicated, non-virtualized Exchange Server 2010 SP1 environment into a Private Cloud based collocated data center without disruption of mail transfer for the users.

Requirements

To easily prepare and run the migration, you need to fulfill the following requirements:

• All Exchange Servers are running Exchange Server 2010 Service Pack 1 and same patch level of Windows and Exchange
• A high available Exchange organization with DAG (Database Availability Group) and dedicated Exchange Servers running the Hub Transport and Client Access Role.
• A “high speed” connection to the internet (100 Mbit or more are quite good, because the more performance you will have, the quicker your migration will be finished)
• Complete routable network
• Local Domain Controllers (with Global Catalog Role) available in the collocated data center
• Clients are already connecting to Exchange using the “Outlook over the Internet” feature

Preparation Tasks

• Installation of 2 Windows Server 2008 R2 Standard Edition (for running Hub Transport and Client Access Role)
• Installation of 2 Windows Server 2008 R2 Enterprise Edition (for running Mailbox Server Roles in a DAG)

Phase 1 – Co-Existence

• Installation of Exchange Server 2010 SP1 on the two Standard Edition Servers with Hub Transport and Client Access Role enabled
• Installation of Antivirus and Backup Agents on these new servers
• Copy the configuration of Hub Transport and Client Access Roles to these new servers
• Configure the Client Access Servers as “CAS Array” for high availability
• Installation of Exchange Server 2010 Sp1 on the two Enterprise Edition Servers with Mailbox Role enabled
• Installation of Antivirus and Backup Agents on these new servers
• Configure these two servers as member of the existing Database Availability Group(s)
• Wait for replication for all databases has completed on the new servers
• Enable network access for all clients to the new Client Access Servers

Phase 2 – Demotion of local Exchange Servers with Hub Transport and Client Access Roles

• Disable SMTP connectors on all local Exchange Hub Transport Servers
• Change remote proxy configuration to route Outlook Web App and Exchange Server Sync to the new Client Access Servers
• Uninstall Exchange Server from both local Client Access and Hub Transport Servers
• Unjoin these Servers from your domain
• Shut them down completely
• Check if all clients can work properly

Phase 3 – Demotion of local Exchange Servers with Mailbox Roles

• Unjoin both local Exchange Mailbox Servers from your DAG configuration
• Uninstall Exchange Server from these servers
• Unjoin them from your domain
• Shut them down completely
• Check if all clients an work properly

Phase 4 – Finalize the Migration

After having finished the migration to the “private cloud”, you should now make sure that:

• Documentation of the new server structure
• Enable Monitoring for your new servers to early find out where possible problems may occur
• Provide QoS (quality of service) on your WAN lines to make sure that you can provide enough performance to your clients when the connect to their Exchange Servers in the collocated network

Unified Communication Role

Because the Unified Communication Role of Exchange Server 2010 SP1 is still not approved for high availability and virtualization, you need to manually transfer this role to your collocated data center with a period of unavailability of this service.

The following steps are usually needed for this transfer:

• Power off your server hosting the Unified Communication Role
• Ship this server to your collocated network
• Power on your server in the collocated network
• Change the IP configuration of this server
• Restart it and enable service availability

General Information

If you do not have “high availability” in your environment today, it might be interesting to implement a single server database availability group (DAG), too. This will make your migration into the cloud much easier because then you could create a temporary DAG solution to easily migrate your mailboxes to the cloud without interfering users.

Conclusion

As you hopefully would have recognized a migration to a private cloud data center with Exchange Server 2010 Service Pack 1 is quite easy. It is a step forward and proved solution.

*****************************************************************************

Author: Markus Klein

What Cloud Computing Really Means?

Cloud computing is all the rage. "It's become the phrase du jour," says Gartner senior analyst Ben Pring, echoing many of his peers. The problem is that (as with Web 2.0) everyone seems to have a different definition. As a metaphor for the Internet, "the cloud" is a familiar cliché, but when combined with "computing," the meaning gets bigger and fuzzier. Some analysts and vendors define cloud computing narrowly as an updated version of utility computing: basically virtual servers available over the Internet. Others go very broad, arguing anything you consume outside the firewall is "in the cloud," including conventional outsourcing. Cloud computing comes into focus only when you think about what IT always needs: a way to increase capacity or add capabilities on the fly without investing in new infrastructure, training new personnel, or licensing new software. Cloud computing encompasses any subscription based or pay-per-use service that, in real time over the Internet, extends IT's existing capabilities. Cloud computing is at an early stage, with a motley crew of providers large and small delivering a slew of cloud-based services, from full-blown applications to storage services to spam filtering. Yes, utility-style infrastructure providers are part of the mix, but so are SaaS (software as a service) providers such as Salesforce.com. Today, for the most part, IT must plug into cloud based services individually, but cloud computing aggregators and integrators are already emerging.

Here's a rough breakdown of what cloud computing is all about:

1. SaaS

This type of cloud computing delivers a single application through the browser to thousands of customers using a multitenant architecture.

On the customer side, it means no upfront investment in servers or software licensing; on the provider side, with just one app to maintain, costs are low compared to conventional hosting. Salesforce.com is by far the best-known example among enterprise applications, but SaaS is also common for HR apps and has even worked its way up the food chain to ERP, with players such as Workday. And who could have predicted the sudden rise of SaaS "desktop" applications, such as Google Apps and Zoho Office?

2. Utility Computing

The idea is not new, but this form of cloud computing is getting new life from Amazon.com, Sun, IBM, and others who now offer storage and virtual servers that IT can access on demand. Early enterprise adopters mainly use utility computing for supplemental, non-mission-critical needs, but one day, they may replace parts of the datacenter. Other providers offer solutions that help IT

Create virtual datacenters from commodity servers, such as 3Tera's AppLogic and Cohesive Flexible Technologies' Elastic Server on Demand. Liquid Computing's LiquidQ offers similar capabilities, enabling IT to stitch together memory, I/O, storage, and computational capacity as a virtualized resource pool available over the network.

3. Web Services In The Cloud

Closely related to SaaS, Web service providers offer APIs that enable developers to exploit functionality over the Internet, rather than delivering full-blown applications. They range from providers offering discrete business services -- such as Strike Iron and Xignite -- to the full range of APIs offered by Google Maps, ADP payroll processing, the U.S. Postal Service, Bloomberg, and even conventional credit card processing services.

4. Platform As A Service

Another SaaS variation, this form of cloud computing delivers development environments as a service. You build your own applications that run on the provider's infrastructure and are delivered to your users via the Internet from the provider's servers. Like Legos, these services are constrained by the vendor's design and capabilities, so you don't get complete freedom, but you do get predictability and pre-integration. Prime examples include Salesforce.com's Force.com, Coghead and the new Google App Engine. For extremely lightweight development, cloud-based mashup platforms abound, such as Yahoo Pipes or Dapper.net.

5. MSP (Managed Service Providers)

One of the oldest forms of cloud computing, a managed service is basically an application exposed to IT rather than to end-users, such as a virus scanning service for e-mail or an application monitoring service (which Mercury, among others, provides). Managed security services delivered by SecureWorks, IBM, and Verizon fall into this category, as do such cloud based anti-spam services as Postini, recently acquired by Google. Other offerings include desktop management services, such as those offered by CenterBeam or Everdream.

6. Service Commerce Platforms

A hybrid of SaaS and MSP, this cloud computing service offers a service hub that users interact with. They're most common in trading environments, such as expense management systems that allow users to order travel or secretarial services from a common platform that then coordinates the service delivery and pricing within the specifications set by the user. Think of it as an automated service bureau. Well-known examples include Rearden Commerce and Ariba.

7. Internet Integration

The integration of cloud-based services is in its early days. OpSource, which mainly concerns itself with serving SaaS providers, recently introduced the OpSource Services Bus, which employs in-the-cloud integration technology from a little startup called Boomi. SaaS provider Workday recently acquired another player in this space, CapeClear, an ESB (enterprise service bus) provider that was edging toward b-to-b integration. Way ahead of its time, Grand Central which wanted to be a universal "bus in the cloud" to connect SaaS providers and provide integrated solutions to customers -- flamed out in 2005.

Today, with such cloud-based interconnection seldom in evidence, cloud computing might be more accurately described as "sky computing," with many isolated clouds of services which IT customers must plug into individually. On the other hand, as virtualization and SOA permeate the enterprise, the idea of loosely coupled services running on an agile, scalable infrastructure should eventually make every enterprise a node in the cloud. It's a long-running trend with a far-out horizon. But among big metatrends, cloud computing is the hardest one to argue with in the long term.

**********************************************************************

The Article, "What Cloud Computing Really Means" was originally published at InfoWorld.com.

Career Development: Top Ten Tips To Move Up The Corporate Ladder.

In the current economic climate, finding a job is no easy feat. Most people settle for the first job they find in order to gain stability. Instead of changing multiple jobs and treating them as stepping stones, it is important to find opportunities to move up the corporate ladder. Here are a few tips to help you make your way up, and never look back.

Learn to be a Leader:

You do not need to be the boss in order to lead. Learn to take initiative at work, and always be approachable. Co-workers will ask for your help if they know that you are a friendly person. This will allow you to enhance your skills and give you the space to develop. Maintaining a positive attitude helps in motivating and inspiring the people you work with.  By helping other teams and departments, you will become an asset within the organization.

Expand Your Knowledge and Skills

Knowing more is always better than knowing less. Regardless of where you work, in order to succeed you need to have an up to date knowledge of all areas critical within your organization. Learn everything you can about the responsibilities of the job you aspire to get in your workplace. You can do this by watching others, or attending relevant trainings. When you have successfully learnt the ins and outs of procedures and resources, you will be an overall better candidate for the job whenever there is an opening.

Become a Team Player

Teamwork is essential in every organization and allows you to build your reputation. Learning to be a team player opens up new opportunities for you as people start to recognize that you are willing to help them and work on their team. Success at the workplace also depends on your ability to cooperate with co-workers. Employees enhance the overall productivity and add to the success of businesses by working together.

Ask for More Responsibilities

You are more likely to succeed at the workplace by asking for more responsibilities than by asking for a promotion. By asking for more responsibilities you not only show your interest towards the business but also increase your value within the organization. Increasing responsibilities will give you an idea of what is expected of you. Furthermore, it allows you to enhance your potential and understand what you are working towards to prepare you for the future.

Ignore Workplace Politics

Every organization has internal politics. However, to move forward you must ignore all negativity and focus on succeeding. Do not engage in unpleasant conversation about anyone or think of alternate ways to the top. The amount of time and negative energy it takes to plot your way to the top could be better spent generating ideas on how to improve your performance. If you always work hard and deliver the results beyond what is expected, you will be well respected and will soon be moving upwards.

Work Hard

In order to move up the corporate ladder, you should always be willing to work hard. You should know what you are working towards and be able to make sacrifices to reach that goal. Keep setting optimistic but attainable goals that will drive you to surpass your own expectations. No matter how well connected you are, hard work is always essential to reach and maintain your position at the top. People are more likely to get promoted and sustain their position if they have worked hard to earn it.

Be Loyal and Committed to your Organization

In order to achieve success, high levels of commitment and loyalty to the organization are essential. Employees who are so dedicated to their work that they believe by committing themselves they are playing an active role in the success of the organization, are assets to the company. Their performance and productivity levels are consistently high which allows them to stand out from the rest. Employee loyalty results in positive financial outcomes for the business, hence giving them an edge in order to succeed. By being loyal to your organization and demonstrating this at work, you automatically increase your chances of advancing in the workplace. If you display a loyalty towards your boss, he will be more likely to take you up the corporate ladder with him as he is able to count on you.

Maintain A Professional Attitude

A professional attitude consists of various qualities. By displaying your reliability, you become an asset to your company. You should always dress professionally and neatly as this reflects on your personality. If you treat others with respect and act professional, you earn the respect of your co-workers and show others that you are there to work and not get involved in unnecessary office gossip. By detaching yourself from such office dynamics, you are creating an example for others to follow, as well as increasing productivity at work. You must maintain punctuality and never be afraid to ask if unsure of anything. This suggests your willingness to learn, as opposed to your lack of knowledge. Finally, don’t whine about problems. When a problematic situation arises, try to come up with a few solutions before going to your boss. This indicates your ability to solve problems and handle difficult situations when in a higher position.

Be Resourceful

Always voice any ideas you have which you feel may have a positive impact on the company. You do not need to have resources to be resourceful – make your voice heard, so everyone is aware that you have an opinion. In some situations, people are so confined in what they think that your solution may be the perfect one. Think outside the box of how you could help your company solve a problem and you will already be a step closer to getting a promotion. Remember, one of the best ways to thrive and to stand out is by doing your own thing, and opposing popular opinion.

Keep Networking

Networking is a fundamental part of developing a name for yourself and constantly growing in your professional career. In order to further your career, you must be prepared to tactically associate yourself to individuals in high positions. Never miss a corporate event, and maintain a positive attitude as these are noticed by everyone. These events are a chance for you to shine and demonstrate your strengths and abilities. Another advantage of networking is that you will learn much more about the company by speaking to people in other areas of the organization, hence expanding your skill sets.
****************************************************************************************************************************
Info.copy right from Rozee.pk

Tips on copying and backing up Group Policy Objects

Takeaway: Group Policy configuration is one of the most powerful aspects of Windows. Read several tips on copying and backing up Group Policy Objects, which can save admins a lot of time.

A cornerstone technology of Windows is Group Policy, which can be assigned locally (a single policy for a Windows system) or managed centrally in an Active Directory domain. When leveraging Active Directory, a number of Group Policy Objects (GPOs) can be assigned to computers and users.

I believe that GPOs are one of the most critical and powerful management tools available; that said, GPOs can also be complicated to work with. For instance, if you need to recreate a GPO, it may require a tedious maneuvering of screens to verify settings from one GPO to another. Fortunately, the Group Policy Management console allows us to do a few things to tackle this task efficiently. The first is a centralized list of GPOs for the entire domain, regardless of the Organizational Unit (OU) where they reside. This panel is shown in Figure A.

This console serves a number of purposes, but one that irritates me is nomenclature. Figure A is a screenshot of my personal lab, and I have not done a good job in naming the GPOs. Ideally, a GPO is self-documenting so that it tells you: what it does, where it lives, and who it applies to (users, groups, computers, etc.).

Please excuse my lab’s sloppy nomenclature, and let’s focus on the ability to copy and back up a GPO in this console. When we right-click the individual GPO, a very powerful context menu appears. (Note: This menu is not available where the GPO resides in terms of the OUs listed above; it is only available in the Group Policy Objects section.) This context menu is shown in Figure B.

The copy and backup options are the two tasks that can really save administrators a lot of time. The copy operation will take an existing GPO, and allow you to paste it into the Group Policy Objects section. This may not be intuitive, and Figure C shows where it becomes an option.

A new GPO is created as a copy of the source GPO, and it can be linked to an OU later. This can be very helpful when a GPO is built over time, but is not ready to be applied to the destination OU.

The ability to back up a GPO exports the GPO to an .XML file, which can be archived and used to recover a previous version of a GPO. There also is an option to back up all GPOs, which will make a large .XML repository in a specified folder path. In both situations, the ability to have the GPOs on outside of the domain controller can be attractive. While backup solutions can protect down to this level, simply for a quick check by hand, the backup options within the Group Policy Management console can be of great aid. Viewing the .XML file isn’t very helpful, but can be an easy way to spot-check settings (Figure D).

**********************************************************************************

info. shared from Rick Vanover@Techrepublic.com Jul 08, 2011, 11:11 AM PDT

Five tips for getting cable clutter under control in data centers:

Takeaway: Does your server room look like it’s ready for some marinara sauce and a few meatballs? Turn your cable chaos into a manageable system by following a few simple steps.

Nothing is worse than a datacenter filled with a tangled maze of wires. Besides being unsightly, cable clutter can make it difficult to troubleshoot cable-related problems. Here are five of my favorite tips for taming that cable mess.

1: Multitask

One of the best ways to get cable clutter under control is to eliminate any cables that are not absolutely necessary. Of course, this is easier said than done. Since you probably can’t go through your datacenter and start unplugging cables, the next best option might be to multitask.

Sometimes, you can achieve the functionality of several cables with a single cable. To give you an idea of what I mean, I recently installed an IP-based video surveillance system in my datacenter. The system was designed so that each of the eight cameras required its own power supply (AC adapter). After spending a little bit of time on Amazon, I found a power supply that could provide power to four cameras. Granted, I still had to use a few power supplies, but I cut the total number of power supplies I was using by 75%.

I’ve also been performing cable multitasking through my KVM switches. Up until a few weeks ago, I was using KVM switches that required a keyboard, video, and mouse connection to every server. I replaced these outdated switches with a new model that uses only a video cable. On the end of the cable that connects to the server is a USB connection for keyboard and mouse input. However, there is no USB connection at the other end of the cable. All keyboard and mouse input is sent through the video adapter and then split out into a USB port at the end of the cable. What previously required three cables is now done through a single cable.

2: Use the shortest cables you can get away with

Another clutter-reducing trick is to make your own network cables. If you use pre-manufactured cables, you’re stuck using cables with standardized lengths. This can result in excessive cable in your datacenter. By making your own network cables, you can ensure that the cables are cut to exactly the required length. This can go a long way toward cutting down on cable clutter.

3: Label your cables

I also recommend investing in a good label maker and labeling all the cables in your datacenter, even if the purpose of a cable seems obvious. Having well-labeled cables can make it far easier to troubleshoot cable-related problems.

The reason it’s a good idea to label the cables that are used for obvious purposes is that troubleshooting a problem can sometimes run late into the night. I can’t speak for anyone else, but I tend to make a lot of stupid mistakes when I start getting tired. I have found that making things as idiot-proof as possible helps prevent dumb mistakes later on.

4: Use zip ties sparingly

I once worked in a place where a number of servers were arranged on a large metal rack (not a traditional server rack). The person who had done the setup used zip ties to secure the various cables to the rack. I have to admit that the person did a good job keeping all the cables nice and neat.

But eventually, one of the computers started having trouble communicating across the network. It turned out that the network cable had been zip tied too tightly and the RJ-45 connector at the end of the cable was being pulled loose. Replacing the cable meant cutting all the zip ties and then replacing them. Because the zip ties bundled cables for multiple machines, this turned out to be a big job.

There is a time and a place for everything, and sometimes zip ties do have a place in the datacenter. However, before you zip-tie a cable, consider the amount of work that will be involved if you ever have to replace the cable.

5: Bundle excess cable

Earlier, I mentioned using custom-made network cables to avoid having excess cable. Sometimes, however, excess cable is unavoidable. For example, the AC adapter for my wireless access point has a three-foot cord, but I need only about a foot of it. When you can’t avoid using a cable that is longer than you need, bundle the excess cord. In the case of the power cord for my wireless access point, I used a twist tab around the excess cable.

**********************************************************************************

info. shared from Brien Posey@Techrepublic.com June 24, 2011, 9:27 AM PDT

Top 5 Fastest Growing Careers in IT

Top 5 Fastest Growing Careers in IT

Use a USB Flash Drive to create Windows Password Reset Disk in Windows 7

Use a USB Flash Drive to create Windows Password Reset Disk in Windows 7

Welcome Note!

Hi and Welcome to my newly launched blog.

First of all thank you for visiting and I will make sure that you don't return disappointed. My blog will majorly be filled up with learning stuff but don't worry as I know how to keep it interesting so you will surely find stuff which will extend your stay on my blog and will give you fun as well as learning. Have a nice and safe surfing...!