Tuesday, July 21, 2009

How to disable the IP Spoof Detection feature in ISA Server 2004,2006

Click this link http://support.microsoft.com/kb/838114

To disable the IP Spoof Detection feature in the Windows registry, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/FwEng/Parameters
    If the Parameters subkey is not displayed, follow these steps to create this subkey:
    1. Click the FwEng subkey.
    2. On the Edit menu, point to New, and then click Key.
    3. To name the key, type Parameters, and then press ENTER.
  3. Right-click Parameters, point to New, and then click DWORD Value.
  4. To name the value, type DisableSpoofDetection, and then press ENTER.
  5. Right-click DisableSpoofDetection, and then click Modify.
  6. In the Value data box, type 1, and then click OK.

    Warning This setting disables IP Spoof Detection. To enable IP Spoof Detection, set the DisableSpoofDetection value to 0. This is the default value.
  7. Exit Registry Editor, and then restart the ISA Server 2004 services or the ISA Server 2006 services.

Tuesday, July 14, 2009

Work Faster with New Hotkey Keyboard Shortcuts in Windows 7

Shortcut

Description

Win + UP Arrow

Maximize the current window

Win + Down Arrow

Restore down or minimize current windows

Win + Left Arrow

Dock the current window to the left half of the screen

Win + Right Arrrow

Dock the current window to the right half of the screen

Win + [number]

Activate and run the program pinned on Windows 7 Taskbar, running program won’t be affected

Win + Home

Minimize all but the current window

Win + Space

Makes all windows transparent so you can see through to the desktop

Win + Pause/Break

Open System Properties

Win + Tab

Flip Aero 3D [press Tab to cycle between Windows]

Win + B

Move focus to notification tray (the right-most portion of the taskbar)

Win + D

Show/Hide desktop

Win + E

Windows Explorer is launched

Win + F

Search

Win + G

Bring all gadgets on top and foreground

Win + L

Lock Computer

Win + M

Minimize all windows

Win + P

Open the projection menu (generally used for laptops connected to projectors)

Win + R

Run Command is launched.

Win + S

OneNote Screen Clipping Tool

Win + T

Show preview thumbnail of running applications in Windows Taskbar one by one without mouse over

Win + X

Mobility Center

Win + #

Quicklaunch

Win + =

Magnifier

Win + [+/-]

Enables the magnifier and zooms in/out

Win + Shift + Up Arrow

Maximize vertical size

Win + Shift + Down Arrow

Restore vertical size

Win + Shift + Left Arrow

Jump to left monitor

Win + Shift + Right Arrow

Jump to right monitor

Win + Shift + M

Undo all window minimization

Win + Shift + T

Cycles backwards

Win + Ctrl + F

Opens the Active Directory Find Computers dialog

Ctrl + Right Arrow

Move the cursor to the beginning of the next word

Ctrl + Left Arrow

Move the cursor to the beginning of the previous word

Ctrl + Up Arrow

Move the cursor to the beginning of the previous paragraph

Ctrl + Down Arrow

Move the cursor to the beginning of the next paragraph

Ctrl + Click

A pinned taskbar icon to cycle through the program’s open windows (e.g. IE)

Ctrl + Win + Tab

Persistent flip 3D

Ctrl + Shift with an arrow key

Select a block of text

Ctrl with any arrow key + Spacebar

Select multiple individual items in a window or on the desktop

Ctrl + Shift + Esc

Open Task Manager directly

Ctrl + Shift + N

Create new folder

Wednesday, July 8, 2009

INSTALLING DPM 2007

 

Log on to the DPM server using a domain user account that has local administrator rights. Insert the DPM DVD in the DVD-ROM drive and double-click Setup.exe. On the System Center Data Protection Manager 2007 screen, click Install Data Protection Manager

image001

Review the license agreement, click I accept the license terms and conditions, and then click OK. On the Welcome page, click Next

image002

On the Prerequisites Check page, wait while DPM Setup checks software and hardware requirements. If one or more required or recommended components are missing or non-compliant, Setup displays a warning( try to fix this warnings) & Click next

image003

On the Product Registration page, enter your registration information  and click Next. On the Installation Settings page, in the DPM Program Files section, accept the default folder or click Change to browse to a different folder. In the SQL Server settings section, specify whether you want DPM Setup to install the MS$DPM2007$ instance of Microsoft SQL Server or if you prefer to use a different local or remote instance of SQL Server that already exists.

image004

image005

  1. On the Security Settings page, specify a strong password for the MICROSOFT$DPM$Acct and DPMR$<computer name> local user accounts, and then click Next.

image006

  1. On the Microsoft Update Opt-In page, specify if you want to sign up for the Microsoft Update service, and then click Next (Figure 13). You can change your Microsoft Update opt-in decision at a later time. On the Customer Experience Improvement Program page, specify if you want to enroll in the program or not, and then click Next (Figure 14).

image007

image008

On the Summary of Settings page, review the summary of installation settings and click Install. After the installation is complete, the Installation page displays the installation status. Click Close and restart the computer.

image009

image010

Links to download services pack 1

DPM 2007 Service Pack 1 (64bit): http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8ae5edac-4de8-44e0-a6f9-8afbb3e23585

DPM 2007 Service Pack 1 (32bit): http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=43cef22c-f027-4c0b-8fad-b081485c3efe

Feature Pack (x86): http://www.microsoft.com/downloads/details.aspx?familyid=E9E1FE35-B175-40A8-8378-2F306CCC9E28&displaylang=en

Feature Pack (x64): http://www.microsoft.com/downloads/details.aspx?familyid=AD5CD1A2-9B87-4A2C-90A2-9DBAF1024310&displaylang=en

HotFix (KB968579): http://www.microsoft.com/downloads/details.aspx?familyid=A5F86E53-45F5-42B1-895F-FD2C5B2BF4DD&displaylang=en

Hotfix (KB963102): http://www.microsoft.com/downloads/details.aspx?familyid=8A551A13-270E-46C0-91EE-4A6D3D8BF034&displaylang=en

Adding disks to the storage pool

Log on to the DPM server with a domain user account that has local administrator rights. On the Start menu, point to All Programs, point to Microsoft System Center Data Protection Manager 2007, and then click Microsoft System Center Data Protection Manager 2007.

In DPM Administrator Console, in the Management task area, on the Disks tab, in the Actions pane, click Add

image011

Install protection agent

To install a Protection Agent, in DPM Administrator Console, in the Management task area, on the Agents tab, in the Actions pane, click Install. The Protection Agent Installation wizard appears and guides you through the process of creating the protection agent. On the Select Computers, select one or more computers from the Computer name list, click Add, and then click Next.

image012

On the Enter Credentials page, type the user name and password for a domain account that is a member of the local administrators group on all selected servers and click next. On the Choose Restart Method page, select the method you will use to restart the computers after the protection agent is installed. The computer must be restarted before you can start protecting data. Click Next.

image013

image014

On the Summary page click Install to begin the installation. On the Installation page, the results appear on the Task tab to indicate whether the installation is successful or not . Click Close.

image015

image016

  1. After the protected server restarts, it will appear as unprotected computers with protection agent On the other hand, if the agent is installed, it will now appear on the Add/Remove Programs and there will be a new service running on that machine.

image017

Creating a Protection Group

To create a Protection Group, in DPM Administrator Console, in the Protection task area, in the Actions pane, click Create protection group. The New Protection Group Wizard appears and guides you through the process of creating the protection group. Click Next.

image018

On the Select Group Members page, verify that all computers that store data you want to protect are displayed in the Available members’ box. In the Available members’ box, expand the server nodes to display the available data sources on each server and to see available Exchange storage groups. Place a check mark in the box next to each storage group you want to include. As you select data sources, your selections appear in the selected members’ box. Click Next.

image019

On the Select Data Protection Method page, select I want short-term protection using check box for short-term protection and then select the media you want to use from the drop-down list. Since we do not have a tape library attached to the DPM server, only Disk is available for short-term protection. Click Next.

image020

On the Specify Exchange Protection Options page, select the Run Eseutil to check data integrity check box to check the integrity of the Exchange Server databases. This will offload the backup consistency checking from the Exchange Server to the DPM server which means the I/O impact of running eseutil on the Exchange Server during the backup itself is eliminated. Click Next.

image021

On the Specify Short-Term Goals page, select the retention duration for data recovery in the Retention range box. In the Synchronization frequency section, select the frequency of the incremental backups or Just before a recovery point to configure DPM to perform an express full backup just before each scheduled recovery point. To modify the recovery point schedule for a data source, click Modify next to the desired data source. Select your desired times and week days and click OK. Click Next.

image022

image023

DPM will display its recommended disk allocations. This step enables you to allocate how much of the disk storage pool will be used to protect these particular data sources. You should allocate the DPM replica volume to slightly larger than the amount you expect each data source to grow in the short term. Sizing the recovery point volume will determine how many previous recovery points are available for rapid, disk-based restore. To allocate disk storage, do one of the following: To accept the recommended allocations, click next. To change a recommended allocation, click Modify, adjust the allocations, click OK, and then click next.

image024

image025

On the Choose Replica Creation Method page, select when you want DPM to execute the initial replication of your data and click next.

  • Select the automatically option to have DPM replicate the data across the network. Select Now to have DPM immediately begin copying the data from the computers you are protecting to the DPM server; Select Later to start the initial copy at a later time if you want to schedule the job to run only during periods of light network traffic.
  • Select Manually to use tape, USB storage, or other portable media to transfer the baseline data to the DPM server.

image026

On the Summary page , review the tasks that DPM is set to perform to create the protection group and then click Create Group. Review the confirmation page  and click Close.

image027

image028

DPM will immediately create the first replica of the storage groups and will show an OK protection status if it succeeds.

image029

image030

Tuesday, July 7, 2009

How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows

http://support.microsoft.com/kb/894435

IIS 6.0 supports both the 32-bit mode and the 64-bit mode. However IIS 6.0 does not support running both modes at the same time on a 64-bit version of Windows. ASP.NET 1.1 runs only in 32-bit mode. ASP.NET 2.0 runs in 32-bit mode or in 64-bit mode. Therefore, if you want to run ASP.NET 1.1 and ASP.NET 2.0 at the same time, you must run IIS in 32-bit mode.

Note If you have Microsoft Exchange Server 2007 installed on the computer, use the instructions for ASP.NET 2.0, 64-bit version.

Before you can switch between the different versions of ASP.NET, visit the following Microsoft Developer Network (MSDN) Web site to download and install both the .NET Framework 1.1 and the .NET Framework 2.0:
http://msdn2.microsoft.com/en-us/netframework/aa731542.aspx (http://msdn2.microsoft.com/en-us/netframework/aa731542.aspx)
For example, if you are running Microsoft Windows x64 Edition, download the following two redistributable packages:
  • The .NET Framework Version 2.0 Redistributable Package x64 (64 Bit)
  • The .NET Framework Version 1.1 Redistributable
After you install the redistributable packages, you can switch between the different versions of ASP.NET. To do this, follow these steps for each ASP.NET version:

ASP.NET 1.1, 32-bit version

To run the 32-bit version of ASP.NET 1.1, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. Type the following command to enable the 32-bit mode:
    cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
  3. Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:
    %SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
  4. Make sure that the status of ASP.NET version 1.1.4322 is set to Allowed in the Web service extension list in Internet Information Services Manager.

ASP.NET 2.0, 32-bit version

To run the 32-bit version of ASP.NET 2.0, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. Type the following command to enable the 32-bit mode:
    cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
  3. Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install the script maps at the IIS root and under:
    %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
  4. Make sure that the status of ASP.NET version 2.0.50727 (32-bit) is set to Allowed in the Web service extension list in Internet Information Services Manager.

ASP.NET 2.0, 64-bit version

To run the 64-bit version of ASP.NET 2.0, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. Type the following command to disable the 32-bit mode:
    cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
  3. Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:
    %SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
  4. Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Note The build version of ASP.NET 2.0 may differ depending on what the currently released build version is. These steps are for build version 2.0.50727.

Set IIS to Allow x64-bit Applications

 

 To make sure that IIS enables 64-bit programs to run, follow these steps on any server that is currently running 32-bit applications and will have an MDM Device Management Server, MDM Enrollment Server, and MDM Gateway Server role. 32-bit applications will no longer function after the script is run. World Wide Web Publishing service does not support running 32-bit and 64-bit worker processes concurrently on the same server.

Note:It is not necessary to run this script on a newly installed 64-bit operating system on which no 32-bit applications are running.

To configure and verify IIS x64-bit configuration

1. On the Start menu, choose Run.

2. At the command prompt, type cmd, and then press ENTER.

3. Type the following command to disable 32-bit mode, and then press ENTER:

Copy Code & past it in CMD:

Cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

The output expected is <boolean> False.

4. In Internet Information Services Manager, make sure that the status of ASP.NET version 2.x is displayed as Allowed in the Web service extension list.

Step by Step Hyper-V Installation

Hyper-V is a new role in Windows Server 2008 that provides you with the tools and services you can use to create a virtualized server computing environment. This guide introduces Hyper-V by providing instructions for installing this role and configuring a virtual machine.

Hardware Requirements
Hyper-V requires an x64-based processor, hardware-assisted virtualization(EG:Intel VT), and hardware data execution protection.

Install Hyper-V
You can use Server Manager to install Hyper-V.
1. Click Start, and then click Server Manager.

2. In the Roles Summary area of the Server Manager main window, click Add Roles.

3. On the Select Server Roles page, click Hyper-V.

4. On the Create Virtual Networks page, click one or more network adapters if you want to make their network connection available to virtual machines.

5. On the Confirm Installation Selections page, click Install.

6. The computer must be restarted to complete the installation. Click Close to finish the wizard, and then click Yes to restart the computer.

7. After you restart the computer, log on with the same account you used to install the role. After the Resume Configuration Wizard completes the installation, click Close to finish the wizard.

Create and set up a virtual machine
After you have installed Hyper-V, you can create a virtual machine and set up an operating system on the virtual machine.

To create and set up a virtual machine
1. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.

2. From the Action pane, click New, and then click Virtual Machine.

3. From the New Virtual Machine Wizard, click Next.

4. On the Specify Name and Location page, specify what you want to name the virtual machine and where you want to store it.

5. On the Memory page, specify enough memory to run the guest operating system you want to use on the virtual machine.

6. On the Networking page, connect the network adapter to an existing virtual network if you want to establish network connectivity at this point.

7. On the Connect Virtual Hard Disk page, specify a name, location, and size to create a virtual hard disk so you can install an operating system on it.

8. On the Installation Options page, choose the method you want to use to install the operating system:

• Install an operating system from a boot CD/DVD-ROM. You can use either physical media or an image file (.iso file). .

9. Click Finish.

After you create the virtual machine, you can start the virtual machine and install the operating system.
Install the operating system and integration services.In the final step of this process, you connect to the virtual machine to set up the operating system. As part of the setup, you install a software package that improves integration between the virtualization server and the virtual machine.

 Note
The instructions in this step assume that you specified the location of the installation media when you created the virtual machine. The instructions also assume that you are installing an operating system for which integration services are available.

To install the operating system and integration services

1. From the Virtual Machines section of the results pane, right-click the name of the virtual machine you created in step 2 and click Connect. The Virtual Machine Connection tool will open.

2. From the Action menu in the Virtual Machine Connection window, click Start.

3. Proceed through the installation.

(Notes) After the operating system is set up, you are ready to install the integration services. From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. If Autorun does not start the installation automatically, you can start it manually.

To download Release Notes for this Release of Hyper-V,see http://go.microsoft.com/fwlink/?LinkId=98821.

To review the release notes, see: http://go.microsoft.com/fwlink/?LinkId=102060.

How to view and transfer FSMO roles in Windows Server 2003

 

http://support.microsoft.com/kb/324801

 

This article describes how to transfer Flexible Single Master Operations (FSMO) roles (also known as operations master roles) by using the Active Directory snap-in tools in Microsoft Management Console (MMC) in Windows Server 2003.

FSMO Roles
In a forest, there are at least five FSMO roles that are assigned to one or more domain controllers. The five FSMO roles are:
  • Schema Master: The schema master domain controller controls all updates and modifications to the schema. To update the schema of a forest, you must have access to the schema master. There can be only one schema master in the whole forest.
  • Domain naming master: The domain naming master domain controller controls the addition or removal of domains in the forest. There can be only one domain naming master in the whole forest.
  • Infrastructure Master: The infrastructure is responsible for updating references from objects in its domain to objects in other domains. At any one time, there can be only one domain controller acting as the infrastructure master in each domain.
  • Relative ID (RID) Master: The RID master is responsible for processing RID pool requests from all domain controllers in a particular domain. At any one time, there can be only one domain controller acting as the RID master in the domain.
  • PDC Emulator: The PDC emulator is a domain controller that advertises itself as the primary domain controller (PDC) to workstations, member servers, and domain controllers that are running earlier versions of Windows. For example, if the domain contains computers that are not running Microsoft Windows XP Professional or Microsoft Windows 2000 client software, or if it contains Microsoft Windows NT backup domain controllers, the PDC emulator master acts as a Windows NT PDC. It is also the Domain Master Browser, and it handles password discrepancies. At any one time, there can be only one domain controller acting as the PDC emulator master in each domain in the forest.
You can transfer FSMO roles by using the Ntdsutil.exe command-line utility or by using an MMC snap-in tool. Depending on the FSMO role that you want to transfer, you can use one of the following three MMC snap-in tools:

Active Directory Schema snap-in
Active Directory Domains and Trusts snap-in
Active Directory Users and Computers snap-in

If a computer no longer exists, the role must be seized. To seize a role, use the Ntdsutil.exe utility.

Transfer the Schema Master Role
Use the Active Directory Schema Master snap-in to transfer the schema master role. Before you can use this snap-in, you must register the Schmmgmt.dll file.
Register Schmmgmt.dll
  1. Click Start, and then click Run.
  2. Type regsvr32 schmmgmt.dll in the Open box, and then click OK.
  3. Click OK when you receive the message that the operation succeeded.
Transfer the Schema Master Role
  1. Click Start, click Run, type mmc in the Open box, and then click OK.
  2. On the File, menu click Add/Remove Snap-in.
  3. Click Add.
  4. Click Active Directory Schema, click Add, click Close, and then click OK.
  5. In the console tree, right-click Active Directory Schema, and then click Change Domain Controller.
  6. Click Specify Name, type the name of the domain controller that will be the new role holder, and then click OK.
  7. In the console tree, right-click Active Directory Schema, and then click Operations Master.
  8. Click Change.
  9. Click OK to confirm that you want to transfer the role, and then click Close.
Transfer the Domain Naming Master Role
  1. Click Start, point to Administrative Tools, and then click Active Directory Domains and Trusts.
  2. Right-click Active Directory Domains and Trusts, and then click Connect to Domain Controller.
    NOTE: You must perform this step if you are not on the domain controller to which you want to transfer the role. You do not have to perform this step if you are already connected to the domain controller whose role you want to transfer.
  3. Do one of the following:
    • In the Enter the name of another domain controller box, type the name of the domain controller that will be the new role holder, and then click OK.
      -or-
    • In the Or, select an available domain controller list, click the domain controller that will be the new role holder, and then click OK.
  4. In the console tree, right-click Active Directory Domains and Trusts, and then click Operations Master.
  5. Click Change.
  6. Click OK to confirm that you want to transfer the role, and then click Close.
Transfer the RID Master, PDC Emulator, and Infrastructure Master Roles
  1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  2. Right-click Active Directory Users and Computers, and then click Connect to Domain Controller.
    NOTE: You must perform this step if you are not on the domain controller to which you want to transfer the role. You do not have to perform this step if you are already connected to the domain controller whose role you want to transfer.
  3. Do one of the following:
    • In the Enter the name of another domain controller box, type the name of the domain controller that will be the new role holder, and then click OK.
      -or-
    • In the Or, select an available domain controller list, click the domain controller that will be the new role holder, and then click OK.
  4. In the console tree, right-click Active Directory Users and Computers, point to All Tasks, and then click Operations Master.
  5. Click the appropriate tab for the role that you want to transfer (RID, PDC, or Infrastructure), and then click Change.
  6. Click OK to confirm that you want to transfer the role, and then click Close.

Monday, July 6, 2009

DPM 2007 Management Pack (SCOM & MOM)

 

The System Center Data Protection Manager (DPM) 2007 Management Pack monitor the state of data protection and recovery for DPM servers and the computers that they protect and monitor key health and performance indicators on DPM servers.

What's New in DPM 2007 Service Pack 1

Service Pack 1 for Microsoft System Center Data Protection Manager (DPM) 2007 provides continuous data protection for Windows application and file servers using seamlessly integrated disk and tape media and includes the following expanded capabilities:

  • Protection of Hyper-V™ virtualization platforms, including both Windows Server 2008 Hyper-V and the Microsoft Hyper-V Server, has been added to the existing set of protected workloads, building on the virtualization protection originally delivered for Virtual Server 2005.

  • Enhanced SQL Server 2008 protection, including the addition of new protection capabilities for mirrored databases, support for parallel backups of databases within a single instance, and the ability to move data from SQL Server 2005 to SQL Server 2008 for migration scenarios.

  • Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 receive index protection, significant catalog optimization, and support for mirrored content databases.

  • Added protection for Exchange Server 2007 Standby Cluster Replication (SCR), enabling a complete disaster recovery solution that leverages SCR failover alongside DPM point-in-time restores.

In addition to enhancing the protection of each of the core Microsoft application workloads, additional capabilities have also been introduced with the release of DPM 2007 SP1, such as:

  • Local Data Source Protection enabling the DPM 2007 SP1 server to act as a branch office server offering self-protecting File Services and Virtualization hosting within one platform.

  • Cross-Forest Protection allowing large enterprise customers with multiple Active Directory® forests to now have even more flexibility in their DPM deployments.

  • Provision for a Client DPML answers customer demand for a more cost-effective way to protect Windows XP and Windows Vista clients using the same DPM 2007 infrastructure that protects their servers.

  • Disaster Recovery capabilities within DPM 2007 SP1 now include the ability to leverage a third-party vaulting partner via the cloud (SaaS).

All of this new functionality builds on the features released in the DPM 2007 ‘Rollup Update’ in June 2008, which provided protection of Windows Server 2008, including Windows Server 2008, Windows Server 2008 core, Windows Server 2008 System State and BitLocker™ support – as well as new tape media capabilities around tape sharing and media library sharing.

Outside of the Service Pack itself, Microsoft is also co-releasing a Management Pack to enable System Center Operations Manager 2007 to monitor and manage DPM deployments, providing an enterprise view of all of the DPM servers and protected workloads, as well as knowledge-based troubleshooting and optimization guidance from a central console.

Between ‘Rollup Update’ and Service Pack 1, many of the core features of DPM 2007 have seen incremental capabilities or workload advancements which promises to keep Data Protection Manager on a trajectory toward improving how Microsoft customers protect and recover their Windows application and file servers with the Microsoft backup and recovery solution.

Sunday, July 5, 2009

How to install Data Protection Manager to a Windows 2008 Server

 

Article http://technet.microsoft.com/en-us/library/bb808814(TechNet.10).aspx describes how to install DPM on to a 2008 Server. However I have found that this article is incomplete. The following is how to install DPM onto a 2008 Server.

After the 2008 Server setup has finished perform the following:

1. Click Start, point to Administrative Tools, and then click Server Manager.

2. Expand Server Manager to the Features node, and then select Features.

3. In the Features pane, click Add Features.

4. Select Windows PowerShell, and then click Next.

5. On the Confirm Installation Selections page, click Install.

6. Click Start, point to Administrative Tools, and then click Server Manager.

7. Expand Server Manager to the Roles node, and then select Roles.

8. In the Roles pane, click Add Roles.

9.  In the Add Roles Wizard, on the Before You Begin page, click Next.

10. On the Select Server Roles page, select Web Service (IIS).

11. In the Add features required for Web Server (IIS)? message box, click Add Required Features.

      1. Ensure that you select the following Role service:
      2. HTTP Redirection
      3. Application Development
        1. ASP.net
        2. .NET Extensibility
        3. ISAPI Extensions
        4. ISAPI Filters
        5. Server Side Includes
      4. IIS 6 Management Compatibility
        1. IIS 6 Metabase Compatibility
        2. IIS 6 WMI Compatibility
        3. IIS 6 Scripting Tools
        4. IIS 6 Management Console
      5. Security (Installed)
        1. Windows Authentication (Installed)

Note: if you do not install these components correctly you will get an error during DPM installation.

12.  Install SIS

  1. At a command prompt (with elevated privileges) type:
    1. Go to system 32 in cmd Ocsetup.exe SIS-Limited
    2. Press enter
    3. Wait for the command to complete (this can take a while)
    4. Reboot the box.
      1. To ensure that the SIS service gets installed you can check the following key. This key will appear after a reboot.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SIS

13.  Run the DPM installation wizard.

14, Install hotfix 950082 Description of the Data Protection Manager 2007 hotfix package rollup 2

http://support.microsoft.com/default.aspx?scid=kb;EN-US;950082

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/300add38-39e5-4053-83d8-67831b499143/

1) Open IIS Manager.

2) Select the "ReportServer" site.

3) Double click the "Handler Mappings" item (in either the IIS area or the Server Components category).

4) Right click the "Enabled" item that's listed in the IE 403.1 error message. Mine was named "AboMapperCustom-341562". I got the error while remoted into the server and using IE to browse http://localhost/ReportServer.

5) Select the "Edit Feature Permissions..."

6) Check the "Script" item.

7) Restarted IIS

Global Vnet Peering

g  Global Vnet Peering Configuration  Ø Global VNet Peering enables peering virtual networks in different Azure regions. Ø Tr...