Category Archives: Microsoft

Remove Powershell and Server Manager Pinned Items from taskbar

To do this, create a new GPO and drill down to: Computer configuration->Policies->Windows settings->Security Settings->File System
Add each file below, removing Users from the permissions so it’s only Administrators, Creator Owner and System:

  • %AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk
  • %AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Server Manager.lnk
  • %AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Windows PowerShell Modules.lnk

Keep in mind the path for %AllUsersProfile% is typically C:\ProgramData.  When you add the files using Group Policy Management you will select the files by drilling down to C:\ProgramData, Microsoft, Windows, Start Menu, etc, but you will notice when you’ve added them it auto-magically changes the path %AllUsersProfile%.
Use the “Configure this file or folder and propagate inheritable permissions to all subfolders and files” option on all three files.  Make sure to attach the new OU to your RDS OU or modify your existing RDS GPO. Run gpupdate /force from the command prompt on your RDS servers after adding/modifying this GPO and you’re ready to go!

Off course you can also configure the security settings manually or script.

icacls "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell" /T /inheritance:d
icacls "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell" /T /remove:g "BUILTIN\Users" Everyone
icacls "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Server Manager.lnk" /inheritance:d
icacls "%ProgramData%\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Server Manager.lnk" /remove:g "BUILTIN\Users" Everyone

** Update 25-02-2013 **

A colleague of mine has also written a blog about the same problem. He solved the problem with a group policy. For his solution see: http://www.emware.nl/articles/remove-server-manager-and-powershell-icons-from-taskbar.html

Windows 2008 virtual machines lose their Gateway IP address after rebooting

I was working on a Windows 2008 Server in an segmented network. This was a fresh new installation of Windows 2008. After a reboot the server was not reachable from another VLan. After some troubleshooting I found the problem. The gateway address has disappeared. Strange, so I started searching on the internet and I found an Knowledgebase article at the VMware site describing my problem, this is VMware KB1016878.

Symptoms

  • After every reboot, Windows 2008 virtual machines lose their Gateway IP address.
  • Gateway IP address is lost or reset after rebooting

Resolution

This issue may occur if there is a problem with the registry keys DefaultGateway and DefaultGatewayMetric.

Microsoft has identified this issue and has released a hotfix. For more information and to download the hotfix, see the Microsoft Knowledge Base article 973243.

To work around this issue:

  1. From the Windows Registry Editor, navigate to HKLM/System/CurrentControlSet/Services/Tcpip/Parameters/Interfaces/%CLSID%.
  2. Check the DefaultGateway and DefaultGatewayMetric keys for issues. For example:
  • Remove any newline feeds before the correct default gateway IP
  • If the address is missing, add it manually.

Device Manager is running in read-only mode

Today I was creating a template for my VMware environment, when I was trying to change the graphical interface card I was running into some problems. This is the message the Device Manager is giving me.

The result is that I cannot change any drivers or devices.

The solution is very simple but not obvious. My computer name is longer than 15 characters. This is a problem for NetBIOS computers. It turns out this is also a problem for the device manager. So I changed my computer name to a name with less than 15 characters, now everything works normal again.

Outlook Best Practices

Microsoft have created a video series about best practices in outlook. These tips might be handy sometime.

Harry was fine using Outlook for email and meeting reminders. But new responsibilities in his job began to overwhelm his schedule and make him feel lost in email. Harry’s co-worker, Renee, knows how to use Outlook to control email and scheduling, and begins to show Harry some best practices. (First part of a 9 video training series)

Continue reading

Turn off the Metrostyle desktop in Windows 8

I was testing the Developer Preview version of Windows 8 and I was not so happy about the new metro style desktop.

I immediately was searching for an option to turn it off and put it back to the normal old style of desktop icons. After a few hours of searching I didn’t find an option to turn it off.

Today I ran in to a Tweet with my solution of how to turn it off, see http://deploymentbunny.com/2011/09/18/windows-8-developer-server-preview-switch-to-classic-start-menu/

It turns out it’s a simple registry key that needs to be set to turn everything back to normal. Change the key: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer

change the RPEnabled value from 1 in to 0 and everything is back to normal again.

Reset Domain Administrator Password

A Client of our company had a problem, they got in an argument with their current IT Management company. Eventually the IT Management company wouldn’t give up the administrator account password of the complete domain. So this client was locked out of his own network. We were asked if there was a way to reset this password. So I started looking on the internet for some solutions.

The first one I tried in my own lab was the one that Daniel Petri describes in het Blog post at: http://www.petri.co.il/reset_domain_admin_password_in_windows_server_2003_ad.htm

There were some requirements for this trick.

  • Local access to the domain controller (DC).
  • The Local Administrator password.
  • Two tools provided by Microsoft in their Resource Kit: SRVANY and INSTSRV. Download them from HERE (24kb).

The first one was no problem, but the second one in my case was a problem, we didn’t no the local administrator password.

So this is how I did it, first of all download the DART tools (Diagnostics and Recovery Toolset) from the Microsoft website, this is available for MDOP License owners. See http://www.microsoft.com/windows/enterprise/products/mdop/dart.aspx

There are other ways to get your hands on this tool, go to the Technet site and get a Technet Subscription. And if you don’t have access to both sources, go search Google.

I restarted the domain domain controller, and boot into the DART tool. Go to the Locksmith tool, and reset the password of the Administator account. Reboot the server, in Active Directory Recovery mode. This is important because now the Local accounts are available for logon. The local accounts are disabled on a Domain Controller, this is by design. In recovery mode logon with your new local Administrator password. Now do the trick that Daniel Petri describes in his post.

This is how it works globally.

Step 1

Restart Windows 2003 in Directory Service Restore Mode.

Note: At startup, press F8 and choose Directory Service Restore Mode. It disables Active Directory. When the login screen appears, log on as Local Administrator. You now have full access to the computer resources, but you cannot make any changes to Active Directory.

clip_image001

Step 2

You are now going to install SRVANY. This utility can virtually run any programs as a service. The interesting point is that the program will have SYSTEM privileges (LSA) (as it inherits the SRVANY security descriptor), i.e. it will have full access on the system. That is more than enough to reset a Domain Admin password. You will configure SRVANY to start the command prompt (which will run the ‘net user’ command).

Copy SRVANY and INSTSRV to a temporary folder, mine is called D:\temp. Copy cmd.exe to this folder too (cmd.exe is the command prompt, usually located at %WINDIR%\System32).

Start a command prompt, point to d:\temp (or whatever you call it), and type:

instsrv PassRecovery "d:\temp\srvany.exe"

(change the path to suit your own).

It is now time to configure SRVANY.

Start Regedit, and navigate to

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PassRecovery

Create a new subkey called Parameters and add two new values:

name: Application

type: REG_SZ (string)

value: d:\temp\cmd.exe

name: AppParameters

type: REG_SZ (string)

value: /k net user administrator 123456 /domain

Replace 123456 with the password you want. Keep in my mind that the default domain policy require complex passwords (including digits, respecting a minimal length etc) so unless you’ve changed the default domain policy use a complex password such as P@ssw0rd

Now open the Services applet (Control Panel\Administrative Tools\Services) and open the PassRecovery property tab. Check the starting mode is set to Automatic.

clip_image002

Go to the Log On tab and enable the option Allow service to interact with the desktop.

Restart Windows normally, SRVANY will run the NET USER command and reset the domain admin password.

Step 3

Log on with the Administrator’s account and the password you’ve set in step #2.

Use this command prompt to uninstall SRVANY (do not forget to do it!) by typing:

net stop PassRecovery

sc delete PassRecovery

Now delete d:\temp and change the admin password if you fancy.

Done!

FREE Exchange 2010 Training

Exchange 2010 Upgrade and Deployment (HOLO)

This 300 level hands-on labs online course (including seven hands-on labs) will prepare learners with the knowledge to engage with customers to help them implement best practices for smooth Exchange 2010 upgrades and deployments. These hands-on labs online (HOLOs) are provided at no charge to Microsoft partners, and provide IT Professionals with the essential information they need to setup, deploy, and configure Microsoft Exchange Server 2010.  The course will address gaps in knowledge around topics such as new features, upgrade paths, tools and processes to support upgrade and deployment planning.

Training includes the following curriculum:

Course (Online): Using Exchange 2010 Tools to Plan a Deployment (Part 1)

Course (Online): Using Exchange Tools to Plan a Deployment (Part 2)

Course (Online): Exchange 2010 Setup, Deployment, and Server Role Configuration

Course (Online): Configuring Mail Flow and Outlook Web Access

Course (Online): Moving Mailboxes to Exchange 2010

Course (Online): Moving Other Services to Exchange 2010 (Part 1)

Course (Online): Moving Other Services to Exchange 2010 (Part 2)

Microsoft Test Lab Guides

Recently Microsoft released a lot of Lab Guides for different Microsoft products to test. See http://social.technet.microsoft.com/wiki/contents/articles/test-lab-guides.aspx

Test Lab Guides

Test lab guides (TLGs) allow you to get valuable hands-on experience with new products and technologies using a pre-defined and tested methodology that results in a working configuration. When you use a TLG to create a test lab, instructions define what servers to create, how to configure the operating systems and system services, and how to install and configure any additional products or technologies. A TLG experience enables you to see all of the components and the configuration steps on both the front-end and back-end that are required for a product or technology or for a multi-product or technology solution.

A challenge in creating useful TLGs is to enable their reusability and extensibility. Because creating a test lab can represent a significant investment of time and resources, your ability to reuse and extend the work required to create test labs is important. An ideal test lab environment would enable you to create a basic lab configuration, save that configuration, and then build out multiple test lab scenarios in the future by starting with the base configuration.

For a test lab based on physical computers, you can image the drives for future test labs. For a test lab based on virtual machines, you can create snapshots for future test labs. This allows you to easily return to a desired configuration for further learning and experimentation.

The types of TLG documents are the following:

  • Base configuration TLG
  • Modular TLGs
  • TLG extensions
  • Troubleshooting TLGs
  • Test lab troubleshooting scenarios
  • TLG portal pages

Base Configuration TLG

The Base Configuration TLG allows you to create the base configuration test lab, upon which you can build test labs based on other TLGs from Microsoft, TLG extensions in the TechNet Wiki, or a test lab of your own design that can include Microsoft or non-Microsoft products.

The base configuration TLG is just the beginning of the test lab experience. Other TLGs or TLG extensions in the TechNet Wiki focus on Microsoft products or platform technologies, but all of them use the Base Configuration TLG as a starting point.

After configuring the computers of the base configuration test lab, make sure that you perform a disk image on each computer if you are using physical computers, or perform virtual machine snapshots if you are using virtual machines.

Modular TLGs

A modular TLG describes how to set up and demonstrate a technology, product, or solution for either the Base Configuration test lab or a test lab based on another modular TLG.

The following modular TLGs are available:

To create your own modular TLG in the TechNet Wiki, see the Wiki: Modular Test Lab Guide Template.

TLG Extensions

A TLG extension article, published in the TechNet Wiki, describes how to configure additional functionality or advanced or uncommon configurations based on a working test lab. A TLG extension extends a modular TLG.

The TLG extension article includes instructions to configure and test the additional functionality, and then manually restore the test lab to its original state. A TLG extension article also includes virtualization advice so that you can create snapshots to store the modified test lab configuration and easily restore the original working test lab configuration.

Examples of TLG extensions are the following:

To create your own TLG extension, see Wiki: Test Lab Extension Template.

Troubleshooting TLGs

A troubleshooting TLG describes the troubleshooting tools and how they appear in a working test lab for a technology, product, or multi-technology and product solution. The working test lab is typically based on a modular TLG.

A troubleshooting TLG also takes you through a set of troubleshooting scenarios. Each troubleshooting scenario steps you through the following:

  • Breaking the configuration of the test lab in a specific way
  • Demonstrating the effect on the technology or product functionality
  • Performing root cause analysis of the problem using the troubleshooting tools and recommended troubleshooting techniques
  • Correcting the problem

The following troubleshooting TLGs are available:

To create your own troubleshooting TLG in the TechNet Wiki, see the Wiki: Troubleshooting Test Lab Guide Template.

Test Lab Troubleshooting Scenarios

A test lab troubleshooting scenario, published in the TechNet Wiki, provides an additional scenario to demonstrate the results of a misconfiguration or other type of common problem and guide the reader through the root cause determination and correction. Test lab troubleshooting scenarios extend a troubleshooting TLG.

For an example of a test lab troubleshooting scenario, click here.

To create your own test lab troubleshooting scenario, see Wiki: Test Lab Troubleshooting Scenario Template.

TLG Portal Pages

A TLG portal page is a TechNet Wiki article that provides links to all of the resources for a specific technology or product.

The following TLG portal pages are available:

Additional Resources

For the latest information about TLGs, see the Microsoft TLG blog.

Exchange 2010 SP1 FAQ and Known Issues

The Exchange Team Blog have posted a great article with lots of information about the installation of Service Pack 1 for Exchange 2010. Read the article at: http://msexchangeteam.com/archive/2010/09/01/456094.aspx

Last week we released Exchange Server 2010 Service Pack 1. It has received some great feedback and reviews from customers, experts, analysts, and the Exchange community.

The starting point for SP1 setup/upgrade should be the What’s New in SP1, SP1 Release Notes, and Prerequisites docs. As with any new release, there are some frequently asked deployment questions, and known issues, or issues reported by some customers. You may not face these in your environment, but we’re posting these here along with some workarounds so you’re aware of them as you test and deploy SP1.

  1. Upgrade order

    The order of upgrade from Exchange 2010 RTM to SP1 hasn’t changed from what was done in Exchange 2007. Upgrade server roles in the following order:

    1. Client Access server
    2. Hub Transport server
    3. Unified Messaging server
    4. Mailbox server

    The Edge Transport server role can be upgraded at any time; however, we recommend upgrading Edge Transport either before all other server roles have been upgraded or after all other server roles have been upgraded. For more details, see Upgrade from Exchange 2010 RTM to Exchange 2010 SP1 in the documenation.

  2. SP1 Prerequisites

    SP1 requires the installation of 4-5 hotfixes, depending on the operating system – Windows Server 2008, or Windows Server 2008 R2. To install the Exchange 2010 SP1 administration tools on Windows 7 and Windows Vista, you requires 2 hotfixes.

    Note: Due to the shared code base for these updates, Windows Server 2008 and Windows Vista share the same updates. Similarly, Windows Server 2008 R2 and Windows 7 share the same updates. Make sure you select the x64 versions of each update to be installed on your Exchange 2010 servers.

    Here’s a matrix of the updates required, including download locations and file names.

    Hotfix Download Windows Server 2008 Windows Server 2008 R2 Windows 7 & Windows Vista
    979744
    A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application
    MSDN
    or Microsoft Connect
    Windows6.0-KB979744-x64.msu (CBS: Vista/Win2K8) Windows6.1-KB979744-x64.msu (CBS: Win7/Win2K8 R2) N. A.
    983440
    An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2
    Request from CSS (select the x64 version) Yes Yes N.A.
    977624
    AD RMS clients do not authenticate federated identity providers in Windows Server 2008 or in Windows Vista. Without this update, Active Directory Rights Management Services (AD RMS) features may stop working
    Request from CSS using the “View and request hotfix downloads” link in the KBA | US-English Select the download for Windows Vista for the x64 platform. N.A. N.A.
    979917
    Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode
    Request from CSS using the Hotfix Request Web Submission Form or by phone (no charge) Yes N. A. N. A.
    973136,
    FIX: ArgumentNullException exception error message when a .NET Framework 2.0 SP2-based application tries to process a response with zero-length content to an asynchronous ASP.NET Web service request: “Value cannot be null”.
    Connect Windows6.0-KB973136-x64.msu N.A. N. A.
    977592
    RPC over HTTP clients cannot connect to the Windows Server 2008 RPC over HTTP servers that have RPC load balancing enabled.
    Request from CSS Select the download for Windows Vista (x64) N.A. N. A.
    979099
    An update is available to remove the application manifest expiry feature from AD RMS clients.
    Download Center N. A. Windows6.1-KB979099-x64.msu N. A.
    982867

    WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1

    MSDN N. A. Windows6.1-KB982867-v2-x64.msu (Win7) X86: Windows6.1-KB982867-v2-x86.msu (Win7)
    x64: Windows6.1-KB982867-v2-x64.msu (Win7)
    977020
    FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.
    Microsoft Connect N. A. N. A. x64: Windows6.1-KB977020-v2-x64.msu

    X86: Windows6.1-KB977020-v2-x86.msu

    Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBAs. The administrator experience when initially downloading these hotfixes may be a little odd. However, once you download the hotfixes, and receive two of the hotfixes from CSS, you can use the same for subsequent installs on other servers. In due course, all these updates may become available on the Download Center, and also through Windows Update.

    These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

  3. Prerequisite download pages linked from SP1 Setup are unavailable

    When installing Exchange Server 2010 SP1 the prereq check may turn up some required hotfixes to install. The message will include a link to click for help. Clicking this link redirects you to a page saying that the content does not exist.

    We’re working to update the linked content.

    Meanwhile, please refer to the TechNet article Exchange 2010 Prerequisites to download and install the prerequisites required for your server version (the hotfixes are linked to in the above table, but you’ll still need to install the usual prerequisites such as .Net Framework 3.5 SP1, Windows Remote Management (WinRM) 2.0, and the required OS components).

  4. The Missing Exchange Management Shell Shortcut

    Some customers have reported that after upgrading an Exchange Server 2010 server to Exchange 2010 SP1, the Exchange Management Shell shortcut is missing from program options. Additionally, the .ps1 script files associated with the EMS may also be missing.

    We’re actively investigating this issue. Meanwhile, here’s a workaround:

    1. Verify that the ConnectFunctions.ps1, commonconnectfunctions.ps1 and RemoteExchange.ps1 files are present in the %ExchangeInstallPath%\bin directory.NOTE: If these files are missing, you can copy the files from the Exchange Server 2010 Service Pack 1 installation media to the %ExchangeInstallPath%\bin directory. These files are present in the \setup\serverroles\common folder.
    2. Click Start -> AdmiinistrativeTools ->, right-click Windows PowerShell Modules, select Send to -> Desktop (as shortcut)
    3. Go to the Properties of the shortcut and on Target replace the path to C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command “. ‘C:\Program Files\Exchange Server\V14\bin\RemoteExchange.ps1’; Connect-ExchangeServer -auto”Note: if the Exchange installation folder or drive name is different than the default, you need to change the path accordingly.
  5. Upgrading Edge Transport on Forefront Threat Management Gateway (TMG) and Forefront Protection for Exchange 2010

    If you upgrade a server with the Edge Transport server role running with ForeFront Threat Management Gateway (TMG) and ForeFront Protection for Exchange (FPE) enabled for SMTP protection, the ForeFront TMG Managed Control Service may fail to start and E-mail policy configuration settings cannot be applied.

    The TMG team is working on this issue. See Problems when installing Exchange 2010 Service Pack 1 on a TMG configured for Mail protection on the ForeFront TMG (ISA) Team Blog. Exchange 2010 SP1 Release Notes has been updated with the above information.

  6. Static Address Book Service Port Configuration Changes

    The location for setting the port the address book service should use has changed in SP1. In Exchange 2010 RTM you had to edit the Microsoft.exchange.addressbook.service.exe.config to configure the service port. In SP1 you must use the following registry key:
    Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters
    Value name: RpcTcpPort
    Type: REG_SZ (String)
    When you apply SP1 to a machine where you had previously configured a static port by editing the Microsoft.exchange.addressbook.service.exe.config file, the upgrade process will not carry forward your static port assignments. Following a restart, the Address Book Service will revert to using a dynamic port instead of a static port specified in the config file. This may cause interruptions in service.

    As with all upgrades where servers are in load balanced pools, we recommend you perform a rolling upgrade — removing servers from the pool, updating them and then moving the pool to the newly upgraded machines. Alternatively, we recommend that you upgrade an array of servers by draining connections from any one machine before you upgrade it.

    There are times when these approaches may not be possible. You can maintain your static port configuration, and have it take effect the moment the address book service starts for the first time following the application of the service pack, by creating the registry key BEFORE you apply SP1 to your server. The registry key has no impact pre SP1, and so by configuring it before you apply the Service Pack you can avoid the need to make changes to set the port post install, and avoid any service interruptions.

  7. iPhone, OWA Premium and POP3 & IMAP4 issues due to invalid accepted domain

    After applying E2010 SP1:

    1. iPhone users may not be able to view the content of incoming messages in their Inboxes, and when they try to open a message, they get an error saying:This message has not been downloaded from the server.Admins may see the following event logged in the Application Event Log on Exchange 2010 CAS Server:Watson report about to be sent for process id: 1234, with parameters: E12, c-RTL-AMD64, 14.01.0218.011, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.InboundConversionOptions.CheckImceaDomain, UnexpectedCondition:ArgumentException, 4321, 14.01.0218.015.
    2. OWA Premium users may not be able to reply or forward a message. They may see the following error in OWA:An unexpected error occurred and your request couldn’t be handled. Exception type: System.ArgumentException, Exception message: imceaDomain must be a valid domain name.
    3. POP3 & IMAP4 users may also not be able to retrieve incoming mail and Admins will see the following event logged in Event Log:ERR Server Unavailable. 21; RpcC=6; Excpt=imceaDomain must be a valid domain name.

    Resolution

    Please run the following command under Exchange Management Shell and verify that there is one domain marked as ‘Default’ and it’s DomainName & Name values are valid domain names. We were able to reproduce the issue by setting a domain name with a space in it, like “aa bb”

    Get-AcceptedDomain | fl

    If you also have an invalid domain name there (for example, a domain name with a space in it), then removing the space and restarting the server will fix the EAS (iPhone), OWA, POP3 & IMAP4 issues as mentioned above.

    Command to run under EMS would be:

    Set-AcceptedDomain –Identity <value> -Name “ValidSMTPDomainName”

    Thes examples update the Name parameter of the “My Company” and “ABC Local” accepted domains (the space is removed from both):

    Set-AcceptedDomain –Identity “My Company” –Name “MyCompany.Com”
    Set-AcceptedDomain –Identity “ABC Local” –Name “ABC.Local”

  8. Error when adding or removing a mailbox database copy

    If a server running Exchange 2010 RTM (or Exchange 2010 SP1 Beta) is upgraded to Exchange 2010 SP1, administrators may experience an error when using the Add-MailboxdDtabaseDopy or Remove-MailboxDatabaseCopy cmdlets to add or remove DAG members.

    When you try to add a DAG member, you may see the following error:

    Add-MailboxDatabaseCopy DAG-DB0 -MailboxServer DAG-2

    The result:

    WARNING: An unexpected error has occurred and a Watson dump is being generated: Registry key has subkeys and recursive removes are not supported by this method.
    Registry key has subkeys and recursive removes are not supported by this method.
    + CategoryInfo : NotSpecified: (:) [Add-MailboxDatabaseCopy], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.SystemConfigurationTasks.
    AddMailboxDatabaseCopy

    The command is not successful in adding the copy or updating Active Directory to show the copy was added. This happens due to presence of the DumpsterInfo registry key.

    Workaround: Delete the DumpsterInfo key, as shown below.

    1. Identify the GUID of the database that is being added using this command:Get-MailboxDatabase DAG-DB0 | fl name,GUIDThe result:Name : DAG-DB0
      Guid : 8d3a9778-851c-40a4-91af-65a2c487b4cc
    2. On the server specified in the add command, using the database GUID identified, remove the following registry key:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Replay\State\<DB-GUID>\DumpsterInfoThe GUID identified in this case is 8d3a9778-851c-40a4-91af-65a2c487b4cc. With this information you can now export and delete the DumpsterInfo key on the server where you are attempting to add the mailbox database copy. This can be easily done using the registry editor, but if you have more than a handful of DAG members, this is best automated using the Shell.This example removes the DumpsterInfo key from the 8d3a9778-851c-40a4-91af-65a2c487b4cc key:

      Remove-Item HKLM:\Software\Microsoft\ExchangeServer\Replay\State\8d3a9778-851c-40a4-91af-65a2c487b4cc\DumpsterInfo

      To automate this across all servers in your organization, use the DeleteDumpsterRegKey.ps1 script.

      File: deletedumpsterregkey_ps1.txt
      Description: The DeleteDumpsterRegkey.ps1 script can be used to delete the offending DumpsterInfo registry keys that can cause this problem on all mailbox servers in the organization. Rename the file to DeleteDumpsterRegkey.ps1 (remove the .txt extension).

      For more info, see Tim McMichael’s blog post Exchange 2010 SP1: Error when adding or removing a mailbox database copy.

Thanks to all the folks in CSS and Exchange teams who helped identify, validate and provide workarounds for some of the issues mentioned above, and to the Exchange community and MVPs for their feedback.

Microsoft Exchange 2010 Service Pack 1 released

Today Microsoft released Service Pack 1 for Microsoft Exchange 2010. The Exchange team released this news on there blog called You Had Me At EHLO. See : http://msexchangeteam.com/archive/2010/08/25/455861.aspx

New Deployment Functionality

During an Exchange 2010 SP1 installation, you can now select a new option to install the required Windows roles and features for each selected Exchange 2010 SP1 server role. For more information, see New Deployment Functionality in Exchange 2010 SP1.

Exchange ActiveSync

In Exchange 2010 SP1, you can manage Exchange ActiveSync devices using the Exchange Control Panel (ECP). Administrators can perform the following tasks:

  • Manage the default access level for all mobile phones and devices.
  • Set up e-mail alerts when a mobile phone or device is quarantined.
  • Personalize the message that users receive when their mobile phone or device is either recognized or quarantined.
  • Provide a list of quarantined mobile phones or devices.
  • Create and manage Exchange ActiveSync device access rules.
  • Allow or block a specific mobile phone or device for a specific user.

For every user, the administrator can perform the following tasks from the user’s property pages:

  • List the mobile phones or devices for a specific user.
  • Initiate remote wipes on mobile phones or devices.
  • Remove old mobile phone or device partnerships.
  • Create a rule for all users of a specific mobile phone or device or mobile phone type.
  • Allow or block a specific mobile phone or device for the specific user.

SMS Sync

SMS Sync is a new feature in Exchange ActiveSync that works with Windows Mobile 6.1 with the Outlook Mobile Update and with Windows Mobile 6.5. SMS Sync is the ability to synchronize messages between a mobile phone or device and an Exchange 2010 Inbox. When synchronizing a Windows Mobile phone with an Exchange 2010 mailbox, users can choose to synchronize their text messages in addition to their Inbox, Calendar, Contacts, Tasks, and Notes. When synchronizing text messages, users will be able to send and receive text messages from their Inbox. This feature is dependent on the user’s mobile phones or devices supporting this feature

Reset Virtual Directory

In Exchange 2010 SP1, you can use the new Reset Client Access Virtual Directory wizard to reset one or more Client Access server virtual directories. The new wizard makes it easier to reset a Client Access server virtual directory. One reason that you might want to reset a Client Access server virtual directory is to resolve an issue related to a damaged file on a virtual directory. In addition to resetting virtual directories, the wizard creates a log file that includes the settings for each virtual directory that you choose to reset. For more information, see Reset Client Access Virtual Directories.

Exchange Store and Mailbox Database Functionality

The following is a list of new store and mailbox database functionality in Exchange 2010 SP1:

  • With the New-MailboxRepairRequest cmdlet, you can detect and repair mailbox and database corruption issues.
  • Store limits were increased for administrative access.
  • The Database Log Growth Troubleshooter (Troubleshoot-DatabaseSpace.ps1) is a new script that allows you to control excessive log growth of mailbox databases.
  • Public Folders client permissions support was added to the Exchange Management Console (EMC).

Mailbox and Recipients Functionality

The following is a list of new mailbox and recipient functionality included in Exchange 2010 SP1:

  • Calendar Repair Assistant supports more scenarios than were available in Exchange 2010 RTM.
  • Mailbox Assistants are now all throttle-based (changed from time-based in Exchange 2010 RTM).
  • Internet calendar publishing allows users in your Exchange organization to share their Outlook calendars with a broad Internet audience.
  • Importing and exporting .pst files now uses the Mailbox Replication service and doesn’t require Outlook.
  • Hierarchical address book support allows you to create and configure your address lists and offline address books in a hierarchical view.
  • Distribution group naming policies allow you to configure string text that will be appended or prepended to a distribution group’s name when it’s created.
  • Soft-delete of mailboxes after move completion

High Availability and Site Resilience Functionality

The following is a list of new high availability and site resilience functionality included in Exchange 2010 SP1:

  • Continuous replication – block mode
  • Active mailbox database redistribution
  • Enhanced datacenter activation coordination mode support
  • New and enhanced management and monitoring scripts
  • Exchange Management Console user interface enhancements
  • Improvements in failover performance

Messaging Policy and Compliance Functionality

The following is a list of new messaging policy and compliance functionality included in Exchange 2010 SP1:

  • Provision personal archive on a different mailbox database
  • Import historical mailbox data to personal archive
  • Delegate access to personal archive
  • New retention policy user interface
  • Support for creating retention policy tags for Calendar and Tasks default folders
  • Opt-in personal tags
  • Multi-Mailbox Search preview
  • Annotations in Multi-Mailbox Search
  • Multi-Mailbox Search data de-duplication
  • WebReady Document Viewing of IRM-protected messages in Outlook Web App
  • IRM in Exchange ActiveSync for protocol-level IRM
  • IRM logging
  • Mailbox audit logging

Technet Exchange 2010 SP1 info
Release Notes for Exchange Server 2010 SP1
What’s New in Exchange 2010 SP1
Downloads:
Microsoft Exchange Server 2010 Service Pack 1
Microsoft Exchange Server 2010 SP1 Language Pack Bundle
Exchange Server 2010 SP1 UM Language Packs
Exchange Server 2010 SP1 Help