Walid Hegazy

How To Do :) IT

Leave a comment

WDS client may hang up after loading the boot.wim file if you import the Windows 8 x86 boot image only the WDS server

enter image description here

Consider the following scenario. You have a Windows Server 2008 R2 WDS (Windows Deployment Service) server and you plan to use it to deploy Windows 8 or Windows Server 2012 operating systems. If you import a Windows 8 x86 boot image only on this WDS server and then if you try to boot up a WDS client from this WDS server, you may find that the system hangs up after loading the \Boot\x86\Images\boot.wim file.

Reade the full KB on Microsoft


1 Comment

Exchange 2013 IGNITE Videos Level (300)

Hay everyone ,yesterday  i came across very nice series of ten videos for Exchange IGNITE level (300) enjoy watching   …

Using the Exchange Administration Center

In this guide, you will explore some of the organization management tasks you can perform using the new Exchange Administration Center.


Deploying Site Mailboxes

This guide will show you how to create a site policy, add the Site Mailbox app to a SharePoint site, create and use site mailboxes, and close a site and site mailbox.


Creating an Exchange Certificate Request

In this guide, you’ll see how to create and complete a certificate request using the Exchange Administration Center.

Continue reading


Windows 8 Migration & Deployment Using MDT 2012 update 1


Before we begin, let’s cover some basics. In short, there are three possible ways for Windows 8 deployment:

  1. Manual deployment
  2. Semi-automated deployment, aka Light Touch Installation or LTI
  3. Fully-automated deployment, aka Zero Touch Installation or ZTI

Manual Deployment: A manual deployment is something that could happen in homes and really small-to-medium business environments. This approach involves taking a backup of the data, reinstalling the PC by starting a manual setup of Windows 8 (DVD, ISO, etc.), and restoring the user data. This is rather time-consuming, and I personally think it is a bit outdated. Even so, this is still a very good solution for all PC environments with less than ten machines.

Light Touch Installation (LTI): Light Touch Installation means you will use a semi-automated approach for Windows 8 deployment. In short, this involves using a deployment tool, creating an image, and reproducing/deploying the same image to multiple clients by booting from a deployment medium (typically a bootable USB-stick).

Zero Touch Installation (ZTI): By using a Zero Touch deployment mechanism, you basically give the option to the end-user to (re)deploy the machine completely by himself or herself. In short, this starts with the configuration of the deployment tool, creating an image, and automatically

What is the Microsoft Deployment Toolkit 2012 (MDT 2012)?

MDT 2012 is the newest version of the Microsoft Deployment Toolkit (MDT), a Solution Accelerator for operating system and application deployment. MDT 2012 Update 1 supports deployment of Windows 8, Windows 7, Office 2010 and 365, Windows Server 2012, and Windows Server 2008 R2, in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.


Let Us Start

Configuring MDT 2012 Update 1 to deploy Windows 8 for the 8650w machines is done in nine easy steps:

clip_image003[394]       Create a deployment share

clip_image003[395]       Import the Windows 8 operating system

clip_image003[396]       Import the drivers

clip_image003[397]       Add the application

clip_image003[398]       Create a task sequence

clip_image003[399]       Configure the deployment share settings

clip_image003[400]       Update the deployment share

clip_image003[401]       Add the MDT 2012 Update 1 boot image to WDS

clip_image003[402]       Deploy the Windows 8 image

System Requirements

clip_image003[403]      A member server named MDT01 running Windows Server 2008 R2 or Windows Server 2012 with the following software installed:

clip_image003[404]       Windows Deployment Services

clip_image003[405]       ADK

clip_image003[406]       .NET Framework 3.5.1

clip_image003[407]       MDT 2012 Update 1

Continue reading


App-V 5.0 installation & Basic configuration (Part2)

During (part 1) we did walkthrough the APP-V requirements and the installation of our server , in this part we will play with APP-V Sequencer,Client,sequence a  sample application and see some troubleshooting steps.

Deploying the App-V 5.0 Sequencer

The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V 5.0 client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.

Specific change to the sequencer

The following table displays information about what has changed with the App-V 5.0 sequencer

Sequencer Feature

App-V 5.0 Sequencer Functionality

Reboot processing

When an application prompts for a restart, you should allow the application to restart the computer running the sequencer. The computer running the sequencer will restart and the sequencer will resume in monitoring mode.

Specifying the virtual application directory

Virtual Application Directory is a mandatory parameter. For best results, it should match the installation directory of the application installer. This results in more optimal performance and application compatibility.

Editing shortcuts/FTAs

The Shortcuts/FTA page is on the Advanced editing page after the sequencing wizard has completed.

Change History Tab

The Change History tab has been removed for App-V 5.0.


The OSD tab has been removed for App-V 5.0.

Virtual Services Tab

The virtual services tab has been removed for App-V 5.0.

Files/Virtual File System Tab

These tabs are combined and allow you to modify package files.

Deployment Tab

There are no longer options to configure the server URL in the packages. You should configure this now using deployment configuration, or the management server.

Package Converter Tool

You can now use PowerShell to convert packages created in previous versions.


You can expand parent packages when you are sequencing an Add-On or Middleware application. Add-ons and Middleware packages must be connected using connection groups in App-V 5.0.

Files output

The following files are created with App-V 5.0, Windows Installer (.msi), .appv, deployment configuration, user configuration, and the Report.XML.

Compression/Security descriptors/MSI packages

Compression and the creation of a Windows Installer (.msi) file are automatic for all packages and you can no longer override security descriptors.

Tools / Options

The Diagnostics window has been removed as well as several other settings.

Installation Drive

An installation drive is no longer required when you install an application.

OOS Streaming

If no stream optimization is performed, packages are stream faulted when they are requested by computers running the App-V 5.0 client until they can launch.


App-V 5.0 uses the native file system and no longer requires a Q:\.

Sequencing error detection

The App-V 5.0 sequencer can detect common sequencing issues during sequencing. The Installation Report page at the end of the sequencing wizard displays diagnostic messages categorized into Errors , Warnings , and Info depending on the severity of the issue.

To display more detailed information about an event, double-click the item you want to review in the report. The sequencing issues, as well as suggestions about how to resolve the issues are displayed. Information from the system preparation report and the installation report are summarized when you have finished creating a package. The following list displays the types of issues available in the report:

clip_image001[72]      Excluded files.

clip_image001[73]      Driver information.

clip_image001[74]      COM+ system differences.

clip_image001[75]      Side-by-side (SxS) conflicts.

clip_image001[76]      Shell Extensions.

clip_image001[77]      Information about unsupported services.

clip_image001[78]      DCOM.

Prerequisites for the App-V 5.0 Sequencer

The following prerequisites are already installed for computers that run Windows 8 and Windows Server 2012.



Software requirements

Installing the Sequencer

The computer that will run the sequencer must not be running any version of the App-V 5.0 client.

Upgrading a previous installation of the App-V sequencer is not supported.

The following list displays information about options for installing the sequencer using the command line and appv_sequencer_setup.exe:




Specifies the installation directory.


Enables participation in the Microsoft Customer Experience Improvement Program.


Specifies where the installation log will be saved, the default location is %Temp%. For example, C:\ Logs \ log.log.


Specifies a quiet or silent installation.


Specifies the removal of the sequencer.

/? Or /h or /help

Displays associated help.



Continue reading

1 Comment

System Center Orchestrator 2012 SP1 installation-step by step

IT administrators perform many tasks and procedures to keep the health of their computing environment up-to-date and their business running. Tasks might include the following diverse activities, for example, new employees require that accounts and resources are configured, a business acquisition requires integrating a system from another vendor, and new hardware requires provisioning. Individual tasks and subtasks are automated, but typically, not the whole process. In addition, the administrators must maintain quality standards and system efficiency.

System Center 2012 – Orchestrator can tie disparate tasks and procedures together by using the graphical user-interface Runbook Designer to create reliable, flexible, and efficient end-to-end solutions in the IT environment.

By using Orchestrator, you can carry out the following tasks:

¨       Automate processes in your data center, regardless of hardware or platform.

¨       Automate your IT operations and standardize best practices to improve operational efficiency.

¨       Connect different systems from different vendors without having to know how to use scripting and programming languages.

Custom automation

Orchestrator provides tools to build, test, debug, deploy, and manage automation in your environment. These automated procedures, called runbooks, can function independently or start other runbooks. The standard activities defined in every installation of Orchestrator provide a variety of monitors, tasks, and runbook controls with which you can integrate a wide range of system processes. Each activity in a runbook publishes data that is available to any subsequent activity in that runbook. You use this Published Data to provide dynamic, decision-making capabilities, which can include creating emails, alerts, log files, accounts, and more.

Orchestrator features & Architecture

Orchestrator feature


management server The management server is the communication layer between the Runbook Designer and the orchestration database.
runbook server A runbook server is where an instance of a runbook runs. Runbook servers communicate directly with the orchestration database. You can deploy multiple runbook servers per Orchestrator installation to increase capacity and redundancy.
orchestration database The database is a Microsoft SQL Server database that contains all of the deployed runbooks, the status of running runbooks, log files, and configuration data for Orchestrator.
Runbook Designer The Runbook Designer is the tool used to build, edit, and manage Orchestrator runbooks.
Runbook Tester Runbook Tester is a run-time tool used to test runbooks developed in the Runbook Designer. For more information about Runbook Tester,
Orchestration console The Orchestration console lets you start or stop runbooks and view real-time status on a web browser.
Orchestrator web service The Orchestrator web service is a Representational State Transfer (REST)-based service that enables custom applications to connect to Orchestrator to start and stop runbooks, and retrieve information about operations by using custom applications or scripts. The Orchestration console uses this web service to interact with Orchestrator.
Deployment Manager Deployment Manager is a tool used to deploy integration packs (IPs), runbook servers, and Runbook Designers.

Architectural diagram

The following diagram illustrates each of the Orchestrator features and the communication between each.


The orchestration database is the center of the Orchestrator installation containing all runbooks, configuration settings, and logs. The management server is required as a communication layer between the Runbook Designer and the orchestration database. One or more runbook servers communicate directly with the database to retrieve runbooks to run and store information about the jobs created from the runbooks. The web service also communicates directly with the orchestration database and provides a web browser connection for the Orchestration console.

Orchestrator Extensions

The following table shows multiple strategies available for extending the functionality provided by a standard installation of Orchestrator.

Orchestrator feature


integration pack (IP) An integration pack is a collection of custom activities specific to a product or technology. Microsoft and other companies provide integration packs with activities to interact with their product from an Orchestrator runbook.
Orchestrator Integration Toolkit The Orchestrator Integration Toolkit lets you extend your library of activities beyond the collection of standard activities and integration packs. The Integration Toolkit has wizard-based tools to create new activities and integration packs for Orchestrator. Developers can also use the Integration Toolkit to create integration packs from custom activities that they build by using the Orchestrator SDK.

Automation by using runbooks

To automate a task or process in Orchestrator, you use the Runbook Designer to create a runbook. You add activities to the runbook by dragging them from the Activities pane, and then link activities in the required order to create a workflow.


This runbook monitors an event log. When it detects the specified event, the runbook checks the status of a particular process in Windows on a specific computer. If the process is found to be running, it is stopped. The runbook then starts the process and sends an email as a notification of the change of process state.

Each runbook activity finishes before proceeding to the next, and activities are available that provide complex logic such as requiring that multiple activities are completed before the runbook proceeds. By using a combination of logic on activities and smart links, you can implement whatever logic your particular automation scenario requires.

Continue reading

Leave a comment

Microsoft Application Virtualization (App-V) Part1

Microsoft Application Virtualization (App-V) enables enterprises to meet the needs of users and IT by empowering anywhere productivity and accelerated application deployment. App-V provides anywhere user access to applications that available on any authorized device without application installs. Virtual applications and user settings are preserved whether users are online or offline. App-V increases business agility through faster application deployment and updates with no user interruptions. It minimizes conflicts between applications, allowing enterprises to reduce application compatibility testing time. App-V together with Microsoft User State Virtualization (USV) provides users with a consistent experience and reliable access to applications and business data, no matter their location and connection to the Internet.


Continue reading