INTUNE – Intune and Autopilot Part 1 – The Blueprint

The previous blog posts were all about packaging and manual deployment of MSIX packages. As promised we will start covering the different scenarios around deploying these packages.   With Modern IT in mind, our first scenario is cloud based, first Intune and Azure based deployment is focused. So why Azure, Intune and Autopilot? With Microsoft…

0

App-V Sync not working if Device Guard is enabled

Hi there, In September 2017 Rollup there where some changes to Device Guard which increase teh Overall security of your System. As a result the way how our SyncAppVPublishingServer.exe does it work no longer works. As a result you see that the Sync Process is crashing – no further notice (except that you don’t have…

0

MSIX – The MSIX Packaging Tool – Using the first package

In our previous blog post we created our first MSIX package, now it’s finally time to  install the MSIX package, and launch the application! We will not go into the details of the different deployment scenario’s. We’ll leave that for a later blog post. Main goal is to install the package with a normal user…

0

MSIX – The MSIX Packaging Tool – signing the MSIX package

So, as we noticed a certificate is needed to sign the MSIX package. Especially for those with a history in packaging, signing an AppX/MSIX-package could potentially be the first time you’re ever faced with the requirement. So…. Why should we sign packages? Signing code or binaries nowadays is common practice. Starting with executables, drivers and…

0

App-V Auto Sequencing – Retrieve the password

Connecting to the Auto Sequencer VM can be done using the Connect-AppVSequencerVM cmdlet   If you want to use a remote desktop connection to the machine, or just open it up from hyper-V, you’ll need the Password. The Password is stored in “C:\ProgramData\Microsoft Application Virtualization\AutoSequencer\SequencerMachines” in a file named after the machine, so in my…

0