Startup Issue with Application Deployment - License needs to be reapplied after every server reboot

System Information

Field Value
Operating System Windows - Windows Server 2022 on x86_64
Product AMPService ‘Phobos’ v2.6.0.12 (Mainline)
Virtualization None
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

I have an HP ProLiant DL380 G10 w/ Windows Server 2022 Standard Desktop Experience installed. The server has two NIC Teams with Static IP Address and Static MAC Address. Every time I reboot the software seems to invalidate the license and forces me to reactivate. Please assist.

Reproduction Steps

  • Activate License in console
  • Reboot the server
  • Check the system, find that I have to Reactivate
  • Repeat the process

Boop reply from a moderator!

After some time and research I was able to resolve the issue.

There were a couple issues that AMP didn’t seem to like:

  1. Native NIC Teaming (Also called Bonding) in Windows Servers doesn’t preserve the MAC Address between reboots. The NIC Team takes the MAC Address of whatever NIC comes online first. Since the license is tied to the Network IDs and the MAC Address is the root of that, having it change is problematic.
  2. My machine was originally used for VMWare and has 3 NICs, each with 4 Ports. I had multiple NIC Teams that I planned to use for different things.

Here’s the Resolution that worked for me:

  • The AMP Service needs to be set to Automatic (Delayed Start). While I didn’t change this, it’s important to note that it is part of the solution. It installs this way by default for a reason. Don’t change it.
  • The MAC Address on the NIC Team needs to be set using Powershell. For some reason changing the settings in the Windows UI doesn’t always work as expected. In order to gaurantee it works you should do it using powershell:
  • Example: Set-NetAdapterAdvancedProperty -Name “Network Team” -DisplayName “MAC Address” -DisplayValue “0000A6123456”

In this example, 0000A6 is an OIU for General Network and should be safe to use as it won’t be on any network device on your network.

  • For me, consolidating everything down to a single team and managing only one team helped solved this problem as well as a couple of issues that were happening on the network layer.

Hope this helps!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.