Well life has been getting in the way but things have not
been standing still. You can now download the AR.c framework and try it out for
yourselves with 10 Community Package Iteration licenses for free.
All you need to do
is download the 3 Installation components, and Guide PDF, then follow the
videos on the download page for a quick overview of the Installation and
Configuration requirements. You can find various videos demonstrating how you
might use the components on the Software Pages of the Website.
Also there is a new integration option available which I’m
excited about. In the AR.c console settings there is now a new tab called Release
You can see that the 1st new option added is the
Release Path. If you add the path to your live content directory the AR.c
client will copy the package here when you finalise the application and place
it into the Released Phase.
Also (and currently in experimental Testing) there is integration
with App-V Scheduler (If you have not seen this you should head over to the
website and take a look). When this option is selected and you Release a
package in the Client you will be prompted with a couple of extra forms.
The 1st form
will ask a couple of questions. The 1st is if this package is
replacing a currently released package (e.g. and Adobe Reader Update. A new
Java release). The 2nd question asks if this package requires a
connection group for it to work (e.g. it needs Java). When you choose Yes to
the 1st Question the form will open as below and allow you to
browser the Release Content path to find the package that will be replaced. It
will then populate the Connection Group List with all CGs that have the “To Be
Archived” package in them. If you choose to update CGs AR.c will back up the current
CG and replace all references to the old package with the correct settings for
the NEW one. This will allow App-V Scheduler to deploy the appropriate
connection group settings when it runs its package refresh. AR.c will also add
an Exclusion item to the App-V scheduler.xml file that will, in a future
release of App-V Scheduler, mean that App-V Scheduler will skip the archived
package completely from being deployed.
The 2nd Question will open the “Create Connection
Group” form and you can browse the file system and create the appropriate
connection group settings needed.
If you watch this space I will produce a “Better Together”
video soon to demonstrate the end to end release of a package from Source Media
to Deployed using App-V Scheduler.