App-V: Error 25122. ASP.NET web service extension

Issue:-

When you install the Application Virtualization 4.5 Management Server either through a typical installation option or a custom option that includes the Application Virtualization Management Web Service on Windows Server 2008 or Windows Server 2008 R2, you may encounter the following error:
Error 25100. An internal error occurred.
or
Error 25122. The installation program was unable to register the ASP.NET web service extension.

Uninstalling Operations Manager 2007 Reporting Services

There are a lot of instances where the Reporting setup does not behave as expected. Data Warehouse errors, Reporting hierarchy failed errors, and many other such errors are an indication that something is wrong. Sometimes it might be a simple fix, but at times we need to completely re do the reporting setup.

These are the high level steps to uninstall the Reporting DB,

Go to control Panel -> Add remove programs -> Uninstall the SCOM 2007 reporting server

Once this is done, use your SCOM 2007 R2 media. Go to the \support tools\

Here you will find the resetsrs.exe utility for your hardware version (x86 or x64)

Update Prerequisites for SCCM 2007 SP2 installation

There are many instances when you try to run Update Prerequisites for SCCM 2007 SP2 during normal installation it may fail or give some error. So using the below command line you can download the Update Prerequisites on another PC and then copy the files on the SCCM server.

1.       Open the command prompt
2.       Go to ConfigMgr07SP2 CD -> SMSSETUP -> BIN -> I386 folder
3.       Run the below command line to download the prerequisites:-
       Setup.exe /download <path>

App-V 4.6 SP1: Management Server Installation and Configuration

In this blog we have evaluated Microsoft Application Virtualization 4.6 SP1 and given the detailed step by step procedure to set up the infrastructure. The blog is divided into 3 parts:-

App-V 4.6 SP1: Management Server Installation and Configuration

App-V 4.6 SP1: Client Installation and Configurati...

App-V 4.6 SP1 : Sequencer Installation and Configu...

Installing App-V Management Server

Windows Domain Controller

·         Windows Server® 2008 or Windows Server 2008 R2 with Active Directory Domain Services and Microsoft DNS

DaRT 7.0 Installation Step by Step Guide

Step by Step Guide to Install and Run DaRT

We’re going to install DaRT on an administrator’s workstation running Windows 7 x 86 Enterprise edition and then use it to troubleshoot computers running Windows 7 that fail to boot properly. Begin by copying DaRT installer files on Windows 7 Machine.

SCCM 2007 R3 OSD Deployment

Through SCCM, OS can be deployed on multiple numbers of computers simultaneously. In SCCM, operating system can be deployed on machines using PXE boot method. This method is used to deploy OS on bare metal machines. OS deployment feature can be also used to upgrade an existing OS on the system. Multiple set of customised OS images can be created. As per the requirement, different OS images can be used for deploying on a particular set of computers.

In this section, the complete procedure for deploying OS is provided. Operating System deployment consists of the following configurations which have to be carried out as given below:-

· Installation of Pre-requisites for PXE boot method

· Installing PXE Service point role on SCCM server

· Creating a separate Collection for OS deployment

· Configuration of Boot Images

· Creating Computer Association for bare metal computers

· Capturing customised OS image from a reference computer

· Creating OS image package

· Creating Task Sequence for OS image

· Advertising Task Sequence on the Collection for deploying OS

Direct Access lab Issue

Troubleshooting DirectAccess Client Connectivity Problems
ISSUE: Cannot resolve intranet FQDNs (root cause)

When CLIENT1 is on the Internet, it uses encrypted IPsec tunnels to the DirectAccess server (EDGE1) to access the intranet DNS server (DC1) and intranet resources. If the IPsec tunnels cannot be successfully negotiated, CLIENT1 cannot resolve intranet names or connect to intranet resources.

In this troubleshooting scenario, you will configure the DirectAccess server to use the wrong root CA for IPsec authentication and then troubleshoot the results.