Archive
To upgrade DPM 2007 SP1 running Windows 2003 server to DPM 2010 Windows Server 2008
Follow these steps:
- Apply ALL hotfixes to the DPM 2007 SP1 first.
Update Type
Version
Release Date
Details
DPM 2010 – Beta
3.0.7336.0
09/25/2009
https://connect.microsoft.com/Downloads/DownloadDetails.aspx?SiteID=840&DownloadID=22070
DPM 2007 – Hotfix
02.00.8861.0000
11/05/2009
DPM 2007 – Hotfix
02.00.8851.0000
08/28/2009
DPM 2007 – Hotfix
02.00.8844.0000
06/04/2009
DPM 2007 – Hotfix
2.0.8836.0
04/14/2009
DPM 2007 – Hotfix
2.00.8824.0
02/16/2009
DPM 2007 – Hotfix
2.0.8811.0
01/09/2009
DPM 2007 – SP1
2.0.8793.0
12/19/2008
DPM 2007 – Hotfix
2.0.8111.0
07/31/2008
DPM 2007 – Feature Pack
2.0.8107.0
07/18/2008
DPM 2007 – Hotfix
DPM 2007 – Hotfix
2.0.5820.0
04/24/2008
DPM 2007 – Hotfix
DPM 2007 – Hotfix
DPM 2007 – Hotfix
01/09/2008
DPM 2007 – RTM
10/17/2008
- Backup the DPM database.
1. From the command prompt, run DPMBackup.exe –db
2. Browse to Program FilesMicrosoft Data Protection ManagerDPMVolumesShadowCopyDatabase Backups. The file name of the DPM database backup is DPMDB.bak. Copy it to the media to which you want. - Uninstall DPM and choose to retain data. ( important!!! )
1. Click Add or Remove Programs on the Control Panel, and then click Change or Remove Programs.
2. Under Currently installed programs, select Microsoft System Center Data Protection Manager 2007 and then click Change/Remove.
3. On the Uninstallation Options page, select the Retain data option, and then click Next.
4. On the Summary of Options page, click Uninstall.
5. When uninstallation is complete, click Close
- Uninstall Powershell.
1. In Control Panel, click Add or Remove Programs, and then click Change or Remove Programs.
2. Under Currently installed programs, select Windows Powershell and then click Change/Remove
- Upgrade the server to Windows Server 2008/Windows 2008 R2 ( remember DPM 2010 only installs on x64 ).
1. Make sure that the bit version of both operating systems are same. If not, then you need to do a clean installation for the x64 bits
- Delete the DPM database.
1. Open the Microsoft SQL Server Management Studio
2. Select the MS$DPM2007$ database, and then click Connect.
3. Expand Databases, right-click the DPMDB database, and then click Delete.
4. Click Yes to confirm the deletion
- Install DPM 2010.
- Restore the DPM database.
1. Browse to the backup Path.
2. From the command prompt, type DpmSync –restored –dbloc < DPMDB location> and then press ENTER
Internet Explorer Security Patch
This cumulative security update resolves seven privately reported vulnerabilities and one publicly disclosed vulnerability in Internet Explorer. The more severe vulnerabilities could allow remote code execution if a user views a specially crafted Web page using Internet Explorer. This security update is rated Critical for all supported releases of Internet Explorer.
Affected Software
Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by This Update |
Internet Explorer 5.01 and Internet Explorer 6 Service Pack 1 | ||||
Microsoft Windows 2000 Service Pack 4 |
Remote Code Execution |
Critical |
||
Microsoft Windows 2000 Service Pack 4 |
Remote Code Execution |
Critical |
||
Internet Explorer 6 | ||||
Windows XP Service Pack 2 and Windows XP Service Pack 3 |
Remote Code Execution |
Critical |
||
Windows XP Professional x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2003 Service Pack 2 |
Remote Code Execution |
Moderate |
||
Windows Server 2003 x64 Edition Service Pack 2 |
Remote Code Execution |
Moderate |
||
Windows Server 2003 with SP2 for Itanium-based Systems |
Remote Code Execution |
Moderate |
||
Internet Explorer 7 | ||||
Windows XP Service Pack 2 and Windows XP Service Pack 3 |
Remote Code Execution |
Critical |
||
Windows XP Professional x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2003 Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2003 x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2003 with SP2 for Itanium-based Systems |
Remote Code Execution |
Critical |
||
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2** |
Remote Code Execution |
Critical |
||
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2** |
Remote Code Execution |
Critical |
||
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 |
Remote Code Execution |
Critical |
||
Internet Explorer 8 | ||||
Windows XP Service Pack 2 and Windows XP Service Pack 3 |
Remote Code Execution |
Critical |
||
Windows XP Professional x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2003 Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2003 x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 |
Remote Code Execution |
Critical |
||
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2** |
Remote Code Execution |
Critical |
||
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2** |
Remote Code Execution |
Critical |
||
Windows 7 for 32-bit Systems |
Remote Code Execution |
Critical |
||
Windows 7 for x64-based Systems |
Remote Code Execution |
Critical |
||
Windows Server 2008 R2 for x64-based Systems** |
Remote Code Execution |
Critical |
||
Windows Server 2008 R2 for Itanium-based Systems |
Remote Code Execution |
Critical |
**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Manage your VMware environment using SCVMM scripts
Do you know that you can create scripts using cmdlets that are provided with SCVMM 2008 to manage your VMware environment ?
For example, you can use the Add-VirtualizationManager cmdlet to add a VirtualCenter Server.
# Description: Adds a VMware VirtualCenter Server to VMM.
# Connect to the VMM server.
Get-VMMServer -ComputerName "VMMServer1.Contoso.com"
# Define the variables.
$AddCredential = Get-Credential
$Cert= Get-Certificate -Computername "VirtMgrServer01.Contoso.com"
# Require user to accept the certificate before adding the VirtualCenter Server.
Write-Host "Following is the certificate information for this VirtualCenter Server:"
$Cert
$AcceptCert = Read-Host "Do you accept this certificate? If you accept, enter Y."
If ($AcceptCert -eq "Y")
{
# Add the Virtual Center Server.
Add-VirtualizationManager -ComputerName "VirtMgrServer01.Contoso.com" -Certificate $Cert –TCPPort 443 -Credential $AddCredential -SecureMode $TRUE
}
Else
{
Write-Host "The script cannot continue unless the certificate is verified. Ending script."
}
After you add the VirtualCenter Server, you can manage the VMware ESX Server hosts.
Cmdlets and Parameters in VMM 2008 R2
The following list summarizes the new and updated cmdlets and parameters in VMM 2008 R2.
Cmdlets
- Disable-VMHost
- This cmdlet places a VMM host into maintenance mode. For more information, see Maintenance Mode for Hosts.
- Enable-VMHost
- This new cmdlet removes a VMM host from maintenance mode and returns it to service. For more information, see Maintenance Mode for Hosts.
Parameters
- AllowUnencryptedTransfers
- You can use the AllowUnencryptedTransfers parameter to specify that network file transfers into or out of a library, or into, out of, or within a host group, do not require encryption. Allowing unencrypted file transfers can improve performance when neither the source computer nor the destination computer requires encryption. This parameter can be used with the Set-LibraryServer and Set-VMHostGroup cmdlets.
- BlockLMIfHostBusy
- You can use the BlockLMIfHostBusy parameter of the Move-VM cmdlet to stop Hyper-V live migration from attempting to restart a live migration that could not previously start because the source host or the destination host was already performing a live migration.
- LimitCPUForMigration
- The LimitCPUForMigration parameter limits the processor features for a virtual machine so that the virtual machine can be migrated to a different physical computer that has a different version of the same processor as the source computer. Migrating virtual machines between physical computers with processors from different manufacturers is not supported. This parameter can be used with the following cmdlets: New-HardwareProfile, Set-HardwareProfile, New-VM, Set-VM, and Set-Template.
- MoveWithinCluster
- When you place a host that is a member of a host cluster into maintenance mode using the Disable-VMHost cmdlet, and you use the MoveWithinCluster parameter, all the virtual machines that are currently deployed on the host will be migrated to another host in the same host cluster.
- RemoveLibraryStoreSharePath
- You can use the RemoveLibraryStoreSharePath parameter of the Set-VMMUserRole cmdlet to clear the path to the specified library share. This share is used by members of a self-service user role to store virtual machines or as a repository from which to deploy stored virtual machines or stored ISO images.
- RetainDeletedObjects
- When you use the RetainDeletedObjects parameter with the Get-VMMServer cmdlet, the objects in the cache that are marked for deletion will be preserved. This parameter is included for users who might develop a user interface.
- RetainObjectCache
- When you use the RetainObjectCache parameter with the Get-VMMServer cmdlet, the objects in the cache remain in memory and are not reclaimed by garbage collection. This parameter is included for users who might develop a user interface.
- UseCluster
- The UseCluster parameter lets you force the transfer of a virtual machine using Windows Server 2008 Cluster Migration, even when Hyper-V live migration is available, when you move a virtual machine using the Move-VM cmdlet. For more information, see Live Migration.
- UseLocalVirtualHardDisks
- The UseLocalVirtualHardDisks parameter specifies that the virtual hard disk file (.vhd) for a new virtual machine that is created by using the New-VM cmdlet is at a specified location on the destination host, and that no .vhd files will be copied from the library. For more information, see Rapid Provisioning of Virtual Machines.
- VMNetworkOptimizationEnabled
- The VMNetworkOptimizationEnabled parameter enables virtual machine network optimization detection. This feature improves network performance for virtual machines with network adapters that support virtual machine queue (VMQ) or TCP Chimney Offload. VMQ enables creation of a unique network queue for each network adapter. TCP Chimney Offload enables network traffic processing to be offloaded from the networking stack. This parameter can be used with the New-VirtualNetworkAdapter, Set-VirtualNetworkAdapter, New-P2V, and New-V2V cmdlets.
- VMWarePortGroup
- You can use the VMWarePortGroup parameter to specify a VMware port group.
About vulnerability in Internet Explorer
. There have been a very limited number of targeted attacks against a small number of corporations.
. Attacks seen to date are only effective against Internet Explorer 6.
. Attacks are NOT widespread.
. Thus far we are NOT seeing attacks focused on consumers.
It is important to note that all software has vulnerabilities and switching browsers in an attempt to protect against this one, highly publicised, but currently limited attack can inadvertently create a false sense of security. Moreover, IE8 has built-in security features, such as the SmartScreen filter, that other browsers do not have.
We strongly recommend those using Internet Explorer 6 or Internet Explorer 7 upgrade to Internet Explorer 8 as soon as possible to benefit from the improved security protections it offers.
Recomendation : those using Windows XP SP2 upgrade to Windows XP SP3.