解决了

将windows 2019应用程序许可证服务器从Hyper-V迁移到AHV集群

  • 2020年12月28日
  • 4回复
  • 210的浏览量
J
  • JosephW
  • “航行者”号
  • 2回答

所以伙计们，我有一个flexlm许可证服务器运行Windows server 2019，我试图使用移动迁移到我的AHV集群。我尝试迁移它一次，它炸毁了许可证服务器，因为我猜它建立了一个独特的机器ID使用磁盘和CPU ID。关于如何在移动中克隆这个，所以当它遇到FlexLM和其他许可证守护进程都不知道的想法?

图标

最佳答案Alona2021年1月5日02:25

Hi JosephW,<\/p>

Have you tried asking the license server software vendor about this? Explain the situation (hypervisors migrations) and ask for options. I\u2019m sure they have come across a similar scenario with other customers. Based on the options they provide we could work something out. It is possible that they may give an easy or an easy\u2019ish way out altogether.<\/p>","className":"post__content__best_answer"}">

查看原始
So guys I\u2019ve got a flexlm license server running Windows Server 2019 that I am trying to use Move to migrate into my AHV cluster.\u00a0 I tried migrating it once and it blew up the license server since I guess it builds a unique machine ID using a disk and perhaps CPU ID. Any idea on how to clone this in Move so when it comes across FlexLM and other license daemons are none the wiser?<\/p>","quoteUsername":"JosephW","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
本主题已关闭供评论

4回复

B
Userlevel 2
徽章 + 12

我觉得你做不到。您可以使用新的Machine ID或不同的CPU ID申请新的许可证吗?

I don\u2019t think you can manage that. Can you apply for a new license with a new Machine ID or a different CPU ID?<\/p>","quoteUsername":"badonders","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
J

这正是我试图避免的，因为它会招致停机时间。在这一点上，我不妨从头开始构建一个新的许可证服务器，以消除Move的任何优势。

That's exactly what I\u2019m trying to avoid as it would incur downtime.\u00a0 At that point I might as well just build a new license server from scratch negating any advantage of Move.<\/p>","quoteUsername":"JosephW","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
B
Userlevel 2
徽章 + 12

没有什么是可能的。据我所知，你可以保留MAC地址的许可目的。其他的都是新创建的。在更改管理程序时，这是一个缺点。

Not anything is possible. As far as I know, you can preserve the MAC address for licensing purposes. Everything else is newly created. That is a disadvantage when changing hypervisors.<\/p>","quoteUsername":"badonders","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Alona
排名
Userlevel 6
徽章 ＋5

嗨JosephW,

你试过询问许可服务器软件供应商吗?解释情况(管理程序迁移)并询问选项。我相信他们在其他客户身上也遇到过类似的情况。根据他们提供的选择，我们可以解决一些问题。他们可能会给出一种简单的或勉强的解决办法。

Hi JosephW,<\/p>

Have you tried asking the license server software vendor about this? Explain the situation (hypervisors migrations) and ask for options. I\u2019m sure they have come across a similar scenario with other customers. Based on the options they provide we could work something out. It is possible that they may give an easy or an easy\u2019ish way out altogether.<\/p>","quoteUsername":"Alona","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

Baidu