ABCO Technology

ABCO Technology - a computer training institute provides job training for all types of applications and software used in the real-world job environment. ABCO’s graduates are prepared to take on the challenges they will face in today’s job market. We endeavor to make our students employable in the field of IT as office managers, technicians, network administrators, developers, and webmasters. Our desire is to create value, earn trust, deliver results, exceed expectations, and empower people.

Tuesday, September 17, 2013

Cisco Certification Network Associate Wireless Exam

WIFI, 3G and 4G networks are rapidly changing how the public uses the internet. The Cisco Certified Network Associate with Wireless course trains information technology professionals to operate Cisco’s equipment, which serves the general public when accessing a wireless server. This article contains basic information about the job duties information technology professionals will perform after passing the CCNA Wireless certification exam.

Clients are an essential part of wireless networks. They require a specific section in CCNA Wireless because not all clients are the same. Wireless clients are differentiated by three types of characteristics:

•Wi-Fi client adapter: Most devices produced today come with built-in wireless adapters. Older devices can be outfitted with an external wireless networking card. Different cards might have different physical characteristics and capabilities.

•Wireless client software: Client software, such as the Intel ProSet, AirPort Extreme for MAC, Windows AutoConfig Service, Apple iOS, and Google Android, can be configured for the client to associate with an AP. Different software applications can have different feature sets and different supports for the underlying physical card capabilities.

•Client security settings: There are several possible security configurations to achieve wireless security. Some clients support only some security types, thus limiting the type of wireless network you can join.

Most clients enable you to associate to a detected network (broadcasted SSID) or configure a specific profile. In all cases, you must configure the network name (SSID), the operating mode (ad-hoc or infrastructure), and some security settings (that will be different depending on whether the SSID uses Pre-Shared Key Security or Enterprise [EAP/802.1x] security). The way each of these three items is configured (sequence, menu names, configuration possibilities) varies from one client to the next.

ABCO Technology’s Cisco Wireless course is a full hands-on class that prepares you to function in the wireless internet environment.

For more information visit us online @ ABCO Technology

Check us Out, We Are All Over the Web

Tuesday, April 23, 2013

PHP Redirect from a single page to the home page.

When we develop websites using PHP, we normally develop pages that are included in other pages. For example, the header.php or footer.php pages are included on the top and bottom of every page respectively, to avoid rewriting of these pages numerous times. However, a smart cookie could figure out these pages and go directly to them by typing their url in the browser window. A professional developer would take precautions to avoid this contingency and redirect any anonymous user visitor to the appropriate page. For example, if someone types www.yourdomain.com/header.php or www.yourdomain.com/footer.php etc. they should be redirected to the home page. PHP has no direct function to accomplish this task. However, the solution to accomplish this would be typing the following code at the top of the page:

$filename = __FILE__;
if(preg_match("/header.php/",$filename)){
header("Location:/");
die();
}

The first line of the code uses a PHP Defined Constant to obtain the name of the file and store it in a variable called filename. The second line of the the code uses an if statement and Regular Expressions to check if the url contains header.php, and redirects the user to the home page. Regular expressions are being widely used in Object Oriented Programming and Database Administration to perform advanced searches. ABCO Technology provides comprehensive training in it's PHP Module located within the CIW Program. Contact us at (310) 216-3067 to obtain enrollment information in our upcoming CIW Classes. For more information about the program, visit our website at www.abcotechnology.com

Tuesday, January 29, 2013

How to restore a Windows 2003 Server Domain Controller to an alternate location

Over the life cycle of a Microsoft Windows operating system, you may have to restore a system state backup that is installed on one computer to the same physical computer or even to a different physical computer. Recovery from the following events may require a restore operation:

hardware failure
software failure
computer theft
natural disaster
user error

You can restore a system state backup from one physical computer to the same physical computer or another computer that has the same make, model, and configuration (identical hardware).

Microsoft does not support restoring a system state backup from one computer to a second computer of a different make, model, or hardware configuration. Microsoft will only provide commercially reasonable efforts to support this process. Even if the source and destination computers seem to be identical makes and models, there may be driver, hardware, or firmware differences between the source and destination computers.

This article describes how to create a system state backup on one computer and restore it to the same computer or to a different physical computer of the same make and model. If you do not follow the steps in this article, you will reduce the probability of success when you restore to different hardware.
Windows Server 2003 Server

To restore Windows Server 2003-based computers , the preferred method of recovery is to use the Automated System Recovery (ASR) feature. ASR automates the whole restore process. This process produces the most reliable result.

The source computer is defined as the computer that you used to create the system state backup. The destination computer is the computer where you will restore the backup.

The following guidelines must be followed for the restore operation to succeed.

Hardware Abstraction Layer (HAL)

The source and destination computers must use the same type of HAL. There is one exception to this rule. If one of the computers contains the Advanced Configuration and Power Interface (ACPI) multiprocessor HAL, the other computer can have the ACPI uniprocessor HAL. The same rule applies to MPS multiprocessor and MPS uniprocessor HALs.

For example, if the source is using the MPS multiprocessor HAL, you can restore data to a destination computer that uses the MPS uniprocessor HAL. However, you cannot restore data to a destination computer that uses the ACPI multiprocessor HAL.

Note If the destination computer's HAL is compatible, but not identical, to the source computer's HAL, you must update the HAL on the destination computer after you finish the restore. For example, if the source computer has a single processor and is using the ACPI uniprocessor HAL, you can restore a backup from that computer to a multiprocessor destination computer. However, the destination computer will not use more than one processor until you update the HAL to an ACPI multiprocessor HAL.

To determine the computer HAL type that you are using on each computer, follow these steps:

Click Start, point to Settings, click Control Panel, and then click System.
On the Hardware tab, click Device Manager, and then expand the Computer branch.

ACPI multiprocessor computer = Halmacpi.dll
ACPI uniprocessor computer = Halaacpi.dll
Advanced Configuration and Power Interface (ACPI) computer = Halacpi.dll
MPS multiprocessor computer = Halmps.dll
MPS uniprocessor computer Halapic.dll standard computer = Hal.dll
Compaq SystemPro multiprocessor or 100% compatible = Halsp.dll

Operating system version

The source and destination computers must use identical operating system versions and identical Windows stock-keeping units (SKUs). For example, you cannot back up Microsoft Windows 2000 Server and then restore it on a computer that is running Windows 2000 Advanced Server. Also, the source and destination computers should both use retail versions of Windows or should both use the same OEM version of Windows. The best practice is to install Windows on the destination computer by using the same installation media that you used to install the source computer.

Filter drivers

Uninstall third-party filter drivers on the source computer before you perform the backup. These kinds of drivers can cause problems when the backup is restored to a different computer.
Windows folder and disk layout

The destination computer must use the same logical drive letter (%systemdrive%) and path (%systemroot%) as the source computer. For domain controllers, the locations of the Active Directory directory service database, Active Directory log files, FRS database, and FRS log files must also be identical for the source and destination computers. For example, if the Active Directory database log files on the source computer were installed on C:\WINNT\NTDS, the destination computer must also use the C:\WINNT\NTDS path.

Hardware

If you remove any hardware on the destination computer that is not required to complete the restore process, you increase the probability of a successful restore operation. For example, physically remove or disable all except one network adapter. Install or enable the additional adapters after you restart the operating system after the restore operation.

Hotfix and service pack level

For Windows 2000 computers, hotfix 810161 or Windows 2000 Service Pack 4 must be installed on the source computer before you back up data. These items must also be installed on the destination computer before you restore the backup. Windows Server 2003 and Windows XP have no hotfix or service pack level requirements for this kind of restore operation.

For Windows Server 2003, Windows XP, and Windows 2000

For client and member server computers, follow these steps to back up the Windows installation and restore it to a different computer. (A member server is any server that is not a domain controller.)

On the source computer, log on by using the administrator account, and then stop all noncritical services and services that you typically stop before you perform a backup. This may include any service that puts locks on files. This includes antivirus, disk scanning, and indexing services.
On the source computer, verify that the TCP/IP start value is set to 1. This value is located in the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
Value Name Start
Value Type REG_DWORD
Value Data 1

On the source computer, use Windows Backup to back up the system drive, the system drive subfolders, and the system state.

On the destination computer, perform a new installation of Windows by using the same operating system version as the source computer. Make sure that you install the operating system in the same drive and path that was used on the source computer. For example, if Windows is installed to C:\WINNT on the source, you must install to the same location on the destination computer

After the new installation is complete, log on to the destination computer as Administrator. By using Disk Management, create, format, and assign drive letters to any additional volumes that may be required to hold a system state component. Make sure that all drive letters match those of the source computer. Disk space for volumes on the destination computer should be as least as large as corresponding volumes on the source.

On the destination computer, create a C:\Backup folder. Put a copy of the C:\Boot.ini file and the whole %systemroot%\Repair folder, including all of its subfolders, in the C:\Backup folder for use in step 8. The Boot.ini file is in the root of the system partition (typically, C:\Boot.ini). The Repair folder is generally in the C:\WINNT\Repair folder or in the C:\WINDOWS\Repair folder.

To restore the backup on the destination computer, follow these steps:

Click Start, click Run, type ntbackup, and then click OK.
On the Tools menu, click Options, click the Restore tab, and then click Always replace the file on my computer.
Restore the system state from the backup that you performed earlier. Make sure that you select the option to restore to the original location.

Note To have access to all removable media (tape or magneto-optical disk) from the source computer after the restore operation is complete, you must click Restore Removable Storage Database under the Advanced button before you start the restore operation.

After the restore operation is complete, but before you restart the destination computer, follow these steps:
Copy the Boot.ini file from the c:\Backup folder that you created in step 6. Copy the Repair folder and its subfolders from the C:\Backup folder to the %systemroot%\Repair folder.

Reinstall the destination computer's hard disk controller drivers if third-party drivers are being used.
Verify that the source computer is turned off, disconnected from the network, or has been reinstalled by using a different computer name and IP address. (If the source computer had a static IP address, the destination computer will have that same static IP address after the restore operation.)
Restart the computer, and then verify that it is functioning correctly.

If the restored computer was a member computer or member server, test the security channel by using the NLTESTcommand:
NLTEST /SC_QUERY:<DomainName>

If SC_QUERY reports a failure condition, reset the security channel by using the following command:
NLTEST /SC_RESET:<DomainName>

If the destination computer is a member computer or member server, you may have to reset its security channel with the domain, depending on how recently the backup occurred. When you run the netdiag /test:trust command, the security channel relationship test will fail if the security channel is broken. The netdiag command is available when you install the Support Tools on the Windows installation media.

If the trust relationship test fails and indicates a failed security channel, you can run the netdom command on the destination computer to reset the channel. The netdom command is also available in the Support Tools. To reset the security channel, use the following netdom command:
netdom reset Destination computer /domain:domain_name usero:admin_user
/passwordo:admin_user_password

Note Destination computer is the destination computer. domain_name is the name of the domain. admin_user is the user who is a member of the administrator group. admin_user_password is the password of the user account.

For Windows Server 2003, Windows XP, and Windows 2000

For client and member server computers, follow these steps to back up the Windows installation and restore it to a different computer. (A member server is any server that is not a domain controller.)

On the source computer, log on by using the administrator account, and then stop all noncritical services and services that you typically stop before you perform a backup. This may include any service that puts locks on files. This includes antivirus, disk scanning, and indexing services.
On the source computer, verify that the TCP/IP start value is set to 1. This value is located in the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
Value Name Start
Value Type REG_DWORD
Value Data 1

On the source computer, use Windows Backup to back up the system drive, the system drive sub-folders, and the system state.
On the destination computer, perform a new installation of Windows by using the same operating system version as the source computer. Make sure that you install the operating system in the same drive and path that was used on the source computer. For example, if Windows is installed to C:\WINNT on the source, you must install to the same location on the destination computer.
After the new installation is complete, log on to the destination computer as Administrator. By using Disk Management, create, format, and assign drive letters to any additional volumes that may be required to hold a system state component. Make sure that all drive letters match those of the source computer. Disk space for volumes on the destination computer should be as least as large as corresponding volumes on the source.
On the destination computer, create a C:\Backup folder. Put a copy of the C:\Boot.ini file and the whole %systemroot%\Repair folder, including all of its subfolders, in the C:\Backup folder for use in step 8. The Boot.ini file is in the root of the system partition (typically, C:\Boot.ini). The Repair folder is generally in the C:\WINNT\Repair folder or in the C:\WINDOWS\Repair folder.
To restore the backup on the destination computer, follow these steps:

Click Start, click Run, type ntbackup, and then click OK.
On the Tools menu, click Options, click the Restore tab, and then click Always replace the file on my computer.
Restore the system state from the backup that you performed earlier. Make sure that you select the option to restore to the original location.

After the restore operation is complete, but before you restart the destination computer, follow these steps:
Copy the Boot.ini file from the c:\Backup folder that you created in step 6. Copy the Repair folder and its subfolders from the C:\Backup folder to the %systemroot%\Repair folder.
Reinstall the destination computer's hard disk controller drivers if third-party drivers are being used.
Verify that the source computer is turned off, disconnected from the network, or has been reinstalled by using a different computer name and IP address. (If the source computer had a static IP address, the destination computer will have that same static IP address after the restore operation.)
Restart the computer, and then verify that it is functioning correctly.

If the destination computer is a member computer or member server, you may have to reset its security channel with the domain, depending on how recently the backup occurred. When you run the netdiag /test:trust command, the security channel relationship test will fail if the security channel is broken. The netdiag command is available when you install the Support Tools on the Windows installation media.

If the trust relationship test fails and indicates a failed security channel, you can run the netdom command on the destination computer to reset the channel. The netdom command is also available in the Support Tools.

To reset the security channel, use the following netdom command:
netdom reset Destination computer /domain:domain_name
usero:admin_user/passwordo:admin_user_password

Note Destination computer is the destination computer. domain_name is the name of the domain. admin_user is the user who is a member of the administrator group. admin_user_password is the password of the user account.

Windows domain controller installation

For Windows Server 2003, Windows XP, Windows 2000

On the source computer, log on by using the administrator account, and then stop all noncritical services and services that you typically stop before you perform a backup. This may include any service that puts locks on files. This includes antivirus, disk scanning, and indexing services.
On the source computer, verify that the TCP/IP start value is set to 1. This value is located in the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
Value Name Start
Value Type REG_DWORD
Value Data 1

Use the Windows backup tool to back up the system drive and the system state. For Windows 2000, if Sysvol resides on a drive other than the system drive, you must also back up that folder and all subfolders. For example, if Sysvol is located in the D:\Sysvol folder, you must back up the system drive, the system state, and the D:\Sysvol folder.
Perform a new installation of Windows on the destination computer by using the same version of Windows as the source computer. Make sure that you install Windows to the same location as on the source computer. For example, if Windows is installed to the C:\WINNT folder on the source, you must install Windows to the same location on the destination.
After the new installation is complete, log on to the destination computer as an administrator. By using Disk Management, create, format, and assign drive letters to any additional volumes that may be required to hold a system state component or an application. Make sure that all drive letters match those of the source computer.
On the destination computer, create a C:\Backup folder. Put a copy of the Boot.ini file in that folder, in the %systemroot%\Repair folder, and in all the subfolders of the Repair folder. The Boot.ini file is in the root of the system partition. (This folder is typically the C:\Boot.ini folder.) The Repair folder is typically in the C:\WINNT\Repair folder or in the C:\WINDOWS\Repair folder.

If the source computer is the only domain controller for the domain, reinstall Windows on the source computer, or disconnect it from the network, before you restore the backup to the destination computer. We recommend those steps, because it is too easy for someone to turn the source computer back on. If someone turns on the source computer, name conflicts or other problems with the destination computer occur.
If the source computer is not the only domain controller for the domain, use the Active Directory Installation Wizard to remove Active Directory from the source computer. Then, either reinstall Windows on the source computer, or disconnect it from the network .
When you have confirmed that the source computer and the restored destination computer are not online at the same time, restore the backup by following these steps:

Click Start, click Run, type ntbackup, and then click OK.
On the Tools menu, click Options, click the Restore tab, and then click Always replace the file on my computer.
Restore the system state and the system drive from the backup that you performed earlier. For Windows 2000, you must also manually select the Sysvol folder to be restored. The system state includes Sysvol. However, there is an issue in Windows 2000 that prevents the Sysvol junction points from being restored correctly if you restore only the system state. Make sure that you select the option to restore to Original location.

After the restore operation is complete, but before you restart the destination computer, follow these steps:
Replace the Boot.ini file and the %systemroot%\Repair folder that has the copies that you made in step 6.
Reinstall the destination computer's hard disk controller drivers if third-party drivers are being used.
In the TCP/IP settings, verify that the computer is configured to use a Domain Name System (DNS) server that is authoritative for the domain and that is currently online. Do not configure the server to use itself for DNS because the DNS records in the backup may no longer be valid. When the restore operation is complete, and when you have verified that the destination computer is functioning correctly, you can configure the server to use itself for DNS.
If the destination computer will be the first or only domain controller for the domain, follow these steps to authoritatively restore the File Replication Service (FRS). This step must also be complete before the first restart after the restore operation is complete.

Warning Do not follow these steps if there are existing domain controllers in the domain.

Click Start, and then click Run, type regedit, and then press ENTER.
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Replica Sets
Expand Replica Sets, identify the subkey that refers to the replica set DOMAIN SYSTEM VOLUME (SYSVOL SHARE).
Then find the subkey of the Cumulative Replica Sets subkey that matches the name of the subkey from the previous step.
Expand Cumulative Replica Sets, click the subkey that represents the Sysvol replica set, double-click BurFlags.
In the Edit DWORD Value dialog box, type D4, and then click OK.
Restart the computer.

Restart the computer and verify that it is functioning correctly by using the dcdiag and netdiag commands. For more information about how to use the dcdiag command, click the following article number to view the article in the Microsoft Knowledge Base:
265706 Dcdiag and netdiag in Windows 2000 facilitate domain join and DC creation

If there are existing domain controllers in the domain, you may have to reset its security channel, depending on how recently the backup occurred. If the security channel is broken, the netdiag /test:trust command will indicate that the trust relationship test failed. If the trust relationship test result indicates that the test was skipped, you can safely ignore the results. This result indicates that the computer that you are running the test on has the PDC emulator operation master role.

If the trust relationship test fails, you have a failed security channel. To fix this, run the netdom command on the destination computer to reset the security channel. To reset the security channel on a domain controller by using thenetdom command, follow these steps:

Stop the Kerberos Key Distribution Center (KDC) service, and set it to Manual startup.
Run the following command to reset the security channel:
netdom resetpwd /server:replication_partner_server_name /userd:domain_name\admin_user/password:admin_user_password

Note replication_partner_server_name is the name of the replication partner server. The command must be running locally on the destination computer.

Restart the computer, start the KDC, and then set it back to Automatic startup.
Make sure that you verify that replication is working if there are existing domain controllers in the domain.

Troubleshooting

After you restart the destination computer, you may experience the following symptoms:
You receive one of the following Stop error messages:

Stop 0x0000007B Inaccessible_Boot_Device
STOP: 0x00000079 Hal_Mismatch
The computer stops responding at startup.
The computer that is running Windows Server 2008 crashes on startup. This occurs when the source HAL and the target HAL do not match.
The computer spontaneously restarts when you receive the following message on a black screen early in the restart process:
Starting Windows 2000
You cannot configure your display settings.
The network adapter does not function correctly.

To resolve issues with the display settings or with a network adapter, remove the graphics adapter or the network adapter from Device Manager, and then restart the computer. Windows will redetect the device and possibly prompt you for drivers.

To resolve the problem when the source HAL and the target HAL under Windows Server 2008, follow these steps:

Click Start, right-click Command Prompt, and then click Run as administrator.
Run the following command: bcdedit /set GUID_identifier detecthal yes
To resolve the Stop error or the problem where a computer stops responding, perform an in-place upgrade of Windows.

Sunday, January 13, 2013

Should we Upgrade to Windows 8?

This is the general question about Windows 8 currently among IT professionals. Here are a few questions answered with respect to Upgrades. For additional questions or training please contact ABCO Technology at (310) 216-3067 or email us at info@abcotechnology.com.

Windows 8 Release Date?

Windows 8 is set to be available since October 26,2012. If you plan to upgrade to Windows 8 yourself, you should know a few things first so that you make the correct decision. I have prepared a list of questions that could be running in your minds and I hope that the answers will satisfy you. Read on.

What are the Different Versions?

Microsoft did well in removing the version clutter and sticking to only three versions- Windows 8, Windows 8 Pro and Windows RT. There is a fourth one, Windows 8 Enterprise, but that would be with large-volume corporate PC purchases only.

To choose which one suits your requirement you may want to read the details and features that comes with them.

What Can You Upgrade From?

An update from the Windows Blog says that consumers will be eligible to upgrade to Windows 8 Pro if their computer is already running Windows XP, Windows Vista, or Windows 7.

Is Upgrade Available at $39.99 Only?

The pricing of the update has been kept quite decent. All those running the above operating systems will be eligible to purchase a downloadable upgrade from Microsoft at the rate of $39.99.

Well, if you have bought a Windows 7 PC (Home Basic, Home Premium, Professional, or Ultimate) after June 22, 2012 or plan to buy one through January 31, 2013 then the good news is that you will have to pay only $14.99 (offer will remain valid until February 28, 2013) for the upgrade.

When Can You Upgrade?

Windows upgrade offer registrations are already available and you can queue up by visiting the Windows Upgrade Offer website. However, it is for purchases made between June 22, 2012 and January 31, 2013.

The actual upgrades have been rolled out after October 26,2012 wherein you can either purchase one for $39.99 or redeem the $14.99 offer.

Should I Download or Buy?

If you wish to buy a packaged DVD version of Windows 8 Pro, it will be available for $69.99 (during the promotion period) at the local stores.

Otherwise you can create your own bootable Windows 8 USB or .ISO file which can be burned onto a DVD. You can also purchase a backup DVD for $15 plus shipping and handling.

What Hardware Support is Required?

The basic requirements from Microsoft are as follows:

    1 GHz or faster processor
    1 GB RAM (32-bit) or 2 GB RAM (64-bit)
    16 GB available hard disk space (32-bit) or 20 GB (64-bit)
    Direct X 9 graphics device with WDDM 1.0 or higher driver

What Comes Along from Previous Versions?
Before you upgrade, please make sure that you thoroughly backup all your files and applications. In addition, you must know what comes along for which versions.

Windows 7: Windows settings, personal files, and apps.
Windows Vista: Windows settings and personal files.
Windows XP: Only personal files.

Of course, if you want you could always start from zero and begin by formatting your hard disk. Besides, the Compatibility Center will generate a report for items that require attention later.

Bonus Tip: If you are interested in what Windows 8 has within then you should check out the top 10 features that it will bring. Also learn about Essential Windows 8 Apps.

Conclusion

I have tried to cover the important points like dates, costs and requisites, however, I may have missed on specific question that you’re not able to find answer to. Jot them down in the comments section below and I will try to find the correct answer to it or send us an email at info@abcotechnology.com. You may also visit our website at www.abcotechnology.com

Overall, try to research as much as possible, backup your data appropriately before you upgrade.

Wednesday, January 9, 2013

MCSE 2012 Training and Certification Track at ABCO Technology

MCSE: Server Infrastructure

Solutions Expert

The globally recognized standard for IT professionals

The Microsoft Certified Solutions Expert (MCSE): Server Infrastructure certification validates that you have the skills needed to run a highly efficient and modern data center, with expertise in identity management, systems management, virtualization, storage, and networking.

Step	Title	Optional training	Required exam
1	Installing and Configuring Windows Server 2012	410	410
2	Administering Windows Server 2012	411	411
3	Configuring Advanced Windows Server 2012 Services	412	412
4	Designing and Implementing a Server Infrastructure	413	413
5	Implementing an Advanced Server Infrastructure	414	414

This MCSE certification requires you to show continued ability to perform in your chosen solution area by completing a re-certification exam every three years.

Thursday, October 4, 2012

The New MCSE Certification and MCITP

The re-invention of MCSE back, has spawned a number of questions and concerns among students. Many students and IT professionals have contacted ABCO Technology with questions regarding the status of the MCITP Certification. I have spent a lot of time researching as much information as possible on this, and have had multiple discussions with the Microsoft Learning team to make sure that we’re sharing the most correct, up-to-date information with you. If you’re confused about the new MCSE or have questions, please contact us at (310) 216-3067 or visit our website at www.abcotechnology.com

Here is where I'll begin with what we know.

All existing Windows Server 2008 MCITP: Server Administrators and MCITP: Enterprise Administrators have been granted the new MCSA certification for Windows Server 2008.
The Windows Server 2008 MCSA is a requirement to achieve the new MCSE: Private Cloud certification.
The MCSE: Private Cloud certification is the only MCSE certification which will be associated with Windows Server 2008.
MCITP: Enterprise Administrator will remain the premier certification for Windows Server 2008.

What exactly is the new re-certification process?

According to a historically reliable source at Microsoft, the new MCSA certifications will NOT have to re-certify because they are product specific.
According to the same source, the new MCSE certifications will have to re-certify every 3 years, but they are looking to simplify the re-certification process.
The explanation for creating the 3 year re-certification is that the new MCSE is not designed to be “product specific” and Microsoft sees the industry moving to a cloud based model where software and services are updated frequently.

Will Microsoft have a lineup of MCSEs?

Microsoft claims to have an entire lineup of MCSEs which will be release in the near future.
Many people seem to be complaining that there is not a premier level certification which is product based for the upcoming Windows Server 2012.
Microsoft representatives are asking us to stay tuned; they believe that IT pros will all be very satisfied with the MCSEs they are going to release based on Windows Server 2012.

Let us sum it all up...

Now here’s my current overall opinion about the new certification program and how I think IT professionals should be approaching it. Overall, I am very excited about the return of the clearly branded MCSA and MCSE certifications. It clearly has a name beyond recognition amongst employers and IT professionals. If anything, I think Microsoft should have brought it back sooner. I like the fact that Microsoft has included the MCSA in the Windows Server 2008 lineup, but wish they would have come up with a better MCSE solution on Windows Server 2008 than the Private Cloud certification.

That being said, I would recommend existing MCITP professionals, especially the ones who are half way down the road to not panic and continue on their path. We all have to wait and clearly see by the beginning of next year to really see the certifications that Microsoft releases with Server 2012. Microsoft’s certification program has been around and very successful for 20 years now, and that doesn't happen by accident. I see no reason to believe it is going anywhere. Yes, I’m sure there will continue to be hiccups along the way, but Microsoft takes their certification program very seriously and will make sure it continues to succeed for many years to come.

If you are currently working toward a Microsoft certification then my clear advice is that you continue to stay the course and essentially pretend that nothing has changed. I have seen many of these types of revisions to certification programs and this is the same advice that I have always given throughout the years. I have never had a single student come back and tell me that they regretted continuing their quest toward certification. Certification has played a huge role in the correct placement of IT professionals in their careers and I don’t see that changing any time soon, even with the introduction of the new MCSE.

If you are looking for training, then I strongly suggest you contact ABCO Technology as quickly as possible and schedule your classes for MCITP before they run out. You can visit our website for more information www.abcotechnology.com or call us at (310) 216-3067.

Sunday, September 9, 2012

What is MCSE?

The MCSE or Microsoft Certified Systems Engineer began as a network certification in the late 1990s. As the field of information technology advanced, employers needed a method of documenting a potential employees knowledge in the networking field. Microsoft and other information technology manufacturers and venders believed strongly in the importance of providing a knowledge based training curriculum, which was designed to raise the level of technical efficiency for networking professionals who work on Microsoft servers.

The MCSE in its past form consisted of 7 exams composed of mandatory and elective tests. The older version of the MCSE was flawed because students received two certificates for passing the entire curriculum. Under MCSE exam rules students received the MCP/Microsoft Certified Professional, which was granted for passing one Microsoft exam and the final MCSE, which students received after passing 7 tests. The problem with this system was students passing exams for the five subjects between the MCP and MCSE could not document their newly acquired knowledge. Microsoft fixed this problem with the introduction of the MCITP in 2008. In 2008 with the introduction of new servers Microsoft decided to retire the MCSE and replace it with the MCITP, which is the Microsoft Certified Information Technology Professional. The new MCITP was composed of five exams. A key difference in the new certificate was a student received a certification for each exam passed. The additional certificates provided documentation for new skills. Under the new MCITP a student will receive certificates for passing exams in Active Directory, network infrastructure, and server configuration along with other Microsoft modules. The advantages for the new MCITP is that employers can document each area of a potential or current employees achievement in a particular field of information technology.

In 2012 Microsoft announced the return of the MCSE in a new form, which is cloud based. The exam structure is similar to the older version of Microsoft’s MCSA, which was the Microsoft Certified Systems Analyst. Under the new MCSE applicants will pass four exams in cloud based subjects. As of this date the new MCSE hasn’t achieved popularity in the information technology field. The new MCSE has generated confusion, especially with new candidates who are preparing to enter the field. We believe it will be some time before the smoke clears. We will be providing more information about the resurrected MCSE in future articles.

If you would like to receive additional information beyond the scope of this article, please email or contact ABCO Technology. Our school offers small Microsoft certification classes with full hands-on instruction.

Check us out we are all over the Web!