{"id":12004,"date":"2023-05-19T06:34:40","date_gmt":"2023-05-19T13:34:40","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=12004"},"modified":"2023-05-19T06:34:40","modified_gmt":"2023-05-19T13:34:40","slug":"version-14-5-released","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/version-14-5-released\/","title":{"rendered":"AlwaysUp 14.5: Smarter Starts for OneDrive, Dropbox and More"},"content":{"rendered":"
\"AlwaysUp<\/div>\n

We released AlwaysUp<\/a> version 14.5 on May 12.<\/p>\n

This significant update makes life easier for customers managing servers that run multiple copies of Dropbox, OneDrive and other applications. It also revises the shutdown logic for Dropbox, which now runs 7 or more instances of itself to implement file synchronization.<\/p>\n

Let’s review the enhancements in detail.<\/p>\n

On startup, AlwaysUp can now close your program in the Session or Account only<\/h2>\n

Some applications fail when you try to run multiple instances of them. For example, if you’re running a web server on a specific network port<\/a>, starting a second copy will fail because the port is already in use.<\/p>\n

For “single-instance” programs like that, you can instruct AlwaysUp to stop all running copies before it starts a new instance of your application. Clearing out those old processes will ensure that your application starts properly under AlwaysUp — automatically and without your intervention.<\/p>\n

But while that capability is useful, we found it a bit overzealous in some circumstances. That’s because some applications (like OneDrive) allow you to run several instances in different accounts without issue. For those apps, AlwaysUp can start its own copy without any interference from the other copies already running. That is, AlwaysUp does not need to stop all<\/span> the other running copies.<\/p>\n

To accommodate those applications, AlwaysUp 14.5 introduces a new option to only stop the processes running in the same Windows session or account. It’s available under the “stop copies” setting on the Startup<\/b> tab when adding or editing your application:<\/p>\n

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

When to stop your application in the session or account only<\/h3>\n

Let’s illustrate the power of the new option with an example.<\/p>\n

Suppose you manage a Windows Server machine. You’ve installed OneDrive as a Windows Service with AlwaysUp and it’s using Bob’s Windows account (on the Logon tab). It’s not yet running though.<\/p>\n

Alice logs in to the server via remote desktop. As she does so, Windows launches OneDrive automatically on her desktop.<\/p>\n

Next, you log in to the server to start the OneDrive entry in AlwaysUp. Here’s where the new option makes a difference.<\/p>\n

In previous versions of AlwaysUp, Alice’s copy of OneDrive would be terminated when you start the OneDrive service. Indeed, AlwaysUp would stop all copies of OneDrive running on the server, regardless of where they’re running.<\/p>\n

However, with the new option that only stops copies of OneDrive in the same session or account, Alice’s OneDrive will not be terminated. That’s because AlwaysUp runs OneDrive in a different user account<\/b> (Bob’s) and in a different session<\/b> (Session 0). As a result, Alice’s OneDrive will not be affected by the instance of OneDrive started by AlwaysUp.<\/p>\n

Note that the new option only makes sense for applications that support running multiple instances in different sessions. If only a single instance of your application must run across all sessions and accounts, you should not check the box.<\/p>\n

Updates for OneDrive and Dropbox Windows Services<\/h3>\n

Going forward, the Application Advisor<\/a> will install Dropbox and OneDrive with the stop-copies setting restricted to the session or account.<\/p>\n

And if you’ve already installed Dropbox or OneDrive and would like to take advantage of the new setting, simply edit your application in AlwaysUp and check the box on the Startup tab.<\/p>\n

Smoother termination of 7+ Dropbox processes<\/h2>\n

These days, a single run of Dropbox can spawn many copies of Dropbox.exe. You can see the plethora of processes in Microsoft’s Process Explorer<\/a>:<\/p>\n

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

Earlier versions of AlwaysUp were optimized for the good old days — when Dropbox launched only 3 copies of itself<\/a>. Now AlwaysUp 14.5 works with the latest 7-process arrangement — and goes beyond that to prepare for a world where Dropbox launches to 9, 13 or even more executables.<\/p>\n

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