Invite a developer to publish LOB apps to your Enterprise

1. Go to the Windows Store For Business page and sign in.
2. Under Settings, choose LOB Publishers.
3. Click Add on the Line-of-Business publishers page to invite a publisher.
4. Send the email invitation.

Enabling Line-of-Business Publishing in your Developer Account

1. Once an Enterprise sends the invitation to a publisher, they will receive an email notification with the invite.
2. Per the directions in the email, after you sign into the Windows Dev Center, go to your Account Settings.  The Dev Center dashboard just recently changed, so click on the gear icon in the upper left.
3. Click on Enterprise Associations on the left.  Any LOB Publisher invitations will be listed with the option to Accept or Reject.
4. Accept the invitation.

Submitting an App for LOB Publishing

1. Sign in to the Windows Dev Center, go to your Dashboard.
2. For an existing app, on the App overview page, under Action, click Update. -OR- If you are submitting an app for the first time, submit your app following the guidelines in App submissions. Be sure to completed steps 3 and 4 when you set app pricing and availability options.
3. Click on Pricing and availability section link.
4. On the Pricing and Availability page, look for Distribution and visibility (you may have to scroll down) and click Show Options to expand.
5. Change the drop-down from Retail to Line-of-business (LOB) distribution, and then choose the enterprise(s) who will get the LOB app. Only designated Enterprises will have access to the application.  It will not be discoverable to the general public in the Windows Store.
6. Next to Organizational Licensing click Show Options to expand.
7. Choose the appropriate licensing.Organizational licensing options apply to all apps, not just LOB apps:
   • Store-managed (online) volume licensing - This is required. You must select this item to make your app available as an a LOB app. By default, it will be selected. This won't make the app available to anyone outside of the enterprise(s) that you selected in Distribution and visibility.
   • Disconnected (offline) licensing - This is optional for LOB apps. Developers also have the option to select Disconnected (offline) licensing.  This allows apps to be installed on unconnected devices, without using the Store’s online licensing system. Organizations with unique security needs or device management tools often need this option to use an app. This allows IT departments to distribute the app using their distribution methods such as management tools or inject the app to company OS images. In other words, this option enables the Enterprises to “download” the app binary and entitlement to distribute them inside of the organization.
8. Save and continue with the App Submission process.

Important Things To Note

• UPDATE 5/10/16: Paid apps can now be distributed through the Windows Store for Business.  See https://blogs.windows.com/buildingapps/2016/05/05/sell-apps-to-organizations-through-windows-store-for-business/
• The app goes through the same certification process, and must comply with all Windows Store Policies.  If you don't want to go through the certification process, sideloading apps is an option but you cannot distribute sideloaded apps with the Windows Store For Business.
• UPDATE 5/16/16: There are certain app capabilities that require apps to be distributed through a Company Developer Account. If you are just getting started with having a developer account, be aware, you need to choose the appropriate account at the onset, as you cannot change to a different account time.

More Information

• Channel 9 Presentation from Build 2016: Enterprise Apps and Windows Store for Business
• Working with line-of-business apps
• Distributing LOB apps to Enterprises
• Distribute apps to your employees from the Windows Store for Business
• Distribute apps from your private store
• Assign apps to employees
• Distribute offline apps
• Sideloading

In reality, this is expected behavior if you are using a version of Windows 10 earlier than the November Update.  Windows Store for Business requires the Windows 10 OS to be at the November Update (Build 1511) or greater.

You check which build you are running by going to a command prompt and typing "WINVER".

If the version listed for your Windows 10 machine does not say "1511" or has a build number lower than 10586.xxx) then you will need to update that system in order to use the Windows Store for Business.

Full details, download and testing recommendations are available at the link above.

For Microsoft Application Virtualization 5.1 RTM, this hotfix package fixes the following issues:

• Issue 1
  The lock on the VFS folder was not getting released when the user logs off from the client service
• Issue 2
  Microsoft Office Click-to-Run apps can't be opened from SharePoint in Internet Explorer. Embedded Office Click-to-Run apps may crash
• Issue 3
  Press and hold (or right-click) app on taskbar, the app icon becomes blank.
• Issue 4
  Provide mitigation for apps which don't handle long paths correctly.
• Issue 5
  Enable users to create multiple instances of Office 2016 Click-to-Run apps.
• Issue 6
  Re-enable APP-V 5.1 Management server address "https://localhost:<port>/packages" and "https://localhost:<port>/packagesummary"
• Issue 7
  The Confirmparameter is ignored when the Groupsparameter is null for Grant-AppvServerPackage command. Use the newly added Forceparameter to avoid the "Confirm Action" dialog.

For Microsoft Application Virtualization 5.0 SP3, this hotfix package fixes the following issue:

• Issue 1
  Microsoft Office Click-to-Run apps can't be opened from SharePoint in Internet Explorer. Embedded Office Click-to-Run apps may crash.

NOTE: The 5.1 Client is backwards compatible with any 5.0 scripting.  There is no need to update your configuration XML files or scripts in order to run on the App-V 5.1 client.

SCRIPTRUNNER FEATURES

• ScriptRunner.exe is a new exe as part of AppV Client
• Script type is not limited to an executable.
  • Essentially, it can be anything that can be run from the "RUN" command in the start menu:
    • .EXE
    • .PS1
    • .BAT
    • .TXT
    • .CMD
    • .VBS
    • and more!

• Execution of multiple scripts
• Scripts running as non-admin work
  • No longer fails as an API call requiring Admin privileges
• Environment variables handled within scripts, not arguments for scripts

MULTIPLE SCRIPT SUPPORT

Multiple scripts are passed as arguments to ScriptRunner.exe and each script is executed in the order provided in the XML. Although the scripts are executed in order, the scripts may end up running concurrently if the "-wait" parameter is not specified. Each script is launched in a separate process, using Process.Start(). If it is important that one script completes before another executes, the "-wait" should definitely be used. Any parameters applied are per individual script and use "-AppVScriptRunnerParameters" as the delimiter to set those values. 

• If a script specifies the wait/timeout/rollback options, it will be applied explicitly for that script.
• If a script does notspecify the wait/timeout/rollback option, default values are be used: no wait, no timeout, no rollbackonerror.
• The wait/timeout/rollbackonerror values specified as a separate node applies to the parent “ScriptRunner.exe” process, and not to the individual scripts.

Although the examples above show MachineScripts, ScriptRunner.exe can be used for both MachineScripts and UserScripts.  Additionally, ScriptRunner.exe can be used for both the UserConfig.xml and the DeploymentConfig.xml.

These eight triggers can be used for both the MachineScripts and the UserScripts:

• <AddPackage>
• <RemovePackage>
• <PublishPackage>
• <UnpublishPackage>
•  <StartProcess>
• <ExitProcess>
• <StartVirtualEnvironment>
• <TerminateVirtualEnvironment>

ERROR HANDLING

Any scripts and parameters used with ScriptRunner.exe is that they are they are tested in the Console and any errors corrected before everything is committed to the DeploymentConfig.xml or the UserConfig.xml.  Any errors and messages are displayed in the Console.

The AppV>Operational Event log on the Client will record the following:

• Error in input parameters to ScriptRunner.exe
• Error in the actual script, no "rollbackonerror" setfor script that failed, execution continues and will eventually report success.
• Error in the actual script, "rollbackonerror" set for script that failed, execution stops and error recorded

Everything you need to know about moving to App-V 5.0 is available in the blog series that begins here on the Official App-V Blog.  However, below are some answers to questions you are probably asking right now.

Moving? Don't you mean Upgrading?

No, we definitely mean moving or more accurately, migrating, to App-V 5.0.  There is no direct upgrade since the database, servers, and client are all new and different.

So, I have to resequence everything?

Many of the packages you sequenced with App-V 4.6 can be converted to App-V 5.0 packages. Please note the keyword "many" was used and not "all".  You will need to account for some time in testing applications to see if the conversion was successful.  Some applications may need to be resequenced and it is best to allow your organization the planning time to address these potential issues.  The TechNet documentation for converting packages is here, but Premier Field Engineer, David Falkus, also has an excellent article with screenshots and examples.

We have hundreds of applications! It will take us forever to get that done!

Two things to remember here: 1. Don't Panic.  2.  Migration

The conversion process of 4.6 packages is all done with PowerShell and this means you can batch convert packages.  A vast majority of your package conversions may be knocked out with just a few Cmdlets.  See the Advanced Conversion Tips section of this article for more details.

App-V 5.0 has a Migration Mode allowing the App-V 5.0 client to be side-by-side with the App-V 4.6 SP2+ client.  This means you can convert your packages, take the time to test them, and then easily publish the 5.0 package and remove the 4.6 package for each application as you certify them.  There is no stress-inducing mega-change from all 4.6 to all 5.0.

We use Citrix with App-V so does that still work with App-V 5.0?

App-V 5.0 still works with Citrix.  You should start with this White Paper, but know that the paper is a guideline and Citrix has released documentation that supersedes any versions of their products mentioned in the paper.  Depending how you use Citrix for application delivery, disk management, or profile management, you may need to be at more recent versions of their products.

If App-V 4.6 is still supported until 2020 can we use it on Windows 10?

UPDATED 10/15/15: The App-V 4.6 support lifecycle was not modified to support Windows 10 and beyond.  Customers should consider and treat App-V 4.6 as unsupported on Windows 10 forward and a "use at your own risk" situation.

App-V 5.0 will be supported on Windows 10, though there will most likely need to be a hotfix or Service Pack that completes that compatibility. Remember, App-V is not an OS compatibility tool.

We have an application that was running great in 4.6 and now it won't work in App-V 5.0.

There is always that possibility that an application that worked in 4.6 doesn't convert or doesn't sequence in App-V 5.0.  You may need to open up a ticket with Microsoft Support.  Before you open that ticket be aware of the following:

• Microsoft 3rd Party software and App-V Support Policy
• Are you on the latest version/patch of the software you need virtualized (remember, App-V is not an OS compatibility tool)?
• Are you getting an error from the software or from App-V?  If it is from the software, have you checked with resources from that vendor?
• Does it work locally installed?  If so, do you have reason that it needs to be virtualized?
  
  • If your answer is "we virtualize everything", weigh the factors of "is it more important that this works or that it is virtualized" as well as "does the vendor support this product virtualized".
• UPDATE 10/15/15:  The App-V 5.1 sequencer has even more improvements in the converter.  If you had a package that did not convert successfully before, you may want to try again with the 5.1 sequencer.

Good luck with your migration to App-V 5.0.  Remember to review the documentation on TechNet before beginning your migration, but I hope this helped answer some immediate questions.

I'm looking forward to writing them, so I hope you look forward to reading them.

In my experience as a Senior Support Escalation Engineer I have seen that IT groups within Enterprises often reflected the separation of products or processes.  This totally makes sense, and I get it, the specialization helps many organizations.  Unfortunately, I have also seen where this specialization leads to each group being in their own "castle" where communication and collaboration only happens if absolutely necessary.  The integration of System Center 2012/2012 SP1 components and connection to other technologies in your environment means its time to form a new team!

Think about it...Superman and Batman together are the "World's Finest"!  Captain America, Iron Man, Hulk are all great on their own, but together they form "The Avengers!" Form your own team of IT Super Heroes with System Center 2012.

Now, the obvious place to start forming your team is one member for each component of System Center 2012.  That's good, now think more strategically. Think deeper.  System Center 2012 SP1 does waaaaayy more than it ever it did in previous versions. Let's look at Virtual Machine Manager just for example:

 It looks like right away our team could use a few more members.  The networking capabilities of SCVMM 2012 on top of Hyper-V 3.0 are amazingly powerful and complex.  Let's get a Networking specialist on our team!

SQL? Everything in System Center 2012 SP1 touches SQL at least once.  We'll need someone with SQL powers!

Application packaging and deployment with Server App-V?  Oh yeah, let's get someone who really knows the right way to install and deploy software so it is packaged up correctly.

Service Templates? That depends on your Enterprise since creating them can be very complex or very easy depending on if you have the three team members above.  They might be their own team within a team.

With just one component there are potentially 3-4 more members needed for your IT department's team.  What about the other System Center 2012 SP1 components?  System Center Configuration Manager is another huge product and depending on your Enterprise it may often team-up for adventures with App-V.  Each new component has new functionality that reaches out to other technologies like Active Directory, Exchange, SharePoint, and more.  Your team should reflect the capabilities and integration of these products as well.

These links will help you discover the new capabilities of System Center 2012.  The "Planning" sections will provide insight into assembling your new team of System Center Heroes!

What's New in System Center 2012 https://technet.microsoft.com/en-us/library/jj649385.aspx

App Controller Deployment Checklist https://technet.microsoft.com/en-us/library/hh709025.aspx

Configuration Manager 2012 https://technet.microsoft.com/en-us/library/gg682041.aspx

Data Protection Manager https://technet.microsoft.com/en-us/library/hh758173.aspx

Key Concepts for Operations Manager https://technet.microsoft.com/library/hh230741.aspx

Orchestrator Architecture https://technet.microsoft.com/en-us/library/hh420377.aspx

Planning for Service Manager 2012 https://technet.microsoft.com/en-us/library/hh495542.aspx

Virtual Machine Manager Overview https://technet.microsoft.com/en-us/library/gg671827.aspx

Well, the button is gone. The term “Monitoring” is essentially gone, except to us “old school” Sequencing Engineers.  But Monitoring is still occurring with the 4.6 SP1 Sequencer.

Monitoring of an application installation occurs in two of the workflow phases: “Installation” and “Configure Software”. Another way to look at it is that as soon as you click “Next” from “Package Name” phase, you’ve started Monitoring.  In the Installation phase, the Sequencer monitors where the files are laid down, what registry changes are made, redirects files to the Virtual Files System, and keeps track of changes to the Sequencing VM.  After selecting “I have finished installing” and clicking “Next”, Monitoring stops.  The user sees that the Sequencer is “Collecting System Changes.”  The Sequencer processes any reboots at this stage.  Next, before going to the Configure Software phase, Monitoring starts back up again.  This automatically directs the Sequencing Engineer to the best practice of running the applications while Monitoring. At then end of the Configure Software phase and you click “Next” the Sequencer stops Monitoring for the second and final time.

TIP:  Since Monitoring is still occurring in the Configure Software phase, you can still make registry changes or run scripts in this phase.

So, to you Sequencing veterans, there is no need to worry about not seeing that button anymore.  The Sequencer guides you through the phases and begins Monitoring at the appropriate time.

The reporting is accurate for the information that is available in the SQL Database.  The problem is that all the available information may not have reached the SQL database.  The application usage information is only reported from the App-V client during a Publishing Refresh.  If your client is set to refresh "On Login" and you are someone like me that only locks their computer and doesn't log off, then the information will never be sent.

In the App-V Client machine's registry, the location of the XML file that tracks a client usage can be found in HKLM\Software\Microsoft\Softgrid\4.5\Client\LastCacheFile\<GUID>.XML.Everytime an application is launched, this XML file is written to with the following information:

- <REPORT_DATA_CACHE>
   - <APP_RECORDS>
          <APP_RECORD Name="WordViewer" Ver="11.0" Server="sblab—mqmt" User="SBLAB\Steve"
          Launched=”7/27/2011 2:27:54 PM” Shutdown=”8/24/2011 12:49:16 AM" />
          <APP_RECORD Name="WordViewer" Ver="11.0" Server="sblab—mgmt" User="SBLAB\Steve"
          Launched="8/24/2011 12:50:39 AM" />
   </APP_RECORDS>
</REPORT_DATA_CACHE>

When a Publishing Refresh happens, the data is uploaded to the SQL database and the APP_RECORD tags are cleared.

So, you need the data, users are not logging off, Publishing Refresh isn't happening because no one is logging off.  What should you do?  Provider Policies are the answer! Provider Policies can manage the Desktop Clients in your environment and force a Publishing Refresh at designated intervals. This in turn will upload the APP_RECORDS information from the local <GUID>.XML.

Wait, you've done all that and you are still not getting the data? Well, there are a few more possible explanations: users may not be part of the Provider Policy Group Assignment, or your environment has a 4.6 client against a 4.1 server.  For Provider Policy Group Assignments, take a look at my Ultimate Guide to Licensing and Provider Policies on the App-V Blog.  If your environment has a 4.1 Server in place, read the article by my colleague, Steve Thomas, for an explanation. Finally, prior to the App-V 4.6 SP1 client, if the XML file grows larger than 64k or has an empty package field in the registry, the data will not upload. The App-V 4.6 SP1 Client corrects this issue.

UPDATE: Another cause of inaccurate reporting may be a mismatch of the "Version" field of the application properties in the App-V Management Console versus the "Version" listed in the application's OSD file.