{"id":12677,"date":"2024-10-11T06:56:20","date_gmt":"2024-10-11T13:56:20","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=12677"},"modified":"2024-10-11T07:12:35","modified_gmt":"2024-10-11T14:12:35","slug":"version-15-5-released","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/version-15-5-released\/","title":{"rendered":"AlwaysUp 15.5: Advanced Support for PowerShell, OneDrive, and more"},"content":{"rendered":"
\"AlwaysUp<\/div>\n

After months of coding and testing, our team published AlwaysUp<\/a> version 15.5 on October 4, 2024.<\/p>\n

Version 15.5 makes it easy to install your PowerShell scripts as services. Beyond that, it delivers timely fixes and improvements to address real-world issues faced by our customers. Indeed, this work is all part of our ongoing commitment to making sure that AlwaysUp runs your applications so smoothly that you forget it’s even there. \ud83d\ude42<\/p>\n

Let’s dig into the details.<\/p>\n

Install your PowerShell script as a Windows Service, with ease<\/h2>\n

We’re pleased to announce that the easy-to-use Application Advisor<\/a> now supports PowerShell scripts!<\/p>\n

To use this new feature, start the Application Advisor (by selecting Application > Advisor<\/b> from the menu) and choosing PowerShell<\/b> from the list of applications:<\/p>\n

\"Choose<\/a><\/div>\n

Afterwards, AlwaysUp will ask you to pinpoint the PowerShell script you’d like to run as a service:<\/p>\n

\"Enter<\/a><\/div>\n

Click Next<\/b> and follow the straightforward prompts to complete the process. In a few seconds, you’ll have a new Windows Service that starts your PowerShell script at boot and runs it continuously in the background.<\/p>\n

Improvements for running OneDrive as a Service<\/h2>\n

Even though some our customers on Windows Server are struggling to run OneDrive as a service in Session 0<\/a>, we’re still making improvements for OneDrive. There were a couple notable changes in version 15.5:<\/p>\n

    \n
  1. \n

    When installing OneDrive with the Application Advisor, we no longer recommend stopping OneDrive by running the executable with the “\/shutdown”<\/nobr> flag. It turns out that running that command could lead to an ill-timed (and lengthy) automatic update — just when you want the program to quit quickly.<\/p>\n

    So with that understanding, it’s best for AlwaysUp to close OneDrive by sending it the standard WM_CLOSE message<\/a> — as it does for other applications. If you have an existing OneDrive configuration that uses the custom stop command (“OneDrive.exe \/shutdown”), please feel free to remove it.<\/p>\n<\/li>\n

  2. \n

    Even though it’s running in the background and you can’t see it, OneDrive may occasionally try to get your attention. And when that happens, OneDrive will probably be stuck, not synchronizing your files.<\/p>\n

    AlwaysUp 15.5 will try to inform you whenever OneDrive is waiting for your input. For example, if OneDrive forgets your credentials and would like you to sign in again, you may see this message in the activity window:<\/p>\n

    \"OneDrive<\/a><\/div>\n

    We’ll continue to improve this kind of detection in future releases — and automatically take action whenever it makes sense.<\/p>\n<\/li>\n<\/ol>\n

    Other fixes & improvements<\/b><\/h2>\n