Does MCP Certifications Expire?

Microsoft Certifications do not expire. They simple lose value with time. For example, an MCSE on Windows NT 4 was all the rage in 1998. In 2009, that certification will not go far in a job interview. Microsoft publishes "upgrade" exams to help keep you up to date in your certification. The upgrade exams test you thoroughly on the new features of the OS. If you were starting for scratch or with a very outdated MCSE, you will have to take all the exams. This will not only test your knowledge of the new features, but also the basics that the certification requires.

Here is a little Q and A I pulled from a Microsoft site:

Q. How long will the certification be valid?

For our newest credentials, such as Microsoft Certified Technical Specialist (MCTS), Microsoft Certified IT Professional (MCITP), and Microsoft Certified Professional Developer (MCPD), the credential retires along with the product support for the technology being tested. The credential will still appear on your transcript but will be listed as retired. In most cases, an upgrade path (usually one exam) will be available for individuals who have that credential so that they can demonstrate their skills on the newest version of the technology without completing all exams associated with the new credential.

The legacy Microsoft credentials, such as Microsoft Certified Systems Engineer (MCSE) and Microsoft Certified Systems Administrator (MCSA) do not expire, but as Microsoft releases new versions of the associated technology, these credentials are likely to be valued less by the industry.

Q. Do hiring managers really value certification?

During a recent poll of IT hiring managers, 55 percent said that they consider employee certification as a criterion for hiring, and 63 percent of hiring managers said that they believe certified employees are more productive than noncertified employees.

http://www.microsoft.com/learning/en/us/certification/cert-get-started.aspx

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog