This file is the exported task scheduler job. These files are necessary for the unattended license import. The necessary files can be downloaded from my GitHub: I wasn’t aware that a few bugs have been fixed over the years, so it was a pleasant surprise to find a really useful log. If a daily task (1) has an expiration date just after the schedule (2), it will only run once.Īn easy option to log something in PowerShell is Start-Transcript. The daily schedule is executed once and due to the expiration date, a Next run time won’t be scheduled (3). So, I created a daily schedule (1) but added an expire date (2) just after the schedule. The one time option didn’t work with the System account for some reason. Importing a license doesn’t happen very often, so I needed an option to create a trigger which is executed once. The task will be executed with administrative privileges. On this one there may not be a dedicated service account. I used the System account, because I want to be able to export the task and reuse it on another system. ![]() I solved the administrative executed by using the System account. The PowerShell script needed to be executed with administrative privileges and I needed some kind of logging, but I did want to solve this using the out of the box options provided by PowerShell. Knowing that it was possible I only had to solve two other ‘problems’. So my first thought was, that I could easily achieve an unattended import using the Windows Task Scheduler. I created a lot of PowerShell scripts in the past, which had to be executed automatically. If I can not be sure, whether I need to restart a server instance, I just need to make sure, that I can do this in an unattended way during the night and log this. Maybe the restart could be prevented by importing the license multiple times, but using a different server instance each time? I haven’t tested this approach but went down another one. Unfortunately, the images are missing, so this turned out to be a dead end. Thank you to all those, who taught me the above along the way. Go to PowerShell and import it then it does not need restarting: ![]() It is possible to install a license file without restarting the service tier: Update License without rebooting the service tier ![]() Using I got a hint that it could be done, without restarting the servers. Searching the internet for an answer did only return an old, and probably deleted blog post. So, do we need to restart all server instances except the one we used for importing the license file, because the warning mentions other services? Asking around my colleagues I received the reply, that I should restart all server instances. C:\run > Import-NAVServerLicense -LicenseFile c:\run\my\license.flf -ServerInstance NAV WARNING: Importing a license file requires a restart of other services using the same database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |