Mi Windows me confunde....

Webcast TechNet: Cómo funciona el Query Optimizer

2011-04-04T07:07:00.000-07:00

Id. de evento: 1032483670

Idiomas: Español.
Productos: Microsoft SQL Server.
Público: Generalista de IT, Implementador de tecnología de la información.

Título:
Cómo funciona el Query Optimizer

Descripción:

Esta sesion describe cómo funciona el Query Optimizer y los pasos más importantes que SQL Server ejecuta desde que recibe un query hasta que un plan de ejecución es generado.

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032483670&EventCategory=4&culture=es-ES&CountryCode=ES

Microsoft SQL Server 2008 Service Pack 2 (SP2) is now available

2010-10-07T03:29:00.000-07:00

Microsoft SQL Server 2008 Service Pack 2 (SP2) is now available for download. These packages may be used to upgrade any edition of SQL Server 2008. We remain committed to providing our customers with essential changes via Service packs. Service Pack 2 contains updates for SQL Server Utility, Data-Tier Application (DAC), as well as integration capability for Microsoft Reporting Services with the Microsoft SharePoint 2010 Technologies. Service Pack 2 introduces support for a maximum of 15,000 partitions in a database, and includes SQL Server 2008 SP1 Cumulative Update 1 to 8. While keeping product changes contained, we have made significant investments to ease deployment and management of Service Packs. Microsoft SQL Server 2008 Service Pack 1 is not a prerequisite for installing SQL Server 2008 Service Pack 2.

For more information about SQL Server 2008 Service Pack 2, please visit our Release Notes.

Download:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8fbfc1de-d25e-4790-88b5-7dda1f1d4e17&displaylang=en

Restore Mailbox Scenarios

2010-09-29T03:31:00.000-07:00

Restore Mailbox Scenarios
In this tip we will examine the different restore mailbox scenarios E12 will support.

General Assumptions on Restore-Mailbox Scenarios:

Servers are in a highly connected network.
Servers are part of a Single Forest or Resource Forests: Mailbox content can only be exported to mailboxes within the same forest. The NT accounts associated with the mailbox can be in an external forest (as in a Resource Forest Scenario), but mailbox content will not be able to be exported to servers in different forests.
These are the supported Source Servers:
1. Exchange 2000 SP3 (or later)
2. Exchange 2003 SP2 (or later)
3. Exchange 2007
These are the supported Target Servers:
1. Exchange 2007
Recipient Admin rights are required
Restore-Mailbox can only use disconnected mailboxes as source of content and connected mailboxes as the target

Recovering old mailbox of an existing employee

Customer Setting:

Restore-Mailbox can also recover data of users that have an active mailbox in the Exchange Organization. The way to do this is to recover the backup to the RSG database, and from there restore the user’s mailbox (or part of it using filtering) by simply specifying the ID for the mailbox to be restored. In this case, source and target should be the same so there is no need to use RSGMailbox.

Customer Goal:
Ability to restore mailbox content from RSG to the active mailbox that has the same ID, individually and in bulk.

Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics

Scenario 1: Restore mailbox content to active mailbox based on User ID
An administrator wants to restore email content from the RSG into a currently active mailbox:

MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:
MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database'

Scenario 2: Restore mailbox content to active mailbox based on User ID and date rangeAn administrator wants to restore email content sent between 02/02/05 and 02/05/05 from a RSG mailbox into a currently active mailbox:

MONAD Syntax – restore all RSG content sent between 02/02/05 and 02/05/05 of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:
MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database' -StartDate ‘02/02/05’ –EndDate ‘02/05/05’

Scenario 3: Restore mailbox content from all mailboxes in a Database to active mailboxes
An administrator wants to restore email content from all mailboxes in the RSG to their currently active mailbox counterparts:

MONAD Syntax – restore all RSG mailboxes to their currently active mailbox counterparts:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox

Scenario 4: Restore mailbox content to folder based on active User ID
An administrator wants to restore email content from a RSG mailbox into a folder inside a currently active mailbox:

MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox:

MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’

Scenario 5: Restore mailbox content to folder based on active User ID and date range
An administrator wants to restore email content sent between 02/02/05 and 02/05/05 from a RSG mailbox into a folder inside a currently active mailbox:

MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox:
MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’ -StartDate ‘02/02/05’ –EndDate ‘02/05/05’

Customer Setting:

After an employee leaves a company, even though his active mailbox might be disabled or deleted, admins can still recover data from previous backups through the RSG. The way to do this is to recover the backup to the RSG database, and from there restore the user’s mailbox (or part of it using filtering) by specifying the RSGMailbox (points to ex-employee’s mailbox) and a target folder in an admin mailbox.

Customer Goal:
Ability to recover data from RSG mailboxes that do not have an active mailbox counterpart. Data is to be recovered to a folder inside another user’s active mailbox.

Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics

Scenario 6: Restore mailbox content to folder inside an active mailbox based on RSG User ID
An administrator wants to restore email content from a RSG mailbox into a folder inside a currently active mailbox:

MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox:

MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’

Scenario 7: Restore mailbox content to folder inside an active mailbox based on RSG User ID and date range
An administrator wants to restore email content sent between 02/02/05 and 02/05/05from a RSG mailbox into a folder inside a currently active mailbox:

MONAD Syntax – restore all RSG content sent between 02/02/05 and 02/05/05 of mailbox testE12mbx1 to a folder called Backup inside the currently used testE12mbx2 mailbox
MSH> restore-mailbox -RSGMailbox 'testE12mbx1' -RSGDatabase 'Recovery Storage Group\Mailbox Database' -id 'testE12mbx2' -TargetFolder ‘Backup’ -StartDate ‘02/02/05’ –EndDate ‘02/05/05’

Scenario 8: Restore mailbox content from all mailboxes in a Database to a folder inside an active mailbox
An administrator wants to restore email content from all mailboxes in the RSG to a folder inside an active mailbox:

MONAD Syntax – restore all RSG mailboxes to a folder called DatabaseBackup inside mailbox testE12mbx2:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox -id 'testE12mbx2' -TargetFolder ‘DatabaseBackup’

Customer Setting:

Hardware malfunction resulted in corrupt databases which cannot be brought online in their current state. End users rely on timely email communication for business continuity. Need to enable email functionality ASAP.
If the current server and disk is available and functioning properly, Exchange administrator can enable dial tone services to all the users by moving the corrupt files to a different location and mounting an empty database online in its original location.
While the dial tone is in production, admin will recover original database from backup in a separate location. After this is complete, the production server switches to the backup database and the dial tone database is copied to the RSG. Then, the dial tone content is merged back into the new production database by using restore-mailbox so users do not lose any content.

Customer Goal:
Ability to restore mailbox content from RSG to the active mailbox that has the same ID, individually and in bulk.

Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics

Scenario 9: Restore mailbox content to active mailbox based on User ID
An administrator wants to restore email content from the RSG into a currently active mailbox:

MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:

MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database'

Scenario 10: Restore mailbox content from all mailboxes in a Database to active mailboxes
An administrator wants to restore email content from all mailboxes in the RSG to their currently active mailbox counterparts:

MONAD Syntax – restore all RSG mailboxes to their currently active mailbox counterparts:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox

Customer Setting:

Hardware failures or some corruption resulted in Exchange server not functioning properly. While OS/Exchange Administrators investigate the issue, end users need access to email.
Exchange does not allow moving mailboxes to a different server if the original server is not available since move is associated with moving a mailbox with its associated full content. In order to provide dial tone functionality in this case, Admin would use a clean database in a separate server, and use the move-mailbox configuration only option to change the AD settings so the mailboxes would point to this new database. While the dial tone is in production, admin will recover original database from backup in a separate location (if the original server was fixed, that can be used as the location for the backup). After this is complete, the production server switches to the backup database and the dial tone database is copied to the RSG. Then, the dial tone content is merged back into the new production database by using restore-mailbox so users do not lose any content.

Customer Goal:
Ability to restore mailbox content from RSG to the active mailbox that has the same ID, individually and in bulk.

Parameters
covered by use
cases:
-Identity, -TargetFolder, -RSGDatabase, -RSGMailbox

Additional tasks
covered by use
cases:
Get-mailboxstatistics

Scenario 11: Restore mailbox content to active mailbox based on User ID
An administrator wants to restore email content from the RSG into a currently active mailbox:

MONAD Syntax – restore all RSG content of mailbox testE12mbx1 to the currently used testE12mbx1 mailbox:

MSH> restore-mailbox -id testE12mbx1 -RSGDatabase 'Recovery Storage Group\Mailbox Database'

Scenario 12: Restore mailbox content from all mailboxes in a Database to active mailboxes
An administrator wants to restore email content from all mailboxes in the RSG to their currently active mailbox counterparts:

MONAD Syntax – restore all RSG mailboxes to their currently active mailbox counterparts:

MSH> get-mailboxstatistics -database 'recovery storage group\mailbox database' | restore-mailbox

Prueba el nuevo Internet Explorer 9

2010-09-23T06:22:00.000-07:00

Internet Explorer 9 Beta is here, and it's fast. Web sites and applications look and perform as if they were native to your PC, and you'll notice a clean look and increased viewing area that makes Web sites shine. Taking full advantage of your PC's hardware through Windows, Internet Explorer 9 Beta delivers graphically rich and immersive experiences.

http://windows.microsoft.com/en-US/internet-explorer/products/ie-9/home?os=win7&arch=a&browser=ie

Nuevo White Paper: Plan, Implement, and Support SQL Server Virtualization

2010-09-23T06:19:00.000-07:00

Ahora es posible virtualizar pesados servidores SQL Server y mover máquinas virtuales Hyper-V dentro de un failover cluster sin tiempo de parada.

Anexo este nuevo documento de Microsoft con toda la información relativa

http://click.email.microsoftemail.com/?qs=8ee6f7c96b13bffa62f7d5631267724ce6516102206ab66324ce454229ee339801d418fbc2fde05a

Active Directory Backup and Restore in Windows Server 2008

2010-02-08T07:48:00.000-08:00

Extraído del siguiente enlace os dejo este magnifico artículo del TechNet que explica las nuevas funcionalidades del bakup de Windows 2008 con respecto a Active Directory.

http://technet.microsoft.com/en-us/magazine/2008.05.adbackup.aspx?pr=blog

Installing Windows Server Backup

Windows Server Backup is a "feature" in Windows Server 2008 and is not installed by default. Before you can perform a backup with Windows Server Backup, you have to install the feature, using either Server Manager, or the SERVERMANAGERCMD command-line utility:

C:\> servermanagercmd -install Backup-Features

Windows Server Backup is composed of two sub-features, Windows Server Backup and Command-line Tools. Note that Command-line Tools refers to a set of Windows PowerShellTM cmdlets—not the WBADMIN .EXE command-line tool. Thus, if you choose to install both sub-features, you must install the Windows PowerShell feature.
After installing Windows Server Backup, you can find the Microsoft Management Console (MMC) snap-in under the Storage node in Server Manager and on the Administrative Tools menu. If you are installing Windows Server Backup on a Windows Server 2008 Server Core installation, use the OCSETUP command (it's important to note that the OCSETUP command is case-sensitive):

C:\> ocsetup WindowsServerBackup

A complete description of the installation process is available at go.microsoft.com/fwlink/?LinkId=113146.
Note that Windows Server Backup can't restore images created with NTBACKUP. For this unlikely scenario, Microsoft has made available a downloadable version of NTBACKUP for Windows Server 2008 (see go.microsoft.com/fwlink/?LinkId=113147).

The Windows Server Backup Components

The way in which the Windows Server Backup application is architected represents a significant change. This new backup solution consists of four components:

•MMC user interface (WBADMIN.MCS)
•Command-line interface (WBADMIN.EXE)
•Backup service (WBENGINE.EXE)
•Set of Windows PowerShell cmdlets

Splitting the application into a client and a service has several advantages, the most important being increased reliability. Whether you start a backup from either the MMC client or the command-line interface, the WBENGINE service is doing the heavy lifting. The client programs just report the status of the backup. Thus, terminating the client will not result in a half-baked backup. The client will stop and the service will continue to completion. Of course, if you really want to stop the backup, you can, but you must do so explicitly.

The other advantage of this split architecture is that you can use the client to manage backups on remote machines. This is particularly nice when you have to back up Windows Server 2008 Core machines.

Windows Server Backup supports bare-metal restores using the Windows Recovery Environment, or WinRE, which comes on the Windows Server 2008 installation media. WinRE simplifies the process of recovering a server from scratch. I will discuss performing a bare-metal restore later in this article. It's worth mentioning that Windows Server Backup supports several Group Policy settings for managing backups—these are outlined in the "Group Policy Settings" sidebar.

Volume Shadow Copy Service

Windows Server Backup uses Volume Shadow Copy Service in three different ways. When you start a full backup on Windows Server 2008, the first thing that the application does is make a shadow copy of all of the source volumes. Doing this provides a consistent view of the file system for the backup software to work with. (This is similar to what NTBACKUP did.) Windows Server Backup then copies blocks from the source volume—block by block—to the backup target, building a VHD image for each backed-up volume in the process.

Unless you specify otherwise, Windows Server Backup also creates a snapshot of the source volume so that Volume Shadow Copy Service will keep track of all changed blocks on the volume. This enables Windows Server Backup to create block-level incremental backups that only require reading the changed blocks of the source volume. Rather than reading and writing an entire file because one bit was changed in the file, Windows Server Backup can read and write only the block that has changed.

This makes for very efficient incremental backups, but at the expense of extra disk I/O for write operations on the source volume. If you are backing up a particularly busy or performance-critical volume, you should disable the Volume Shadow Copy Service snapshot on the source volume by selecting the Configure Performance Settings link and then disabling incremental backups on that volume (as shown in Figure 1).

Figure 1 Disable incremental backups on busy volumes (Click the image for a larger view)

When the backup is complete, Windows Server Backup takes a snapshot of the target volume (assuming you are backing up to a locally attached hard disk). During the next backup, the target VHD files are overwritten. But since Volume Shadow Copy Service is maintaining shadow copies of the target volume, there are, in effect, multiple versions of each VHD file corresponding to each of the full backups. You essentially get multiple full backups for the cost of one full backup and the changed blocks.

Backing Up to Network Shares

Backing up to a network share is just as easy as backing up to a local volume. The significant difference is that it can't create a Volume Shadow Copy Service snapshot of the remote volume. Therefore, each full backup will overwrite the previous, leaving you with just the latest full backup image of each server on a network share. Due to this limitation, you can't use the Windows Server Backup scheduler to schedule backups to a network share. You can, however, use the Windows Task Scheduler to run the WBADMIN command-line program to perform full backups to a network share. If you elect to schedule full backups to a network share this way, change the target folder for each backup to avoid overwriting previous backups.

Backing Up to Recordable DVDs

Windows Server Backup also supports backing up to optical media, such as writable DVDs. And you can create backup sets that span multiple volumes, as well. Windows Server Backup always compresses backups to DVDs, which means that you can only perform full system or full volume restores from DVD. Windows Server Backup doesn't support system state or file level backups and restores when using DVDs. And you can't schedule backups to DVD.

System State Backups and Restores

System state backups, which include only select files and some application databases (rather than entire volumes) is handy and often essential. But early builds of Windows Server 2008 didn't support system state backups and restores. Instead, the backup tool just backed up critical system volumes (meaning any volumes necessary for recovering and rebooting the OS and key applications). These critical system volumes were the volume-oriented equivalent of a system state backup.

Acknowledging feedback from customers, Microsoft added system state backup and restore capabilities to Windows Server Backup. The application creates multiple VHD files, one for each volume that hosts the system state data, but it only copies the necessary files and databases to the VHDs. Another issue is that when you perform a system state backup, Windows Server Backup does not create a snapshot of the target volume as it does in the normal backup process. Instead, each system state backup generates an entirely new set of VHD files, which means you don't get the space efficiencies you find with the snapshot-based volume backups.

You can only perform a system state backup using the WBADMIN.EXE command-line program—the MMC snap-in doesn't provide this option. To perform a system state backup, you use this command:

C:\> wbadmin start systemstatebackup –backuptarget:e:

WBADMIN will then back up the critical system files and application databases to the target volume, in a folder reserved for system state backups. The system state backup on a 32-bit Windows Server 2008 domain controller (DC) with a default directory information tree (DIT) runs a little more than 6GB—this is more than 5GB larger than on Windows Server 2003 due in part to the fact that Windows Server Backup is capturing core OS files that NTBACKUP didn't.
The time required to back up the system state is also greater, as you would expect. These initial numbers, of course, are based on a pre-release version of the OS. You'll certainly need to test this in your own environment, but it's likely that you'll need to plan for larger system state backups (and longer backup times) when you move your domain controllers to Windows Server 2008.

Backing Up a Server with the MMC

When you run the Windows Server Backup MMC (see Figure 2), you have the option of either setting up a backup schedule or immediately running an ad hoc backup. In this case, I select Backup once to perform an immediate backup.

Figure 2 Windows Server Backup MMC (Click the image for a larger view)
As you can see in Figure 3, I can choose whether to back up all the volumes on the server or back up just the specific volumes that I choose. If I select Full server, Windows Server Backup will back up all mounted volumes, but I won't have the option of backing up to a mounted hard drive—instead, I will have to back up to a recordable DVD or to a network share.

Figure 3 Using the backup configuration dialog to specify all or select volumes (Click the image for a larger view)
In this example, I want to back up to a local hard drive, so I select the Custom option.
A dialog then lets me select the volumes to back up (see Figure 4).

By default, Windows Server Backup checks the Enable system recovery box, which causes Windows Server Backup to select the boot volume, the OS volume, and any other volumes with critical system files and application databases. On a DC, this includes the volumes hosting SYSVOL, the Active Directory DIT, and Active Directory logs. This is the equivalent of a system state backup but it backs up all the critical volumes, not just the critical files on those volumes.
In fact, I even have the ability to perform a system state recovery from a system recovery backup set.

Figure 4 Selecting specific volumes to back up (Click the image for a larger view)

After I select the destination type (local drive or network share) and specify the destination, Windows Server Backup prompts me to select either a "VSS copy" backup or a "VSS full" backup. The terminology is a little confusing, as both options will back up the selected volumes in their entirety. The difference lies in the way Windows Server Backup handles the source files after they've been backed up. If you select the copy option, Windows Server Backup will leave the backed up files alone. If you choose the full option, Windows Server Backup will then reset the archive.

Backing Up a Server from the Command Line

If you want to script the backup process, or if you are backing up a server on a Server Core installation, you can use the WBADMIN.EXE command-line program. WBADMIN provides a complete set of options that perform essentially the same functions as the MMC snap-in, including managing backup schedules.

Suppose I want to start the WBENGINE service, which will in turn perform the backup process. All I do is enter this command:

C:\> wbadmin start backup –include:c:,d: –backuptarget:e:

Or to back up all critical system volumes, I can enter this command:

C:\> wbadmin start backup -allcritical –backuptarget:e:

After starting the backup, WBADMIN continues to run and show the progress of the backup. If I terminate WBADMIN, the backup will continue in the background. I can then reconnect WBADMIN to a running backup using this command:

C:\> wbadmin get status

And if I want to terminate a running backup, I just enter this:

C:\> wbadmin stop job

Scheduling Backups with the MMC

The backup scheduler that is integrated with the Windows Server Backup is really designed to do one thing: simplify scheduling of daily full-system backups to a local disk volume. You can use the built-in scheduler to automatically rotate backups among multiple target volumes.
If you have easily removable hard drives (or you are using USB-attached hard drives), you can use this feature to set up a rotation scheme where you remove the backup disk and store it off-site and return the oldest backup disk to the server for the next scheduled backup.

The Windows Server Backup scheduler only lets you schedule backups that always occur daily. There is no way to schedule backups for, say, Mondays, Wednesdays, and Fridays. So if you don't want to run your scheduled backups daily, you'll have to work directly with the Windows Task Scheduler.

When you set up a scheduled backup to a local disk, Windows Server Backup takes responsibility of the disk, formatting it, setting up a specific folder structure, and making the target disk invisible to Windows Explorer. The target disk must be a basic volume—Windows Server Backup cannot backup to disks configured as dynamic volumes.

Scheduling backups through the MMC snap-in is very easy. In this example, I first select the Backup Schedule link, specify the type of backup and the volumes to back up, and then Windows Server Backup shows the "Specify backup time" dialog (see Figure 5).

Figure 5 Specifying when daily backups should occur (Click the image for a larger view)

After selecting the times at which I want the backup to occur, I can select the volume (or volumes) to which I want to back up. In this case, I select the backup volume E:, as shown in Figure 6.

Windows Server Backup tries to select an appropriate target volume for you, but if it happens that the disk you want to back up to doesn't appear, you can use the Show All Available Disks button to view all attached disk devices. After going through a couple of "confirm" dialogs, Windows Server Backup formats the target volume(s) and schedules the backup task using the Windows Task Scheduler.

Figure 6 Specifying the destination disk for a scheduled backup (Click the image for a larger view)

Each time a scheduled backup is completed, Windows Server Backup takes a snapshot of the target volume. And every seven days, it creates a new base image. Activity is logged in the Microsoft/Backup/Operational log. You can check there to see if your backups completed successfully; you can also associate a task, such as sending an e-mail message, with the success and failure events so you will always know the status of your scheduled backups.

Scheduling Backups from the Command Line

If you are scheduling backups on a Server Core installation or you just want to script the process, you can manage the backup schedule using the WBADMIN command-line. To add a scheduled backup, you use the WBADMIN ENABLE BACKUP command, specifying the target, source, and scheduled time, like so:

C:\> wbadmin enable backup –addtarget:e: -include:c:,d: -schedule:06:00,12:00,18:00

This command would back up the C: and D: drives to the E: drive three times a day, at 6:00 A.M., 12:00 P.M., and 6:00 P.M. (note that all times are specified using a 24-hour clock). To back up all critical system volumes (from which you can perform a bare metal restore or a system state restore), replace the –include switch with –allcritical.

You can also use WBADMIN to disable all scheduled backups, like this:

C:\> wbadmin disable backup

This command will delete all the scheduled backup jobs created by the Windows Server Backup scheduler and release all the backup target volumes for normal use. Note that you can always use the WBADMIN MMC snap-in to remotely manage the backup and restore activities of Server Core servers.

Bare-Metal Recovery of a Domain Controller

One of the most exciting improvements for backup and recovery is how the WinRE has been incorporated into the installation process. When you boot Windows Server 2008 from the installation media, you can choose the Repair your computer option, as shown in Figure 7. I point this out because it is easy to miss if you're not looking for it.

Figure 7 The Repair your computer option is available on the installation screen (Click the image for a larger view)
After I select the repair option on the installation screen, Windows lets me select a recovery option, as shown in Figure 8. In this case, I select Windows Complete PC Restore, which invokes the Windows Recovery Environment.

Figure 8 Specifying system recovery options (Click the image for a larger view)

After you select the operating system you want to repair (there is typically only one choice), WinRE allows you to select the backup from which you want to restore. By default, WinRE selects the most recent complete system backup, but you can specify other backups stored on local disks or search the network for backups that are stored on file shares on other servers.

In my example, I select the most recent complete system backup. The next dialog lets me format and repartition all the disks before they are restored. This is an appropriate option if the problem you are recovering from was caused by some sort of disk failure or if you've replaced one or more disk drives in the server.

After a couple of confirming dialogs, WinRE starts the restore process and the server reboots. This is a pretty painless way to perform a bare-metal recovery on a server.

System State Recovery of a Domain Controller

If you need to recover from some sort of Active Directory-related problem—such as recovering a deleted OU from backup—you should restore the Active Directory Domain Services (ADDS) database to an earlier state, rather than restore the entire system. Even though you can stop ADDS like a service in Windows Server 2008, you still need to boot the server into Directory Services Restore Mode (DSRM) to perform a system state restore on a domain controller.

Changing the boot options to make Windows Server 2008 boot into DSRM is not quite as easy as it used to be. The entire Windows boot environment has been re-engineered to support the new Extensible Firmware Interface (EFI) and the old school boot.ini file no longer exists. Instead, Windows Server 2008 uses Boot Configuration Data (BCD) to control the boot process.

The simplest way to manage the BCD is to use the BCDEDIT command line program. A discussion covering all the BCDEDIT commands and options would require its own article, so I'll just show you some useful examples here.
To reboot a Windows Server 2008 DC into DSRM, use the following command:

C:\> bcdedit /set safeboot dsrepair

This will set the safeboot option for the default boot loader entry. In a fresh Windows Server 2008 installation, there is only one boot loader entry, WINLOAD.EXE. To remove the safeboot option and reboot in normal mode, use this command:

C:\> bcdedit /deletevalue safeboot

To make things a little easier for yourself, you can configure two bootloader entries on your DCs—one for a normal boot and one for a DSRM boot. This way, you can change the boot options using the Startup and Recovery settings dialog available under System Settings. To add a new bootloader entry, use this command:

C:\> bcdedit /copy {default} /d "Directory Service Repair Mode"

This action will create a new bootloader entry by copying the default bootloader entry. BCDEDIT will display something like this: Copy Code The entry was successfully copied to {c50d4710-a1f0-11dc-9580-0003ff402ae9}.
The GUID identifies the new entry. Then use this command to set the safeboot option for the new bootloader entry in the BCD:

C:\> bcdedit /set {} safeboot dsrepair

You can now switch from normal boot mode to DSRM boot mode using the Startup and Recovery settings (see Figure 9).

Figure 9 Disable incremental backups on busy volumes

Before you use WBADMIN to start a system state restore, you must identify the backup from which you want to restore. WBADMIN can perform a system state restore from either a full system backup, a backup that contains just the critical system volumes, or a system state backup.

In any of these cases, you have to specify the version of the backup you want to use. The easiest way to identify the backup versions that are available is to use the following WBADMIN command:

C:\> wbadmin get versions

WBADMIN will then display the backup versions in a form similar to the info shown in Figure 10. Note that each backup has a backup time, backup target, a version identifier (which, by the way, is the time and date the backup was started in Universal Mean Time), and a list of the types of recovery operations the backup can support.

Figure 10 Identify backups available for recovery

wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Backup time: 11/30/2007 3:47 PM
Backup target: Fixed Disk labeled E:
Version identifier: 11/30/2007-22:47
Can Recover: Application(s), System State
Backup time: 12/1/2007 10:46 PM
Backup target: Fixed Disk labeled Backup(E:)
Version identifier: 12/02/2007-05:46
Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State
Backup time: 12/2/2007 5:58 PM
Backup target: Fixed Disk labeled Backup(E:)
Version identifier: 12/03/2007-00:58
Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State
Backup time: 12/3/2007 11:25 AM
Backup target: Fixed Disk labeled E:
Version identifier: 12/03/2007-18:25
Can Recover: Application(s), System State

In this case, I select the most recent backup and start the system state restore with this WBADMIN command:

C:\> wbadmin start systemstaterecovery –version:12/03/2007-18:25

This will perform a non-authoritative restore. If you want to perform an authoritative restore of the SYSVOL, you can just mark the restored SYSVOL replica as being authoritative by adding the authsysvol option to the WBADMIN command. For more information on this process, see go.microsoft.com/fwlink/?LinkId=113152.

Taking Active Directory Snapshots

One of the most exciting changes in terms of backup for Active Directory has nothing at all to do with Windows Server Backup. In Windows Server 2008, you can take advantage of the fact that Active Directory can provide Volume Shadow Copy Service snapshots. These snapshots are very lightweight, point-in-time backups of the running Active Directory service. And even better, they take only a few seconds of your time to create! You can then mount these snapshots and access them using normal LDAP-based utilities, such as the LDP tool.

You take snapshots of ADDS or Active Directory Lightweight Directory Services (ADLDS) using the NTDSUTIL command, as shown here:

ntdsutil: snapshot
snapshot: activate instance ntds
Active instance set to "ntds".
snapshot: create
Creating snapshot...
Snapshot set {42c44414-c099-4f1e-8bd8-4453ef2534a4} generated successfully.
snapshot: quit
ntdsutil: quit

This sequence of NTDSUTIL commands creates a Volume Shadow Copy Service snapshot of the volumes that contain the Active Directory DIT, logs, and SYSVOL.
Even though Active Directory is still being updated, Volume Shadow Copy Service uses a copy-on-write strategy to make sure that the snapshots you've taken are properly maintained. Note that the snapshots are not a complete copy of the DIT.
They are really just a collection of disk blocks in the DIT that have been modified since the snapshot was taken. By combining these blocks with the current copy of the DIT, VSS can present the Active Directory DIT just as it appeared at the time of the snapshot. Figure 11 shows how to delete old or unneeded snapshots.

Figure 11 Delete unneeded snapshots

C:\> ntdsutil
ntdsutil: snapshot
snapshot: list all
1: 2007/12/03:23:18 {42c44414-c099-4f1e-8bd8-4453ef2534a4}
2: C: {c0dd71ba-5bcd-4daf-9fbb-5cfbdd168022}
3: D: {2bbd739f-905a-431b-9449-11fba01f9931}
snapshot: delete 1
Snapshot {c0dd71ba-5bcd-4daf-9fbb-5cfbdd168022} mounted as C:\$SNAP_200712032318_VOLUMEC$\
Snapshot {2bbd739f-905a-431b-9449-11fba01f9931} mounted as C:\$SNAP_200712032318_VOLUMED$\
snapshot: quit
ntdsutil: quit
C:\>

Mounting Active Directory Snapshots

In order to use one of these snapshots, you must first instruct Volume Shadow Copy Service to make the snapshot available to the file system. You do this using the ntdsutil command to list the available snapshots and then mount the snapshot you are interested in (see Figure 12).

Figure 12 Using ntdsutil to mount a snapshot

C:\> ntdsutil
ntdsutil: snapshot
snapshot: list all
1: 2007/12/03:23:18 {42c44414-c099-4f1e-8bd8-4453ef2534a4}
2: C: {c0dd71ba-5bcd-4daf-9fbb-5cfbdd168022}
3: D: {2bbd739f-905a-431b-9449-11fba01f9931}
snapshot: mount 1
Snapshot {c0dd71ba-5bcd-4daf-9fbb-5cfbdd168022} mounted as C:\$SNAP_200712032318_VOLUMEC$\
Snapshot {2bbd739f-905a-431b-9449-11fba01f9931} mounted as C:\$SNAP_200712032318_VOLUMED$\
snapshot: quit
ntdsutil: quit
C:\>

The "list all" command lists all the available Active Directory snapshots that are currently being maintained by Volume Shadow Copy Service. The "mount 1" command mounts the selected snapshots of the Active Directory DIT and log volumes and makes them available in the file system. They are located at C:\$SNAP_200712032318_VOLUMEC$\ and C:\$SNAP_200712032318_VOLUMED$\.
If you look in these folders, you'll see the entire contents of those volumes as they were when the snapshot was taken. Note, however, that the mounted snapshots are read-only—meaning you can't modify any of the files in the mounted snapshot.

Recovering Data from Active Directory Snapshots

The task of mounting the snapshots of the volumes that contain Active Directory seems a bit like magic. How can you get to the Active Directory data contained in those snapshots? The secret is the DSAMAIN command. This is the executable that runs ADLDS. It is essentially a standalone LDAP server that shares almost all of its code with ADDS. You can use DSAMAIN to make the mounted snapshots look like a read-only LDAP server containing the Active Directory data as it was at the time the snapshot was taken.
Consider this command:

C:\> dsamain –dbpath c:\$snap_200712032318_volumed$\ntds\dit\ntds.dit -ldapport 10000

This mounts the ntds.dit file located in the c:\$snap_200712032318_volumed$\ntds\dit folder and makes it available to LDAP operations on TCP port 10000 (or whatever open port you specify). DSAMAIN will open the LDAPS port (the port used for LDAP over Secure Sockets Layer) on the port you specified plus one (in this case, 10001), the GC port (the port used for global catalog connections) on the port you specified plus two (10002), and the GCS (Global Catalog over Secure Sockets Layer) port on the port you specified plus three (10003).

You can use any LDAP program (such as LDP) to access the mounted DIT on the specified port. But in Windows Server 2008, Active Directory Users and Computers (ADUC), Sites and Services, and Domains and Trusts, as well as ADSIEDIT, have all been modified to allow you to connect them to a DIT mounted using DSAMAIN. If you right-click on the top-level node in the navigation pane of any ADUC and select Change Domain Controller, you will see the dialog box shown in Figure 13. If you simply type the name or IP address of the server hosting the mounted snapshot, along with the port (in my example, localhost:10000), ADUC will connect to the mounted snapshot, allowing you to browse the contents of the directory as it existed at the time of the snapshot. Pretty amazing, isn't it?

Figure 13 Connecting Active Directory users and computers to a mounted snapshot (Click the image for a larger view)
Being able to access directory data in this way makes many kinds of data recovery tasks much easier than they used to be. For instance, to recover a deleted object from a backup formerly required that you perform a non-authoritative restore of the backup on an existing DC and then perform an authoritative restore of the deleted object. And if the backup you restored didn't have the correct data, you had to start all over again with a different backup. Now, using tombstone reanimation and snapshots, you can quickly find and recover deleted data, and you don't even have to take the domain controller offline to do it.

There are some limitations, however. For instance, each active snapshot increases the disk I/O associated with write operations to the directory, so you probably shouldn't have more than one or two snapshots active at any point in time on a production DC. Also, the longer you keep snapshots active, the larger the Volume Shadow Copy Service delta store becomes—this can also affect performance. And, of course, simply recovering a deleted object is only the first part of the recovery problem. You will probably have to recover the object's linked attributes, such as group memberships, as well. But even in this case, the snapshot can help you identify all the groups the deleted object was a member of.

A Sound Backup and Recovery Strategy for Active Directory

Windows Server 2008 brings an entirely new backup and recovery system to the table. Some of the changes may at first cause weeping and gnashing of teeth. But once IT organizations have accepted these changes and incorporated the new backup technology into their day-to-day operations, they will wind up with a more effective backup and recovery implementation.
Even with all of the changes in the way you back up servers in Windows Server 2008, the basic strategy for backing up and recovering Active Directory doesn't really change that much. So when planning your strategy, be sure to keep these best practices in mind:

•Schedule periodic full system backups so you can recover a DC after a hardware failure. How frequently you schedule full backups of a DC depends on how frequently your data is updated, your tolerance for downtime and/or data loss, and the effort that may be required to rebuild the DC from scratch.

•Schedule frequent system state backups to back up changes in Active Directory. How frequently you perform system state backups depends on your tolerance for lost Active Directory data. But you should do this at least once a day. If you have the hardware, keep at least one or two system state backups on a local disk and copy older system state versions to a DVD or to a network share.

•Be sure to do system state backups on at least two DCs in each domain. This will provide some insurance in case one of the backups is bad or unavailable.
Be sure to back up DCs with application partition replicas if you have defined them. And consider creating a Windows Recovery Environment partition on your DCs so you can boot quickly into WinRE in case a critical system drive fails

Windows 2008 AD Recycle Bin

2010-02-07T23:50:00.000-08:00

Para todos aquellos que están interesados en la carácteristica AD Recycle Bin de Windows Server 2008 R2, hemos recolectado los siguientes recursos para vosotros...

Active Directory Services Team Blog – Recycle Bin Post

Active Directory Recycle Bin Step-by-Step Guide

Joey Snow’s AD Recycle Bin Demo on TechNet EDGE

Cris e. avis article with answers to common AD recycle Bin questions…

Test de registros SRV con NSLOOKUP

2010-02-04T08:05:00.000-08:00

Con estos test, se pueden comprobar con nslookup si DNS tiene las entradas correctas apuntando a los registros SRV de Directorio Activo GC, LDAP y KERBEROS donde
DOMINIO.ES es el nombre de la zona de busqueda directa.

TEST DE REGISTROS SRV EN LA RUTA _MSDCS.DOMINIO.ES

1) Teclea Start, click Run.
2) En Open, Teclea cmd.
3) Teclea nslookup, and then press ENTER.
4) Teclea set type=all, and then press ENTER.

Para Comprobar SRV Records de LDAP

Teclea:

_ldap._tcp.Nombre-predeterminado-primer-sitio._sites.dc._msdcs.dominio.es

then press ENTER.

Para Comprobar SRV Records de KERBEROS

Teclea:

_kerberos._tcp.Nombre-predeterminado-primer-sitio._sites.dc._msdcs.dominio.es

then press ENTER.

Para Comprobar SRV Records de CATALOGO GLOBAL

Teclea:

_gc._tcp.Nombre-predeterminado-primer-sitio._sites.dc._msdcs.dominio.es

then press ENTER.

TEST DE REGISTROS SRV EN LA RUTA _TCP.DOMINIO.ES

1) Teclea Start, click Run.
2) En Open, Teclea cmd.
3) Teclea nslookup, and then press ENTER.
4) Teclea set type=all, and then press ENTER.

Para Comprobar SRV Records de LDAP

Teclea:

_ldap._tcp.dominio.es

then press ENTER.

Para Comprobar SRV Records de KERBEROS

Teclea:

_kerberos._tcp.dominio.es

then press ENTER.

Para Comprobar SRV Records de CATALOGO GLOBAL

Teclea:

_gc._tcp.dominio.es

then press ENTER.

Habilitar / Deshabilitar réplicas de Directorio Activo

2010-02-04T07:15:00.000-08:00

Turn on inbound replicationUpdated:

Applies To: Windows Server 2008, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

You can use this procedure to turn on inbound replication after it has been turned off manually.

Administrative credentials

To complete this procedure, you must be a member of the Domain Admins group in the domain of the domain controller whose replication you are enabling, or you must be a member of the Enterprise Admins group.

To turn on inbound replication
1.Open a Command Prompt.

2.Type the following command, and then press ENTER:

repadmin /options ServerName -DISABLE_INBOUND_REPL

where ServerName is the network basic input/output system (NetBIOS) name of the domain controller.

3.Verify that the option is set. The following message should appear:

Current DC options: DISABLE_INBOUND_REPL

New DC Options:

Current DC Options displays the conditions that were in effect at the time that you ran the command. New DC Options shows the effect of the command, which is that the option to disable replication is not set.

Turn off inbound replicationUpdated:

Applies To: Windows Server 2008, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

You can use this procedure to turn off inbound replication so that objects on a domain controller cannot be updated by replication from another domain controller.

Administrative credentials

To complete this procedure, you must be a member of the Domain Admins group in the domain of the domain controller whose replication you are disabling, or you must be a member of the Enterprise Admins group.

To turn off inbound replication
1.Open a Command Prompt.

2.Type the following command, and then press ENTER:

repadmin /options ServerName +DISABLE_INBOUND_REPL

where ServerName is the network basic input/output system (NetBIOS) name of the domain controller.

3.Verify that the option is set. The following message should appear:

New DC Options: DISABLE_INBOUND_REPL

Error 8457 The destination server is currently rejecting replication requests

2010-02-04T07:14:00.000-08:00

Si tu ejecutas "repadmin /showreps" ves este error:

"Can't retrieve message string 8456 (0x2108), error 1815"

Additional Data
Error value:
8457 The destination server is currently rejecting replication requests.

Ejecuta estos comandos

repadmin /options dcname -disable_inbound_repl

repadmin /options dcname -disable_outbound_repl

Después ejecuta "repadmin /showreps" o abre el Replication Monitor

Windows 7: Copy A Modified User Profile Over The Default Profile

2010-01-21T23:58:00.000-08:00

Según el artículo de Microsoft que anexo, para personalizar un perfil de usuario de red predeterminado o un perfil de usuario obligatorio, es necesario personalizar en primer lugar el perfil de usuario local predeterminado. Una vez realizado, ya puedes copiar el perfil de usuario local predeterminado en el recurso compartido correspondiente para convertir ese perfil de usuario en el perfil predeterminado de red o en un perfil de usuario obligatorio.

Cuando el perfil predeterminado se personaliza de la forma descrita en este artículo, éste reconstruye el perfil de origen con un formato que permite que lo utilicen varios usuarios. Se trata del único método de personalización del perfil de usuario predeterminado para el sistema operativo Windows 7. Si intenta utilizar otros métodos para personalizar el perfil, puede provocar que se incluya información extraña en el nuevo perfil de usuario predeterminado. Dicha información podría causar graves problemas relacionados con la aplicación y la estabilidad del sistema operativo.

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

Después de esto, aquí debajo describimos un Workaroun que puedes usar en entornos de testing para modificar el Default User Profile.Tener en cuenta que no está soportado por Microsoft con lo que usarlo bajo vuestra propia resposnsabilidad.
Espero que os sea de utilidad.

Windows 7: Copy A Modified User Profile Over The Default Profile

Below is the work around you can use to modify the Default profile by copying any profile you have previously modified over the Default profile. It is VERY much not supported by Microsoft, but for my limited tests seems to work.

The Steps: After setting up the profile for one user, lets call the account "Test", do the following:

0. Login as an admin user, but NOT Test (you don't want the files in the profile to be locked).

1. Go to c: drive in Explorer (or whatever your system drive is), hit the ALT key, go to the Tools Menu-> Folder Options and start unchecking "Hides" so Explorer sees all files (system, hidden and what not).

2. Go to Users\ and rename "Default" to "Default Back" (we want to keep the old one around in case things go south and we need to but the original Default profile back).

3. Make a copy of "Test", then rename the copy of "Test" (not the original!!!) to "Default".

4. Right click on "Default" and set the permissions so that the "Everyone" and "Users" groups have "Read & Execute", "List Folder Content" and "Read" NTFS permissions (this was the default already when I tested). At this point, you can use the Right click Computer -> "Properties"-> "Advanced System Settings"->"User Profiles" tool to delete the Adrian profile if you like.

5. Try to login as an account that does not already have a profile. If the new user's profile looks like the setting you did for "Test", all is good in the hood.

I have no idea what other problems may crop up later with this method, and keep in mind this is not the way Microsoft wants you to copy profiles. Use at your own risk, but so far these instructions have worked fine when I try to overwrite the Default user profile.

Security Advisory KB979352

2010-01-21T09:02:00.000-08:00

Buenas tardes.Os informo de la próxima publicación de un nuevo boletín de seguridad considerado como Crítico y que afecta a todas las versiones de Internet Explorer, el cual será lanzado hoy 21 de Enero, fuera del ciclo mensual de boletines, debido a su alto impacto y criticidad.

Por este motivo, os recomiendo su revisión y la instalación de la actualización correspondiente.
A continuación os dejo los detalles técnicos de este boletín de seguridad.

--------------------------------------------------------

What is the purpose of this alert?

This is an advance notification of one out-of-band security bulletin that Microsoft is intending to release on January 21, 2010. The bulletin will be for Internet Explorer to address limited, targeted attacks against customers using Internet Explorer 6, as well as fixes for vulnerabilities rated Critical that are not currently under active attack.

The purpose of the notification is to assist customers with resource planning for this security bulletin release. The information offered in the notification is purposely general in nature to provide enough information for customers to plan for deployment without disclosing vulnerability details or other information that could put them at risk.

New Bulletin Summary
Bulletin Identifier Internet Explorer
Maximum Severity Rating Critical
Impact of Vulnerability Remote Code Execution
Restart Requirement The update will require a restart.
Affected Software All supported versions of Internet Explorer on Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008*, Windows 7, and Windows Server 2008 R2*.

* Where indicated in the Affected Software table on the Advance Notification Web Page, the vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2, when installed using the Server Core installation option. Please see the Advance Notification Web page at the link below for more details.

Although we do not anticipate any changes, the information provided in this summary is subject to change until the release.

The full version of the Microsoft Security Bulletin Advance Notification for this release can be found at http://www.microsoft.com/technet/security/bulletin/ms10-jan.mspx.

Public Bulletin Webcast

Microsoft will host a webcast to address customer questions on these bulletins:
Title: Information about Microsoft January (OOB) Security Bulletin (Level 200)
Date: Thursday, January 21, 2010, at 1:00 PM Pacific Time (U.S. & Canada).
URL: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032440627
At this time no additional information on these bulletins, such as details regarding severity or details regarding the vulnerability, will be made available until the bulletin is published.

Resources related to this alert

1. Security Advisory 979352 – Vulnerability in Internet Explorer Could Allow Remote Code Execution: http://www.microsoft.com/technet/security/advisory/979352.mspx

2. Microsoft Knowledge Base Article 979352: http://support.microsoft.com/kb/979352

3. Issue Landing Page: http://www.microsoft.com/security/updates/ie.aspx

4. Microsoft Security Response Center (MSRC) Blog: http://blogs.technet.com/msrc/

5. Microsoft Security Research & Defense (SRD) Blog: http://blogs.technet.com/srd/

6. Microsoft Malware Protection Center (MMPC) Blog: http://blogs.technet.com/mmpc/

7. Microsoft Security Development Lifecycle (SDL) Blog: http://blogs.msdn.com/sdl/

SQL Server: Recovering from Disasters Using Backups

2009-12-11T02:06:00.001-08:00

Extraido integramente del artículo original de Paul S. Randal publicado en TechNet Magazine, os incluimos este valioso artículo de recuperación de desastres de SQL Server:

http://technet.microsoft.com/en-gb/magazine/ee677581.aspx

SQL Server Disaster Recovery

There isn't much point taking SQL Server backups unless you know how to restore them. If you have anything more complicated than just a full database backup, you're going to need to know some RESTORE options to be able to successfully restore your database to the desired point in time.

This is even more the case if you have a complicated database layout or a complex backup strategy and you want to be able to restore, for example, a single file or filegroup, or take advantage of partial database availability.
As long as you have an effective backup strategy and your backups are valid, you should be able to recover from a disaster within your Recovery Time Objective (RTO) and to your Recovery Point Objective (RPO). In the first article in this three-part series, I discussed the various types of backups and how to formulate a backup strategy (see "Understanding SQL Server Backups" in the July 2009 issue).

In this article, I'll explain how restore works and how to perform some of the more common restore operations. It will be helpful if you've read the backup article, and the background material I mentioned in that article's introduction. I'm also going to explain a few more tricky operations, such as doing a point-in-time restore and an online piecemeal restore with partial database availability.

Just as in the previous article on BACKUP, I'm not going to explain how the RESTORE syntax works or go through the specific steps of all restore operations. SQL Server Books Online does an excellent job of that. See "RESTORE (Transact-SQL)" for more info, especially the examples spread throughout the topic. There are actually so many options to RESTORE that it's a whole other topic to explain them! "Backing Up and Restoring How-to Topics (SQL Server Management Studio)" explains how to use the tools to perform restores.

The Four Phases of Restore

Let's start with how restore actually works. A restore operation has up to four phases:

File creation and initialization
Data and/or transaction log copy
REDO phase of recovery
UNDO phase of recovery

One of the primary goals of disaster recovery is to bring the database online as quickly as possible. If your disaster-recovery plan involves restoring backups (instead of, say, failing over to a database mirror), you're going to want the restore process to be as fast as possible. With each of the four restore steps in mind, is there anything you can do to speed them up?

The first step can be essentially skipped if the data and log files already exist. This means that if you're going to overwrite an existing database, don't drop the database before doing the restore. Instead, use the WITH REPLACE option on the first restore operation to tell SQL Server to use the existing files. If the files don't exist, they will be created and then initialized. Creating the files is very fast, but the process of zero-initializing them can be very slow.

For security reasons, and by default, all database files are zero-initialized. You can enable instant file initialization for the SQL Server instance, which skips the zeroing process for data file create and grow operations, including those required during a restore -- possibly saving hours of downtime, even if the data files are only gigabytes in size. Transaction log files are always zero-initialized because of the circular nature of the transaction log itself.

You can read more about all of this, with references to Books Online, in my "Instant Initialization" blog post category.

You may be wondering about the second phase -- why does the item say "and/or transaction log"? If you read the previous article, you'll remember that all full and differential backups also include some transaction log records, to enable the database to be restored to a transactionally consistent point in time. Phase two is a pure copy operation -- no processing of the data is performed -- so the main way to speed this up is to have a better-performing I/O subsystem. This is one of the few times when it's acceptable to "throw hardware at the problem."

The other way to speed up the copy phase is to use some kind of backup compression technology, either native to SQL Server 2008 or through one of the various third-party solutions. The two parts of the copy phase are reading from the backup media and writing out to the data and/or log files. If you can do fewer reads (using compressed backup media), you can speed up the overall process, at the expense of a small amount of CPU resources.

Phases three and four are about running recovery on the transaction log to bring the database to a transactionally consistent point in time. I explained the details of recovery in the February 2009 article "Understanding Logging and Recovery in SQL Server". Note that phase four is optional, as I'll explain later.

Suffice it to say that the more transaction log that needs to be recovered during a restore, the longer the restore will take. This means that if, for instance, you have a full database backup from a week ago and hourly transaction log backups since then, the restore process will essentially replay all the transactions from the last week before completing. I discussed a solution for this in the previous article -- adding differential backups into a full-plus-log backup strategy.

A differential database backup contains all the datafile pages that have changed since the last full database backup, and can be used in a restore operation to avoid having to replay all the transactions that occurred in the period between the full database backup and the differential database backup. This can vastly reduce the time it takes to restore the database, but at the expense of a slightly more complicated backup strategy.

You can find more information in the Books Online topic "Optimizing Backup and Restore Performance in SQL Server".

What Do You Need to Restore?

When disaster strikes, the first thing you need to do is work out what has been damaged, as this is going to dictate the actions you must take to recover from the disaster. For storage media failure, the possibilities include:

Damage to the entire database (for instance, whatever was storing the database was destroyed, or the database was a single data file and it was damaged).
Damage to a single filegroup of a multi-filegroup database.
Damage to a single file of a multi-file filegroup.
Damage to a single page in the database.
Damage spread through the database.

You can ascertain the damage by looking through the SQL Server error log for notifications that file(s) are inaccessible, that page-read errors occurred (for instance, page checksum failures or a torn-page detection error), or that general corruption was encountered. If damage occurred, it is usual practice to run the DBCC CHECKDB consistency-checking operation to get an idea of how pervasive the damage is.

An explanation of consistency checking is beyond the scope of this article, but you can watch a video of a presentation I made at the Tech-Ed IT Forum in November 2008 titled "Corruption Survival Techniques", and listen to a TechNet Radio interview from earlier this year where I discuss database corruption (direct download links are here).

Disasters are not limited to I/O subsystem or server failures -- there's also human error to consider. Database tables (or data from them) are often accidentally deleted by poorly programmed applications or careless Transact-SQL statements (the "I didn't realize I was on the production server" scenario). In such cases, it can be very difficult to figure out what needs to be restored and from what point in time, especially if no one owns up to making the mistake. You might get lucky using standard reports from the default trace where the DDL operation is still available or the DELETE statement was caught by your own logging -- but often there's no record of who did what to the database. I'll discuss recovering from this situation in more detail later. Regardless of who performed the accidental data deletion or when it happened, the longer you wait to recover -- or the more time that passes before you are made aware of the problem -- the more complex it can be to recover.

So, as a first step if the database is running in the FULL recovery model and the transaction log is undamaged, perform a tail-of-the-log backup to ensure that all transactions up to the point of the disaster are backed up. This "final" transaction log backup will have everything up until the time of the disaster and can be used to bring the database being restored as far as possible, possibly up-to-the-minute.

In a nutshell, you need to work out what you have to restore. Then it becomes a question of what you are able to restore.

What Are You Able to Restore?

The aim of any restore operation is to restore the fewest possible backups, so the restore operation is as fast as possible and completes within your RTO, while also allowing you to meet your RPO.

The main question to ask here is "What backups do I have?" If the only backup you have is a full database backup from a week ago and the whole database has been lost, there's only one restore option -- to a point in time a week ago, losing all work since then. Simply put, your backup strategy should always ensure that you are able to restore what you need to in the event of a disaster, as I discussed in the previous article.

So how can you determine what backups you have available? First, you can query that various backup history tables in the msdb database. These tables contain a record of all backups that have been taken in the SQL Server instance since the last time the backup history tables were cleared out.

As far as the backups themselves are concerned, it is a best practice to name backup files to include the database, type of backup, date and time so that the backup can be identified at a glance. If you haven't done this, you can find out what a backup file contains using the RESTORE HEADERONLY command. This will display the contents of the backup file's header, essentially the metadata that describes the backup itself. You can read more in the Books Online topic "Viewing Information About Backups".

Using either method, you are trying to work out the restore sequence to use to restore the damaged or deleted data. A restore sequence is a set of backups that must be restored and the appropriate order in which to restore them. The restore sequence may be as simple as just one full backup (of a database, filegroup or file), or a complicated set of full, differential and transaction log backups.

For instance, imagine a scenario where the backup strategy involves full database, differential database and transaction log backups. If a system crash occurs and the data files are damaged, what is the restore sequence? Figure 1 illustrates this example.

In this case, the shortest and fastest restore sequence is the most recent full database backup (F), the most recent differential database backup (D2), and then all subsequent transaction log backups, up to and including the tail-of-the-log backup (L7 and L8).

One of the tricky problems when planning a restore sequence is finding the earliest required transaction log backup to restore (sometimes called finding the "minimum-LSN," or "minimum-Log Sequence Number"). In the example in Figure 1, only transaction log backups L7 and L8 are required, because the differential database backup D2 brings the database to a more recent point in time than all the previous transaction log backups.

Figure 1: Example Restore Sequence

SQL Server will allow previous, unneeded transaction log backups to be restored, but they will not be used and essentially just waste disaster-recovery time.Continuing my example, what would happen if the differential database backup D2 was damaged or missing? Figure 2 shows this case.

Figure 2: Restore Sequence with a Damage Differential Database BackUp

In this scenario, the shortest and fastest restore sequence is the most recent full database backup (F), the next most recent differential database backup (D1), and then all subsequent transaction log backups (L4, L5, L6, L7 and L8). This is possible only as long as backups D1, L4, L5 and L6 are still available. It is important that you do not delete backups too soon; otherwise you could run into problems during a disaster.

For instance, if the full database backup F is damaged, unless the previous full database backup is still available, the database will not be recoverable. If the differential database backup D1 is deleted as soon as D2 completes, then the scenario in Figure 2 will not be possible, and the restore sequence will involve all transaction log backups since the full database backup -- a potentially very long restore sequence.

This raises the question of "When should you delete your previous backups?" The answer is definitely "It depends!" If you don't have a legal obligation to keep your backups around for a certain length of time, then it's up to you, and depends on the backup strategy you have and how much disk space is required. Regardless, don't immediately delete previous backups as soon as a new one is taken; it's best to keep at least one or two complete cycles of backups before getting rid of older backups. Ideally, you should test your backups before removing older ones.

For transaction log backups, in general you must have all of them since the last full database backup was taken, as that is the final fall-back restore sequence. If a single transaction log backup from the transaction log backup "chain" is missing or damaged, the restore operation can't proceed past the gap. As I mentioned in the previous article, verifying the integrity of your backups is a key part of being able to restore successfully.

You can find more details on figuring out what you're able to restore in the comprehensive Books Online topic "Working with Restore Sequences for SQL Server Databases".

Example Restore Scenarios

The most common restore scenario involves a full database backup and then one or more transaction log backups to bring the database forward in time. You can do this through SQL Server Management Studio (SSMS) or through Transact-SQL, although there is something you need to be aware of if you're going to use RESTORE commands directly.

When a backup is restored, there are three options for how the restore operation completes and they all relate to the UNDO phase of recovery. As each successive backup in the restore sequence is restored, the REDO phase of recovery is always performed, but the UNDO phase cannot be performed until the very last backup in the transaction log backup chain has been restored. This is because as soon as recovery is completed, no further transaction log backups can be applied, so all restores in the restore sequence must specify not to run the UNDO phase of recovery.

The default, unfortunately, is to run the UNDO phase of recovery -- the equivalent of using the WITH RECOVERY option on the RESTORE statement. When restoring multiple backups, you must be careful that each one specifies WITH NORECOVERY. In fact, the safest way is to use the WITH NORECOVERY option on all restores in the restore sequence, and then manually complete recovery afterward. Here is some example Transact-SQL code to restore a full database backup and two transaction log backups, and then manually complete recovery to bring the database online:

RESTORE DATABASE DBMaint2008 FROM
DISK = 'C:\SQLskills\DBMaint2008_Full_051709_0000.bak'
WITH REPLACE, CHECKSUM, NORECOVERY;
GO

RESTORE LOG DBMaint2008 FROM
DISK = 'C:\SQLskills\DBMaint2008_Log_051709_0100.bak'
WITH NORECOVERY;
GO

RESTORE LOG DBMaint2008 FROM
DISK = 'C:\SQLskills\DBMaint2008_Log_051709_0200.bak'
WITH NORECOVERY;
GO

RESTORE DATABASE DBMaint2008 WITH RECOVERY;
GO

Notice that I also used the CHECKSUM option on the restore of the full database backup to ensure that any page checksums present in the database being restored are verified as they are restored.

If WITH NORECOVERY was not specified on the first RESTORE statement, the following error is returned:

Msg 3117, Level 16, State 1, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.

You must be very careful to use the right option, otherwise you risk having to start a long restore sequence again -- there's no way to undo recovery once it's completed.

There is, however, an interesting option which kind of does that -- the WITH STANDBY option. This is the last of three options I mentioned earlier. It works by running the UNDO phase of recovery, but it keeps a note of what it did (in an "undo" file whose name and path you specify) and then allows read-only access to the database. The database is transactionally consistent, but you have the ability to continue with the restore sequence. If you decide to continue, the UNDO is reversed (using the contents of the undo file) and then the next transaction log file is restored. This is useful in two scenarios: for allowing read-only access to a log-shipping secondary database and for looking at the contents of the database during the restore sequence.

If the disaster you're recovering from involves accidental deletion of a table, for instance, you may want to do a point-in-time restore. There are several ways to do this, but the most common is where you want to restore the database but ensure that recovery does not proceed past a certain time. In that case you can use the WITH STOPAT option to prevent transaction log restore from going past the time you know the table was deleted. For instance, using the Transact-SQL example above, if I wanted to prevent the database from being restored past 1:45 a.m., I could use the following syntax on the second RESTORE LOG statement:

RESTORE LOG DBMaint2008 FROM
DISK = 'C:\SQLskills\DBMaint2008_Log_051709_0200.bak'
WITH NORECOVERY, STOPAT = '2009-05-17 01:45:00.000';
GO

I could even combine STOPAT and STANDBY to see whether that was the correct point in time and then, if not, restore the same transaction log backup with a time a few seconds later and so on. This kind of operation becomes very tedious, but it may be the only solution if you don't know what time an operation took place.

A comprehensive discussion of these and other options for the RESTORE statement can be found in the Books Online topic "RESTORE Arguments (Transact-SQL)".

One of the coolest new features introduced in SQL Server 2005 Enterprise Edition was partial database availability. This feature allows a multi-filegroup database to be online and available as long as at least the primary filegroup is online. Obviously, data in any offline filegroups can't be accessed, but this feature allows a very large database to be split into separate filegroups for easier and faster recoverability. Another Enterprise-only feature that was added is the ability to perform piecemeal restores (for instance, a single filegroup from a multi-filegroup database) online, while the rest of the database is being used for processing.

These two features combined enable some quite sophisticated and efficient restore scenarios, as long as the database has been architected that way and the correct backups exist.

You'll find an excellent, in-depth SQL Server Technical Article titled "Microsoft SQL Server 2005 Partial Database Availability" with some extensive examples available at tinyurl.com/mbpa65. There's also a 75-minute recording of Kimberly L. Tripp delivering a Tech-Ed EMEA session titled "SQL Server 2005 VLDB Availability and Recovery Strategies" that is well worth watching.

Considerations When Restoring to a Different Location

The simplest restore scenario is when the database is being restored on the same SQL Server instance to which it is usually attached, and with the same name. As you move further away from that scenario, the aftermath of the restore operation becomes more complicated.

If the database is being restored on the same instance, but with a different name, you may need to make changes to elements like DTS/SSIS packages, database maintenance plans, application strings and anything that relies on a database name.

If the database is being restored on a different instance on the same server, things get a lot more complicated:

The SQL Server logins will be different or may not exist.
SQL Agent jobs and DTS/SSIS packages will be different or may not exist.
The master database is different, so any user-defined stored procedures may be missing.
The SQL Server instance name will be different, so there may be client connectivity issues.
If the database is being restored on an instance on a different server, everything listed applies, but there may be added security issues as Windows accounts may be different, and they may be in a different Windows domain.
One other consideration is the edition of SQL Server the database is being restored on. There are some features that, if used in the database, make the database "Enterprise-only" -- it cannot be restored on a Standard Edition (or lower) SQL Server instance.
In SQL Server 2000 and earlier, this is not an issue. In SQL Server 2005, if table or index partitioning is used, the database is "Enterprise-only." In SQL Server 2008, the feature list is:
Change data capture
Transparent data encryption
Data compression
Partitioning

All of these require sysadmin privileges to enable except data compression, which can be enabled by a table owner, thus potentially breaking a disaster-recovery plan involving restoring to a Standard Edition instance. You can tell whether any of these features are being used in the database using the DMV sys.dm_db_persisted_sku_features and adjust your disaster-recovery plan accordingly.

Dig Deeper

Just as with the first article in the series on backups, there are lots of facets of restore operations that I didn't have space to cover. Now that you know the basics, however, you can dive into some of the Books Online and blog links for deeper information. The best place to start in Books Online is the topic "Restore and Recovery Overview (SQL Server)". You can also find a lot of information on my blog, starting with the Backup/Restore category.

The main takeaway I'd like you to gain from this article is that to successfully recover a database using backups, you need to practice to make sure you know what to do. You don't want to be learning the syntax for the RESTORE command during a high-pressure disaster-recovery situation. You may also find that your backup strategy does not allow you to recover within your business requirements. Maybe the backups take too long to restore, maybe your log backups are accidentally overwriting each other, or maybe you forgot to back up the server certificate used to enable transparent database encryption in SQL Server 2008.

By far the best way to prepare for disaster is to have a restore plan that lists the steps to go through, and to have a set of scripts that will help identify what backups exist and the order in which to restore them. I always like to say that this should be written by the most senior DBA on the team and tested by the most junior DBA -- to ensure that everyone can follow the steps safely. However, if you're an involuntary DBA, you're going to need to put a plan together yourself and make sure you can follow it.

Poster de Características y Componentes de Windows 2008 y Windows 2008 R2

2009-12-11T01:50:00.000-08:00

Brief Description
Windows Server 2008 y Windows Server 2008 R2 Component Posters, originally printed in the July 2007 issue of TechNet Magazine.

Overview
These two posters, originally published in the July 2007 issue of TechNet Magazine, provide a strong visual tool to aide in the understanding of various features and components of Windows Server 2008. One poster focuses exclusively on powerful new Active Directory technologies, while the other provides a technical look at a variety of new features available in Windows Server 2008 (such as Server Core, Network Access Protection, and more).

http://www.microsoft.com/downloads/details.aspx?FamilyID=C2B9E44E-0BBD-47CB-BC09-B3D48BE7F867&displayLang=en

http://www.microsoft.com/downloads/details.aspx?FamilyID=64a5cc28-f8a1-4b30-a4a2-455c65bda8d7&displaylang=en

Boletines de seguridad de Diciembre 2009

2009-12-10T05:46:00.000-08:00

Este pasado martes Microsoft ha publicado seis boletines de seguridad (del MS09-069 y MS09-074) correspondientes a su ciclo habitual de actualizaciones, que corrigen un total de doce vulnerabilidades. Según la propia clasificación de Microsoft tres de los boletines presentan un nivel de gravedad "crítico", mientras que los tres restantes son "importantes".

Los boletines "críticos" son:

* MS09-071: Actualización destinada a corregir dos vulnerabilidades en el Servicio de autenticación de Internet al tratar los intentos de autenticación PEAP. Sólo están afectados los servidores con el Servicio de Autenticación de Internet cuando usan PEAP con la autenticación MS-CHAP v2. Estos problemas que afectan a Windows 2000, XP, Vista, Server 2003 y Server 2008, podrían permitir la ejecución remota de código.

* MS09-072: Actualización acumulativa para Microsoft Internet Explorer que además soluciona cinco nuevas vulnerabilidades que podrían permitir la ejecución remota de código arbitrario. Afecta a Internet Explorer 5.01, 6, 7 y 8.

* MS09-074: Actualización de seguridad para evitar una vulnerabilidad Microsoft Office Project, que podría permitir la ejecución remota de código si un usuario abre un archivo de Project especialmente creado. Afecta a Project 2000, 2002 y Office Project 2003.

Los boletines clasificados como "importantes" son:

* MS09-069: Actualización destinada a corregir una vulnerabilidad de denegación de servicio, si en un sistema afectado un usuario remoto autenticado envía mediante protocolo IPSEC un mensaje ISAKMP especialmente diseñado al Servicio LSASS (Subsistema de Autenticación de la Autoridad de Seguridad Local).

* MS09-070: Actualización que soluciona dos vulnerabilidades en Servicios de federación de Active Directory (ADFS, Active Directory Federation Services). Un usuario remoto autenticado podría lograr la ejecución remota de código si envía una petición http especialmente diseñada a un servidor web habilitado para ADFS.

* MS09-073: Actualización que soluciona una vulnerabilidad en Microsoft WordPad y Office Word, que podría permitir la ejecución remota de código si un usuario abre un archivo Word 97 específicamente manipulado.

Las actualizaciones publicadas pueden descargarse a través de Windows Update o consultando los boletines de Microsoft donde se incluyen las direcciones de descarga directa de cada parche. Dada la gravedad de las vulnerabilidades se recomienda la actualización de los sistemas con la mayor brevedad posible

Más Información:

Boletín de seguridad de Microsoft MS09-071 - Crítico
Vulnerabilidades en el Servicio de autenticación de Internet podría permitir la ejecución remota de código (974318)
http://www.microsoft.com/spain/technet/security/Bulletin/ms09-071.mspx

Boletín de seguridad de Microsoft MS09-072 - Crítico
Actualización de seguridad acumulativa para Internet Explorer (976325)
http://www.microsoft.com/spain/technet/security/Bulletin/ms09-072.mspx

Boletín de seguridad de Microsoft MS09-074 - Crítico
Una vulnerabilidad en Microsoft Office Project podría permitir la ejecución remota de código (967183)
http://www.microsoft.com/spain/technet/security/Bulletin/ms09-074.mspx

Boletín de seguridad de Microsoft MS09-069 - Importante
Una vulnerabilidad en el servicio del subsistema de autoridad de seguridad local podría permitir la denegación de servicio (974392)
http://www.microsoft.com/spain/technet/security/Bulletin/ms09-069.mspx

Boletín de seguridad de Microsoft MS09-070 - Importante
Vulnerabilidades en Servicios de federación de Active Directory podrían permitir la ejecución remota de código (971726)
http://www.microsoft.com/spain/technet/security/Bulletin/ms09-070.mspx

Boletín de seguridad de Microsoft MS09-073 - Importante
Una vulnerabilidad en los convertidores de texto de WordPad y Office podría permitir la ejecución remota de código (975539)
http://www.microsoft.com/spain/technet/security/Bulletin/ms09-073.mspx

December 2009 Security Release ISO Image

2009-12-09T07:53:00.000-08:00

Esta ISO contiene los security updates de Windows que publicados en Windows Update el 8 de Diciembre de 2009. Este DVD está orientado a administradores que necesitan descargar diferentes lenguajes de las actualizaciones para diferentes versiones de Sistema Operativo y no usan soluciones tipo WSUS, SMS o System Center Configuration manager.

Importante:
Asegurate de chequear cadea uno de los updates desde http://www.microsoft.com/technet/security antes de implementarlos.

http://www.microsoft.com/downloads/details.aspx?FamilyID=015876AE-2335-48E3-8B60-0E7D7D7EAAB2&displaylang=en

Overview
This DVD5 ISO image file contains the security updates for Windows released on Windows Update on December 8th, 2009. The image does not contain security updates for other Microsoft products. This DVD5 ISO image is intended for administrators that need to download multiple individual language versions of each security update and that do not use an automated solution such as Windows Server Update Services (WSUS). You can use this ISO image to download multiple updates in all languages at the same time.

Important: Be sure to check the individual security bulletins at http://www.microsoft.com/technet/security prior to deployment of these updates to ensure that the files have not been updated at a later date.

http://www.microsoft.com/downloads/details.aspx?FamilyID=015876AE-2335-48E3-8B60-0E7D7D7EAAB2&displaylang=en

This DVD5 image contains the following updates:
KB951748 / (MS08-037)
Windows 2000 - 24 languages
KB972187 / (MS08-076)
Windows XP - 24 languages
KB974392 / (MS09-069)
Windows 2000 - 24 languages
Windows Server 2003 - 18 languages
Windows Server 2003 x64 Edition - 11 languages
Windows Server 2003 for Itanium-based Systems - 4 languages
Windows XP - 24 languages
Windows XP x64 Edition - 2 languages
KB971726 / (MS09-070)
Windows Server 2003 - 18 languages
Windows Server 2003 x64 Edition - 11 languages
Windows Server 2008 - 19 languages
Windows Server 2008 x64 Edition - 19 languages
KB974318 / (MS09-071)
Windows 2000 - 24 languages
Windows Server 2003 - 18 languages
Windows Server 2003 x64 Edition - 11 languages
Windows Server 2003 for Itanium-based Systems - 4 languages
Windows XP - 24 languages
Windows XP x64 Edition - 2 languages
Windows Vista - 36 languages
Windows Vista for x64-based Systems - 36 languages
Windows Server 2008 - 19 languages
Windows Server 2008 x64 Edition - 19 languages
Windows Server 2008 for Itanium-based Systems - 4 languages
KB976325 / (MS09-072)
Windows 2000 - 24 languages
Windows Server 2003 - 18 languages
Windows Server 2003 x64 Edition - 11 languages
Windows Server 2003 for Itanium-based Systems - 4 languages
Windows XP - 24 languages
Windows XP x64 Edition - 2 languages
Windows Vista - 36 languages
Windows Vista for x64-based Systems - 36 languages
Windows Server 2008 - 19 languages
Windows Server 2008 x64 Edition - 19 languages
Windows Server 2008 for Itanium-based Systems - 4 languages
Windows 7 - 36 languages
Windows 7 for x64-based Systems - 36 languages
Windows Server 2008 R2 x64 Edition - 19 languages
Windows Server 2008 R2 for Itanium-based Systems - 4 languages
KB973904 / (MS09-073)
Windows 2000 - 24 languages
Windows Server 2003 - 18 languages
Windows Server 2003 x64 Edition - 11 languages
Windows Server 2003 for Itanium-based Systems - 4 languages
Windows XP - 24 languages
Windows XP x64 Edition - 2 languages

Fin de Soporte para SQL Server 2005 Service Pack 2 y SQL Server 2008 RTM

2009-12-09T01:53:00.000-08:00

Recordaros a todos que el soporte para SQL Server 2005 Service Pack 2 (SP2) termina el 12 de Enero de 2010 y el soporte para SQL Server 2008 RTM terminará el 13 de Abril de 2010. Microsoft termina el soporte para estos productos como parte de su política de soporte para Service packs que podeis consultar en el siguiente enlace:

http://support.microsoft.com/lifecycle.

Ambos productos no recibirán asistencia ni actualizaciones por parte de Microsoft en las fechas de fin de soporte.
La auto ayuda online seguirá estando disponible un mínimo de 12 meses después de la finalización del ciclo de vida. Las opciones de autoayuda incluyen:

- Public knowledge base articles
- FAQs
- Troubleshooting tools disponibles desde http://support.microsoft.com y Microsoft Download Center.

Más información desde el enlace:

http://blogs.msdn.com/sqlreleaseservices/archive/2009/10/08/end-of-service-pack-support-for-sql-server-2005-sp2-and-sql-server-2008-rtm.aspx

Windows Catalog

2009-12-03T08:10:00.000-08:00

En este artículo se describe cómo descargar actualizaciones desde el Catálogo de Windows Update.

http://catalog.update.microsoft.com

El Catálogo de Windows Update ofrece actualizaciones para todos los sistemas operativos que se admiten actualmente. Entre estas actualizaciones se incluyen las siguientes:

- Controladores de dispositivo
- Revisiones
- Archivos de sistema actualizados
- Service Pack
- Nuevas características de Windows
Le guiaremos por los diferentes pasos para buscar el Catálogo de Windows Update y encontrar las actualizaciones que desea. Después, puede descargar las actualizaciones para instalarlas en su red doméstica o corporativa de los equipos basados en Microsoft Windows.

También trataremos cómo los profesionales de TI pueden utilizar Software Update Services, como Windows Update y Actualizaciones automáticas.

Importante: este contenido está pensado para usuarios avanzados de equipos informáticos. Se recomienda que sólo los usuarios avanzados y los administradores descarguen actualizaciones del Catálogo de Windows Update. Si no es un usuario avanzado ni un administrador, visite el siguiente sitio web de Microsoft para descargar directamente las actualizaciones:

http://windowsupdate.microsoft.com

Para descargar actualizaciones desde el Catálogo de Windows Update, siga estos pasos:

Paso 1: obtener acceso al Catálogo de Windows Update
Para obtener acceso al Catálogo de Windows Update, visite el siguiente sitio web de Microsoft:
http://catalog.update.microsoft.com/v7/site/Home.aspx (http://go.microsoft.com/fwlink/?LinkId=8973)
Para ver una lista de las preguntas más frecuentes sobre el Catálogo de Windows Update, visite el siguiente sitio web de Microsoft:
http://catalog.update.microsoft.com/v7/site/Faq.aspx (http://catalog.update.microsoft.com/v7/site/Faq.aspx)

Paso 2: buscar actualizaciones en el Catálogo de Windows Update

Para buscar actualizaciones en el Catálogo de Windows Update, siga estos pasos:
En el cuadro de texto Buscar, escriba los términos de búsqueda. Por ejemplo, podría escribir Seguridad de Windows Vista.
Haga clic en Buscar o presione ENTRAR.
Explore la lista que se muestra para seleccionar las actualizaciones que desea descargar.
Haga clic en Agregar en cada selección para agregarla a la cesta de descarga.
Para buscar actualizaciones adicionales para descargarlas, repita los pasos de 2a
a 2d.

Paso 3: descargar actualizaciones

Para descargar actualizaciones en el Catálogo de Windows Update, siga estos pasos:
Haga clic en Ver cesta en el cuadro Buscar para ver la cesta de descarga.
Compruebe la lista de actualizaciones y, a continuación, haga clic en Descargar.

Nota: si se le pide, haga clic en Aceptar para aceptar el contrato de licencia.
Seleccione la ubicación donde desea guardar las actualizaciones. Puede escribir la ruta completa de la carpeta o bien hacer clic en Examinar para buscarla.
Haga clic en Continuar para iniciar la descarga.
Una vez finalizada la descarga, haga clic en Cerrar para cerrar la ventana de descarga.
Cierre la ventana del Catálogo de Windows Update.
Encuentre la ubicación especificada en el paso 3c.
Nota: si ha descargado controladores de dispositivos para su instalación, vaya a "Instalar controladores".
Haga doble clic en cada actualización y, a continuación, siga las instrucciones para instalar la actualización. Si las actualizaciones están destinadas a otro equipo, copie las actualizaciones en dicho equipo y, a continuación, haga doble clic en las actualizaciones para instalarlas.
Si todos los elementos que ha agregado a la cesta de descarga están instalados correctamente, ya ha terminado.

Si desea obtener información sobre servicios de actualizaciones adicionales, consulte la sección "Software Update Services para profesionales de TI".
Instalar controladores
Abra un símbolo del sistema desde el menú Inicio.
Para extraer los archivos del controlador, escriba el comando siguiente en el símbolo del sistema y presione ENTRAR:

expand -F:*

Para preparar el controlador para una instalación plug and play o para el Asistente para agregar impresoras, utilice PnPutil tal como se describe en el siguiente artículo de Microsoft Knowledge Base:

937793 (http://support.microsoft.com/kb/937793/ ) Preparación e instalación de paquetes de controlador con la utilidad PnP (pnputil.exe) en Windows Vista

Nota: para instalar un controlador de impresora para múltiples arquitecturas, debe haber instalado el controlador de arquitectura local, y todavía necesitará la copia para múltiples arquitecturas de Ntprint.inf de otro sistema. Para obtener más información, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base:

952065 (http://support.microsoft.com/kb/952065/ ) No puede instalar controladores de impresora de terceros para múltiples arquitecturas en Windows Vista o Windows Server 2008

How To: Export local Group Policy settings made in gpedit.msc

2009-11-17T23:50:00.000-08:00

This is a good solution on how you can “export” the Group Policy and Security settings you made in on a machine with the Local Group Policy Editor (gpedit.msc) to other machines pretty easy:

Normal settings can be copied like this:

1.) Open %systemroot%\system32\grouppolicy\

Within this folder, there are two folders - “machine” and “user”. Copy these to folders to the “%systemroot%\system32\grouppolicy - folder on the target machine. All it needs now is a reboot or a “gpupdate /force”.

Note: If you cannot see the “grouppolicy” folder on either the source or the target machine, be sure to have your explorer folder options set to “Show hidden files and folders”…

For security settings:

1.) Open MMC and add the Snapin “Security Templates”.

2.) Create your own customized template and save it as an “*inf” file.

3.) Copy the file to the target machine and import it via command line tool “secedit”:

secedit /configure /db %temp%\temp.sdb /cfg yourcreated.inf

Further information on secedit can be found here: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/secedit_cmds.mspx?mfr=true

If you’re building custom installations, you can pretty easy script the “overwriting” of the “machine”/”user”-folders or the import via secedit by copying these file to a share and copy and execute them with a script.

Presentaciones de Windows 2008 R2 y Windows 7

2009-11-13T06:37:00.000-08:00

Estimados todos,
a continuación os dejo diferentes presentaciones sobre Windows 2008 R2 y Windows 7 que espero que sean de vuestro agrado.

Licensing Your Windows Server 2008 and Windows Vista Deployments - TechEd 2009 Presentation

http://download.microsoft.com/download/8/C/2/8C21BAFE-3432-48D1-962A-F7A9DD54A2AC/Licensing%20Your%20Windows%20Server%202008%20and%20Windows%20Vista%20Deployments.pptx

Windows 7 and Windows Server 2008 R2 Kernel Changes - TechEd 2009 Presentation

http://download.microsoft.com/download/8/C/2/8C21BAFE-3432-48D1-962A-F7A9DD54A2AC/Windows%207%20and%20Windows%20Server%202008%20R2%20Kernel%20Changes.pptx

Windows Server 2008 R2 - A Technical Overview - TechEd 2009 Presentation

http://download.microsoft.com/download/8/C/2/8C21BAFE-3432-48D1-962A-F7A9DD54A2AC/Windows%20Server%202008%20R2%20-%20A%20Technical%20Overview.pptx

Microsoft Exchange Server 2007 Service Pack 2 Help

2009-11-13T06:34:00.000-08:00

Brief Description
This download contains a standalone version of Microsoft Exchange Server 2007 SP2 Help.

Overview
The Exchange Server 2007 SP2 Help can help you in the day-to-day administration of Exchange. Use this information to guide you through Exchange Server 2007 SP2 features, tasks, and administration procedures.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=85c5ef71-6a1f-4eb0-9ff3-3feee6057e96

Microsoft Baseline Security Analyzer 2.1.1 (for IT Professionals)

2009-11-13T06:31:00.000-08:00

Brief Description
The Microsoft Baseline Security Analyzer provides a streamlined method to identify missing security updates and common security misconfigurations. MBSA 2.1.1 is a minor upgrade to add support for Windows 7 and Windows Server 2008 R2.

Overview
To easily assess the security state of Windows machines, Microsoft offers the free Microsoft Baseline Security Analyzer (MBSA) scan tool. MBSA includes a graphical and command line interface that can perform local or remote scans of Microsoft Windows systems.

MBSA 2.1.1 builds on previous versions by adding support for Windows 7 and Windows Server 2008 R2. As with the previous MBSA 2.1 release, MBSA includes 64-bit installation, security update and vulnerability assessment (VA) checks, improved SQL Server 2005 checks, and support for the latest Windows Update Agent (WUA) and Microsoft Update technologies. More information on the capabilities of MBSA 2.1 and 2.1.1 is available on the MBSA Web site.

MBSA 2.1.1 runs on Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP and Windows 2000 systems and will scan for missing security updates, rollups and service packs using Microsoft Update technologies. MBSA will also scan for common security misconfigurations (also called Vulnerability Assessment checks) using a known list of less secure settings and configurations for all versions of Windows, Internet Information Server (IIS) 5.0, 6.0 and 6.1, SQL Server 2000 and 2005, Internet Explorer (IE) 5.01 and later, and Office 2000, 2002 and 2003 only.

To assess missing security updates, MBSA will only scan for missing security updates, update rollups and service packs available from Microsoft Update. MBSA will not scan or report missing non-security updates, tools or drivers.
Choose the appropriate download below for English (EN), German (DE), French (FR) and Japanese (JA) for x86 (32-bit) or x64 (64-bit) platforms.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b1e76bbe-71df-41e8-8b52-c871d012ba78

Consideración importante para clusteres de Windows Server 2008

2009-11-13T06:12:00.000-08:00

Extraído integramente del Blog de David Cervigón os pongo el enlace y resumo este grave problema que ha descubierto Microsoft en Clusteres de Windows 2008.

http://blogs.technet.com/davidcervigon/archive/2009/11/12/consideraci-n-importante-para-clusteres-de-windows-server-2008.aspx

--------------------------------------------------------------------------

Se están dando algunos casos de clústeres de Windows Server 2008 en los que los procesos RSH (Resource Monitor Host) se caen o entran en estados de “deadlock”, lo que en los casos más graves puede acabar produciendo fallos en los recursos existentes en cada uno de los grupos. En otras circunstancias los procesos se reinician y el problema puede llegar a pasar desapercibido.

En el par de casos que me ha tocado vivir, los afectados principales han sido los recursos de disco y el propio nombre del cluster. Esto produce la caída de cualquier cosa que dependa de esos discos, con el agravante de que al no estar disponible el network name el uso de la consola de gestión se hace complicada, sobre todo en remoto. Y a mayor número de nodos, mayor probabilidad de encontrarnos el problema, y mayor complicación a la hora de resolverlo.

Una vez experimentados estos síntomas, cuando nos ponemos a rascar, nos encontramos este tipo de información en el visor de sucesos y en el log del cluster:

•Event ID: 1146 - The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource vendor
•Cluster.log: Múltiples ocurrencias de ERROR_RESOURCE_CALL_TIMED_OUT(5910)
En los casos en los que el sistema es capaz de recuperarse solo, hay otra manera de detectar el problema, también bastante sutil. Cuando falla el monitor de un recurso, el sistema lo marca para que se ejecute en un proceso diferente, lo que dispara el numero de procesos RSH.exe que podemos ver en el task manager. Si ejecutamos este comando, podemos ver en que recursos tenemos esa casilla marcada (SeparateMonitor = 0x1), y si no lo hemos hecho a propósito puede que haya estada afectada por el problema:

•cluster res /prop |findstr SeparateMonitor

La solución

Paradójicamente, la solución al problema está oculta detrás de un paquete de recomendaciones que se viene aplicando a problemas de lentitud de red en Windows Vista y en Windows Server 2008, curiosamente debido a las optimizaciones de red incluidas en estos sistemas operativos (TCP Offload, Receive-side scaling (RSS), TCP Window Scaling Auto Tunning, etc.).

Así es que para prevenir/resolver este problema hay que seguir estos pasos en todos los nodos del cluster

•Aplicar el fix mencionado en http://support.microsoft.com/default.aspx?scid=kb;EN-US;967224, para asegurarnos de que los cambios que hagamos en el paso siguiente tengan el resultado esperado.
•Ejecutar:
◦Netsh int tcp set global RSS=Disabled
◦Netsh int tcp set global chimney=Disabled
◦Netsh int tcp set global autotuninglevel=Disabled
◦Netsh int tcp set global congestionprovider=None
◦Netsh int tcp set global ecncapability=Disabled
◦Netsh int ip set global taskoffload=disabled
◦Netsh int tcp set global timestamps=Disabled
•Adicionalmente, y dado que no vamos a usar esas opciones a nivel de sistema operativo, pueden deshabilitarse también a nivel de opciones avanzadas del driver de la tarjeta de red:

Una vez aplicados los cambios en todos los nodos, los reiniciamos ordenadamente para que estos apliquen, y comprobamos que todos los servicios que corran encima lo estén haciendo correctamente. Es posible que queramos volver a poner los valores “SeparateMonitor” a cero, como era el defecto. Lo podemos hacer con el comando cluster.exe, o bien por la interfaz gráfica (última casilla de la imagen , marcada es 1 y desmarcada es 0):

Espero que esto os pueda ahorrar algún disgusto, acompañado de unas cuantas horas de agobio en clústeres que estén corriendo algún tipo de servicio crítico en vuestra organización.

Group Policy Settings References for Windows and Windows Server

2009-09-15T16:14:00.000-07:00

Estimados todos,
aquí os dejo un enlace donde podréis descargar todos los settings de políticas de grupo para Windows y Windows Server.

Group Policy Settings References for Windows and Windows Server
Brief Description
These spreadsheets list the policy settings for computer and user configurations included in the Administrative template files delivered with the Windows operating systems specified. You can configure these policy settings when you edit Group Policy objects (GPOs).

Overview
Using column filters, you can filter the information in these spreadsheets by operating system, component, or computer or user configuration. You can also search for information by using text or keywords.
These spreadsheets include the following categories of security policy settings: Account Policies (Password Policy, Account Lockout Policy, and Kerberos Policy), Local Policies (Audit Policy, User Rights Assignment, and Security Options), Event Log, Restricted Groups, System Services, Registry, and File System policy settings. These spreadsheets do not include security settings that exist outside of the Security Settings extension (scecli.dll), such as Wireless Network extension, Public Key Policies, or Software Restriction Policies.

Group Policy Settings Reference for Windows Server 2008 R2 and Windows 7: This spreadsheet lists the policy settings for computer and user configurations included in the Administrative template files (.admx/.adml) delivered with Windows Server 2008 R2 and Windows 7. The policy settings included in this spreadsheet cover Windows 7, Windows Server 2008 R2, Windows Server 2008, Windows Vista with SP1, Windows Server 2003 with SP2 and earlier service packs, Windows XP Professional with SP2 and earlier service packs, and Windows 2000 with SP4 and earlier service packs.
Group Policy Settings Reference for Windows Server 2008 and Windows Vista Service Pack 1: This spreadsheet lists the policy settings for computer and user configurations included in the Administrative template files (.admx/.adml) delivered with Windows Server 2008 and Windows Vista with Service Pack 1 (SP1). The policy settings included in this spreadsheet cover Windows Server 2008, Windows Vista with SP1, Windows Server 2003, Windows XP Professional with SP2 or earlier service packs, and Windows 2000 with SP4 or earlier service packs.
Group Policy Settings Reference for Windows Vista: This spreadsheet lists the policy settings for computer and user configurations included in the Administrative template files (.admx/.adml) delivered with Windows Vista with no service packs installed. The policy settings included in this spreadsheet cover Windows Vista, Microsoft Windows Server 2003, Windows XP Professional with SP2 or earlier service packs, and Windows 2000 with SP4 or earlier service packs.
Group Policy Settings Reference for Windows Server 2003 Service Pack 2: This spreadsheet lists the policy settings for computer and user configurations included in the Administrative template (.adm) files and Security Settings that shipped with Windows Server 2003 with SP2. The policy settings included in this spreadsheet cover Microsoft Windows Server 2003 with SP2 or earlier service packs, Windows XP Professional with SP3 or earlier service packs, and Microsoft Windows 2000 with SP4 or earlier service packs.
This spreadsheet includes separate worksheets for each of the .adm files and the security policy settings that shipped in Windows XP SP3, a consolidated worksheet for easy searching, and an Update History worksheet that lists policy settings that have been added since the Windows Server 2003 operating systems were released.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=18c90c80-8b0a-4906-a4f5-ff24cc2030fb

Windows 7 y Windows 2008 R2 Upgrade Paths

2009-09-15T16:07:00.000-07:00

Hola a todos,
os dejo dos documentos que explican los posibles pasos de actualización desde diferentes sistemas operativos a Windows 7 y Windows 2008 R2.

Windows 7 Upgrade Paths
Brief Description
Outlines supported and unsupported upgrade paths for Windows 7 SKUs.

Overview
This document outlines supported and unsupported upgrade paths for Windows® 7 SKUs.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=e170eba1-5bab-401f-bbf5-00f0ee7fe0fb

Windows Server 2008 R2 Upgrade Paths
Brief Description
Outlines supported and unsupported upgrade paths for Windows Server 2008 R2 SKUs.

Overview
This document outlines supported and unsupported upgrade paths for Windows Server® 2008 R2 SKUs.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=f2d08680-0875-44d3-bb5f-c5b05ac7201b

Downloadable Technical Library in Compiled Help format

2009-09-04T06:25:00.000-07:00

Estimados todos,
hoy os dejo unos enlaces que seguro os van a ser de utilidad. Cuantas veces necesitais consultar el TechNet Online de algún producto y pensais que os gustaría descargarlo completamente a vuestro PC para futuras consultas. Hoy os traigo los enlaces para bajar en formato CHM algunas guías. Según sigan saliendo las iremos incorporando.

Microsoft Search Server 2008 Technical Library in Compiled Help format

Brief Description

Downloadable CHM version of Search Server 2008 content on TechNet.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6cf0f7b6-c0a7-48f8-977e-9bc76b97ff98

Office SharePoint Server 2007 Technical Library in Compiled Help format

Brief Description

Downloadable CHM version of SharePoint Server content on TechNet.
On This Page

http://www.microsoft.com/downloads/details.aspx?familyid=ba006584-711d-4ce7-9e1f-181aedf6434a&displaylang=en

Windows SharePoint Services 3.0 Technical Library in Compiled Help format

Brief Description

Downloadable CHM version of Windows SharePoint Services 3.0 content on TechNet.

http://www.microsoft.com/downloads/details.aspx?FamilyID=c9d6c8c5-8a62-4961-8c1b-df08b667b1c4&displaylang=en

Microsoft SQL Server 2008 Technical Library in Compiled Help format (July 2009)

Brief Description

Download the documentation and tutorials for Microsoft SQL Server 2008.

http://www.microsoft.com/downloads/details.aspx?familyid=765433F7-0983-4D7A-B628-0A98145BCB97&displaylang=en

Office Project Server 2007 Technical Library in Compiled Help format

Brief Description

Downloadable CHM version of Project Server content on TechNet.

http://www.microsoft.com/downloads/details.aspx?familyid=7D243A2C-90B7-425D-B586-C48A0C3BEBBB&displaylang=en

SQL Server 2008 Migration White Papers

2009-08-31T07:46:00.000-07:00

Hola a todos,
aquí os dejo un enlace a varios White Papers de Microsoft que ofrecen ayuda y recursos para migrar desde diferentes gestores de Bases de Datos de terceros a Microsoft SQL Server 2008. Algunos de estois gestores son:

- MySQL
- Oracle
- Informix
- Sybase ASA
- Sybase ASE

Espero os sea de utilidad.

SQL Server 2008 Migration White Papers
Brief Description
Read white papers for guidance on how to migrate to Microsoft SQL Server 2008 from other database products.

Overview
SQL Server 2008 delivers exceptional value in database management and business intelligence causing many customers to choose SQL Server over other database solutions. The white papers available here will help you find the resources needed to migrate your data to SQL Server 2008.
Guide to Migrating from MySQL to SQL Server 2008
In this migration guide you will learn the differences between the MySQL and SQL Server 2008 database platforms, and the steps necessary to convert a MySQL database to SQL Server.
Guide to Migrating from Oracle to SQL Server 2008
This white paper explores challenges that arise when you migrate from an Oracle 7.3 database or later to SQL Server 2008. It describes the implementation differences of database objects, SQL dialects, and procedural code between the two platforms. The entire migration process using SQL Server Migration Assistant (SSMA) 2008 for Oracle is explained in depth, with a special focus on converting database objects and PL/SQL code.
Guide to Migrating from Informix to SQL Server 2008
This white paper explores challenges that arise when you migrate from an Informix 11 database to SQL Server 2008. It describes the implementation differences of database objects and procedural code between the two platforms. Emulation of system functions is also discussed.
Guide to Migrating from Sybase ASA to SQL Server 2008
This white paper explores challenges that arise when you migrate from a Sybase Adaptive Server Anywhere (ASA) database of version 9 or later to SQL Server 2008. It describes the implementation differences of database objects, SQL dialects, and procedural code between the two platforms.
Guide to Migrating from Sybase ASE to SQL Server 2008
This white paper covers known issues for migrating Sybase Adaptive Server Enterprise database to SQL Server 2008. Instructions for handling the differences between the two platforms are included. The paper describes how SQL Server Migration Assistant, the best tool for this type of migration, can help resolve various migration issues.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c7933d3e-b7b9-43a6-ade3-f8e37c8cb046

Windows 2008: Read Only Domain Controllers (RODCs)

2009-08-24T07:51:00.000-07:00

Aquí os dejo unos breves apuntes sobre Read-Only Domain Controllers en Windows 2008, un video de como instalarlo y enlaces oficiales de Microsoft, que incluyen:

- Whitepaper: Planning and Deploying Read-Only Domain Controllers
- TechNet: Deploying RODCs in the Perimeter Network
- TechNet: Administering RODCs in Branch Offices

Using Read-Only Domain Controllers
----------------------------------------------------
The RODC is designed to address the branch office scenario.
An RODC is a DC that maintains a copy of all objects in the domain and all Attributes except confidential attributes (secrets) such as password-related properties. When a user in the branch office logs on, the RODC receives the
request and forwards it to a DC in the hub site for authentication.

You are able to configure a password replication policy (PRP) for the RODC that specifies user accounts the RODC is allowed to cache. If the user logging on is included in the PRP,the RODC caches that user’s credentials so that the next time the user requests authentication, the RODC can perform the task locally. As users who are included in the PRP log on, the RODC builds its cache of credentials so that it can perform authentication locally for those users.

Deploying an RODC
----------------------------------
The high-level steps to install an RODC are as follows:

1. Ensure that the forest functional level is Windows Server 2003 or higher.
2. If the forest has any domain controllers running Microsoft Windows Server 2003, run
adprep /rodcprep
3. Ensure that at least one writable domain controller is running Windows Server 2008
4. Install the RODC.

If you are upgrading an existing forest to include DCs running W2008, you must run the command adprep /rodcprep.

This command configures permissions so that RODCs are able to replicate DNS application directory partitions. If you are creating a new Active Directory forest that contains only DCs running W2008, you do not need to run adprep /rodcprep.

You can find the adprep command in the cdrom\Sources\Adprep folder of the Windows Server 2008 installation DVD.

An RODC must replicate domain updates from a writable DC running W2008, and the RODC must be able to establish a replication connection with the writable W2008 DC.
Ideally, the writable W2008 DC should be in the closest site—the hub site. If you want the RODC to act as a DNS server, the writable W2008 DC must also host the DNS domain zone.

Installing an RODC
--------------------------------------
After you complete the preparatory steps, you can install an RODC on either a full or Server Core installation of W2008. On a full installation of W2008, you can use the Active Directory Domain Services Installation Wizard to create an RODC.
You select Read-Only Domain Controller (RODC) on the Additional Domain Controller Options page of the wizard

Alternatively, you can use the dcpromo command with the /unattend switch to create the RODC.
On a Server Core installation of W2008, you must use the dcpromo /unattend command.

Your answer file would be similar to the following:

[DCInstall]
Username=Pepe_Perez
Password=P@ssw0rd
UserDomain=windowsmeconfunde.internal
InstallDns=yes
ConfirmGC=yes
ReplicaOrNewDomain=ReadOnlyReplica
ReplicaDomainDNSName=windowsmeconfunde.internal
Sitename=MyBranch
databasePath="e:\ntds"
logPath="e:\ntdslogs"
sysvolpath:"f:\sysvol"
SafeModeAdminPassword:P@ssw0rd
RebootOnCompletion:yes

Password Replication Policy
----------------------------------------
PRP determines which users’ credentials can be cached on a specific RODC. If PRP allows an RODC to cache a user’s credentials, that user’s authentication and service ticket activities can be processed by the RODC. If a user’s credentials cannot be cached on an RODC, authentication and service ticket activities are referred to a writable domain controller by the RODC.

An RODC PRP is determined by two multivalued attributes of the RODC computer account.
These attributes are known as:

- Allowed List
-----------------
If a user’s account is on the Allowed List, the user’s credentials are cached. You can include groups on the Allowed List, in which case, all users who belong to the group can have their credentials cached on the RODC.

- Denied List
------------
If a user’s account is on the Denied List, the user’s credentials are not cached. You can include groups on the Denied List, in which case, all users who belong to the group can not have their credentials cached on the RODC.

If a user is on both the Allowed List and the Denied List, that user’s credentials will not be cached—the Denied List takes precedence

Configuring Domain-Wide Password Replication Policy
-----------------------------------------------------------
To facilitate the management of PRP, W2008 creates two domain local security groups in the Users container of AD DS.

- Allowed RODC Password Replication Group
-------------------------------------------
Is added to the Allowed List of each new RODC. By default, the group has no members.
Therefore, by default, a new RODC will not cache any user’s credentials. If there are users whose credentials you want all domain RODCs to cache, add those users to the Allowed RODC Password Replication Group.

- Denied RODC Password Replication Group
------------------------------------------
It is added to the Denied List of each new RODC. If there are users whose credentials you want to ensure domain RODCs never cache, add those users to the Denied RODC Password Replication Group. By default, this group contains security-sensitive accounts that are members of groups such as Domain Admins, Enterprise Admins, and Group Policy Creator Owners.

Configuring an RODC-Specific Password Replication Policy
---------------------------------------------------------------
The Allowed RODC Password Replication Group and Denied RODC Password Replication
Group provide a method of managing PRP on all RODCs. However, you typically need to
allow the RODC in each branch office to cache user and computer credentials for that specific location. Therefore, you must configure the Allowed List and the Denied List of each RODC.
To configure an RODC PRP, open the properties of the RODC computer account in the
Domain Controllers OU. On the Password Replication Policy tab, you can view the current PRP settings and add or remove users or groups from the PRP.

Administering Credentials Caching on an RODC
-----------------------------------------------------
When you click the Advanced button on the Password Replication Policy tab,the Advanced Password Replication Policy dialog box appears.

The drop-down list at the top of the Policy Usage tab enables you to select one of the following RODC reports:

- Accounts Whose Passwords Are Stored On This Read-Only Domain Controller--------------------------------------------------------------------------
This report displays the list of user and computer credentials currently cached on the RODC. You can use this list to determine whether credentials are being cached that you do not want to be cached on the RODC and modify the PRP accordingly.

- Accounts That Have Been Authenticated To This Read-Only Domain Controller
-----------------------------------------------------------------------------
This report displays the list of user and computer credentials that have been referred to a writable domain controller for authentication or service ticket processing. You can use this list to identify users or computers that are attempting to authenticate with the RODC. If any of these accounts are not being cached and you want them to be, add them to the PRP.

The Resultant Policy tab of the Advanced Password Replication Policy dialog box enables
you to evaluate the effective caching policy for an individual user or computer.
Click Add to select a user or computer account for evaluation.

Video: How install a RODC
--------------------------------------------

More Inf:
-----------------

Planning and Deploying Read-Only Domain Controllers

A read-only domain controller (RODC) is a new type of domain controller in the Windows Server® 2008 operating system. This guide explains what RODCs are and how they function. See the Overview below for links to other guides about how to deploy them in various scenarios.

http://www.microsoft.com/downloads/details.aspx?familyid=AE33A129-FF41-4BEC-B2B7-6DDCD4998828&displaylang=en

Deploying RODCs in the Perimeter Network

This topic describes how to deploy a read only domain controller (RODC) in a perimeter network, thereby extending the corporate forest into the perimeter network.

http://technet.microsoft.com/en-us/library/dd728035(WS.10).aspx

Administering RODCs in Branch Offices

This topic provides guidelines for common administrative tasks for read-only domain controllers (RODCs) in branch offices:

-Using Remote Desktop to administer RODCs in branch offices
-Reestablishing replication for an RODC
-Checking the lastLogonTimeStamp attribute on an RODC to discover stale accounts in a branch office
-Resolving an account lockout problem in a branch office with an RODC
-Performing backups of an RODC

http://technet.microsoft.com/en-us/library/dd736126(WS.10).aspx

Windows Server 2008 R2 Evaluation for Intel-Based, Itanium, Virtual Hard Drive for Hyper-V, and Remote Server Administration Tools for Windows® 7

2009-08-21T03:50:00.000-07:00

Windows Server 2008 R2 Evaluation for Itanium-Based Systems (180 days)
Brief Description
Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new features to enable organizations to increase the reliability and flexibility of their server infrastructures.

Overview
This software is for evaluation and testing purposes. The evaluation is available in ISO format. Evaluating any version of Windows Server 2008 R2 software does not require entering a product key, however will require activation within 10 days. Failing to activate the evaluation will cause the licensing service to shut the machine down every hour (The 10 day activation period can be reset five (5) times by using the rearm command. See below for further information on activation rearm). Once activated, the evaluation will run for 180 days. After this time, you will need to uninstall the software or upgrade to a fully-licensed version of Windows Server 2008 R2 for Itanium-Based Systems.
This download is also available through our new Download Manager. This will ensure 100% completion rate, and accelerate download times on slower links.
To start this download via the Download Manager, please click here.

http://www.microsoft.com/downloads/en/results.aspx?displaylang=en&period=30&nr=50&sortCriteria=Date&sortOrder=Ascending&stype=s_adv

Windows Server 2008 R2 Evaluation (180 days)
Brief Description
Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new features to enable organizations to increase the reliability and flexibility of their server infrastructures.

Overview
This software is for evaluation and testing purposes. The evaluation is available in ISO format. Web, Standard, Enterprise and Datacenter editions are available via the same download. You will be prompted for edition installation at setup. Evaluating any version of Windows Server 2008 R2 software does not require entering a product key, however will require activation within 10 days. Failing to activate the evaluation will cause the licensing service to shut the machine down every hour (The 10 day activation period can be reset five (5) times by using the rearm command. See below for further information on activation rearm). Once activated, the evaluation will run for 180 days. After this time, you will need to uninstall the software or upgrade to a fully-licensed version of Windows Server 2008 R2.
This download is also available through our new Download Manager. This will ensure 100% completion rate, and accelerate download times on slower links.
To start this download via the Download Manager, please click here.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=96a3a4b4-9453-4d30-97aa-c977560a0da4

Windows Server 2008 R2 Evaluation Virtual Hard Drive Images for Hyper-V (180 Days)
Brief Description
Windows Server 2008 R2 Evaluation Enterprise Edition and Server Core Virtual Hard Drive Images for Hyper-V

Overview
The Microsoft VHD format is the common virtualization file format for Hyper-V that provides a uniform product support system, and provides more seamless manageability, security, reliability and cost-efficiency for customers.
This VHD release is available in English only and is for evaluation and testing purposes. Evaluating any version of Windows Server 2008 R2 software does not require entering a product key, however will require activation within 10 days. Failing to activate the evaluation will cause the licensing service to shut the machine down every hour (The 10 day activation period can be reset four (4) times by using the rearm command. See below for further information on activation rearm). Once activated, the evaluation will run for 180 days. After this time, you will need to uninstall the software or upgrade to a fully-licensed version of Windows Server 2008 R2.
As this installation requires Hyper-V, you will need to have a base install of Windows Server 2008 (64-bit edition) or Windows Server 2008 R2, running Hyper-V. For more information on obtaining and installing the latest version of Hyper-V, please visit the Hyper-V Homepage.
Both virtual machines available here are running Windows Server 2008 R2 Enterprise Edition Evaluation. One is the default full installation, and the other has been configured as a default Core installation. For more information on the difference between full and core installation please see the Windows Server 2008 Editions Overview pages. For download options please see the IMAGE SELECTION section in the instructions below.
As both virtual machines do not have anti-virus installed, they should not be connected to any network until it has anti-virus installed.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9040a4be-c3cf-44a5-9052-a70314452305

Remote Server Administration Tools for Windows 7
Brief Description
Remote Server Administration Tools for Windows® 7 enables IT administrators to manage roles and features that are installed on computers that are running Windows Server® 2008 R2, Windows Server® 2008, or Windows Server® 2003, from a remote computer that is running Windows 7.

Overview
Remote Server Administration Tools for Windows 7 enables IT administrators to manage roles and features that are installed on remote computers that are running Windows Server 2008 R2 (and, for some roles and features, Windows Server 2008 or Windows Server 2003) from a remote computer that is running Windows 7. It includes support for remote management of computers that are running either the Server Core or full installation options of Windows Server 2008 R2, and for some roles and features, Windows Server 2008. Some roles and features on Windows Server 2003 can be managed remotely by using Remote Server Administration Tools for Windows 7, although the Server Core installation option is not available with the Windows Server 2003 operating system.
This feature is comparable in functionality to the Windows Server 2003 Administrative Tools Pack and Remote Server Administration Tools for Windows Vista with Service Pack 1 (SP1).

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d

TechNet Tour 2009: Lanzamiento Windows 7, Windows Server 2008 R2, Exchange server 2010

2009-08-17T05:50:00.000-07:00

Otro año más Microsoft TechNet llega a tu ciudad con las novedades de los productos de Microsoft.
Este evento pretende dar conocimiento de las novedades en los nuevos productos de Microsoft, Windows 7, Windows Server 2008 R2, Exchange Server 2010, Forefront y System Center, en el evento se realizaran demostraciones de los productos.

Idiomas: Español.
Productos: Microsoft Exchange Server 2010, Microsoft Forefront Client Security, Microsoft Forefront Security for Exchange Server, Microsoft System Center Virtual Machine Manager, Microsoft System Center Virtual Machine Manager 2007, Microsoft Windows Small Business Server, Security, Windows 7, Windows Essential Business Server y Windows Server 2008 R2.
Audiencia(s): Generalista de IT y Gerente de IT.

Calendario

Ciudad Real - 16 de Septiembre de 2009
Madrid - 23 de Septiembre de 2009
Barcelona - 6 de Octubre de 2009
Murcia - 8 de Octubre de 2009
Valencia - 13 de Octubre de 2009
Málaga - 15 de Octubre de 2009
Sevilla - 20 de Octubre de 2009
Cáceres - 22 de Octubre de 2009
Valladolid - 29 de Octubre de 2009
A Coruña - 3 de Noviembre de 2009
Bilbao - 5 de Noviembre de 2009
Pamplona - 10 de Noviembre de 2009
Zaragoza - 12 de Noviembre de 2009
Palma de Mallorca - 17 de Noviembre de 2009
Logroño - 19 de Noviembre de 2009
Las Palmas - 24 de Noviembre de 2009
Tenerife - 26 de Noviembre de 2009

Más información y Registro

http://technet.microsoft.com/es-es/ee256076.aspx

Diagnosticos de Directorio Activo con Microsoft IT Environment Health Scanner

2009-08-13T06:44:00.000-07:00

Microsoft IT Environment Health Scanner es una herramienta de diagnóstico diseñada para administradores de pequeñas o medianas empresas que necesitan comprobar la salud de sus servidores de directorio y de sus clientes.
Os añado la información original de Microsoft.

This tool identifies common problems that can prevent your network environment from functioning properly as well as problems that can interfere with infrastructure upgrades, deployments, and migration.

When run from a computer with the proper network access, the tool takes a few minutes to scan your IT environment, perform more than 100 separate checks, and collect and analyze information about the following:

- Configuration of sites and subnets in Active Directory
- Replication of Active Directory, the file system, and SYSVOL shared folders
- Name resolution by the Domain Name System (DNS)
- Configuration of the network adapters of all domain controllers, DNS servers, and e-mail servers running Microsoft Exchange Server
-Health of the domain controllers
- Configuration of the Network Time Protocol (NTP) for all domain controllers

If a problem is found, the tool describes the problem, indicates the severity, and links you to guidance at the Microsoft Web site (such as a Knowledge Base article) to help you resolve the problem. You can save or print a report for later review. The tool does not change anything on your computer or your network

System Requirements
Supported Operating Systems: Windows Server 2003 Service Pack 2; Windows Server 2008; Windows Vista Service Pack 1; Windows XP Service Pack 2

Note: make sure that you have installed the latest service packs and Windows operating system updates.

Required Software:

-.NET Framework 2.0
- Minimum Screen Resolution: 800 x 600

Descarga de la Herramienta:

http://www.microsoft.com/downloads/details.aspx?FamilyID=dd7a00df-1a5b-4fb6-a8a6-657a7968bd11&displaylang=en

Video de la Herramienta

Instalación de AD LDS (ADAM) en Windows 2008

2009-07-22T07:00:00.000-07:00

Requirements for AD LDS Installation and Removal

AD LDS installation requirements include the following:

- A supported operating system such as W2008 Standard, Enterprise, or Datacenter
- An account with local administration access rights

To remove AD LDS from a W2008 server, you must log on to the server by using an account that has local administrator rights. You then do the following:

- Use Programs And Features in Control Panel to uninstall any instance of AD LDS youcreated after the role installation.

- Use Server Manager to remove the AD LDS role.

Take care to ensure that you remove all AD LDS instances from a server before you remove the role itself.

Remember that you need to remove all instances of AD LDS from a server before you can
remove the role from the server.

Installing AD LDS on Server Core

To install AD LDS on a Server Core installation of W2008, log on with local administrative
credentials to a W2008 member or standalone server running Server Core and enter the following
command:

start /w ocsetup DirectoryServices-ADAM-ServerCore

Note that this command is case-sensitive. Using the start /w command ensures that the command prompt does not return until the role installation is complete. You can verify that the role is installed and discover the role name (DirectoryServices-ADAM-ServerCore) by using the following command:

oclist | more

Granular Password Settings en Windows 2008

2009-06-30T15:20:00.000-07:00

Hola a todos,
hoy vamos a contar la nueva funcionalidad de Windows 2008 "Granular Password Settings"

Como todos sabéis las Políticas de Password en Windows 2003 a través de la "Default Domain Policiy" solo permitían establecerlas y linkarlas a nivel de dominio, haciendo imposible el tener dos políticas de password diferentes

Este problema obligaba muchas veces en empresas donde era un requerimiento
a tener dos dominios distintos y hacer relaciones de confianza entre ambos.

Ahora Windows 2008 permite una política de password granular pudiendo tener mas de una "Password Policiy" en el dominio.

Os dejo un enlace sobre el tema , un virtual lab y un video explicativo:

AD DS: Fine-Grained Password Policies

http://technet.microsoft.com/en-us/library/cc770394.aspx

Granular Password Setting Video

In this video, Chris Henley shows you a new feature in Windows Server 2008 Active Directory that allows you to set additional password policies beyond the domain settings.

http://technet.microsoft.com/en-us/windowsserver/bb896051.aspx

TechNet Virtual Lab: Fine Grained Password Settings in Windows Server 2008

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032343981&EventCategory=3

Cursos Elearning Gratuitos de Microsoft (Junio 2009)

2009-06-24T07:51:00.000-07:00

Estimados todos,
a continuación os dejo los enlaces de los siguientes cursos gratutitos de Microsoft.
Espero os sean de utilidad.

Collection 6899: Exploring Features of Exchange Server 2010

Información general

This two-hour collection provides you with an overview of the new features in Exchange Server 2010. It also describes the enhancements made over Exchange Server 2007.

The clinics within this collection cover:

-New features in Exchange Server 2010
-Technology enhancements
-Management tools used in Exchange Server 2010
-Managing a Mailbox server
-Unified Messaging in Exchange Server 2010
-High availability features in Exchange Server 2010

Users completing this collection should have three or more years of experience working with previous versions of Exchange Server, including the implementation of Exchange Server 2007. They should be familiar with Active Directory, Exchange messaging, and SharePoint and fundamentals of Microsoft Office 2003, Microsoft Office 2007, Windows Server 2003, and Windows Server 2008. It is beneficial if they have experience with a Windows or command-line scripting.

https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=249671

Esta oferta incluye los cursos siguientes:

Clinic 6900: Introduction to Exchange Server 2010
Clinic 6901: Exchange Server 2010 in an Enterprise

Instalación del Cliente SCCM 2007

2009-06-23T07:51:00.000-07:00

Aquí os dejo este video donde se explica paso a paso como instalar el cliente
de Systenm Center Configuration Manager.
Espero os sea de utilidad.

Instalacion del cliente SCCM

Using Exchange Server Database Utilities (eseutil.exe) in Exchange 2003 / 2007 (Part 2)

2009-06-23T06:29:00.000-07:00

Eseutil work with ESE db files and logs. You can use to verify, modify and repair Exch db files.
When db is corrupt you must restore from backup first because Eseutil repair can result in data loss. Eseutil is located in
:\Program Files\Microsoft\Exchange server\Bin

You can use in Mailbox, Edge and Hub roles
You mustt use the same version of eseutil as version of Exch you are working. The Exch07 version does not support working with *.stm files.
You can only run one instance for eseutil. Eseutil modes:
- Defrag /D
Defrag offline but leaves the new db in temp location and reduces the size
- Repair /P
Repair a corrupt offline db discarding pages that cannot be fixed
- Restore /C
Displays restore log files (restore.env) and control hard recovery after restoration from
online backups
- Recovery /R
Replay logs or rolls them forward to restore a db to internall consistency or to bring
an older copy of a db up to date
- Integrity /G
Verifies the page level and ESE level logical integrity of db.
- File Dump /M
Displays headers of database files, transaction log files and checkpoints. Also display
database pagre header information and db space allocation
- Checksum /K
Verifies checksum on all pages in he db, logs and checkpoints
- Copy File /Y
Perform a fast copy of very large files

Exportar e importar cuentas de Outlook

2009-05-25T02:54:00.000-07:00

En este video relizado por Pilar Arguiñariz (MVP de Outlook), nos cuenta cómo exportar la configuración de las cuentas,
desde el registro de Windows, de un perfil ya configurado con cuentas y luego importarlas en nuevos perfiles o nuevas instalaciones
Aplicable a nuevos perfiles, nuevas instalaciones o instalaciones en otros ordenadores de Outlook.

Exchange 2010: What's your Favorite Feature

2009-05-25T02:39:00.000-07:00

En este video podemos ver que características del nuevo Exchange 2010 han gustado más a los asistentes del TechEd09.

Cursos Elearning Gratuitos de Microsoft (Mayo 2009)

2009-05-24T23:57:00.000-07:00

Clinic 6339: Database Fundamentals in Microsoft SQL Server 2008

Tiempo estimado para completar curso: 1 Hora
Publicado:
Idioma: Inglés
Público(s): IT Professional
Tecnología:
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí

Introducción

In this 1 hour clinic students are introduces to the fundamental concepts of database, how Microsoft SQL Server 2008 fits into the enterprise and be introduced to the applications used in Microsoft SQL Server 2008.

Topics covered in the courses within the course Include:

Introduction to fundamental database concepts.
Describe SQL Server 2008 in the enterprise.
Introduction to applications used to manage SQL Server.
This clinic provides useful pre requisite know for Microsoft E-Learning collections 2778BE, 6369AE and 6370AE.

Objetivos

Al finalizar el curso, los alumnos serán capaces de:
Describe fundamental database concepts.
Describe SQL Server 2008 in the enterprise.
Describe the applications used to manage SQL Server.

https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=106546&tab=overview

Clinic 6258: New Features Of Microsoft SQL Server 2008 Reporting Services

Tiempo estimado para completar curso: 1 Hora
Publicado:
Idioma: Inglés
Público(s): IT Professional
Tecnología: SQL Server 2008
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí

Introducción

This Clinic cover topics on New Reporting Services Features in SQL Server 2008 (BETA)

Objetivos

Al finalizar el curso, los alumnos serán capaces de:
This online course addresses several of the new features and functionality of Microsoft SQL Server 2008 Reporting Services
It includes the new Microsoft Report Designer
A look at the innovate tablix data region
Enhancements in visualization through improved charting and gauges
Exploration of new administration and management features are also explored

https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=89922&tab=overview

Collection 6187: What's New in Microsoft SQL Server 2008

Información general

In this 3 hour online collection, IT Professionals will learn about the new features in SQL Server 2008. Topics covered within these clinics include:

What's New in SQL Server 2008 for Enterprise Data Platform
https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=83564
What's New in SQL Server 2008 for Business Intelligence
https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=83565
What's New in SQL Server 2008 for Database Development
https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=83566

Student prerequisites
To get the most out of this clinic, the target audience should have previous experience with SQL Server technologies such as:

SQL Server 2005
SQL Server 2000

https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=139087

System Center Configuration Manager 2007 Logs

2009-05-21T07:50:00.000-07:00

Client Log Files
The Configuration Manager 2007 client logs are located in one of the following locations: · On computers that serve as management points, the client logs are located in the SMS_CCM\Logs folder. · On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder or the %Windir%\SysWOW64\CCM\Logs.

The following table lists and describes the client log files.

CAS
Content Access service. Maintains the local package cache.

CcmExec.log
Records activities of the client and the SMS Agent Host service.

CertificateMaintenance.log
Maintains certificates for Active Directory directory service and management points.

ClientIDManagerStartup.log
Creates and maintains the client GUID.

ClientLocation.log
Site assignment tasks.

ContentTransferManager.log
Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.

DataTransferService.log
Records all BITS communication for policy or package access.

Execmgr.log
Records advertisements that run.

FileBITS.log
Records all SMB package access tasks.

Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs)
Windows Management Instrumentation (WMI) provider for software inventory and file collection.

InventoryAgent.log
Creates discovery data records (DDRs) and hardware and software inventory records.

LocationServices.log
Finds management points and distribution points.

Mifprovider.log
The WMI provider for .MIF files.

Mtrmgr.log
Monitors all software metering processes.

PolicyAgent.log
Requests policies by using the Data Transfer service.

PolicyAgentProvider.log
Records policy changes.

PolicyEvaluator.log
Records new policy settings.

Remctrl.log
Logs when the remote control component (WUSER32) starts.

Scheduler.log
Records schedule tasks for all client operations.

Smscliui.log
Records usage of the Systems Management tool in Control Panel.

StatusAgent.log
Logs status messages that are created by the client components.

SWMTRReportGen.log
Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Site Server Log Files
Most Configuration Manager 2007 site server log files are located in the \LOGS folder.
Because Configuration Manager 2007 relies heavily on Microsoft Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server.
The IIS log file is located in the %Windir%\System32\logfiles\W3SVC1 folder on the IIS server. The following table lists and describes the site server log files.

Ccm.log
Client Configuration Manager tasks.

Cidm.log
Records changes to the client settings by the Client Install Data Manager (CIDM).

Colleval.log
Logs when collections are created, changed, and deleted by the Collection Evaluator.

Compsumm.log
Records Component Status Summarizer tasks.

Cscnfsvc.log
Records Courier Sender confirmation service tasks.

Dataldr.log
Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.

Ddm.log
Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.

Despool.log
Records incoming site-to-site communication transfers.

Distmgr.log
Records package creation, compression, delta replication, and information updates.

Hman.log
Records site configuration changes, and publishes site information in Active Directory Domain Services.

Inboxast.log
Records files that are moved from the management point to the corresponding SMS\INBOXES folder.

Inboxmgr.log
Records file maintenance.

Invproc.log
Records the processing of delta MIF files for the Dataloader component from client inventory files.

Mpcontrol.log
Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.

Mpfdm.log
Management point component that moves client files to the corresponding SMS\INBOXES folder.

MPMSI.log
Management point .msi installation log.

MPSetup.log
Records the management point installation wrapper process.

Ntsvrdis.log
Configuration Manager 2007 server discovery.

Offermgr.log
Records advertisement updates.

Offersum.log
Records summarization of advertisement status messages.

Policypv.log
Records updates to the client policies to reflect changes to client settings or advertisements.

Replmgr.log
Records the replication of files between the site server components and the Scheduler component.

Rsetup.log
Reporting point setup log.

Sched.log
Records site-to-site job and package replication.

Sender.log
Records files that are sent to other child and parent sites.

Sinvproc.log
Records client software inventory data processing to the site database in Microsoft SQL Server.

Sitecomp.log
Records maintenance of the installed site components.

Sitectrl.log
Records site setting changes to the Sitectrl.ct0 file.

Sitestat.log
Records the monitoring process of all site systems.

Smsdbmon.log
Records database changes.

Smsexec.log
Records processing of all site server component threads.

Smsprov.log
Records WMI provider access to the site database.

SMSReportingInstall.log
Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.

Srvacct.log
Records the maintenance of accounts when the site uses standard security.

Statmgr.log
Writes all status messages to the database.

Swmproc.log
Processes metering files and maintains settings.

Admin UI log files

The Admin UI log files are located in \AdminUI\. The following table lists and describes the Admin UI log files.

RepairWizard.log
Records errors, warnings, and information about the process of running the Repair Wizard.

ResourceExplorer.log
Records errors, warnings, and information about running the Resource Explorer.

SMSAdminUI.log
Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files
If management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer. The following table lists and describes the management point log files.

MP_Ddr.log
Records the conversion of XML.ddr records from clients, and copies them to the site server.

MP_GetAuth.log
Records the status of the site management points.

MP_GetPolicy.log
Records policy information.

MP_Hinv.log
Converts XML hardware inventory records from clients and copies the files to the site server.

MP_Location.log
Records location manager tasks.

MP_Policy.log
Records policy communication.

MP_Relay.log
Copies files that are collected from the client.

MP_Retry.log
Records the hardware inventory retry processes.

MP_Sinv.log
Converts XML hardware inventory records from clients and copies them to the site server.

MP_Status.log
Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files
If mobile device management is enabled in the site hierarchy, mobile device management point log files are generally stored in the \LOGS folder on the mobile device management point computer. The following table lists and describes the mobile device management point log files.
Mobile Device Management Point Logs

DmClientHealth.log
Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.

DmClientRegistration.log
Records registration requests from and responses to the mobile device client in Native mode.

DmpDatastore.log
Records all the site database connections and queries made by the Device Management Point.

DmpDiscovery.log
Records all the discovery data from the mobile device clients on the Device Management Point.

DmpFileCollection.log
Records mobile device file collection data from mobile device clients on the Device Management Point.

DmpHardware.log
Records hardware inventory data from mobile device clients on the Device Management Point.

DmpIsapi.log
Records mobile device communication data from device clients on the Device Management Point.

dmpMSI.log
Records the MSI data for Device Management Point setup.

DMPSetup.log
Records the mobile device management setup process.

DmpSoftware.log
Records mobile device software distribution data from mobile device clients on the Device Management Point.

DmpStatus.log
Records mobile device status messages data from mobile device clients on the Device Management Point.

FspIsapi.log
Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Management Client Logs
For the locations of log files on managed mobile devices and on computers that are used to deploy the mobile device client, see How to Configure Logging for Windows Mobile and Windows CE Devices. The following table lists and describes the mobile device management client log files.

DmCertEnroll.log
Records certificate enrollment data on mobile device clients.

DMCertResp.htm (in \temp)
Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.

DmClientSetup.log
Records client setup data on mobile device clients.

DmClientXfer.log
Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.

DmCommonInstaller.log
Records client transfer file installation for setting up mobile device client transfer files on client computers.

DmInstaller.log
Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.

DmInvExtension.log
Records Inventory Extension file installation for setting up Inventory Extension files on client computers.

DmSvc.log
Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files
The following table lists and describes the operating system deployment log files.

CCMSetup.log
Provides information about client-based operating system actions.

CreateTSMedia.log
Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.

DriverCatalog.log
Provides information about device drivers that have been imported into the driver catalog.

MP_ClientIDManager.log
Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.

MP_DriverManager.log
Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.

MP_Location.log
Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.

Pxecontrol.log
Provides information about the PXE Control Manager.

PXEMsi.log
Provides information about the PXE service point and is generated when the PXE service point site server has been created.

PXESetup.log
Provides information about the PXE service point and is generated when the PXE service point site server has been created.

Setupact.log Setupapi.log Setuperr.log
Provide information about Windows Sysprep and setup logs.

SmpIsapi.log
Provides information about the state migration point Configuration Manager 2007 client request responses.

Smpmgr.log
Provides information about the results of state migration point health checks and configuration changes.

SmpMSI.log
Provides information about the state migration point and is generated when the state migration point site server has been created.

Smsprov.log
Provides information about the SMS provider.

Smspxe.log
Provides information about the Configuration Manager 2007 PXE service point.

SMSSMPSetup.log
Provides information about the state migration point and is generated when the state migration point site server has been created.

Smsts.log
General location for all operating system deployment and task sequence log events.Log file location:· If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: \logs· If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG· If task sequence completes when running in WindowsPE: \SMSTSLOG

Note

is %windir%\system32\ccm\logs for most Configuration Manager 2007 clients and is \SMS_CCM for the Configuration Manager 2007 site server. For 64-bit operating systems, it is %windir%\SysWOW64\ccm\logs.

TaskSequenceProvider.log
Provides information about task sequences when they are imported, exported, or edited.

USMT Log loadstate.log
Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.

USMT Log scanstate.log
Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files
By default, client log files related to Network Access Protection are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs.The following table lists and describes the Network Access Protection log files.

Ccmcca.log
Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.

CIAgent.log
Tracks the process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details on installing the software updates required for compliance.

locationservices.log
Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.

SDMAgent.log
Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.

SMSSha.log
The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

The System Health Validator point

The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs, and they are listed and described in the following table.

Ccmperf.log
Contains information about the initialization of the System Health Validator point performance counters.

SmsSHV.log
The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.

SmsSHVADCacheClient.log
Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.

SmsSHVCacheStore.log
Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.

SmsSHVRegistrySettings.log
Records any dynamic changes to the System Health Validator component configuration while the service is running.

SmsSHVQuarValidator.log
Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Setup information for the System Health Validator point can be found in a setup log file, described in the following table, on the computer running the Network Policy Server.

\Logs\SMSSHVSetup.log
Records the success or failure (with failure reason) of installing the System Health Validator point.

Desired Configuration Management Log Files

By default, the Configuration Manager 2007 client computer log files are found in %windir%\System32\CCM\Logs or in %windir%\SysWOW64\CCM\Logs. For client computers that are also management points, the client log files are located in the SMS_CCM\Logs folder. The following table lists and describes these log files.

ciagent.log
Provides information about downloading, storing, and accessing assigned configuration baselines.

dcmagent.log
Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.

discovery.log
Provides detailed information about the Service Modeling Language (SML) processes.

sdmagent.log
Provides information about downloading, storing, and accessing configuration item content.

sdmdiscagent.log
Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files
The Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder \Logs on the site server. There are no client-side log files for Wake On LAN. The following table lists and describes the Wake On LAN log files.

Wolmgr.log
Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.

WolCmgr.log
Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files
The Configuration Manager 2007 site server log files are found, by default, in \Logs. The following table lists and describes the software updates site server log files.

ciamgr.log
Provides information about the addition, deletion, and modification of software update configuration items.

distmgr.log
Provides information about the replication of software update deployment packages.

objreplmgr.log
Provides information about the replication of software updates notification files from a parent to child sites.

PatchDownloader.log
Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.

Note

On 64-bit operating systems and on 32-bit operating systems with no Configuration Manager 2007 installed, PatchDownloader.log is created in the server logs directory. On 32-bit operating systems, if the Configuration Manager 2007 client is installed, PatchDownloader.log is created in the client logs directory.

replmgr.log
Provides information about the process for replicating files between sites.

smsdbmon.log
Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.

SUPSetup
Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.

WCM.log
Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.

WSUSCtrl.log
Provides information about the configuration, database connectivity, and health of the WSUS server for the site.

wsyncmgr.log
Provides information about the software updates synchronization process.

WSUS Server Log Files
By default, the log files for WSUS running on the software update point site system role are found in %ProgramFiles%\Update Services\LogFiles. The following table lists and describes the WSUS server log files.

Change.log
Provides information about the WSUS server database information that has changed.

SoftwareDistribution.log
Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files
By default, the Configuration Manager 2007 client computer log files are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs. The following table lists and describes the software updates client computer log files.

CAS.log
Provides information about the process of downloading software updates to the local cache and cache management.

CIAgent.log
Provides information about processing configuration items, including software updates.

LocationServices.log
Provides information about the location of the WSUS server when a scan is initiated on the client.

PatchDownloader.log
Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

PolicyAgent.log
Provides information about the process for downloading, compiling, and deleting policies on client computers.

PolicyEvaluator
Provides information about the process for evaluating policies on client computers, including policies from software updates.

RebootCoordinator.log
Provides information about the process for coordinating system restarts on client computers after software update installations.

ScanAgent.log
Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.

ScanWrapper
Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.

SdmAgent.log
Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.

ServiceWindowManager.log
Provides information about the process for evaluating configured maintenance windows.

smscliUI.log
Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.

SmsWusHandler
Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.

StateMessage.log
Provides information about when software updates state messages are created and sent to the management point.

UpdatesDeployment.log
Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.

UpdatesHandler.log
Provides information about software update compliance scanning and about the download and installation of software updates on the client.

UpdatesStore.log
Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.

WUAHandler.log
Provides information about when the Windows Update Agent on the client searches for software updates.

WUSSyncXML.log
Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File
By default, the Windows Update Agent log file is found on the Configuration Manager Client computer in %windir%. The following table provides the log file name and description.

WindowsUpdate.log
Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

Windows Server 2008 R2 Release Candidate

2009-05-21T06:15:00.000-07:00

Estimados todos,
ya está aquí la nueva generación del sistema operativo de Microsoft.
Microsoft Windows Server 2008 R2 RC te permitirá probar y evaluar esta versión.

Overview
This software is for evaluation and testing purposes. Evaluating any version of Windows Server 2008 R2 Release Candidate software does not require product activation or entering a product key. Any edition of Windows Server 2008 R2 Release Candidate may be installed without activation and evaluated for an initial 30 days. If you need more time to evaluate Windows Server 2008 R2 Release Candidate, the initial 30 day evaluation can be extended to March 1, 2010 (at which time the OS will become inoperable) by entering the product key below for your selected edition.
Windows Server 2008 R2 Release Candidate Product Keys for Evaluation
Windows Server 2008 R2 Release Candidate Enterprise

 Product Code : Q7Y83-W4FVQ-6MC6C-6QQTD-TPM88
Windows Server 2008 R2 Release Candidate Standard

 Product Code : V4KRB-QDWK2-GVT4X-BV4XG-34TV4
Windows Server 2008 R2 Release Candidate Datacenter

 Product Code : WXGKX-XXW8X-P8KTJ-PFX7T-DPYYW
Windows Web Server 2008 R2 Release Candidate

 Product Code: RBBKH-BVD6B-74FV9-RYPJ7-TCFXB
Download the evaluation version below. Images are ISO formats. Web, Standard, Enterprise and Datacenter editions are available via the same download Windows_Server_2008_R2_RC_EN.iso

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a4e21e2e-e992-4aec-9ed4-086de21632a2

Disponible el Service Pack 1 de SQL Server 2008

2009-04-23T06:30:00.000-07:00

El Service Pack 1 (SP1) de SQL Server 2008 ya está disponible.
Con este service pack puedes actualizar cualquier edición de SQL Server 2008.
Os anexo toda la información disponible:

Note:We remain committed to our plans to keep service packs contained, focusing on essential updates only, primarily a Roll-up of Cumulative Update 1 to 3, Quick Fix Engineering (QFE) updates, as well as fixes to issues reported through the SQL Server community. While keeping product changes contained, we have made significant investments to ease deployment and management of Service Packs:

Slipstream – You are now able to integrate the base installation with service packs (or Hotfixes) and install in a single step.

Service Pack Uninstall – You are now able to uninstall only the Service Pack (without removing the whole instance)
Report Builder 2.0 Click Once capability

For more information about SQL Server 2008 Service Pack 1, please review the Release Notes.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19

Disponible la Beta de Microsoft Exchange Server 2010

2009-04-15T23:50:00.000-07:00

Estimados todos,
hoy se ha publicado la primera Beta disponible para su descarga y que podréis testear durante 360 días.
Os dejo el enlace de descarga ,las novedades incluidas en ésta Beta, enlaces al sitio de TechNet donde se publicará la documentación técnica y el foro oficial de TechNet.

Microsoft Exchange Server 2010 helps you achieve new levels of reliability and performance by delivering features that help to simplify your administration, protect your communications, and delight your users by meeting their demands for greater business mobility.

http://technet.microsoft.com/en-us/exchange/2010/default.aspx

What’s New in Exchange Server 2010 Beta?

New Rights-Protected E-Mail Functionality with Active Directory RMS
· Transport rules to apply AD RMS protection to messages based on conditions
· Persistent protection of attachments in rights-protected messages
· Support for AD RMS templates
· An Internet confidential AD RMS template for protection over the Internet
· AD RMS protection for Unified Messaging voice mail messages

New Transport and Routing Functionality
· Cross-premises mail routing - An organization can choose to outsource some of their mailboxes to a hosted solution while maintaining their on-premises deployment. Exchange 2010 allows routing of messages between the on-premises and hosted mailboxes.
· Enhanced disclaimers - Exchange 2010 lets you add disclaimers that can include hyperlinks, images, and HTML-formatted text. You can also insert Active Directory attributes that are substituted for the sender's attributes when a disclaimer rule is triggered.
· Transport rules integration with AD RMS - Exchange 2010 gives you the ability to create rules that require AD RMS protection based on keywords or patterns.
· Moderated Transport - Exchange 2010 provides an approval workflow for sending messages to recipients. When you configure a recipient for moderation, all messages sent to that recipient must go through an approval process.
· Shadow redundancy - Messages that are submitted to an Exchange 2010 Hub Transport server are stored in the transport database until the next hop reports successful delivery of the message. If the next hop doesn't report successful delivery and it fails, the message is resubmitted for delivery.
· Transport dumpster truncation based on log copy status - When messages that are in the dumpster are replicated to all mailbox databases, they're removed from the dumpster.
· Latency SLA management - Exchange 2010 Transport lets you measure service levels delivered relative to your service level agreement (SLA) goals. Exchange 2010 gives you the ability to measure latencies for each hop, as well as end-to-end latency.
· Transport database improvements - Performance improvements in the Transport database result in reduced database I/O per second (IOPS) per message, which increases message throughput.

New Permissions Functionality
In Exchange 2010, Role Based Access Control (RBAC) has replaced the permissions model that was used in Exchange 2007. RBAC lets you define extremely broad or extremely precise roles and assignments based on the roles of your administrators and users, and the tasks they perform. Access to the cmdlets and parameters required to perform a task is granted by assigning the related RBAC management role to a user or universal security group. If you want to grant an administrator or user the ability to perform tasks in Exchange 2010, you must either add the administrator or user to a universal security group that already has been assigned a specific RBAC role, or you must assign the role directly to the administrator or user.

New High Availability Functionality
Exchange 2010 combines the key availability and resilience features of cluster continuous replication (CCR) and standby continuous replication (SCR) into a single high availability solution that handles both on-site data replication and off-site data replication. Mailbox servers can be defined as part of a Database Availability Group to provide automatic recovery at the individual mailbox database level instead of at the server level. Each mailbox database can have up to 16 copies.
The following features in Exchange 2007 and Exchange 2007 Service Pack 1 (SP1) no longer exist in Exchange 2010:
· Local continuous replication (LCR)
· Single copy clusters (SCC)

New Messaging Policy and Compliance Features
· Exchange 2010 compliance features make retention independent of users' mailbox management and filing habits, and these features ensure retention policies are applied continuously
· interface for applying retention policies
· Auto tagging for retention policies
· Mailbox search features for cross-mailbox search with Advanced Query Syntax (AQS) support
· New transport rules predicates and actions

New Outlook Web Access Features
· Favorites in the Navigation Pane
· Search folders
· Message filtering
· The ability to set categories in the message list
· Options in the Web management interface for Outlook Web Access
· A side-by-side view for calendars
· Multi-client language support
· The ability to attach messages to messages
· Expanded right-click capabilities
· Integration with Office Communicator, including presence, chat, and a contact list
· Conversation view
· The ability to send and receive text (SMS) messages from Outlook Web Access
· Outlook Web Access mailbox policies

New Unified Messaging Features
· Personal auto attendants (call answering rules)
· Additional language support including in Outlook Voice Access and Voice Mail Preview
· Enhancements to name lookup from caller ID
· Voice Mail Preview
· Messaging Waiting Indicator
· Missed call and voice mail notifications using text messaging (SMS)
· Protected Voice Mail
· Built-in Unified Messaging administrative roles

Web Management Interface
· Text messaging (SMS) integration
· Voice messaging integration
· Mailbox Search
· Distribution list creation and management
· Moderation and approval for distribution list submission

New Exchange Core Store Functionality
· Storage groups are deprecated
· Mailbox databases are no longer connected to the server object
· Extensible Storage Engine (ESE) has many improvements for high availability, performance, and database mobility
· The Store schema has been flattened

New Administration Functionality in the Exchange Management Console
The core EMC refers to new functionality that affects how you use the Exchange Management Console that includes:
· Customer Experience Improvement Program (CEIP)
· Organizational Health
· Community and Resources
· Command logging
· Property dialog command exposure

New Administration Functionality in the Exchange Management Shell
· Remote administration - With the new Shell, you can connect to remote Exchange 2010 servers across the network with only Windows PowerShell V2 CTP3 and Windows Remote Management 2.0 CTP installed.
· Administrator audit logging - Actions that result in the modification of Exchange organization configuration and other object properties in the Exchange Management Console, the Web management interface, and the Shell can now be logged for later review.

FAQ
What is the release schedule for Exchange 2010? That information will be published very soon – stay tuned!
How long does the beta last? This time-limited, free beta version of Microsoft® Exchange Server 2010 will end 360 days after installation.

Can I upgrade from Exchange 2003 directly to Exchange Server 2010?

http://technet.microsoft.com/en-us/library/aa998604(EXCHG.140).aspx

Where can I find more about Exchange Server 2010?

http://technet.microsoft.com/en-us/library/bb124558(EXCHG.140).aspx

Is there a forum where I can ask questions? Yes -

http://social.technet.microsoft.com/Forums/en-US/exchange2010/threads

Como usar esutil.exe en Exchange 2003 / 2007 (Parte 1)

2009-04-13T16:33:00.000-07:00

Vamos a ver los diferentes usos de Eseutil.exe y a dar información al respecto:

- Uso del switch /K para detectar daños en las cabezeras de ficheros.

File header damage puede ocurrir in databases, log files, patch files, o ficheros de checkpoint.

C:\Program Files\ExchSrvr\Bin\eseutil /k "c:\program files\exchsrvr\mdbdata\priv1.edb"

Verificar la integridad checksum de los transaction logs.
Todas las bases de datos del Storage Group deben estár desmontadas:

c:\Exchsrvr\bin>eseutil /k c:\exchsrvr\mdbdata\e00.log

How To: Use the Eseutil Utility to Detect File Header Damage in Exchange 2003
http://support.microsoft.com/kb/825088/en-us

Comprobar que todos los logs de una secuencia son correctos.

c:\Exchsrvr\bin>eseutil /ml Enn

Comprobar Estado de Cierre (Clean Shutdown o Dirty Shutdown) y Log_required (Log requerido para arrancar)

c:\Exchsrvr\bin>eseutil /MH D:/msdbdata/priv1.edb

En caso que uno de los ficheros esté corrupto:

1) Usar siempre un backup para restaurar
2) En caso de no disponer de backup ejecutar:
2.1) Primero hacer un backup de las bases de datos publicas y privadas y logs
copiandolos a otra carpeta con los servicios de exchange parados

2.2) Para un EDB corrupto

c:\Exchsrvr\bin>eseutil /p D:/msdbdata/priv1.edb

2.3 Para un STM corrupto:

c:\Exchsrvr\bin>eseutil /p D:/msdbdata/priv1.stm

2.4 Para reparar en una localización temporal (problemas de espacio en el disco (110%)):

c:\Exchsrvr\bin>eseutil /p D:/msdbdata/priv1.edb /t z:/eseutiltemporal.edb

Bibliografia:

Exchange Command-Line Parameters for the Isinteg.exe Tool
http://support.microsoft.com/default.aspx?scid=kb;en-us;301460

How to re-create STM File in Exchange 2000/2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;555146

XADM: Exchange 2000 Server Eseutil Command Line Switches
http://support.microsoft.com/default.aspx?scid=kb;EN-US;317014

How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;248122

XADM: Exchange and Antivirus Software
http://support.microsoft.com/default.aspx?scid=kb;[LN];328841

XADM: Ramifications of Running the ESEUTIL /P or EDBUTIL /D /R Command
http://support.microsoft.com/?id=259851

Preview: Exchange Server 2003 Disaster Recovery Planning Guide
http://www.microsoft.com/downloads/details.aspx?FamilyId=784BBEA2-28DD-409A-8368-F9914E993B28&displaylang=en

Hyper-V Live Migration Video Series (Parte 5)

2009-04-13T16:24:00.000-07:00

Quinta entrega de estos seis pequeños de Technet Edge que explican como configurar "Live Migration" de Máquinas Virtuales con Windows Server 2008 R2 e Hyper-V.

Hyper-V Live Migration Video Series (Parte 4)

2009-04-13T16:12:00.000-07:00

Hola a todos, aquí teneis el cuarto de los seis webcast de Technet Edge que explican como configurar "Live Migration" de Máquinas Virtuales con Windows Server 2008 R2 e Hyper-V.

Hyper-V Live Migration Video Series (Parte 3)

2009-03-11T17:38:00.000-07:00

Hola a todos,
aquí teneis la tercera de seis pequeños webcast de Technet Edge que explican como configurar "Live Migration" de Máquinas Virtuales con Windows Server 2008 R2 e Hyper-V.

Hyper-V Live Migration Video Series (Parte 2)

2009-03-11T17:34:00.001-07:00

Hola a todos,
aquí teneis el segundo de seis webcast de Technet Edge que explican como configurar "Live Migration" de Máquinas Virtuales con Windows Server 2008 R2 e Hyper-V.

Hyper-V Live Migration Video Series (Parte 1)

2009-03-11T17:11:00.000-07:00

Hola a todos,
hoy os dejo el primero de seis pequeños webcast de Technet Edge que explican como configurar "Live Migration" de Máquinas Virtuales con Windows Server 2008 R2 e Hyper-V.

Este experimento lo puedes reproducir con tres máquinas para familiarizarte con esta nueva tecnología.
La primera parte te explica la configuración del almacenamiento.
Puedes ver el enlace siguiente para ver más detalles:
http://edge.technet.com/Media/HPC-Server-2008-High-Availability-Part-1/

Uso de repadmin para resolución de problemas de réplica de Directorio Activo

2009-02-05T15:41:00.000-08:00

A continuación voy a mostrar varias sentencias de repadmin del kit de recursos para resolución de problemas de replicación de directorio activo:

1) Ver los socios de réplica de un controlador de dominio

repadmin /showrepl server1.microsoft.com

Resultados:
repadmin /showrepl server1.microsoft.com
Building7a\server1
DC Options : IS_GC
Site OPtions: (none)
DC object GUID : 405db077-le28-4825-b225-c5bb9af6f50b
DC invocationID: 405db077-le28-4825-b225-c5bb9af6f50b

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=microsoft,Dc=com
Building7b\server2 via RPC
objectGuid: e55c6c75-75bb-485a-a0d3-020a44c3afe7
last attempt @ 2002-09-09 12:25.35 was successful.

CN=Configuration,DC=microsoft,Dc=com
Building7b\server2 via RPC
objectGuid: e55c6c75-75bb-485a-a0d3-020a44c3afe7
last attempt @ 2002-09-09 12:25.10 was successful.

DC=microsoft,Dc=com
Building7b\server2 via RPC
objectGuid: e55c6c75-75bb-485a-a0d3-020a44c3afe7
last attempt @ 2001-09-09 12:25.11 was successful.

2) Ver los Números de Secuencia de Actualización (USN) más altos en un servidor para una partición determinada

repadmin /showutdvec . dc=microsoft,dc=com server2.microsoft.com

Resultados:
repadmin running command /showutdvec against server localhost

Caching GUIDs.
..
Building7b\Server1 @ USN 295458 @ Time 2002-09-09 19:33:42
Building7b\Server2 @ USN 338194 @ Time 2002-09-09 19:38:16

3) Ver los cambios sin replicar entre dos servidores

repadmin /showchanges server2.microsoft.com ObjectGUID dc=microsoft,dc=com

donde el ObjectGUID Ejemplo: 5c02bcaf-86d9-4bed-811e-d17a5cebf8bb hay que reemplazarlo por el ObjectGUID de la partición de directorio del servidor origen

Resultados:

repadmin /showchanges server2.microsoft.com 5c02bcaf-86d9-4bed-811e-d17a5cebf8bb dc=microsoft,dc=com

server2.microsoft.com
Building starting position from destination server rktlabdc2.rktlabdom.com

Source Neighbor:
dc=microsoft,dc=com
==== INBOUND NEIGHBORS ======================================

dc=microsoft,dc=com
Building7b\Server1 via RPC
DC object GUID: 5c02bcaf-86d9-4bed-811e-d17a5cebf8bb
Address: 5c02bcaf-86d9-4bed-811e-d17a5cebf8bb._msdcs.microsoft.com
DC invocationID: 064152bc-f8e8-404f-bd64-cdd9bb3958cb
SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
USNs: 296048/OU, 296048/PU
Last attempt @ 2002-09-09 20:03:53 was successful.

Destination's up-to-date vector:
064152bc-f8e8-404f-bd64-cdd9bb3958cb @ USN 296163
fea22f1d-a456-4f70-aa06-bedbda29e7eb @ USN 338287

==== SOURCE DC: 5c02bcaf-86d9-4bed-811e-d17a5cebf8bb._msdcs.microsoft.com ====

No Changes

4) Ver el estado de replicación de los controladores de dominio en un bosque

repadmin /replsummary FOURTH*

Resultados:
repadmin /replsummary FOURTH*
Replication Summary Start Time: 2002-09-18 14:54:49

Beginning data collection for replication summary, this may take awhile:

Source DC largest delta fails/total %% error
FOURTH-CLT-DC-01 54m:57s 0 / 9 0
FOURTH-DC-05 41m:23s 0 / 175 0
FOURTH-DC-06 55m:08s 0 / 66 0
FOURTH-DC-07 09m:29s 0 / 97 0
FOURTH-DC-08 18h:05m:02s 56 / 56 100 (1722) The RPC server is unavailable.
FOURTH-DC-09 56m:47s 0 / 12 0
FOURTH-DC-10 55m:10s 0 / 13 0
FOURTH-DC-11 56m:48s 0 / 46 0
FOURTH-DC-12 57m:09s 0 / 34 0
FOURTH-DC-13 55m:52s 0 / 64 0
FOURTH-DC-14 55m:52s 0 / 85 0
FOURTH-DC-15 09m:21s 0 / 50 0
FOURTH-DC-16 58m:02s 0 / 37 0
FOURTH-DC-17 57m:00s 0 / 48 0
FOURTH-DC-18 57m:00s 0 / 22 0
FOURTH-DC-19 58m:02s 0 / 22 0
FOURTH-DC-20 08m:05s 0 / 22 0
FOURTH-DC-21 05m:43s 0 / 22 0
FOURTH-DC-22 09h:06m:29s 0 / 199 0
FOURTH-DC-23 09m:29s 0 / 34 0
FOURTH-DC-24 56m:48s 0 / 184 0
FOURTH-DC-25 41m:22s 0 / 71 0
FOURTH-DC-26 08m:16s 0 / 108 0
FOURTH-DC-30 55m:13s 0 / 47 0
FOURTH-DC-31 41m:23s 0 / 56 0
FOURTH-SVC-DC-40 57m:02s 0 / 9 0
FOURTH-TK-DC-27 07m:02s 0 / 54 0
FOURTH-TK-DC-28 08m:01s 1 / 161 0 (8461) The replication operation was preempted.
FOURTH-TK-DC-29 55m:10s 0 / 115 0

Experienced the following operational errors trying to retrieve replication information:
58 - fourth-dc-08.fourthcoffee.com

http://technet.microsoft.com/en-us/library/cc773062.aspx

Papelera de Reciclaje de Active Directory en Windows 2008 R2

2009-01-28T03:55:00.000-08:00

Active Directory Recycle Bin te ayuda a minimizar pérdidas de servicio permitiéndote la habilidad de preservar y restaurar objetos de Directorio Activo borrados accidentalmente sin tener que restaurarlos de Backup, o rebotar Controladores de Dominio.
Por defecto esta funcionalidad está deshabilitada y hay que habilitarla en el bosque.
El nivel funcional del bosque debe ser elevado a Windows 2008 R2 Aquí os dejo este vídeo con una demostración de esta valiosa característica que hará las delicias de todos aquellos a los que el ratón y no leer los mensajes de Warning nos ha jugado una mala pasada.

Más información en los siguientes enlaces:

Active Directory Recycle Bin Step-by-Step Guide

http://technet.microsoft.com/en-us/library/dd392261.aspx

Enable Active Directory Recycle Bin
http://technet.microsoft.com/en-us/library/dd379481.aspx

Restore a Deleted Active Directory Object

http://technet.microsoft.com/en-us/library/dd379509.aspx

Como mapear impresoras de red en modo comando con PrintUI.dll

2009-01-28T02:47:00.000-08:00

Seguro que se os ocurren muchas ocasiones para usar estos bonitos comandos para salir de algún aprieto

1) Añadir impresoras:

Como añadir una impresora solo para la sesión de usuario que ejecuta el comando:

rundll32 printui.dll,PrintUIEntry /in /n\\servidorimpresion\nombre_impresora

Para que la impresora esté disponible para todos los perfiles de usuario del equipo:

rundll32 printui.dll PrintUIEntry /ga /n\\ servidorimpression\nombre_impresora

2) Eliminar impresoras:

Como eliminar una impresora existente a la sesión de usuario que ejecuta el comando:

rundll32 printui.dll,PrintUIEntry /dn /n\\ servidorimpresion\nombre_impresora

Para eliminar la impresora para todos los perfiles de usuario del equipo:

rundll32 printui.dll PrintUIEntry /gd /n\\ servidorimpresion\nombre_impresora

3.- Establecer una impresora por defecto:

rundll32 printui.dll,PrintUIEntry /y /n\\ servidorimpresion\nombre_impresora

Si consultáis la ayuda encontraréis el resto de opciones disponibles para este comando

rundll32 printui.dll PrintUIEntry /?

Extraído del artículo:

http://blogs.technet.com/plataformas/archive/2009/01/22/mapeo-de-impresoras-de-red-por-l-nea-de-comandos-printui-dll.aspx

Win32/Conficker.B worm (MS08-067)

2009-01-27T07:52:00.000-08:00

Numerosas empresas están teniendo problemas por gusanos de la familia Conficker/Downadup si no se ha aplicado la actualización de seguridad MS08-067

En cuanto a la información relativa al gusano, podéis obtenerla actualizada en :

Microsoft Malware Protection Center - Entry: Worm Win32/Conficker.B: http://www.microsoft.com/security/portal/Entry.aspx?name=Worm%3aWin32%2fConficker.B

En cuanto a las acciones a llevar a cabo, existe una recopilación de acciones a llevar a cabo en el artículo:

Virus alert about the Win32/Conficker.B worm:

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

Cualquier plan de acción pasará por actualizar todos los motores o firmas antivirus (si ya han sido infectados por el worm), la MSRT también puede ayudar, y pasar las actualizaciones de seguridad a todas las máquinas.

Mientras tanto, como recomendaciones generales es conveniente hacer logon con cuentas con las credenciales estrictamente necesaria para cada momento y evitar emplear cuentas de administrador y domain admins siempre que sea posible en máquinas que puedan estar infectadas. Es conveniente que todas las contraseñas (sobre todo éstas últimas) sean seguras (incluyan complejidad)… y si no es así resetear las contraseñas de administradores incluyendo complejidad.

Enlaces de interés:

Blog de Soporte en Español

http://blogs.technet.com/plataformas/archive/2009/01/22/la-importancia-de-instalar-las-actualizaciones-de-seguridad-ms-08-067-y-el-virus-conficker.aspx

The MMPC Malware Encyclopedia entry for Worm:Win32/Conficker.B Is here:

http://www.microsoft.com/security/portal/Entry.aspx?Name=Worm:Win32/Conficker.B

The MMPC blog is also being used to communicate our current intelligence regarding these attacks:
http://blogs.technet.com/mmpc/archive/2008/12/31/just-in-time-for-new-years.aspx

The Microsoft Malware Protection Center (MMPC): http://www.microsoft.com/security/portal/default.aspx

MMPC entries for all variants of conficker: http://www.microsoft.com/security/portal/SearchResults.aspx?query=conficker

Microsoft Security Advisory 958963 – Exploit Code Published Affecting the Server Service:

http://www.microsoft.com/technet/security/advisory/958963.mspx

Microsoft Security Bulletin MS08-067 - Vulnerability in Server Service Could Allow Remote Code Execution (958644) -

http://www.microsoft.com/technet/security/bulletin/MS08-067.mspx

MSRC Blog:
http://blogs.technet.com/msrc

Como reconstruir las bases de datos de sistema master,model,msdb en Microsoft SQL Server 2005 (Rebuilm.exe)

2009-01-15T16:31:00.000-08:00

Como todos sabréis, la utilidad Rebuildm.exe que nos dio tantas alegrías y acompaño tantas noches en vela ante esos servidores de SQL Server caídos de nuestros clientes, ha sido descontinuada en los productos SQL 2005 y SQL 2008.

http://technet.microsoft.com/es-es/library/ms191431.aspx

A partir de ahora la manera de reconstruir un SQL Server que no arranca a causa de una master,model o msdb dañada o perdida, es usando parametros del SETUP.EXE.

Para reparar una instancia predeterminada en un servidor no agrupado(No Cluster)

1) Introducir el CD/DVD de Instalación
2) Ejecutar el comando:

CD or DVD Drive\setup.exe /qn INSTANCENAME=InstanceName REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=NewStrongPassword

Ejemplo:

D:\setup.exe /qn INSTANCENAME=SERVER1 REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=Passw0rdSA

Para reparar una instancia predeterminada en un servidor agrupado(En Cluster)

1) Introducir el CD/DVD de Instalación
2) Ejecutar el comando:
CD or DVD Drive\setup.exe /qn VS=VSName INSTANCENAME=InstanceName REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=StrongPassword SAPWD=NewStrongPassword SQLCOLLATION=NewSystemCollation SQLACCOUNT=domain\user SQLPASSWORD=DomainUserPassword AGTACCOUNT=domain\user AGTPASSWORD=DomainUserPassword

Ejemplo:

D:\setup.exe /qn VS=SQLVIRTUAL INSTANCENAME=SRV1 REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=Passw0rd1 SAPWD=Passw0rdSA SQLCOLLATION=Modern_Spanish_CI_AS SQLACCOUNT=mydomain\sqlservice SQLPASSWORD=SQLService1Pass AGTACCOUNT=mydomain\sqlservice AGTPASSWORD=SQLService1Pass

NOTA IMPORTANTE: Este procedimiento elimina toda la información de logins y bases de datos de usuario (Bases de datos de aplicaciones), con lo que debeis estar seguros de entender este procedimiento que debe ser el último a usar en caso de recuperación de un desastre.

http://technet.microsoft.com/es-es/library/ms144259(SQL.90).aspx

Posibles Errores:--------------------------

Error "The installation was cancelled by the user"

El el progreso de setup lanzando el comando con /qb para mostrar el progreso:

C:\Software\SQL\CD1>setup.exe /qb VS=VIRTUALSERVER INSTANCENAME=INSTANCENAME REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=Password SAPWD=Password SQLCOLLATION=Modern_Spanish_CI_AS

aparece el siguiente error en el programa de instalación bajo "SQL Server Database Services" el estatus cambia a "The installation was cancelled by the user" y el setup se cierra. El el log bootstrap aparece el error:
Se interrumpio el programa de instalación de SQL Server. para obtener más información revise el archivo de registro de la instalación en .........Summary.txt.

Solución:
-------------
Aseguraté que en el valor ADMINPASSWORD= pones la password del Administrador del dominio o con el que estás logado.

Disponible la Beta de Windows 7

2009-01-09T06:32:00.000-08:00

Ya está disponible la Beta pública de Windows 7 disponible para descarga.

Las versiones descargables de Windows 7 son para plataformas x86 y x64 solo para los idiomas Inglés, Japonés, Alemán y Árabe.

http://technet.microsoft.com/es-es/evalcenter/dd353205.aspx

Los subscriptores de TechNet y MSDN ya podían descargar esta ISO hace días desde el enlace de Suscripciones Technet.

https://technet.microsoft.com/es-es/subscriptions/securedownloads/default.aspx

Windows 7 es…
la siguiente versión del sistema operativo del cliente de Windows, sobre una base estable de Windows Vista y Windows Server 2008.
Rendimiento, confiabilidad, seguridad y compatibilidad son los principios esenciales de esta versión ya que recopilamos sus
comentarios para alcanzar nuestros objetivos de ingeniería para convertir a Windows 7 en el sistema operativo Windows de mejor
rendimiento y más estable hasta la fecha. Las innovaciones del producto se han diseñado para aumentar su capacidad
como profesional de TI para aprovisionar y administrar mejor el número creciente de equipos móviles, proteger los datos y
mejorar la productividad tanto del usuario final como personal.

Windows Sev7n en el PDC

2008-12-29T16:21:00.000-08:00

Como ya sabreis en el Professional Developer's Conference 2008(PDC) , Julie Larson-Green Corporate Vice President, Windows Experience ha presentado Windows Seven.
Os dejo parte de la presentación.

Enjoy It!!

Como restaurar un item individual de Exchange 2007 con DPM

2008-12-29T16:13:00.000-08:00

DPM 2007 SP1 -- how to do individual item restore for Exchange

Lectura Obligada para esta semana (30-12-2008)

2008-12-29T15:17:00.000-08:00

Extraido del artículo de Chris Avis , os dejo estos interesantes artículos.

Infrastructure Development, Operations & Maintenance
Microsoft System Center Mobile Device Manager 2008 SP1 Resource Kit Tools - Client Tools
Brief Description
System Center Mobile Device Manager (MDM) 2008 Service Pack 1 (SP1) Client Tools provides tools to help administrators troubleshoot connections and monitor device synchronization for Windows Mobile devices as part of an MDM system.

Overview
MDM Client Tools provides tools to help administrators troubleshoot connections and monitor device synchronization for Windows Mobile devices as part of an MDM system. The following are tools included in this download:

• MDM Connect Now Tool
• MDM VPN Diagnostics Tool
• MDM Managed Device Status Viewer

MDM Connect Now Tool enables users of Windows Mobile 6.1 managed devices to download new software updates queued since the managed device last synchronized with the MDM system. The tool initiates a session between MDM Device Management Server and a managed device. Once the tool establishes a connection, new software updates are downloaded to the managed device.
MDM VPN Diagnostics Tool helps users diagnose VPN issues between the MDM and the devices it manages. The tool allows users to see the VPN configuration and status on the managed Windows Mobile device and to diagnose any VPN-related problems. The tool also allows the managed device user to collect device logs and send them to a diagnostics team for further analysis.
MDM Managed Device Status Viewer is a troubleshooting tool that enables managed device users to browse through values of Open Mobile Alliance Device Management (OMA DM) management objects, device synchronization information, and a list of all managed programs installed on the managed device.
To learn about additional MDM tools, see System Center Mobile Device Manager Resource Kit Tools.
MDM Client Tools Release History
4/1/2008 – Initial release, Version 1.0
5/1/2008 – Minor release, Version 1.01
5/14/2008 – Updated, Version 1.1
12/15/2008 – Updated, Version 2.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=61691925-07c8-4d29-bf11-9df43aedae94&DisplayLang=en

Microsoft System Center Mobile Device Manager 2008 SP1 Resource Kit Tools - Best Practices Analyzer
Brief Description
Best Practices Analyzer Tool for System Center Mobile Device Manager (MDM) 2008 Service Pack 1 (SP1) helps you analyze a group of servers to determine if the prerequisites and best practices are met for MDM deployment.

Overview
Best Practices Analyzer (BPA) Tool for MDM 2008 SP1 helps you to analyze the prerequisites for MDM setup and deployment. Because each MDM server component has different prerequisites, the tool helps you to plan and build a successful deployment environment by assessing each server's readiness for MDM before you run MDM Setup.
In addition to analyzing each server's individual readiness, BPA Tool helps you to verify the firewall configuration that MDM requires between servers running MDM Device Management Server and servers running MDM Gateway Server.
Finally, after you deploy MDM, you can run a post-deployment scan to help make sure your installation works properly and follows MDM best practices.
To learn about additional MDM tools, see System Center Mobile Device Manager Resource Kit Tools.
MDM 2008 SP1 Best Practices Analyzer Tool Release History
4/1/2008 – Initial release, Version 1.0
5/14/2008 – Updated, Version 1.1
12/15/2008 - Updated, Version 2.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=e233f84f-9d96-4b33-80b1-fd563c4fb241&DisplayLang=en

Microsoft System Center Mobile Device Manager 2008 SP1 Resource Kit Tools - Server Tools
Brief Description
System Center Mobile Device Manager (MDM) 2008 Service Pack 1 (SP1) Server Tools provides tools to help administrators manage deployment and cleanup tasks in an MDM system.

Overview
MDM Server Tools includes a set of tools to help administrators configure, deploy, and manage System Center Mobile Device Manager (MDM) 2008 and its components.
The following are tools included in this download:

• MDM Certificate Tool
• MDM Bulk Pre-Enrollment Tool
• MDM Cleanup Tool
• MDM Device Enrollment Cleanup Tool
• MDM Application Hash Code Tool
• MDM Device Records Synchronization Tool
• MDM Additional Group Policies
• MDM Group Policy Models
• MDM Blocked Device Cleanup Tool
• MDM Security Configuration Wizard Templates
• MDM Active Directory Upgrade Helper
• MDM Set-MDMInstance Cmdlet
• MDM Gateway Bootstrapping Tool
• MDM Active Directory Configuration Tool (ADConfig) for MDM 2008

MDM Certificate Tool helps administrators to request certificates for MDM components. Administrators can also set access control lists (ACLs) on certificates, place requested certificates in a specific folder, and invalidate Global Certification Manager (GCM) certificates.
MDM Bulk Pre-Enrollment Tool enables administrators to pre-enroll groups of Windows Mobile 6.1 devices into MDM. Bulk pre-enrollment can be simpler and more efficient than pre-enrolling a large number of devices individually.
MDM Cleanup Tool enables administrators to completely uninstall MDM from servers when other removal options have not fully removed MDM components and settings.
MDM Device Enrollment Cleanup Tool is a PowerShell script–based tool that helps administrators remove from Active Directory and the MDM databases devices that are older or are no longer needed.
MDM Applications Hash Code Tool allows administrators to create an XML file for use with a Group Policy object (GPO) to allow or help prevent an application from running on managed devices.
MDM Device Records Synchronization Tool synchronizes device records maintained in the MDM AdminServices database with managed device information in Active Directory.
MDM Additional Group Policies includes ADM templates for the following Group Policy settings:

• Synchronize Sent Items folder during Exchange Active Sync
• Do not automatically run auto-run applications when a storage card is inserted
• Wireless WAN (WWAN) connection profile used for Mobile VPN
• Allow failover to the default WWAN connection configured for Mobile VPN

MDM Group Policy Models provides Group Policy settings configured to appropriately set up managed devices for three common roles. The models provided are the following: single purpose model, restricted connection model, and minimum recommended model.
MDM Blocked Device Cleanup Tool removes wiped managed devices from the list of blocked managed devices maintained by MDM Gateway Server.
MDM Security Configuration Wizard Templates includes three SCW templates that you can apply to MDM servers to help enhance security by disabling functionality that is not required for the servers.
MDM Active Directory Upgrade Helper helps you detect the Active Directory directory service objects and templates, and also generates a report with details and actions that you can perform to assist you in upgrading MDM.
MDM Set-MDMInstance Cmdlet helps administrators configure several settings - such as database server name, enrollment server name, and port number for MDM servers - that are maintained as an Active Directory service connection point (SCP).
MDM Gateway Bootstrapping Tool automates the steps to deploy required certificates and certificate chain on the server where you plan to install MDM Gateway Server.
MDM Active Directory Configuration Tool (ADConfig) for MDM 2008 is a tool that you use to configure Active Directory for MDM 2008. MDM 2008 Service Pack 1 (SP1) includes an updated version that is not backwards compatible with MDM 2008.
To learn about additional MDM tools, see System Center Mobile Device Manager Resource Kit Tools.
MDM Server Tools Release History
4/1/2008 – Initial release, Version 1.0
5/1/2008 – Minor release, Version 1.01
5/14/2008 – Updated, Version 1.1
12/15/2008 – Updated, Version 2.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=0433b453-15a5-48ae-a343-6a1053f46251&DisplayLang=en

System Center Mobile Device Manager 2008 SP1 Resource Kit Tools - Reporting Services

Brief Description
System Center Mobile Device Manager (MDM) 2008 Server Pack 1 (SP1) Reporting Services provides a reporting and data access service across all areas of an MDM system.

Overview
MDM Reporting Services provides a reporting and data access service across all areas of an MDM system. MDM Reporting Services is based on and integrated with SQL Server Reporting Services 2005.
To learn more about MDM, see System Center Mobile Device Manager TechCenter.
MDM Server Tools Release History
5/14/2008 – Initial release, Version 1.1
12/15/2008 – Updated, Version 2.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=f72c0546-1b10-4636-96a5-a2455b1f77b3&DisplayLang=en

System Center Mobile Device Manager 2008 SP1 MSDN

Brief Description
System Center Mobile Device Manager (MDM) 2008 SP1 MSDN is a system that enables Windows Mobile devices to become managed and authenticated members of the IT infrastructure of an organization.

Overview
MDM is a Microsoft technology that helps Windows Mobile 6.1 devices work within the IT infrastructure of a company as trusted and managed members of the enterprise.
MDM consists of the following four main system components: MDM Device Management Server, MDM Enrollment Server, MDM Gateway Server, and Microsoft SQL Server 2005 databases. The SQL Server databases must be installed separately.
These components work with key IT services to give managed devices access to selected business data. The primary IT services that work with MDM are the following: Active Directory Domain Service, MDM software distribution, certificate services, and line-of-business application servers, such as Microsoft Exchange.
To learn more about MDM, see System Center Mobile Device Manager TechCenter.
(Related Resources - _http://technet.microsoft.com/en-us/scmdm/default.aspx)

http://www.microsoft.com/downloads/details.aspx?FamilyID=813b041e-885e-4f5e-a653-f70d480e43a9&DisplayLang=en

System Center Mobile Device Manager 2008 SP1 Evaluation Edition

Brief Description
System Center Mobile Device Manager (MDM) 2008 SP1 Evaluation Edition is a system that enables Windows Mobile devices to become managed and authenticated members of the IT infrastructure of an organization.

Overview
MDM is a Microsoft technology that helps Windows Mobile 6.1 devices work within the IT infrastructure of a company as trusted and managed members of the enterprise.
MDM consists of the following four main system components: MDM Device Management Server, MDM Enrollment Server, MDM Gateway Server, and Microsoft SQL Server 2005 databases. The SQL Server databases must be installed separately.
These components work with key IT services to give managed devices access to selected business data. The primary IT services that work with MDM are the following: Active Directory Domain Service, MDM software distribution, certificate services, and line-of-business application servers, such as Microsoft Exchange.
To learn more about MDM, see System Center Mobile Device Manager TechCenter.
(Related Resources - _http://technet.microsoft.com/en-us/scmdm/default.aspx)

http://www.microsoft.com/downloads/details.aspx?FamilyID=30a51b90-c00a-4b42-a1b7-1405560b8289&DisplayLang=en

Microsoft System Center Mobile Device Manager 2008 SP1 Resource Kit - Password Reset Client

Brief Description
System Center Mobile Device Manager (MDM) Password Reset Client provides a .cab file that you install on Windows Mobile 6.1 devices enrolled in MDM so that users can use the password reset feature in MDM.

Overview
MDM Password Reset Client provides a .cab file that you install on Windows Mobile 6.1 devices enrolled in MDM so that users can use the password reset feature in MDM. Password reset in MDM 2008 Service Pack 1 (SP1) enables a user who has forgotten his or her Windows Mobile device password to reset it by using MDM.
Password reset is supported on Windows Mobile 6.1 devices, starting with version 6.1.4. To use the feature, you must install the .cab file on the user’s Windows Mobile device as well as enable the feature in MDM by using Group Policy.
To reset the device password, the user chooses the password reset option, resets the device password, and then enters a one-time recovery password on the device to complete the process. The recovery password is stored on MDM servers and retrieved by the user when she or he has forgotten the device password.
To learn about additional MDM tools, see System Center Mobile Device Manager Resource Kit Tools.
MDM Password Reset Client Application Release History
12/15/2008 – Initial release, Version 1.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=53799354-e949-47e6-8f2d-8395fc213d60&DisplayLang=en

System Center Mobile Device Manager 2008 Service Pack 1 Management Pack for Operations Manager 2007

Brief Description
This Microsoft System Center Mobile Device Manager Service Pack 1 (MDM SP1) 2008 Management Pack provides proactive monitoring of your Microsoft System Center Mobile Device Manager 2008 SP1 environment.

Overview
Microsoft System Center Mobile Device Manager Service Pack 1 2008 Management Pack for Operations Manager 2007 provides proactive monitoring of your Microsoft System Center Mobile Device Manager 2008 SP1 environment. This management pack includes:

Detection and monitoring of all MDM SP1 servers and dependent services
The alert-driven state
Performance and backlog monitoring and configuration
Before you install the MDM SP1 management pack, read the MDM Management Pack Guide document, which includes instructions for properly deploying and configuring the management pack.
Feature Summary
The System Center Mobile Device Manager 2008 SP1 (MDM SP1) Management Pack for Operations Manager 2007 provides capabilities for MDM SP1 monitoring, including the following:

Collection of events from MDM Device Management Server, MDM Enrollment Server, MDM Gateway Server, and MDM Self Service Portal.
Health state monitoring and alerting for MDM service errors requiring administrative intervention.
Collection of MDM performance counters from MDM Device Management Server, MDM Enrollment Server, MDM Gateway Server, and MDM Self Service Portal.
Events indicating service outages.
Alerts indicating configuration and data source connectivity issues.
Verification that all dependent services are functioning properly.
Release History

12/15/2008 - Version 1.0.2430.0, Subsequent release of the Management Pack for MDM SP1
6/30/2008 - Version 1.0.2300.0, Original release of the English version of the Management Pack
http://www.microsoft.com/downloads/details.aspx?FamilyID=10ef0cd1-345d-48a0-934d-f1a42ebd0f98&DisplayLang=en

TS Session Broker Load Balancing Step-By-Step Guide

Brief Description
Step-by-step procedures for installing and configuring Terminal Services Session Broker (TS Session Broker) and TS Session Broker Load Balancing.

Overview
Terminal Services Session Broker (TS Session Broker) is a role service in Windows Server 2008 that enables you to load balance sessions in a terminal server farm, and allows a user to reconnect to an existing session in a load-balanced terminal server farm. This step-by-step guide describes how to configure the new TS Session Broker Load Balancing feature.

http://www.microsoft.com/downloads/details.aspx?FamilyID=1b3551ba-aef4-4772-90d4-dde08f62c6c3&DisplayLang=en

DNS in Small Networks Step-by-Step Guide
Brief Description
This article explains how to deploy the DNS Server role in a network containing a single Active Directory domain controller.

Overview
This guide helps you implement Domain Name System (DNS) on the Windows Server 2008 operating system in a small network. Windows Server 2008 uses DNS to translate computer names to network addresses. An Active Directory domain controller can act as a DNS server that registers the names and addresses of computers in the domain and then provides the network address of a member computer when the domain controller receives a query with the name of the computer. This guide explains how to set up DNS on a simple network that consists of a single domain.

http://www.microsoft.com/downloads/details.aspx?FamilyID=ec1fd9db-dbc4-4e80-8e95-6f63920fe805&DisplayLang=en

Windows Firewall with Advanced Security Step-by-Step Guide - Deploying Firewall Policies

Brief Description
This step-by-step guide illustrates how to deploy Active Directory® Group Policy objects (GPOs) to configure Windows Firewall with Advanced Security in Windows Vista® and Windows Server® 2008.

Overview
This step-by-step guide illustrates how to deploy Active Directory® Group Policy objects (GPOs) to configure Windows Firewall with Advanced Security in Windows Vista® and Windows Server® 2008. Although you can configure a single server locally by using Group Policy Management tools directly on the server, that method is not consistent or efficient when you have many computers to configure. When you have multiple computers to manage, create and edit GPOs, and then apply those GPOs to the computers in your organization.

http://www.microsoft.com/downloads/details.aspx?FamilyID=0b937897-ce39-498e-bb37-751c00f197d9&DisplayLang=en

TS Gateway Step-By-Step Guide

Brief Description
Step-by-step procedures for installing and configuring Terminal Services Gateway (TS Gateway)

Overview
Terminal Services Gateway (TS Gateway) is a new role service available to users of Windows Server 2008. TS Gateway enables authorized remote users to connect to resources on an internal corporate or private network, from any Internet-connected device that can run the Remote Desktop Connection (RDC) client. The network resources can be terminal servers running RemoteApp™ programs, terminal servers, or computers with Remote Desktop enabled. TS Gateway encapsulates Remote Desktop Protocol (RDP) within RPC, within HTTP over a Secure Sockets Layer (SSL) connection. In this way, TS Gateway establishes a secure, encrypted remote connection between remote users on the Internet and the internal network resources on which their productivity applications run.

http://www.microsoft.com/downloads/details.aspx?FamilyID=dda11460-9d11-4090-aff8-e81cbfe76691&DisplayLang=en

TS RemoteApp Step-by-Step Guide
Brief Description
Step-by-step guide to using TS RemoteApp in Windows Server 2008.

Overview
Step by-step guide to using Terminal Services RemoteApp (TS RemoteApp) in Windows Server 2008. You can use several different methods to deploy RemoteApp programs, such as Terminal Services Web Access (TS Web Access). With TS Web Access, you can provide access to RemoteApp programs through a Web page over the Internet or over an intranet. TS Web Access is also included in Windows Server 2008.

http://www.microsoft.com/downloads/details.aspx?FamilyID=96596fd3-dbdd-4809-b64a-80fd044f984a&DisplayLang=en

AD RMS Deployment in a Multiple Forest Environment Step-by-Step Guide
Brief Description
Step-by-step procedures for deploying Active Directory Rights Management Services with Office SharePoint Server 2007.

Overview
This step-by-step guide walks you through the process of deploying Active Directory Rights Management Services (AD RMS) across multiple Active Directory forests.

http://www.microsoft.com/downloads/details.aspx?FamilyID=795e5984-48a8-40e3-a553-0b975d340ab0&DisplayLang=en

Windows Server DNS 2000/2003/2008 Management Pack for Operations Manager 2007
Brief Description
This management Pack monitors DNS 2000/2003/2008 infrastructure health, availability and performance.

Overview
The Windows Server DNS 2000/2003/2008 Management Pack includes monitors, rules, views, tasks and knowledge for the monitoring of your DNS infrastructure. By not only proactively monitoring servers but also DNS zones, DNS global zones and DNS domains, small problems can be detected and corrected before outages occur.
Note: This package includes library MP, 2000 and 2003 MPs, and DNS 2008 MP. DNS 2008 MP can only be installed on System Center OpsMgr 2007 SP1. Others can be installed on either OpsMgr 2007 RTM or OpsMgr 2007 SP1.
Feature Bullet Summary:

DNS 2003/2008
Native Systems Center Operations Manager 2007 MP
DNS Global Zone Support
Windows 2008 DNS Server Support
Updated Health Logic
New context sensitive tasks
Updated Knowledge Base Information
Coexists with the included DNS 2000 MP
DNS 2000
Converted Systems Center Operations Manager 2007 MP
Coexists with new native DNS 2003 / 2008 MP
Management Pack Release History:

10/23/2007 - Original release of DNS 2000/2003 MP for OpsMgr 2007, version 6.0.5000.0
8/14/2008 - Updated version 6.0.6278.27. Added support for Windows DNS 2008.
12/19/2008 - Updated vesion 6.0.6480.0. Fixed high CPU utilizations and DNS servers disappeared from the discovery.
http://www.microsoft.com/downloads/details.aspx?FamilyID=633b718f-5fe8-47d5-a395-8203f8ec354f&DisplayLang=en

Windows Server 2003/2008 Group Policy Management Pack for Operations Manager 2007
Brief Description
Windows Server 2003/2008 Group Policy Management Pack for Operations Manager 2007 monitors the health, availability, and performance of the Microsoft group policy client component of Microsoft Windows Server 2008.

Overview
The Windows Server 2008 Group Policy Management Pack includes monitors, rules, views, and knowledge for the monitoring of the application of group policy settings on Windows Server 2008. It provides a knowledge base of useful information to help administrators resolve an issue when group policy fails to process.
The Windows Server 2003 Group Policy Management Pack for Microsoft Operations Manager 2007 includes monitors, rules, views, and knowledge for the monitoring of the proper application of Group Policy included in Windows Server 2003.
Feature Summary
Windows Server 2008 Group Policy MP

Native Operations Manager 2007 management pack
Windows Server 2008 Support
Updated Health Logic
Updated Knowledge Base Information
Dashboard Views
Windows Server 2003 Group Policy MP
The Group Policy Management Pack for Operations Manager 2007 monitors Group Policy infrastructure and in-scope client side extensions. Specifically, it provides Group Policy health monitoring for:

Group Policy core infrastructure/registry client-side extension
Scripts client-side extension
Software installation client-side extension
Security client-side extension
Folder redirection client-side extension
Disk quota
Provides a knowledge base of useful information to help administrators resolve an issue when Group Policy fails to process.
Release History

12/19/2008 - Combined Windows Server 2008 and 2003 Group Policy MP, version 6.0.6278.22
7/28/2008 - Initial release of Windows Server 2008 Group Policy MP, version 6.0.6278.22
7/28/2008 - Updated release of Windows Server 2003 Group Policy MP, version 6.0.6278.22
6/1/2007 - Initial Release of Windows Server 2003 Group Policy MP, version 6.0.5000.0
http://www.microsoft.com/downloads/details.aspx?FamilyID=12a29de3-7147-4488-8b1d-5825892f2b05&DisplayLang=en

Microsoft Exchange Server 2003 Calendar Connector for Lotus Notes
Brief Description
The Calendar Connector for Lotus Notes is a tool designed for organizations that need to coexist during a migration from Lotus Domino to Microsoft Exchange Server 2003.

Overview
The Microsoft Exchange Server 2003 Calendar Connector for Lotus Notes supports the sharing of calendar free/busy schedules between Lotus Domino R5 and R6 and Exchange Server 2003. This tool replaces the Calendar Connector that ships with Exchange Server 2003 (including SP2), and is designed to be used with the Microsoft Exchange Server 2003 Connector.

http://www.microsoft.com/downloads/details.aspx?FamilyID=c14932a1-55f4-4256-af7e-617639d46024&DisplayLang=en

Microsoft Exchange Server 2003 Migration Wizard for Lotus Notes
Brief Description
The Migration Wizard for Lotus Notes is a tool designed for organizations that are migrating from Lotus Notes/Domino to Microsoft Exchange Server 2003.

Overview
The Microsoft Exchange Server 2003 Migration Wizard for Lotus Notes supports the migration of Lotus Domino R5 and R6 mailboxes and associated Domino directory information to Microsoft Exchange Server 2003 and Windows Server 2003 Active Directory. This tool replaces the Migration Wizard that ships with Exchange Server 2003 (including SP2), and includes improved retention of contents and Unicode characters during the migration from Domino to Exchange Server 2003.

http://www.microsoft.com/downloads/details.aspx?FamilyID=c105b3e4-3beb-4f1e-8f52-e345af6c3e50&DisplayLang=en

System Center Data Protection Manager 2007 Service Pack 1 (32bit)
Brief Description
Service Pack 1 for Data Protection Manager 2007 delivers additional functionality across every workload currently protected by DPM, plus new capabilities to broaden customers’ ability to protect Windows environments with a Microsoft backup solution.

Overview
DPM 2007 SP1 maintains DPM 2007 as the new standard for Windows backup and recovery by introducing new workload capabilities, performance enhancements, features and options.
New workload capabilities include host-level and guest-level protection for Windows Server 2008 Hyper-V and Microsoft Hyper-V Server. DPM SP1 also enables protection of SQL Server 2008, Windows SharePoint Services and SQL Server mirrored databases, Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 indexes, and Exchange Standby Cluster Replication (SCR). DPM SP1 also enhances Windows SharePoint Services catalog backup performance.
DPM 2007 with SP1 can protect data across multiple Active Directory® forests (with two-way trust) as well as Hyper-V and file data stored locally on the DPM server. DPM SP1 also bundles features introduced in previous updates such as Windows Server 2008 System State and SQL Server 2008 protection, tape library sharing, and improved tape utilization.
Installing DPM SP1 adds functionality relevant to the new Data Protection Client Management License offering. This offering provides existing DPM Client protection at a preferred price.
With DPM SP1, DPM 2007 provides an integrated approach for backing up DPM data to the cloud. This new option is delivered in conjunction with a solution provider that provides a backup and recovery service in the cloud specifically designed to support DPM. To enable backup to the cloud, in DPM Administrator Console, go to “Manage online protection” in the Protection task area.
For release details for DPM SP1, please refer to Knowledge Base article KB959605: http://go.microsoft.com/fwlink/?LinkId=137147.
DPM SP1 Release Notes can be found at http://go.microsoft.com/fwlink/?LinkID=135756.
For detailed information on features available in SP1, please visit http://go.microsoft.com/fwlink/?LinkId=132612.
Feature Bullet Summary:
New Workload Capabilities:

Protection of Hyper-V™ virtualization platforms, including both Windows Server 2008 with Hyper-V and the Microsoft Hyper-V Server 2008. Note: For more information about the list of required updates to protect a Hyper-V Server, visit the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=132612.
SQL Server 2008 protection and seamless mirrored DB protection for SQL Server 2005 and 2008 as well as capability for parallel database backups within a single instance of SQL Server and enabling data migration from SQL Server 2005 to SQL Server 2008.
Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 index protection, catalog optimization, and support for mirrored content databases.
Exchange Server 2007 Standby Cluster Replication (SCR) protection.
Other Capabilities Introduced:

Local data source protection enables 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 with two-way trust enables flexibility in DPM deployments across multiple Active Directory® forests.
Included Capabilities from the DPM 2007 Feature Pack (KB949779):

Protection of virtual machines on clustered Virtual Server 2005 R2 SP1 hosts
Protection of tape libraries shared between multiple DPM servers.
Improved utilization of tape capacity by collocating data from multiple protection groups with similar retention range.
Windows Server 2008 System State protection.
SQL Server 2008 protection.
New Options Available:

Installing DPM 2007 SP1 adds functionality relevant to the new Data Protection Client Management License offering.
Cloud (or Internet) based backup and recovery: DPM 2007 SP1 now provides an integrated approach for backing up DPM data to the cloud.
Release Details:

For release details please refer to Knowledge Base article KB959605: http://go.microsoft.com/fwlink/?LinkId=137147.
Release Notes can be found here: http://go.microsoft.com/fwlink/?LinkID=135756 .
For new features available in DPM SP1, please visit http://go.microsoft.com/fwlink/?LinkId=132612.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cef22c-f027-4c0b-8fad-b081485c3efe&DisplayLang=en

System Center Data Protection Manager 2007 Service Pack 1 (64bit)
Brief Description
Service Pack 1 for Data Protection Manager 2007 delivers additional functionality across every workload currently protected by DPM, plus new capabilities to broaden customers’ ability to protect Windows environments with a Microsoft backup solution.

Overview
DPM 2007 SP1 maintains DPM 2007 as the new standard for Windows backup and recovery by introducing new workload capabilities, performance enhancements, features and options.
New workload capabilities include host-level and guest-level protection for Windows Server 2008 Hyper-V and Microsoft Hyper-V Server. DPM SP1 also enables protection of SQL Server 2008, Windows SharePoint Services and SQL Server mirrored databases, Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 indexes, and Exchange Standby Cluster Replication (SCR). DPM SP1 also enhances Windows SharePoint Services catalog backup performance.
DPM 2007 with SP1 can protect data across multiple Active Directory® forests (with two-way trust) as well as Hyper-V and file data stored locally on the DPM server. DPM SP1 also bundles features introduced in previous updates such as Windows Server 2008 System State and SQL Server 2008 protection, tape library sharing, and improved tape utilization.
Installing DPM SP1 adds functionality relevant to the new Data Protection Client Management License offering. This offering provides existing DPM Client protection at a preferred price.
With DPM SP1, DPM 2007 provides an integrated approach for backing up DPM data to the cloud. This new option is delivered in conjunction with a solution provider that provides a backup and recovery service in the cloud specifically designed to support DPM. To enable backup to the cloud, in DPM Administrator Console, go to “Manage online protection” in the Protection task area.
For release details for DPM SP1, please refer to Knowledge Base article KB959605: http://go.microsoft.com/fwlink/?LinkId=137147.
DPM SP1 Release Notes can be found at http://go.microsoft.com/fwlink/?LinkID=135756.
For detailed information on features available in SP1, please visit http://go.microsoft.com/fwlink/?LinkId=132612.
Feature Bullet Summary:
New Workload Capabilities:

Protection of Hyper-V™ virtualization platforms, including both Windows Server 2008 with Hyper-V and the Microsoft Hyper-V Server 2008. Note: For more information about the list of required updates to protect a Hyper-V Server, visit the following Microsoft Web site: http://go.microsoft.com/fwlink/?LinkId=132612.
SQL Server 2008 protection and seamless mirrored DB protection for SQL Server 2005 and 2008 as well as capability for parallel database backups within a single instance of SQL Server and enabling data migration from SQL Server 2005 to SQL Server 2008.
Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 index protection, catalog optimization, and support for mirrored content databases.
Exchange Server 2007 Standby Cluster Replication (SCR) protection.
Other Capabilities Introduced:

Local data source protection enables 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 with two-way trust enables flexibility in DPM deployments across multiple Active Directory® forests.
Included Capabilities from the DPM 2007 Feature Pack (KB949779):

Protection of virtual machines on clustered Virtual Server 2005 R2 SP1 hosts
Protection of tape libraries shared between multiple DPM servers.
Improved utilization of tape capacity by collocating data from multiple protection groups with similar retention range.
Windows Server 2008 System State protection.
SQL Server 2008 protection.
New Options Available:

Installing DPM 2007 SP1 adds functionality relevant to the new Data Protection Client Management License offering.
Cloud (or Internet) based backup and recovery: DPM 2007 SP1 now provides an integrated approach for backing up DPM data to the cloud.
Release Details:

For release details please refer to Knowledge Base article KB959605: http://go.microsoft.com/fwlink/?LinkId=137147.
Release Notes can be found here: http://go.microsoft.com/fwlink/?LinkID=135756 .
For new features available in DPM SP1, please visit http://go.microsoft.com/fwlink/?LinkId=132612.
http://www.microsoft.com/downloads/details.aspx?FamilyID=8ae5edac-4de8-44e0-a6f9-8afbb3e23585&DisplayLang=en

System Center Essentials 2007 Operations Guide
Brief Description
Best practices for using System Center Essentials 2007

Overview
This guide discusses best practices for everyday use of System Center Essentials 2007. The guide includes the following:
• Getting Ready to Operate Essentials 2007
• Managing Computers
• Monitoring Network Devices
• Deploying Software and Updates

http://www.microsoft.com/downloads/details.aspx?FamilyID=dbf51282-1784-4b9f-abd1-e2b5cb12f1a8&DisplayLang=en

Systems Center Operations Manager 2007 SP1 Documentation
Brief Description
This download contains documentation for System Center Operations Manager 2007 SP1.

Overview
This download contains the following documentation for System Center Operations Manager 2007:

Operations Manager 2007 Operations Guide:
This guide is a comprehensive resource that can be used to understand and use your Operations Manager 2007 implementation to your best advantage. It teaches the Operations Manager administrator what to do after successfully deploying Operations Manager for the first time as well as serving as a reference for ongoing maintenance.
Operations Manager 2007 Deployment Guide:
This guide steps you through the deployment process for System Center Operations Manager 2007.
The Operations Manager 2007 Design Guide:
This guide takes the reader through the necessary steps to develop a complete architectural plan for their OpsMgr2007 implementation.
Operations Manager 2007 Migration Guide:
This guide is intended to help you understand the migration process from Microsoft Operations Manager 2005 (MOM 2005) to Operations Manager 2007 and the tools that are used in the process.
Operations Manager 2007 Report Authoring Guide:
This guide provides an overview of the Operations Manager reporting feature, including procedures for generating pre-populated reports and authoring custom reports. There is also reference information for users looking to create custom reports.
http://www.microsoft.com/downloads/details.aspx?FamilyID=d826b836-59e5-4628-939e-2b852ed79859&DisplayLang=en

Microsoft SQL Server 2005 Express Edition Service Pack 3
Brief Description
Microsoft SQL Server 2005 Express Edition is a free, easy-to-use, lightweight version of SQL Server 2005. It is fast and easy to learn, allowing you to quickly develop and deploy dynamic data-driven applications.

Overview
Microsoft SQL Server 2005 Express Edition (SQL Server Express) is a free, easy-to-use, lightweight version of SQL Server 2005. It is fast and easy to learn, allowing you to quickly develop and deploy dynamic data-driven applications. SQL Server Express provides powerful and reliable data management tools along with rich features, data protection, and fast performance. It is ideal for embedded application clients, light Web applications, and local data stores. Designed for easy deployment and rapid prototyping, SQL Server Express is available at no cost, and you are free to redistribute it with applications. If you need more advanced database features, you can upgrade SQL Server Express seamlessly to more sophisticated editions of SQL Server.
Free to download, free to deploy, and free to redistribute as an embedded part of an application, SQL Server Express is the fast and easy way to develop data-driven applications.
For more information about SQL Server Express, including other editions and downloadable components now available, see the SQL Server Express page on MSDN.
For a list of new features and improvements that are included in SQL Server 2005 SP3, review the What's New document.

http://www.microsoft.com/downloads/details.aspx?FamilyID=3181842a-4090-4431-acdd-9a1c832e65a6&DisplayLang=en

Microsoft SQL Server 2005 Express Edition Toolkit Service Pack 3
Brief Description
Microsoft SQL Server 2005 Express Edition Toolkit provides additional tools and resources for SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services.

Overview
Microsoft SQL Server 2005 Express Edition Toolkit (SQL Server Express Toolkit) provides additional tools and resources for SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services. The SQL Server Express Toolkit contains SQL Server 2005 Management Studio Express, a graphical management tool, and Business Intelligence Development Studio, a creation and editing environment for reports using SQL Server Reporting Services.
The SQL Server Express Toolkit contains these two components:

SQL Server 2005 Management Studio Express (SSMSE) – Easily manage SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services database instances with this free, easy-to-use graphical management tool.
Business Intelligence Development Studio (BIDS) – Create and edit reports for SQL Server 2005 Reporting Services (SSRS). BIDS provides the ability to create and edit Reporting Services projects that are reporting on local relational data in local SQL Server Express databases.
For more information about SQL Server Express Toolkit, including other editions and downloadable components now available, see the SQL Server Express page on MSDN.
For a list of new features and improvements that are included in SQL Server 2005 SP3, review the What's New document.

http://www.microsoft.com/downloads/details.aspx?FamilyID=d434dc36-a24d-44ee-937e-553c382557e3&DisplayLang=en

Microsoft SQL Server Management Studio Express Service Pack 3
Brief Description
Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical management tool for managing SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services.

Overview
Microsoft SQL Server Management Studio Express (SSMSE) is a free, easy-to-use graphical management tool for managing SQL Server 2005 Express Edition and SQL Server 2005 Express Edition with Advanced Services. SSMSE can also manage instances of the SQL Server Database Engine created by any edition of SQL Server 2005.
Note: SSMSE cannot manage SQL Server Analysis Services, Integration Services, Notification Services, Reporting Services, SQL Server Agent, or SQL Server 2005 Mobile Edition.
For more information about SQL Server Express, including other editions and downloadable components now available, see the SQL Server Express page on MSDN.
For a list of new features and improvements that are included in SQL Server 2005 SP3, review the What's New document.

http://www.microsoft.com/downloads/details.aspx?FamilyID=5d76230d-580d-4874-8c7d-93491a29db15&DisplayLang=en

Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 3
Brief Description
Microsoft SQL Server 2005 Express Edition with Advanced Services is a free, easy-to use version of SQL Server Express that includes more features and makes it easier than ever to start developing powerful data-driven applications for web or local desktop development.

Overview
Microsoft SQL Server 2005 Express Edition with Advanced Services (SQL Server Express) is a free, easy-to-use version of SQL Server Express that includes a graphical management tool and powerful features for reporting and advanced text-based searches. SQL Server Express provides powerful and reliable data management tools and rich features, data protection, and fast performance. It is ideal for embedded application clients, light Web applications, and local data stores.
SQL Server Express with Advanced Services has all of the features in SQL Server 2005 Express Edition, plus you can:

Easily manage and administer SQL Server Express with an easy-to-use graphical management tool -- SQL Server 2005 Management Studio Express (SSMSE).
Issue full-text queries against plain character-based data in SQL Server tables. Full-text queries can include words and phrases, or multiple forms of a word or phrase.
Run SQL Server Reporting Services reports on local relational data.
Free to download, free to deploy, and free to redistribute as an embedded part of an application, SQL Server Express with Advanced Services is the fast and easy way to develop and manage data-driven applications with powerful built-in reporting and full-text search functionality.
For more information about SQL Server Express, including other editions and downloadable components now available, see the SQL Server Express page on MSDN.
For a list of new features and improvements that are included in SQL Server 2005 SP3, review the What's New document.

http://www.microsoft.com/downloads/details.aspx?FamilyID=b448b0d0-ee79-48f6-b50a-7c4f028c2e3d&DisplayLang=en

Microsoft SQL Server Protocol Documentation
Brief Description
The Microsoft SQL Server protocol documentation provides technical specifications for Microsoft proprietary protocols that are implemented and used in Microsoft SQL Server 2008.

Overview
The Microsoft SQL Server protocol documentation provides detailed technical specifications for Microsoft proprietary protocols (including extensions to industry-standard or other published protocols) that are implemented and used in Microsoft SQL Server to interoperate or communicate with Microsoft products.
The documentation includes a set of companion overview and reference documents that supplement the technical specifications with conceptual background, overviews of inter-protocol relationships and interactions, and technical reference information.

http://www.microsoft.com/downloads/details.aspx?FamilyID=91ef5106-944a-41e1-b3a0-5bd3f2356f32&DisplayLang=en

Feature Pack for Microsoft SQL Server 2005 - December 2008
Brief Description
Download the December 2008 Feature Pack for Microsoft SQL Server 2005, a collection of standalone install packages that provide additional value for SQL Server 2005.

Overview
The Feature Pack is a collection of standalone install packages that provide additional value for SQL Server 2005. It includes:

Latest versions of redistributable components for SQL Server 2005
Latest versions of add-on providers for SQL Server 2005
Latest versions of backward compatibility components for SQL Server 2005
For a list of new features and improvements that are included in SQL Server 2005 SP3, review the What's New document.

http://www.microsoft.com/downloads/details.aspx?FamilyID=536fd7d5-013f-49bc-9fc7-77dede4bb075&DisplayLang=en

Microsoft SQL Server 2005 Service Pack 3
Brief Description
Download Service Pack 3 for Microsoft SQL Server 2005.

Overview
Service Pack 3 for Microsoft SQL Server 2005 is now available. SQL Server 2005 service packs are cumulative, and this service pack upgrades all service levels of SQL Server 2005 to SP3. You can use these packages to upgrade any of the following SQL Server 2005 editions:

Enterprise
Enterprise Evaluation
Developer
Standard
Workgroup
Note: To upgrade SQL Server 2005 Express Edition, obtain the SP3 version of Express Edition or Express Edition with Advanced Services.
For a list of new features and improvements that are included in SQL Server 2005 SP3, review the What's New document.

http://www.microsoft.com/downloads/details.aspx?FamilyID=ae7387c3-348c-4faa-8ae5-949fdfbe59c4&DisplayLang=en

SQL Server 2005 Books Online (December 2008)
Brief Description
Download an updated version of the documentation and tutorials for Microsoft SQL Server 2005. See the "Additional Information" section for an update on SQL Server Express Books Online.

Overview
Download an updated version of Books Online for Microsoft SQL Server 2005. Books Online is the primary documentation for SQL Server 2005. The December 2008 update to Books Online contains new material and fixes to documentation problems reported by customers after SQL Server 2005 was released. Refer to "New and Updated Books Online Topics" for a list of topics that are new or updated in this version. Topics with significant updates have a Change History table at the bottom of the topic that summarizes the changes. Beginning with the December 2008 update, SQL Server 2005 Books Online includes documentation updates for the SQL Server 2005 Service Pack 3 (SP3) release.
Books Online includes the following types of information:

Setup and upgrade instructions.
Information about new features and backward compatibility.
Conceptual descriptions of the technologies and features in SQL Server 2005.
Procedural topics describing how to use the various features in SQL Server 2005.
Tutorials that guide you through common tasks.
Reference documentation for the graphical tools, command prompt utilities, programming languages, and application programming interfaces (APIs) that are supported by SQL Server 2005.
Descriptions of the sample databases and applications included with SQL Server 2005.
For a list of updated topics, see "New and Updated Books Online Topics (17 November 2008)."

http://www.microsoft.com/downloads/details.aspx?FamilyID=be6a2c5d-00df-4220-b133-29c1e0b6585f&DisplayLang=en
SAP Documents
Brief Description
Technical documentation for SAP implementation on Microsoft Windows platform.

Overview
Technical documentation for SAP implementation on Microsoft Windows platform.

http://www.microsoft.com/downloads/details.aspx?FamilyID=63d54a72-bc62-43cf-8eae-444935e08b40&DisplayLang=en

AD RMS with AD FS Identity Federation Step-by-Step Guide
Brief Description
Step-by-step procedures for using identity federation services with Active Directory Rights Management Services (AD RMS). This guide walks you through the Active Directory Federation Services integration with AD RMS.

Overview

This step-by-step guide assists you in using Active Directory Rights Management Services (AD RMS) with Active Directory® Federation Services (AD FS) in a test environment. Specifically, this guide looks at how to implement AD RMS if you have also deployed AD FS in your organization and have established a trust relationship with another organization that has not deployed AD RMS. Using the information in this guide, you can extend the basic AD RMS deployment to use AD FS credentials to establish trusted user accounts. This will enable you to share access to rights-protected content with another organization without having to establish a separate trust.

http://www.microsoft.com/downloads/details.aspx?FamilyID=1ce54040-cb96-4f37-a5b1-adf5c1e21b2b&DisplayLang=en

AD RMS Deployment in an Extranet Step-by-Step Guide
Brief Description
Step-by-step procedures for installing and configuring Active Directory Rights Management Services in an Extranet.

Overview
This step-by-step guide walks you through the process of configuring Active Directory Rights Management Services (AD RMS) in a test environment that includes an extranet. An extranet is an extension of your organization's network to an external source.

http://www.microsoft.com/downloads/details.aspx?FamilyID=262768eb-81d8-4c8f-bf2a-66a8d2dc4665&DisplayLang=en

AD RMS Step-by-Step Guide
Brief Description
Step-by-step procedures for installing and configuring Active Directory Rights Management Services, including installation by using Server Manager.

Overview
This step-by-step walks you through the process of setting up a working Active Directory Rights Management Services (AD RMS) infrastructure in a test environment. During this process you create an Active Directory® domain, install a database server, install the AD RMS server role, configure the AD RMS cluster, and configure the AD RMS-enabled client computer.

http://www.microsoft.com/downloads/details.aspx?FamilyID=a0ea7cd0-7de7-43a5-b1f9-b4cc679cecb3&DisplayLang=en

Microsoft Office Outlook Connector 12.1
Brief Description
With Microsoft Office Outlook Connector, you can use Microsoft Office Outlook 2003 or Microsoft Office Outlook 2007 to access and manage your Microsoft Windows Live Hotmail or Microsoft Office Live Mail accounts, including e-mail messages, contacts and calendars for free!

Overview
With Microsoft Office Outlook Connector, you can use Microsoft Office Outlook 2003 or Microsoft Office Outlook 2007 to access and manage your Microsoft Windows Live Hotmail or Microsoft Office Live Mail accounts, including e-mail messages, contacts and calendars for free!
Outlook Connector enables you to use your Live Hotmail accounts within Outlook:

Read and send your Office Live Mail/Windows Live Hotmail e-mail messages.
Manage your contacts in Windows Live Hotmail.
Use advanced options for blocking junk e-mail messages.
Manage multiple e-mail accounts in one place.
Manage, and synchronize multiple calendars, including shared calendars to Windows Live Calendar from Outlook.
Note to Premium Subscribers: If you are currently using MSN Calendar service, the Outlook Connector 12.1 will automatically migrate your calendar to the new Windows Live Calendar service. Once upgraded to Windows Live Calendar, you will be able to synchronize multiple calendars, including shared calendars to Outlook! However you will no longer be able to access MSN Calendar through Microsoft Office Outlook.
In order to make sure that all of your calendar items on the MSN Calendar service are correctly migrated to the Windows Live Calendar, you should follow these steps:

With Outlook Connector 12.0 installed, synchronize your calendar in Microsoft Office Outlook with the MSN Calendar service one last time.
After synchronization is complete, do not create new items on the MSN Calendar site. If you do, you will have to synchronize again using Outlook Connector 12.0 before migrating to Outlook Connector 12.1.
Install Outlook Connector 12.1.
Start Outlook. At this point, the Outlook Connector 12.1 will upload all of your appointments and meetings to your new Windows Live Calendar.
http://www.microsoft.com/downloads/details.aspx?FamilyID=9a2279b1-df0a-46e1-aa93-7d4870871ecf&DisplayLang=en

Cursos Elearning Gratuitos de Microsoft (Diciembre 2008)

2008-12-11T03:25:00.000-08:00

Título: Clinic 5935: Introducing Hyper-V in Windows Server 2008
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 2 Horas
Idioma: Inglés

Descripción:
This 2-hour online clinic provides IT Professionals experienced in Windows 2000 Server or Windows Server 2003 with the knowledge and skills to implement and manage Hyper-V in an IT environment.

Topics covered in the clinic include:

Features of Hyper-V
Features of server consolidation
Hyper-V implementation
Creation of virtual machines
Dynamic datacenters
Clustering in virtual environments

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
Describe features of Hyper-V and server consolidation.
Implement and manage Hyper-V.
Describe business continuity and high-availability enhancements with Hyper-V.

Título: Clinic 3404: What's New in Windows Vista™
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 45 Minutos
Idioma: Inglés

Descripción:
Windows Vista is here. This short, online course explains and demonstrates many of the new features in Windows Vista, to help you get you up-to-speed quickly. Learn about the new look and feel of the Windows Vista desktop, including the Start Menu, Windows Sidebar and Gadgets. Next, see what's new in Internet Explorer 7, Desktop Search, securing your PC with Windows Defender, and managing your tablet and notebook PC with Mobility Center.

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
In this online course you will learn about the:
Windows Vista user interface
Windows Sidebar and Gadgets
Internet Explorer 7
Desktop Search
Windows Defender
Mobility Center

Título: Clinic 5936: Introducing Security and Policy Management in Windows Server® 2008
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 2 Horas
Idioma: Inglés

Descripción:
In this online clinic, you are introduced to security and policy management in Windows Server 2008. You learn about how to secure and manage your environment through Network Access Protection, IPSec, 802.1X authentication, VPNs, and DHCP. This online clinic is composed of a rich multimedia experience. It is intended for IT Professionals who are interested in the new features and functionality in Windows Server 2008. To get the most out of this clinic, it is recommended that you have experience implementing Windows Server 2000 or Windows Server 2003. This is one of five clinics in collection 5934.

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
Identify the concepts and features of Network Access Protection.
Describe how to verify and check the health and compliancy of desktops and laptops.
Describe how to implement IP Security Enforcement in Network Access Protection
Describe how to implement IEEE 802.1x Authentication Enforcement in Network Access Protection.
Describe how to implement Virtual Private Network Enforcement in Network Access Protection.
Describe how to implement Dynamic Host Protocol Control Enforcement in Network Access Protection.

Título: Clinic 5939: Introducing Server Management in Windows Server®2008
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 2 Horas
Idioma: Inglés

Descripción:
In this online clinic, you learn the new tools and improved features for server management and administration of Windows Server 2008. This includes PowerShell task automation, remote administration, performance, and diagnostic tools. This online clinic is composed of a rich multimedia experience. It is intended for IT Professionals who are interested in the new features and functionality in Windows Server 2008. To get the most out of this clinic, it is recommended that you have experience implementing Windows Server 2000 or Windows Server 2003. This is one of five clinics in collection 5934.

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
Describe the Initial Configuration Tasks window in Windows Server 2008.
Describe Server Manager Console in Windows Server 2008.
Describe Server Core in Windows Server 2008.
Describe the improvements to automation of administration for Windows Server 2008.
Describe the improvements to Remote Administration in Windows Server 2008.
Describe how to collect error information using Event Viewer in Server Manager Console.
Describe the improved performance and diagnostic tools in Windows Server 2008.

Título: Clinic 6188: What's New in Microsoft SQL Server 2008 for Enterprise Data Platform
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 1 Hora
Idioma: Inglés

Descripción:
In this 1 hour on-line clinic, IT Professionals will learn about the new features in SQL Server 2008 that will help them to secure the enterprise data platform. Topics covered in this clinic include:

Data Protection Features in SQL Server 2008
Data Monitoring Features in SQL Server 2008
Data Management Features in SQL Server 2008

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
Describe the new features in SQL Server 2008 that help you to secure the enterprise data platform.

Collection 6187: What's New in Microsoft SQL Server 2008

In this 3 hour online collection, IT Professionals will learn about the new features in SQL Server 2008. Topics covered within these clinics include:

What's New in SQL Server 2008 for Enterprise Data Platform
What's New in SQL Server 2008 for Business Intelligence
What's New in SQL Server 2008 for Database Development

Título: Clinic 6334: Exploring Microsoft System Center Virtual Machine Manager 2008
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 2 Horas
Idioma: Inglés

Descripción:

This 2-hour online clinic provides IT Professionals experienced in Windows 2000 Server or Windows Server 2003 with the knowledge to implement and manage Microsoft System Center Virtual Machine Manager 2008.

Topics covered in the clinic include:

Features and functionalities of VMM
Implementation and management of VMM
Management of VMM library
Management of hosts by using VMM
Implementation of virtual machine Self-Services

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
Describe the features and functionalities of VMM.
Describe how to implement VMM.
Work with virtual machines by using VMM.
Describe how to manage the VMM library.
Describe how to manage hosts by using VMM.
Describe how to implement virtual machine Self-Service.

Título: Clinic 6336: Exploring Terminal Services in Windows Server 2008
Tipo de curso: Curso paso a paso
Disponible sin conexión: Sí
Tiempo estimado para completar curso: 2 Horas
Idioma: Inglés

Descripción:
This 2-hour online clinic provides IT Professionals experienced in Windows 2000 Server or Windows Server 2003 with the knowledge to implement and manage Terminal Services in Windows Server 2008.

Topics covered in the clinic include:

Implementation of Terminal Services
Working with Terminal Services RemoteApp, Terminal Services Web Access, Terminal Services Gateway, Terminal Services Session Broker, and Terminal Services Licensing

Objetivos:
Al finalizar el curso, los alumnos serán capaces de:
Describe how to implement Terminal Services to securely access remote programs and resources.
Work with Terminal Services RemoteApp to access standard programs on a remote computer running Windows Server 2008.
Work with Terminal Services Web Access to launch Terminal Services RemoteApp applications from a browser.
Work with Terminal Services Gateway to access Terminal Servers and remote desktops over the Internet.
Work with Terminal Services Session Broker to balance the load in sessions between Terminal Servers.
Work with Terminal Services Licensing to manage Terminal Services client access licenses (TS CALs).

Collection 5934: Introducing Windows Server® 2008

In this online collection composed of five clinics, you are introduced to the new features and functionality in Windows Server 2008. This includes server virtualization, security and policy management, branch office management, centralized application access, and server management. This online collection is composed of a rich multimedia experience. It is intended for IT Professionals who are interested in the new features and functionality in Windows Server 2008. To get the most out of this collection it is recommended that you have experience implementing Windows Server 2000 or Windows Server 2003.

Esta oferta incluye los cursos siguientes:

Clinic 5935: Introducing Hyper-V in Windows Server 2008
Clinic 5936: Introducing Security and Policy Management in Windows Server® 2008
Clinic 5937: Introducing Branch Office Management in Windows Server®2008
Clinic 5938: Introducing Terminal Services Presentation Virtualization in Windows Server®2008
Clinic 5939: Introducing Server Management in Windows Server®2008

Hyper-V: Artículos y WhitePapers

2008-12-01T16:23:00.000-08:00

Inmersos en la virtualización y para ir abriendo boca, aquí os dejo estos interesantes enlaces a Artículos y WhitePapers sobre Hyper-V

Windows Server 2008 Hyper-V Technical Overview

Windows Server 2008 Hyper-V Datasheet

Top 10 Reasons for Windows Server 2008 Hyper-V

Windows Server 2008 Virtualization Product Overview

Windows Server 2008 Quick Migration with Hyper-V

Windows Server 2008 Advanced Virtualization Benefits

http://www.microsoft.com/windowsserver2008/en/us/white-papers.aspx

Lectura Obligada para esta semana (21-11-2008)

2008-11-26T16:04:00.000-08:00

Extraido del artículo de Chris Avis , os dejo estos interesantes artículos.

Infrastructure Development, Operations & Maintenance

Active Directory Migration Tool v3.0

Brief Description

The Active Directory Migration Tool version 3 (ADMT v3) provides an integrated toolset to facilitate migration and restructuring tasks in an Active Directory infrastructure.
Overview
The Active Directory Migration Tool version 3 (ADMT v3) simplifies the process of restructuring your operating environment to meet the needs of your organization. You can use ADMT v3 to migrate users, groups, and computers from Microsoft® Windows NT® 4.0 domains to Active Directory® directory service domains; between Active Directory domains in different forests (interforest migration); and between Active Directory domains in the same forest (intraforest migration). ADMT v3 also performs security translation from Windows NT 4.0 domains to Active Directory domains and between Active Directory domains in different forests.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6f86937b-533a-466d-a8e8-aff85ad3d212&DisplayLang=en

Update Rollup 5 for Exchange Server 2007 Service Pack 1 (KB953467)

Brief Description

Update Rollup 5 for Exchange Server 2007 Service Pack 1 (KB953467)

Overview

Update Rollup 5 for Exchange Server 2007 Service Pack 1 (SP1) resolves issues that were found in Exchange Server 2007 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP1 customers. For a list of changes that are included in this update rollup, see KB953467. This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM). For a list of update rollups applicable to Exchange Server 2007 RTM, refer to the section Update rollups for Exchange Server 2007 RTM in the Knowledge Base article KB937052. This is a cumulative update rollup and replaces the following:
KB945684 Update Rollup 1 for Exchange Server 2007 Service Pack 1 (KB945684)
KB948016 Update Rollup 2 for Exchange Server 2007 Service Pack 1 (KB948016)
KB949870 Update Rollup 3 for Exchange Server 2007 Service Pack 1 (KB949870)
KB952580 Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580)
http://www.microsoft.com/downloads/details.aspx?FamilyID=652ed33a-11a1-459c-8ffe-90b9cbfe7903&DisplayLang=en

Microsoft .NET Framework 3.5 Service Pack 1

Brief Description

Microsoft .NET Framework 3.5 Service Pack 1 is a full cumulative update that contains many new features building incrementally upon .NET Framework 2.0, 3.0, 3.5, and includes cumulative servicing updates to the .NET Framework 2.0 and .NET Framework 3.0 subcomponents.
Overview
.NET Framework version 3.5 Service Pack 1 provides the following new features and improvements:
ASP.NET Dynamic Data, which provides a rich scaffolding framework that enables rapid data driven development without writing code, and a new addition to ASP.NET AJAX that provides support for managing browser history (back button support). For more information, see What’s New in ASP.NET and Web Development.
Core improvements to the CLR (common language runtime) that include better layout of .NET Framework native images, opting out of strong-name verification for fully trusted assemblies, improved application startup performance, better generated code that improves end-to-end application execution time, and opting managed code to run in ASLR (Address Space Layout Randomization) mode if supported by the operating system. Additionally, managed applications that are opened from network shares have the same behavior as native applications by running with full trust.
Performance improvements to WPF (Windows Presentation Foundation), including a faster startup time and improved performance for Bitmap effects. Additional functionality for WPF includes better support for line of business applications, native splash screen support, DirectX pixel shader support, and the new WebBrowser control.
ClickOnce application publishers can decide to opt out of signing and hashing as appropriate for their scenarios, developers can programmatically install ClickOnce applications that display a customized branding, and ClickOnce error dialog boxes support links to application-specific support sites on the Web.
The Entity Framework is an evolution of the existing suite of ADO.NET data access technologies. The Entity Framework enables developers to program against relational databases in according to application-specific domain models instead of the underlying database models. For more information, see Getting Started with the Entity Framework. The Entity Framework introduces some additional features, including support for new SQL Server 2008 types, default graph serialization of Entities, and the Entity Data Source. This release of the Entity Framework supports the new date and file stream capabilities in SQL Server 2008. The graph serialization work helps developers who want to build Windows Communication Foundation (WCF) services that model full graphs as data contracts. The Entity Data Source provides a traditional data source experience for ASP.NET Web application builders who want to work with the Entity Framework.
LINQ to SQL includes new support for the new date and file stream capabilities in SQL Server 2008.
The ADO.NET Data Services Framework consists of a combination of patterns and libraries, which enable data to be exposed as a flexible REST (Representational State Transfer)-based data service that can be consumed by Web clients in a corporate network or across the Internet. The ADO.NET Data Services Framework makes data service creation over any data source. A conceptual view model of the underlying storage schema can easily be exposed through rich integration with the ADO.NET Entity Framework. Services created by using the ADO.NET Data Services Framework, and also compatible Windows Live (dev.live.com) services, can be easily accessed from any platform. For client applications that are running on Microsoft platforms, a set of client libraries are provided to make interaction with data services simple. For example, .NET Framework-based clients can use LINQ to query data services and a simple .NET Framework object layer to update data in the service.
Windows Communication Foundation now makes the DataContract Serializer easier to use by providing improved interoperability support, enhancing the debugging experience in partial trust scenarios, and extending syndication protocol support for wider usage in Web 2.0 applications.
The .NET Framework Data Provider for SQL Server (SqlClient) adds new support for file stream and sparse column capabilities in SQL Server 2008.
http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&DisplayLang=en

Visual Round Trip Analyzer

Brief Description

Tool to view web page performance Web page performance visualizer and analyzer

Overview

The Visual Round Trip Analyzer tool helps web developers and testers visualize the download of their page, identify best practices and changes that improve web performance. The network Round-Trip between the client and server(s) is the single biggest impact to web page performance – much greater than server response time. VRTA examines the communications protocol, identifying the causes of excessive round-trips, and recommending solutions. Performance engineers, testers, developers, operations personnel should use VRTA to conduct their web performance analysis.
http://www.microsoft.com/downloads/details.aspx?FamilyID=119f3477-dced-41e3-a0e7-d8b5cae893a3&DisplayLang=en

Security, Policy & Compliance

Microsoft® Forefront™ codename "Stirling" Beta

Brief Description

An integrated security system that is easier to manage and control Microsoft® Forefront™ codename "Stirling" is an integrated security system that delivers comprehensive, coordinated protection across endpoints, messaging and collaboration servers and the network edge that is easier to manage and control.
Overview
Microsoft® Forefront™ codename “Stirling” is an integrated security system that delivers comprehensive, coordinated protection across endpoints, messaging and collaboration servers and the network edge that is easier to manage and control. By delivering simplified management and providing critical visibility into threats, vulnerabilities, and configuration risks, Forefront codename "Stirling" helps reduce costs and achieve greater insight into the enterprise security state. At release, “Stirling” will include:
 A central management console and dashboard for security configuration and enterprisewide visibility.
 The next-generation versions of Forefront products: the next generation of Forefront Client Security, Forefront Security for Exchange Server, Forefront Security for SharePoint and the Internet Security & Acceleration Server (to be renamed the Forefront Threat Management Gateway).
 Dynamic Response, an innovative Microsoft technology built into each component of "Stirling" that allows the entire system to share and use security information to dynamically respond to threats across multiple layers of the organization.
http://www.microsoft.com/downloads/details.aspx?FamilyID=65bd5f8a-d94c-457a-9f88-2046597130e1&DisplayLang=en