App-V | Enforce Licenses Policies

If you open the Properties of the Default Provider under Provider Policies, you will find the Licensing tick box under the Provider Pipeline tab. In order to activate the Application Licenses that you have created (Unlimited Licenses, Concurrent Licenses, Named Licenses), you need to check the Licensing tick box. Select Enforce Licenses Policies from the drop down menu like the picture below. Then link all the application with the licenses you created accordingly.

Important Note:
If you select <none> for the Application Licenses Group like picture below, all your clients/user will not be able to launch the application. A non-authorisation message will prompt when user launch the application.

Reuse Your Sequenced Application

Do you know that you can reuse the sequenced application for another App-V environment? In order to do that, you need to modify the App-V Management Server name in the .osd file. Search CODEBASE HREF="RTSP:// and replace the parameter with your full FQDN App-V Management Server name. Then import the sequenced application to the new App-V Server.

I found this extremely useful when comes to POC, I can reuse my sequenced applications again.

OnSearchComplete - Failed to end search job. Error = 0x80244007. Scan failed with error = 0x80244007

I bumped into this error today and I was scratching my head to troubleshoot the error. I have done the WSUS client diagnostic test, turned off the firewall, make sure there are no GPO overwriting the WU server.

Finally I found a similar case which discussed in the forum. The discussion says that the Windows Update ”Target Group” is enabled and corrupted. Therefore, I refer the registry (HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate) of those good computers and do a comparison. I found out that those good computers doesn’t have the “Target Group” registry key and hence I delete it from the bad computers. Bravo~!!! it works afterward. =)

Lastly, I found out that those bad computers were managed by Windows Intune. Windows Intune did patch management and this is the reason why those computers failed with the error 0x80244007.