This video will provide a deeper look at how Microsoft uses secure, reliable, scalable and efficient best practices to deliver over 200 cloud services to more than a billion customers and 20 million businesses in over 70 countries.It provides an understanding at how we view our end-to-end cloud strategy from an infrastructure perspective.
Microsoft began to distribute Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) as a high-priority update through Automatic Updates. However, as with most large corporate environments, IT organizations may want to delay the introduction of a new Service Pack until they have tested compatibility with internal applications and sites.
Microsoft created a tool called “Windows Service Pack Blocker Tool Kit” to stop it from updating your servers and workstations without your permission. Unlike the Blocker Toolkit for IE9, this tool does have an expiration date – the 22nd of February 2012. The tool and can be configured either by running the registry file on the client machines or through Group Policy in domain joined environments.
The tool can be used with:
- Windows 7 Service Pack 1
- Windows Server 2008 R2 Service Pack 1
The tool contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You need to only use one of the components, the one that best serves your organization’s computer management infrastructure.
The components are:
- A Microsoft-signed executable
- A script
- An ADM template
The executable creates a registry key on the computer on which it is runs that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.
Key value name: DoNotAllowSP
- When the key value name is not defined, distribution is not blocked.
- When the key value name is set to 0, distribution is not blocked.
- When the key value name is set to 1, distribution is blocked.
The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.
When the ‘/B’ command line option is used, the key value name ‘DoNotAllowSP‘ is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.
When the ‘/U’ command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.
Note: The executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.
Group Policy Administrative Template (.ADM file)
The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.
Add the .ADM file to the Group Policy by going to Computer Configuration > Administrative Templates. Right click and select Add/Remote Templates. Browse to the location of the .ADM file and click Ok.
Users running Windows 7 and Windows Server 2008 R2 will see the policy setting under Computer Configuration > Administrative Templates > Classic Administrative Templates (ADM) > Windows Components > Windows Update.
Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) from being delivered over Windows Update.
In Outlook 2007, when a user does a reply to some emails the E-mail Type: changes from the normal SMTP to MAILTO and then when the user sends the email it is rejected because either Outlook or our Exchange server is adding @domain.nl to the end of the recipient’s email address.
This also happens with emails where the senders address is shown as a clickable option [mailto:email@example.com].
Email address has been changed to Persons.firstname.lastname@example.org for confidentiality reasons.
Delivery has failed to these recipients or distribution lists:
A problem occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message later, or provide the following diagnostic text to your system administrator.
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: ward-ex01.wardvissers.nl
#550 5.4.4 ROUTING.NoNextHop; unable to route ##
Original message headers:
Received: from ward-ex01.wardvissers.nl ([fe80::d597:2413:93ab:cf17]) by ward-ex01.wardvissers.nl ([fe80::d597:2413:93ab:cf17%13]) with mapi; Thu, 14 Oct 2010 13:58:28 +0100
Content-Type: application/ms-tnef; name="winmail.dat"
From: Internal User <Internal@wardvissers.nl>
Date: Thu, 14 Oct 2010 13:58:27 +0100
Accept-Language: en-US, en-GB
Removing Microsft Office Word 2007 (KB2344993) update from the computer did the trick