Skip to content

Releases: microsoft/FactoryOrchestrator

Factory Orchestrator 10.3.7

18 May 17:58
Compare
Choose a tag to compare
Pre-release
  • Fixed a bunch of accessibility issues with the Factory Orchestrator App.

Factory Orchestrator 10.3.6

06 May 07:37
c3a09af
Compare
Choose a tag to compare
Pre-release
  • Fixed a bunch of accessibility issues with the Factory Orchestrator App.

Factory Orchestrator 10.3.5

21 Oct 16:58
Compare
Choose a tag to compare
Pre-release
  • Fixed a bunch of accessibility issues with the Factory Orchestrator App.

Factory Orchestrator 10.3.3

10 Sep 02:58
Compare
Choose a tag to compare
Pre-release
  • Fixed a bunch of accessibility issues with the Factory Orchestrator App.

Factory Orchestrator 10.3.2

26 Aug 21:23
Compare
Choose a tag to compare
Pre-release
  • Fixed a bunch of accessibility issues with the Factory Orchestrator App.

Factory Orchestrator 10.3.1

27 Jul 22:09
Compare
Choose a tag to compare
Pre-release
  • Fixed a bunch of accessibility issues with the Factory Orchestrator App.

Factory Orchestrator 10.3.0

14 May 02:53
355783c
Compare
Choose a tag to compare

App bugs ➡️ App fixes!

image

  • A bunch of app UI improvements to ensure it is responsive and easy to use.
  • UWP apps page now shows app names in addition to AUMID, no more guessing what app is what.
  • The app is now "multi-instance". Launch it multiple times and connect to multiple devices simultaneously!
  • The service log now logs the first time a new client connects.

Other improvements include:

  • Fixed a bunch of app crashes.
  • Added new IpcLogLevel service setting, for detailed service logging. Setting this to "Debug" ensures every client API call is logged, with the IP address and command run. Yay for a (very basic) audit log📃!

As always, the service binaries are below, while NuGet packages and the PowerShell module are published to NuGet.org and PowerShell Gallery respectively.

Factory Orchestrator 10.2.0

11 May 09:20
Compare
Choose a tag to compare

🤷‍♂️ Lost 🤷‍♀️ a device? Let Factory Orchestrator find it for you!

The app, C# client library and PowerShell module now all support discovering Factory Orchestrator devices! No more scrounging around looking for your devices' IP addresses! app connect page

Other improvements include:

As always, the service binaries are below, while NuGet packages and the PowerShell module are published to NuGet.org and PowerShell Gallery respectively.

Factory Orchestrator 10.1.0

03 May 20:09
7986766
Compare
Choose a tag to compare

🪲 No one likes bugs (except entomologists), so we fixed a bunch of them for this release! 🪲

  • The service's install PowerShell scripts are now signed. Updated Get Started with details.
  • Support service configuration via /etc/FactoryOrchestrator/appsettings.json on Linux.
  • Fixed ResetService's "FactoryReset" option.
  • Fixed a frequent crash in the Windows service during service teardown.
  • Fixed Windows Device Portal support on Windows. If Windows Device Portal is configured to run with no authentication & HTTP enabled, it will work on any Port. See Get Started for details.
  • Fixed issue preventing service from running inside a container on Windows.
  • Fixed app crash when multiple ContentDialog boxes are shown.

As always, the service binaries are below, while NuGet packages and the PowerShell module are published to NuGet.org and PowerShell Gallery respectively.

Factory Orchestrator 10.0.0

20 Apr 17:09
792d05d
Compare
Choose a tag to compare

🐧 Factory Orchestrator 10.0.0 is here! 🐧

  • Why penguins 🐧? Factory Orchestrator 10.0.0 provides full Linux support for the Factory Orchestrator service! It can run as a systemd daemon on your Linux distro of choice! The service and any clients are fully cross platform (except for the app, which can only be installed on Windows for now). For example, you can run remotely execute tasks on the service running on Linux with a client running on Windows!
  • The service is now easily configurable via an appsettings.json file 📄.
  • We also added SSL encryption to the service 🔒, so data is no longer transmitted to clients in plaintext. The SSL cert can be manually provided as a service configuration option, or you can use our default cert for when you're just testing things out.

Other improvements include:

As always, the service binaries are below (now with Linux options), while NuGet packages and the PowerShell module are published to NuGet.org and PowerShell Gallery respectively.