fixing a Windows universal audio architecture error

First Step is to make sure all instances Realtek Audio
and its associative softwares are
uninstalled from add remove programs and device manager.
This includes Intel High Definition audio.
On your PC change the CSDVersion registry key to Windows XP SP2:
HKLM\SYSTEM\CurrentControlSet\Control\Windows\CSDVersion value=200
This problem arises as the patch thinks that SP3 includes a
better version of the patch itself and hence doesn’t install itself.

3. Download the latest drivers from the Intel website,
navigate to the KB888111 patch.

4. But before installing the patch, goto your device manager and
disable the UAA.
Now uninstall the UAA.

5. Install your patch now.

6. Install the Realtek drivers now and things should work.

7. Change the SP version to 300 again.

If it didnt work, try once again. I can enjoy 7.1 channel
high definition sound
from my Intel Original motherboard now. Realtek HD Audio
now works fine.
Hopefully Error 0xE000027 is fixed now.

Day Two

Today i installed my first client machine unsuccessfully, the problem contrary to my opinion lay not with me but with the company server, im looking forward observing and getting hands on with the rectification of it.

MDT is a very expansive program from Microsoft with endless pre-install possibilities for a network administrator.

It enables a pre-execution environment to be simplified and clients can either be added in its library or alternatively in the Active Directory

i hope you find this intro productive to your organization as a start
Introduction
Microsoft® Deployment Toolkit (MDT) 2008 delivers end-to-end guidance for the efficient planning, building, testing, and deployment of Windows® operating systems, the 2007 Microsoft Office system, and Microsoft Office 2003. MDT 2008 provides proven tools and practices with which information technology (IT) personnel can:
· Create a software and hardware inventory to assist in deployment planning.
· Test applications for compatibility with Windows operating systems and mitigate compatibility issues discovered during the process.
· Set up an initial lab environment with imaging and deployment servers.
· Customize, package, and deploy applications.
· Automate image creation and deployment.
· Manage processes and technologies to produce comprehensive and integrated Lite Touch Installation (LTI) and Zero Touch Installation (ZTI) deployments.
· During deployment, migrate users’ documents and settings to their new computer configurations.
· During deployment, support the installation of all roles, such as Active Directory® Domain Services (AD DS), Domain Name System (DNS) server, Dynamic Host Configuration Protocol (DHCP) server, Microsoft Internet Information Services (IIS), Windows Deployment Services, Windows SharePoint® Services, Windows Internet Naming Service (WINS) server, and Windows Server® 2003 Terminal Services.
· Additionally, MDT 2008 supports the configuration of the AD DS, DNS, and DHCP roles.
· Ensure that computers are hardened to improve security within the environment.
MDT 2008 brings together time-honored and proven practices in addition to the following Microsoft technologies:
· Application Compatibility Toolkit (ACT) version 5.0 for gathering application inventory and for testing and mitigating application-compatibility issues.
· Windows User State Migration Tool (USMT) for migrating user settings and data.
· Windows Automated Installation Kit (Windows AIK) for configuring unattended Setup answer files (Unattend.xml) and capturing images.
· Windows Deployment Services for starting Windows Preinstallation Environment (Windows PE) on target computers across the network.
· Windows PE version 2.0 for starting computers.
MDT 2008 contains guidance, sample templates, and technology files (such as scripts and configuration files). MDT 2008 documentation discusses in detail required software that must be downloaded from the Internet. The documentation also discusses media that must be provided. The focus of MDT 2008 is computer deployment versus the integration that organizations can achieve on the platform by combining computers and domains. MDT 2008 supports deployment in Windows Server 2008 and Windows Server 2003 domains.
Note For the latest information regarding MDT 2008, see Release Notes.doc in the documentation subfolder of the MDT 2008 installation folder.
Note MDT 2008 combines abstract concepts that are sometimes difficult to follow without citing specific examples. To make these concepts easier to understand, this deployment project references a sample project at a fictional company named Woodgrove Bank. This deployment project also provides sample job aids for Woodgrove Bank. The content in each planning template is specific to Woodgrove Bank; replace it with information specific to the organization.Note In this document, Windows applies to the Windows Vista®, Windows XP Professional, Windows XP Tablet PC Edition, Windows Server 2008, and Windows Server 2003 operating systems unless otherwise noted.

Day One

MONDAY 2009-09-14:

1. Introduction

Ø Basic company information

Ø Personal development assessment

Ø Work ethics established

2. Objectives

Ø Company network documents should be updated regularly (products/brands)

Ø Knowing the correct utilities for the following

i. Switching

ii. VLANS (virtual local area networks)

iii. DHCP (dynamic host configuration protocol)

iv. DNS (domain naming system)

v. AD (active directory services)

Ø Deployment of client Pc’s using Microsoft Deployment Tool

All in all very interesting iam pleased by the fact that this was not the wrong career choice after all, so for all those in doubt, do not fear a little hard work nver killed anyone.

Zwai K