Yesterday we released Microsoft Deployment RC1 on the Microsoft Connect Site (http://connect.microsoft.com/). Many of you have already started testing and providing feedback (thank you!). There are two issues that have been uncovered this morning with the RC1 release. An error will occur when running Configure ConfigMgr Integraion or Configure WDS PXE Filter. The error occurs because two files were not properly signed in the release. We will be releasing an updated build and updated files within the next 24 hours.
If you would like to work around the issue. You can follow the following steps:
1. Click on Start, All Programs, Accessories, Command Prompt, and then select Run as administrator2. You may see the screen grey and a 'User Account Control' dialog box appear. If this happens, click Continue so that the command prompt starts.
Obtain a copy of sn.exe. Sn.exe installed with Visual Studio 2005, and the .NET Framework 2.0 SDK, and therefore it may already be on the computer. If it is not on the computer, then download .NET Framework 2.0 SDK to obtain it. The x86 version of the Software development kit can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=FE6F2099-B7B4-4F47-A244-C96D69C35DEC. The x64 version of the SDK can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=1AEF6FCE-6E06-4B66-AFE4-9AAD3C835D3D<
32-bit computer:"<path_to_sn>\sn.exe" -Vr *,31bf3856ad364e35
64-bit computer:"<path_to_sn>\sn.exe" -Vr *,31bf3856ad364e35
This should only be used as a temporary workaround until the updated files are posted as this might weaken the security of your system. Once we have released the updated files you will need to run sn.exe -Vx to re-enable Strong Name validation.
Thank you for your patience and your diligence in testing Microsoft Deployment.
Le blog de l’équipe BDD précise une erreur nécessitant l’utilisation du programme sn.exe. http://blogs
L'équipe Microsoft Deployment vient de corriger la RC1 de Microsoft Deployment Toolkit, vous
The development team has isolated issues in the initial Microsoft Deployment RC1 build. Toolkit was throwing