This can be solved by disabling the time synchronization between the host, set the date to one in the past, and restart de SQL services afterwards.

net stop vmictimesync
date 24/2/2011
net start mssql$pocserver
net start mssql$microsoftscm
net start mssql$maps
net start vmictimesync

source: http://social.technet.microsoft.com/Forums/en-US/w7itpropoc/thread/6ccb11d4-e2cf-4af3-8df1-d2fdfb294d33

Edit: Proof of Concept Jumpstart Kit v3.0 was released, start your download managers!

The result can be found here:

http://seminar.the-d-spot.org/Desktop optimisation – notes from the field – 17102011.pdf

I prepared my sequence machine with:

• Windows patches, dummy printer, dummy odbc connections
• App-V Sequencer 4.6
• Placed new addin sources and the sequence to upgrade on the desktop
• Made a snapshot

Started the Sequencer, opened the package for upgrade. Enabled “Show Advanced Monitoring Options”, and select “Allow Microsoft Update to run during monitoring”. So far so good, but after downloading & installing the patches all of them failed to install!

All patches failed with error code 0×80070643.

What went wrong?

I forgot to install the OSPP (Office Software Protection Platform) service on my sequence machine! (AKA Office 2010 Deployment Kit for App-V).

After installing the prerequisite all security fixes installed successful:

All my xml tags where closed like it should, I couldn’t find any syntax error. But then I remembered something learned at school (it’s been 10 years!); opening an XML file in Internet Explorer to verify the syntax!

I used the Dutch word “geïnstalleerd”. After removing the special character (changed to “geinstalleerd)”, the Office 2010 installation was successful.

Desktop deployment involves much more than just migrating from Windows XP to Windows 7. In fact it’s mainly about managing your desktop and application infrastructure effectively. This Technet article covers all about optimized desktop and why a properly managed desktop has a good TCO. Also the new tools in MDOP are covered and how to use the cloud with Windows Intune. You can take a short tour (half an hour), mid tour (half day) or the full tour (full day).

The following topics are covered:

• Application Compatibility
• Office 2010 Deployment – Office 365
• Desktop Optimization Pack
• Windows 7 Deployment
• Internet Explorer 9
• Windows Intune

Take the deployment dive at Technet.

• Download SP1 for Office 2010 (x86)
• Extract the sources: execute this at the command line:

officesuite2010sp1-kb2460049-x86-fullfile-en-us.exe /extract:c:\temp\SP1>

Accept the License Terms and click continue.

After extracting is complete, you will find the unpacked files into the folder you specified.

• Apply SP1: Copy the extracted files to your Office 2010 network installation point into the Updates folder, no more no less.

New in this version

• System Center Configuration Manager (SCCM) 2012 support (console integration..).
• Improved Lite Touch user experience and functionality (brand new wizard and designer).
• Cross-platform deployment (using another WinPE architecture than the OS you’re deploying).
• Enhancements for partitioning with UEFI .
• Native VHD support (Deploy to VHD).
• Bugs fixes.

Downloads and other resources

Downloads:

• Download MDT 2012 beta 1 from MS Connect.

Resources:

• Technet Radio on MDT 2012.
• MDT tagged articles here on The D-Spot.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1b23c540-9b9f-4d41-a05d-d4b216061957

The WAIK contains tools like ImageX, DISM, WinPE, USMT and VAMT.

This update isn’t needed to deploy Windows 7/Server 2008 R2 with SP1 or the standalone Service Pack 1, it is an optional update. Be sure to read what is changed in this version: http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx#SP1

Download WAIK for Windows 7 SP1 at Microsoft. (this is pointing to the original WAIK 2.0, not version 3.0! Read more below).

UPDATE: Apparently Microsoft didn’t updated the WAIK ISO, but only released supplemental files for the WAIK.  These supplemental files are packaged in an ISO file (waik_supplement_en-us.iso), and doesn’t contain an installer like the original WAIK.  You need to extract the ISO and (old school) xcopy the content to your Windows AIK directory (\Program Files\Windows AIK\Tools\PETools\).

Contents of the supplemental ISO file (waik_supplement_en-us.iso):

(X)Copy them to:

C:\Program Files\Windows AIK\Tools\PETools

More on Michael’s blog.

First grab the Reader X sources and the Adobe Customization Wizard X.

Download Sources

Adobe Reader 10.0 Engish sources: ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.0.0/en_US/

UPDATE: Reader 10.0.1 sources (fix for DFS issue and others): ftp://ftp.adobe.com/pub/adobe/reader/win/10.x/10.0.1/en_US/

Adobe Customization Wizard 10: ftp://ftp.adobe.com/pub/adobe/acrobat/win/10.x/10.0.0/misc/

Extract sources

To unpack the downloaded exe file, use the –nos_ne parameter:

AdbeRdr1000_en_US.exe -nos_ne

Find the extracted files in (WinXP):

%AllUsersProfile%\Application Data\Adobe\Setup\{AC76BA86-7AD7-1033-7B44-AA0000000001}

The above path is described in the log file %temp%\AdobeSFX.log (shown at the background of the screenshot below).

Create a Distribution Point

Copy the extracted files to a (network) location. This will be your distribution point.

Create a transform file (.mst) using the Adobe Customization Wizard

Installation Options

Launch Adobe’s Customization Wizard 10, and open the extracted AcroRead.MSI. Then change the settings to suit your needs, use the following screenshots as an example.

Registry: Prevent Updates

Create two extra registry keys in the Registry-tab. The same keys as we created for Reader 9.

Create new key: AVGeneral (in HKCU\Software\Adobe\Acrobat Reader\10.0), within that key create a new DWORD Value ‘bCheckForUpdatesAtStartup’.

DWORD: bCheckForUpdatesAtStartup

Value: 0

The second one is a new DWORD Value ‘OptIn’:

Create new DWORD: OptIn (in HKCU\Software\Adobe\CommonFiles\Usage\Reader 10)

Value: 0

To summarize both created registry keys, click the Summary tab:

Registry: Remove Speed Launcher and ARM

To prevent the installer from adding registry keys that will enable Adobe ARM and Adobe Speed Launcher, delete the following two registry keys.  Browse to Destination Computer > HKLM > Software > Microsoft > Windows > CurrentVersion > Run. Delete ARM & Speed Launcher by right-clicking them and choose Modify and set Action to Remove value.

You should end up with these two registry keys removed:

Shortcuts

Change the shortcuts to your needs:

End User License Agreement

Accept End User License Agreement (EULA):

Online and Acrobat.com Features

Disable al Updates:

Generate the Transform file

Save your transform file by choosing Generate Transform within the Transform menu:

Now our Distribution Point is updated with a MST (Transform) file:

I need to copy these files to my distribution point, which is of course a network location.

Deployment

Use the MST file to deploy Adobe Reader X, with Active Directory, ConfigManager or whatever your deployment solution is. Here is the command line to install AcroRead.msi with the transform file we created:

msiexec /i “dp_path\AcroRead.msi” TRANSFORMS=”dp_path\TransformFileCreatedWithCustomWizard.mst” /qb REBOOT=ReallySuppress /log “logfilepath\reader10.txt”