Archive

Archive for the ‘App-V’ Category

App-V package not streaming to client using ConfigMgr

April 28, 2011 Leave a comment

 

If you get the following error, or something similar, when trying to deploy an App-V package using ConfigMgr there could be a variety of reasons for it’s cause.

Failed to instantiate Updates UI Server
{2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a

Maybe the “Advertised Programs Client Agent” found within the ConfigMgr console in “System Center Configuration Manager – Site Database – Site Management – SITECODE – Site Settings – Client Agents” does not have the appropriate settings (see the screenshot).

image

Maybe IIS is not configured properly on the DP the client is trying to pull from.

Maybe the package is not located on the DP and you have protected sites configured.

Or, as it was in my case, maybe somehow the Windows Firewall is on and does not have any exceptions so it is blocking the traffic.

The bottom line is that it is not necessarily a client-side issue and I would suggest looking for configuration mistakes – we are all human after all.

App-V Recipe – SCCM 2007 Console with App-V 4.6 RTM

March 10, 2011 Leave a comment

– Not all functions may exist within the console if running on x64 when sequenced on x86.
– I am not claiming that this is necessarily the best way, or only way to build the package.
– This recipe was done on a Windows 7 SP1 x86 VM with the App-V Sequencer installed on Hyper-V. Nothing more.
– The folder structure used is what I use in production and are only suggested locations.
– I use SCCM with App-V integration.
– I use “B:\” as the App-V drive. You can use whatever you would like.
– The final App-V package was tested with SCCM for both cached and streaming successfully.

Instructions:

1. Before starting do the following if you have not already:
a. On a device with the SCCM Console already installed locally export the following registry keys and store them in \\SERVERNAME\install\Packages\Microsoft\SCCM Console\2007 SP2\R018_Custom Actions
i. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{6de537a5-7a1c-4fa4-ac3a-1b6fc1036560}]
ii. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\FX:{a77b774c-ce32-4ab0-982a-6bb3c078e5c1}]
iii. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConfigMgr\AdminUI\QueryProcessors\WQL]

2. Join the VM to your domain

3. Reboot

4. Log in as the local administrator

5. Add your domain account as a local administrator

6. Logoff

7. Be certain that your domain account has access to the SCCM console (this has to be set in the console by a SCCM administrator)

8. Logon with your domain account

9. Create a folder in “B:\” named “SCCM.001”

clip_image002

10. Navigate to \\SERVERNAME\install\Packages\Microsoft\SCCM Console\2007 SP2\R011_Original Source Media and be sure you have access

11. Launch the App-V sequencer from the “Start Menu”

12. Click on “Create a Package”

clip_image004

13. Type “SCCM_Console” in the “Package Name” field and click “Next”

clip_image006

14. Click “Begin Monitoring”

clip_image008

15. Select the “SCCM.001” folder in “B:\” and click “OK”

clip_image010

16. The sequencer will get ready for the installation

clip_image012

17. The sequencer will let you know when to begin the application installation

clip_image014

18. Run “splash” from \\SERVERNAME\install\Packages\Microsoft\SCCM Console\2007 SP2\R011_Original Source Media

clip_image016

19. Click on “Configuration Manager 2007 SP2”

clip_image018

20. Click “Next”

clip_image020

21. Click “Next”

clip_image022

22. Accept the EULA and click “Next”

23. Click “Next”

clip_image024

24. Click “Next”

clip_image026

25. Type the name of your primary site server and then click “Next”

26. Click “Next”

clip_image030

27. Click “Begin Install”

clip_image032

28. The console will install

clip_image034

29. Click “Next”

clip_image036

30. Click “Finish”

clip_image038

31. Launch “adminconsole.msc” from “C:\Program Files\Microsoft Configuration Manager Console\AdminUI\bin”

32. In the console expand “Site Database”, expand all features, and click on them

33. Close the SCCM console

34. Import the three registry keys from \\vdawwsccm1\install\Packages\Microsoft\SCCM Console\2007 SP2\R018_Custom Actions

35. In the App-V sequencer click “Stop Monitoring”

clip_image042

36. The changes will be applied

clip_image044

37. Click “Next”

clip_image046

38. Expand “Virtual Machine Manager” and click on “Shortcuts”

39. Right click “ConfigMgr Console” and click “Edit”

clip_image048

40. Click on “Change Icon…” and browse to “C:\Program Files\Microsoft Configuration Manager Console\bin\i386\” and select “SETUP.EXE”

clip_image050

41. Select the proper icon

clip_image052

42. Click “Save”

clip_image054

43. Right click “ConfigMgr Documentation” and click “Edit”

clip_image056

44. Click on “Change Icon…” and browse to “C:\Windows” and select “hh”

clip_image058

45. Select the proper icon

clip_image060

46. Click “Save”

clip_image062

47. Click “Next”

clip_image064

48. Click “Launch All” and verify that all of the applications open

clip_image066

49. The applications will launch (close each one when done)

clip_image068

50. Click “Next”

clip_image070

51. The application sequencing will finalize

clip_image072

52. Click “Finish”

clip_image074

53. Click “Package – Save”

clip_image076

54. Save in “B:\SCCM.001” as the default name

clip_image078

55. The project will save

clip_image080

56. In the “Deployment” tab make the application available to all Operating Systems

clip_image082

57. Save and close the App-V sequencer

58. Copy “B:\SCCM.001” to \\SERVERNAME\install\Packages\Microsoft\SCCM Console\2007 SP2\R019_App-V

App-V Sequencing Best Practices

It is amazing how much better things work with best practices…for example Microsoft Word does not error upon launch.

http://support.microsoft.com/kb/932137/

Categories: App-V
%d bloggers like this: