Reading through my RSS feeds I found an article from ExtremeTech comparing routers and switches and how most home based routers, i.e. Linksys, D-Link, are not really routers.

Here’s my favorite quote:

“…it is technically incorrect to call most home routers, well, routers. I’m about to go off on a rabbit trail here, but this can be a fun piece of trivia to stump your local tech store rep with…(or not).”

Now, I’ve only been doing this for 13 years, but the author of the article is completely incorrect.  His reasoning that these “routers” aren’t routers is because they don’t use routing protocols such is BGP, OSPF, RIPv1, RIPv2 etc.

“Most home routers do not run any routing protocols (EIGRP, BGP, OSPF, etc). Some do support RIP for very basic networks, but RIP is not needed for home use (as you only have one routable IP address issued to you by your ISP), and your ISP, and the Internet for that matter, know where to find you.”

I may just be argumentative today, but these routers ARE routers.  Why, do you ask?  They do not run any routing protocols, but inherently connect one network (an internal network) to an external network (the Internet).  They have an internal ROUTING table that routers use because they ROUTE traffic between two separate networks.  This is the true definition of routing.  The existence of routing protocols has no bearing on a Linksys home router being a router, considering that they have ONE static route based on information it receives from the ISP.

If you want to be more technically informed, these home routers are a basic OSI Layer 3 switch, which has ROUTING functionality.  They have ONE static route based on the DHCP address that the router receives via the ISP.  The router uses the DHCP packet to collect the IP address, subnet mask and default gateway.

Yes, everyone, it IS a router.  And a switch.

Popularity: 5% [?]

{ 0 comments }

How To Design Your AD Structure Made Simple

by Jason on February 27, 2009

ADWindows Server 2008 Differences

Active Directory (AD) in Windows 2008 is not changed very much from Windows 2000 or Windows 2003, at least not in a visual or design sense.  There have been continual improvements in AD since the start and Windows 2008 incorporates many changes that enhance Active Directory.  Among others, Windows Server 2008 boasts two excellent new features to AD, ignoring the increased functionality in Group Policy Objects (GPO).  This article will assume you are familiar with AD Organizational Units, Trees, Forests and other nomenclature.

Active Directory Domain Services replaces Active Directory.  Microsoft, in a great move, removed AD services from being integrated directly into the OS.  This allows ADDS to be restarted without having to restart the server.  No longer will administrators need to boot into AD restore mode to defragment the database.  Now the services can be stopped, the database defragmented, and the services started without having to reboot the system.

Other changes to AD are Fine-Grained Password Policies allowing a higher level of control over password criteria between users.  AD Lightweight Domain Services replace Active Directory Application Mode (ADAM).

Windows 2008 Server also introduces the Backup Domain Controller, I mean Read-Only Domain Controller, that contains a Read-Only copy of the Active Directory Database and only authenticates a specific set of users or groups specified by the administrators.  This reduces the risk of having a domain controller at a remote site with a read-write copy of the database that could be exploited.  Combine RODC with BitLocker and you have a well-protected Read-Only database that is hardened against attack or corruption.

Active Directory Design Made Simple

AD design can be as complex or as simple as you want it to be.  The key to AD is that once a design is in place it’s hard to simply change without detrimental impact to the business.  Good design work at the beginning is crucial.  If you are inheriting an AD that was created incorrectly, or inefficiently, you will need to take a lot of time reviewing the configuration, GPOs, security rights, etc until you have effectively mapped out the key elements and drafted a new design, along with all of the steps to get there.

There are two basic styles to Active Directory design.  Geography based or Organizational based.  Some organizations have a “hybrid” design but at the end, you either start based on geography or start with the organization.

Geography Based Active Directory Design

Based on physical location, the design is focused around nations, states, principalities, provinces or cities.  If you have a small organization this may be simple to setup and design.  The larger the company the more complex your AD may become due to political considerations.

CompanyABC.com
CompanyABC.com/New Mexico
CompanyABC.com/New Mexico/Marketing
CompanyABC.com/New Mexico/Design
CompanyABC.com/New York
CompanyABC.com/New York/Marketing
CompanyABC.com/New York/Design

Organizational Based Active Directory Design

Simply said, the structure of the organization determines the structure of AD.  Organizational Units may be based on departments, or locations and departments.  There are no real best practices on how deep your OU structure can go, but I prefer to have no more than three-to-four OUs nested for ease of administration.

CompanyABC.com
CompanyABC.com/Marketing
CompanyABC.com/Marketing/New Mexico
CompanyABC.com/Marketing/New York
CompanyABC.com/Design
CompanyABC.com/Design/New Mexico
CompanyABC.com/Design/New York

Flexibility in your AD Structure

The structure that you choose should be flexible.  Considering that your business may be acquired, or acquire other companies, means that your simple structure could become quickly become a Forest and no longer a Tree.  Personally, if I have the resources I prefer to start the root of my own forest, as Forests can trust Forests via Active Directory Federated Services.  The root of my forest is not used for anything else and administration is limited to very few individuals to be Enterprise Administrators.  My “working” domains are subdomains of my root domain.  There is additional cost in doing this to support the equipment for the root domain.

CompanyABC.com
noram.CompanyABC.com
noram.CompanyABC.com/New Mexico

CompanyABC.com
noram.CompanyABC.com/Marketing
normal.CompanyABC.com/Marketing/New Mexico

Active Directory Design is highly dependent upon the culture and disposition of the business.  There may be political disputes that require resolution to properly design your network.

Other considerations are remote offices, intersite replication, Universal Group replication, use of Read-Only Domain Controllers, placement of Global Catalog servers and bandwidth between locations.  All of these must be considered while planning your domain strategy.

In Summary…

There are two main ways to design your AD structure, by the geography of the organization or by the organization of the different business units.  Each strategy requires careful design and preparation work to ensure that you have a flexible model and optimal server placement.  Keeping that goal in mind, work with the business to determine what strategy will be best for the organization and create detailed planning and implementation documentation for the deployment.

Popularity: 36% [?]

{ 0 comments }

Blerg

by Jason on February 27, 2009

I wrote a huge post about Twitter at the workplace and then had a browser error and lost an hours worth of typing.  For some reason there’s no history or revisions in WordPress either.  I will retype later.  Frustrated, ftl. =)

Popularity: 1% [?]

{ 0 comments }

My Leadership Core Values

by Jason on February 26, 2009

Values are strength

Values are strength

Values are defined as:  a person’s principles or standards of behavior; one’s judgment of what is important in life.  Your values are based on your beliefs, created from your feelings and experiences.  I believe that not only do we have personal values that we hold dear to ourselves, but we have values that impact our work life.  We display these every day through our actions.

I have three values that I follow when it comes to everything I do.  My personal goal has to always instill these into my team, no matter how far up, or down they were in the organization.  Leaders have one of the most important roles in the organization and their values and actions display to their teams who they really are.  It’s important to stay focused on the essentials and lead teams honestly and with integrity.

Never Ask Them To Do Something You Won’t Do

Simple and to the point.  Never ask someone to do something you aren’t willing to do.  Lead from the front and take the risks WITH the team and don’t make them take the risks for something you won’t have a hand in.  Sharing in the triumphs, or failures of the team, shows your determination and belief in the team and improves the morale of everyone involved.

Learn or Teach Something New Every Day

I love learning and I love teaching.  Being able to help reinforce new skills in someone else is a great way to mentorship someone.  Not only that, when people learn they feel more confidant and secure in their job.  By learning new skills, and passing them on, both you and your team grows professionally.

Leave It Better Than You Found It

This final value is probably my favorite.  Leave it better than you found it.  Seek continual improvement in what you do and what your team does.  If it’s broke don’t fix it, but if it is something that needs improve, do so.  Don’t delay, start making small changes and improve whatever you are doing it.  Add value to what you do by taking accountability and giving responsibility for these changes to occur.  Build momentum with continual improvement and give your teams the authority and responsibility to leave their mark.  People crave ownership and knowing that they make a difference.  Give them the chance.

In Conclusion…

Good leaders are at the front, teaching and mentoring their people.  The continually seek improvement in themselves, in their teams and in their work.  Don’t be afraid to step up and drive yourself to the next level.   Get out of your comfort zone and seek those challenges.

Don’t be afraid to leave a comment with your personal values. I look forward to hearing from you!

Popularity: 100% [?]

{ 0 comments }

iPhone App Usage

by Jason on February 23, 2009

iPhone

iPhone

As seen on Gizmodo.  I have had experience with this personally.  I love my iPhone but most of the apps aren’t on my phone very long.  Free apps don’t last very long and even paid apps have a short lifespan on my iPhone.  The graphs at Gizmodo validate that I am not alone.

I have several friends that fill their iPhone up with apps and games but rarely use them.  It’s ironic that people who want a clean computer desktop want their iPhone buried with junk.

I’ll save my App Store rant for some other time I think.

Popularity: 1% [?]

{ 0 comments }

How To Build A Solid Process

by Jason on February 23, 2009

SLDC Process Flow

In my previous post I discussed why I hate processes and frameworks.  In all fairness, I don’t hate them for what they are, I do not see value in creating processes for the sake of having them.

The Facts…

Let me give you an example:  Company A has been notified that they need a Configuration and Change Management (CCM) process by their auditing company to have compliance with XYZ standard.  Company A is a software develoment firm and has had these processes in place, only not well documented.  Company A implements a full blown CCM software solution to track and approve all changes and deploys it out to the organization.  Within months the employees are overwhelmed by the complexity of the software, don’t understand the models and discouraged by having to manually perform work that should be done by the system.

Has This Happened To You?

Does this sound familiar?  This could be any process or project that becomes overly complex and actually HAMPERS productivity when it should have been speeding up the process and giving developers and staff more time to perform the work.  Not only does this have a negative effect on morale, it makes the business lose money.  Businesses are in business to generate revenue and not burn cash.  We all want profits and that is where good process design fits in.  For simplicity sake, ahem, we’ll use CCM as the process we are reviewing throughout this article.

How To Build A Process

A good process is the building block to any team or function.  Every team already has a process for how certain tasks are performed on a day-to-day basis.  Like a good house with a solid foundation, solid processes are the bedrock upon which your team or business is built.  Below are the seven steps required to build or enhance any new or existing business processes.

1.  Identify the current process
2.  Determine Best Practices
3.  Perform a gap analysis
4.  Draft the new process
5.  Organizational Review
6.  Implement new and improved process
7.  Review and adjust accordingly

Identify The Current Process

Your business already has a process for everything they do.  If they don’t, I’m surprised you’re still in business.  That would be constant chaos.  Everything your business does, from how the bathrooms are cleaned to how performance reviews are accomplished, is a process.  There’s a workflow, or series of steps, that leads from the beginning to the end.  Sit down and look at what the process currently is.  Talk to the business owners, team members and identify what is currently in place.  Document the process in it’s simplest, basic form and have the key players review it for accuracy.  You must know what the end goal should be and keep that in mind as you move forward.

Determine Best Practices

Chances are, everything you are trying to do has been done by someone else.  Not only has someone done it before you did, someone else probably did it better than that other guy did.  Over time, hundreds or thousands of companies have done the same thing and somewhere along the line somebody else developed a standard set of best practices.  Examples are ITIL, COBIT and SDLC.

Best Practices are your best friend.  There’s no point in recreating the wheel and spending money that doesn’t need spent.  Following best practices for your processes will put you in line, or ahead of competition and help your business grow on a solid foundation.  Look at your business process and compare it to the best practice for that process.  That leads us to the next step.

Perform A Gap Analysis

Now is your chance to create positive change.  Review your process and compare it to the best practice.  Go step-by-step through your process and see how it fits into industry best practices.  In some cases the best practice may not be the right fit for your business.  Not because it doesn’t work, but because it is too expensive or not the right fit for right now.  Leave your current process flexible enough to incorporate this and add improvements where possible.

Draft The New Process

Now that you have reviewed your process and brought it in-line with best practices, it is time to document your work.  Use whatever program you want but diagram it out.  Personally, I prefer to whiteboard my changes first and make any adjustments before I commit it to digital form.  Be sure to add supporting documentation, budgetary figures, sales examples, etc to your documentation.  Keep your diagram simple and your support information more complex.  People, particularly management, prefers to see something simple upfront with more detailed information available to support the new process.

Organizational Review

You are ready to hand the process over to the business to review.  First, the management team needs to be brought in and made aware of the new process.  Executive buy-in is the most important step in process change.  Without the management team on your side the rest of the business will not fall in line and support the new process.

Not only must management agree and support the change, but the team leaders and their teams must also accept the new process.  This may take days, weeks or months to accomplish through various meetings and presentations.  The people doing the work must believe in the process and embrace it as positive change.  Your job as the leader is to show that to them with concrete facts.

Implement The New And Improved Process

This is where the rubber meets the road.  Now that everyone has bought in to the new process it is time to implement it.  At this time you should have determined key milestones or key performance indicators for your process.  You must be able to quantify your new process in a tangible way, be that via revenue, saved time, etc.  Set a realistic goal and a stretch goal for your process improvement.  A good rule of thumb is to use a quarterly goal as a performance indicator if your process change is on track.

Review And Adjust Accordingly

Positive change happens with help and assistance.  You have put your new process change in place and have monitored your key performance indicators.  Quarter over quarter your improvements haven’t been as big as you anticipated.  It’s time to take a look at the process and make any adjustments.  What to adjust?  Get feedback from the team and see if there are any inefficiencies that have cropped up.  Use that feedback to make tweaks or adjustments to your process and continue to monitor it over time.

Where To Go From Here?

Process improvement is a continuous effort in any business.  The business climate changes, as do best practices and governmental/industry compliance.  It’s important to perform a review of your business processes and how it is impacting your team.  Setup a feedback loop with your team leaders and teams to keep in touch with what is working and what isn’t.  Positive change grows over time, time a snow flake turning into an avalanche.  Look at making small, gradual changes over time.  This will have the most impact on the business and help create momentum upon which your teams will grow.

Popularity: 2% [?]

{ 1 comment }

Why I Hate Processes and Frameworks

by admin on February 22, 2009

Process Flow

Process Flow

Let me be frank.  I love process and change management but I hate process flows.  Confusing, eh?  Well, not really.  To be completely honest, a well-designed business process works wonders for an IT professional.  Not only do they show all of your inputs, outputs and decisions, but they also define responsibility.  Responsibility leads to accountability and I’m in favor of that.

Now, to what I hate about process flows.  I hate process flows that are forced into place against business or best practice.  Particularly processes that are implemented for the sake of having a process.  This is bureaucracy at its’ finest.

Every organization needs to identify frameworks that apply to them and validate which portions work for their business.  Most frameworks, including the ITIL (Information Technology Infrastructure Library) are designed to be implemented in pieces that are customized.  They are not a one-size fits all solution.  Implement the pieces that apply to your business and look at implementing other pieces when your business needs it.

In many instances, organizations want to follow ITIL without any real knowledge of what that entails.  Thousands of dollars are spent implementing processes without an end goal in mind for the sake of “best practice.”  The end goal must be determined by the business before frameworks are put in place.  You get out of a system or process what you put into it.  One of the largest drivers of frameworks are governmental or industry compliance.  Many times I have seen compliance auditors push a process or improvement without guidance to the business.

Simply said, if you automate a BS process, you get BS at the speed of light.  This doesn’t matter if you’re a small business or a Fortune 500 company.

In my next article I will discuss how to put a process in place that will be more easily accepted by the business and embraced by your teams.  Not only can your team flourish when following good, solid practices, but your productivity will increase, and not decrease, like I have seen.

Popularity: 2% [?]

{ 1 comment }

An Introduction

by Jason on February 22, 2009

I’ve decided it’s time to separate my personal blogging from my technical, more geeky blogging.  Most of my posts on Likertland.com are of a personal nature and more interesting to those who have a personal relationship with me and my family and less of an interest in my tech writing.

So consider this my new “professional” writing home.  I’ll continue to update Likertland.com regularly but this will be my home-away-from-home.  I look forward to it!

Please feel free to drop comments or contact me via the contact page.

Thanks!

Jason

Popularity: 1% [?]

{ 0 comments }