The Windows Image Acquisition (WIA) library wiaaut.dll is unavailable (Paint.Net via App-V 4.6 SP1)

We’re using Windows 7 x64 as operating system so I tried Windows XP 32bit, same issue here. But after registering wiaaut.dll (in (c:\windows\system32) the printing issue was solved in XP 32bit, no luck with Win7x64. Also registering the DLL in the bubble with following OSD script wasn’t helpfull:

regsvr32 %SFT_SYSTEM%\\wiaaut.dll /s

After reading Kalle’s article about mixing 32-bit and 64-bit App-V environments, I realized the wrong environment variable was used. If running on 64-bit then %CSIDL_SYSTEM% will be mapped to c:\Windows\Syswow64 and not  to c:\Windows\System32. So I needed this to register the correct DLL:

regsvr32 %SFT_SYSTEM32_X64%\\wiaaut.dll /s

Still, the printing issue in Paint.NET remains.

Apparently App-V 4.6 adds the EXTERN parameter to run OSD scripts.  When setting the EXTERN parameter to TRUE scripts are executed from a 64bit command prompt! (more info)

<SCRIPT EVENT="LAUNCH" TIMING="PRE" WAIT="FALSE" PROTECT="TRUE" EXTERN="TRUE">

<SCRIPTBODY>

some action\n

some other action\n

regsvr32 %SFT_SYSTEM32_X64%\\wiaaut.dll /s

</SCRIPTBODY>

</SCRIPT>

When using the EXTERN="TRUE" parameter the correct DLL at the correct location was registered and printing works again!

The lab exercises will give you an overview of the functions in App-V 5.0. You will experience the new admin functions, learn how to migrate from App-V 4.6, learn how to enable app to app communication and how to reduce storage requirements via the shared content Store.

Take the vitual lab.

Microsoft Deployment Toolkit (MDT) 2012 is the newest version of Microsoft Deployment Toolkit, a Solution Accelerator for operating system and application deployment. MDT 2012 supports deployment of Windows 7, Office 2010 and 365, and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.

Download MDT 2012 from Microsoft.

The App-V Management Server remains, but changes are huge! No more RTSP(S) protocol, bits & bytes will transfert over HTTP. The Client Console is Siverlight based in Metro style (screenshot below), there is no more Q-Drive, OSD files are gone and SFT package format is history! Goodbye Softgrid!

Time for some hands on with the beta release!

App-V Client

We have to respect the order for upgrading the infrastucture. That is clients first, server second and sequencer last. Let’s start with the client.

Installing App-V 5.0 beta is a follow-the-wizard-process:

Joining the Customer Experience Improvement Program is mandatory:

After installing the product, I wanted to launch the App-V Client Console with the command sftcmc.msc, but apparently they got rid of the SFT –naming?

After browsing to All Programs > Microsoft Application Virtualization Client –container, a shortcut to AppVClientUX.exe is available;

Wow! A Metro Style interface!

My packages did not appear, probably I have to convert them to the new format.

App-V Server

Hitting the App-V 5.0 beta server executable (appv_server_setup.exe) didn’t launched the installer. Probably .NET Framework 4.0 is also a prerequisite for the server component?

The AppV Server log:

Loading prerequisite bootstrapper application because managed host could not be loaded, error: 0×80070490.
Error 0x8007007e: Failed to create the pre-requisite bootstrapper application.

After installing .Net Framework 4.0 the App-V installer finally shows an error:

I’ll have to remove my 4.5.3 server prior to installing the 5.0 beta server!

Loading managed bootstrapper application.
AppvUX: Application Virtualization Server cannot be installed on this system because an incompatible version of the Microsoft Application Virtualization Server has been detected. Please uninstall the previous version and try again.

Upgrading isn’t supported, so a side-by-side migration is the only way. From the App-V 5.0 beta AdminGuide:

Installing the App-V 5.0 Beta server is not supported for the following scenarios:

• Installing on a domain controller.
• Installing on a server running previous versions of App-V server components.
• Installing on Server Core.

I need to install a updated SQL Server version, because I’m running SQL Server 2008 SP1.

The AppV Server log says:

The database pre-deployment feature can only be installed on a server running the Standard, Enterprise or Datacenter editions of SQL Server 2008 SP2, SQL Server 2008 R2 or greater.
AppvUX: The database pre-deployment feature can only be installed on SQL Server 2008 R2 or SQL Server 2008 servers running Service Pack 2.

Ok, I’m running SQL Server 2008 SP1 (10.0.2531.0). Need to upgrade to SP2.

The database pre-deployment feature can only be installed on a server running the Standard, Enterprise or Datacenter editions of SQL Server 2008 SP2, SQL Server 2008 R2 or greater.

..Also no SQL Express, although it wasn’t supported in previous App-V versions, it does work (in a Lab environment).

After installing SQL Server 2008 with SP2, the installation can proceed.

Next blog will be about converting sequences (packages) to the new format.

While saving my sequence an I/O File Error showed up. Some log file couldn’t be read or write. I deleted the log file from the sequence and saved sequence again, with success this time. Probably this is the cause of the issue.

Solved this by opening the package for upgrade and saving the sequence As New Package, this way the Package GUID is regenerated.

Windows cannot read the <ProductKey> setting from the unattend answer file.

Other sources say to remove the floppy drive from the VM, but this didn’t solved the ProductKey issue for me:

The solution was rather simple, I had to change SkipProductKey to NO in customsettings.ini.

After changing SkipProductKey=0, the Deployment Wizard asks for the Windows 8 Consumer Preview product key, and the deployment will proceed like it should.

Get Windows 8 Consumer Preview and the ProductKey from Microsoft.

The first streamed application always asked for credentials:

Please enter your user name and password.

When you hit Cancel:

The launch was cancelled during authentication Error Code; 01-0003100E

The App-V client log (sftlog.txt) shows a 0A-00002002 error:

The client was unable to connect to an Application Virtualization Server (rc 1690900A-00002002)

Also sporadically this error pops up:

App-V NTLM credentials 0A-00002002

After a long search we’ve found that Windows Live Essentials was the cause of this issue. Uninstalling WLE and a reboot solved the problem.

Is this problem only caused by Windows Live Essentials? I don’t think so, because I’ve used WLE in combination with a variety of App-V clients with no issues at all.

Update: On the App-V forums a workaround was posted. Removing “livessp” from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages, solves this issue as well. Without the need to uninstall Windows Live Essentials.

After handing over all the lists on the application and current client side infrastructure, the first question that came is: “ok I see a lot of applications listed that are only installed on one machine, can you give us the machinenames?”.

ehm well, it should be possible…

in the ACT GUI you can find the computername if you click on the application, but I had to find a way to automate this

So I installed the SQL management studio express and dived into the ACT database.

Here is the SQL query to give you all applications installed on only 1 machine:

SELECT DISTINCT
Application_Computer_Count.computerCount,
Application_Computers_Query.machineName,
Application_Report_Complete_vw.AppName,
Application_Report_Complete_vw.AppID

FROM         Application_Computer_Count INNER JOIN
Application_Report_Complete_vw ON Application_Computer_Count.appID = Application_Report_Complete_vw.AppID INNER JOIN
Application_Computers_Query ON Application_Report_Complete_vw.AppID =Application_Computers_Query.appID

WHERE     (Application_Computer_Count.computerCount= 1)

ORDER BY
Application_Report_Complete_vw.AppName

What is more interesting is the following query, which will give you all applications installed on 1 pc marked with 1 or more issues:

SELECT DISTINCT

App_Issue_Counts.appID,
App_Issue_Counts.activeIssuesCount, Application_Computer_Count.computerCount,
Application_Computers_Query.machineName,Application_Report_Complete_vw.AppName

FROM         App_Issue_Counts INNER JOIN

Application_Computer_Count ON App_Issue_Counts.appID =Application_Computer_Count.appID INNER JOIN

Application_Computers_Query ON App_Issue_Counts.appID =Application_Computers_Query.appID INNER JOIN

Application_Report_Complete_vw ON App_Issue_Counts.appID =Application_Report_Complete_vw.AppID

WHERE     (App_Issue_Counts.activeIssuesCount >=’1′) AND (Application_Computer_Count.computerCount = 1)

ORDER BY
Application_Report_Complete_vw.AppName

another thing with ACT 5.6, was that it did not seem clear to me why none of the 16 bit applications were listed in the collected data

Luckily there is a way to find them with another SQL query, checkout (and credits to): http://www.theexperienceblog.com/2011/04/14/how-to-find-16-bit-applications-in-your-act-inventory

The last thing for now on ACT is that the collector is not capable yet to work with windows 7 sp1.

you need to import a sql script to make this possible

Here is the content of this script (the import can be done via osql.exe -E -i<thenameofthesqlscript> -S”<sqlserver\instance>” -d<dbname> :

INSERT INTO.[dbo].[OS]
([osID]
,[osName]
,[majorVersion]
,[minorVersion]
,[buildNumber]
,[servicePackName]
,[servicePackMajor]
,[servicePackMinor]
,[csdVersion]
,[productType]
,[suite]
,[publishedDate])
VALUES
(N’6.1.1′
,N’Windows 7 SP1′
,6
,1
,0
,N’Service Pack 1′
,1
,0
,N’Service Pack 1′
,0
,0
,’2011-02-22′)
GO

Also remember, the infliction point to test applications during a migration is:

COST of failure X PROBABILITY of failure > COST of testing

Of course I updated my Deployment Share after the upgrade. Updating a second time, and completely regenerate the boot images got my attention that I didn’t reimported the boot images into WDS.

After reimporting the new generated boot images with MDT 2012 my Task Sequences showed up and I was able to start deploying again!

So don’t forget to reimport your WinPE boot images after upgrading to MDT 2012!

Windows could not parse or process unattend answer file [C:\MININT\unattend.xml] for pass [windowsPE]. A component or setting specified in the answer file does not exist.

According to the MS forums this should be solved in MDT 2012 beta 1. So we upgraded to MDT 2012 beta 2, but unfortunately the error remains.

Deleting the <UpgradeData> node from the unattend.xml, like Michael mentioned, fixed the issue. Windows ThinPC deployed successful when this node was removed.