From: Guy <guy@britewhite.net>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Solidworks 2020 refuse to help me
Date: Mon, 14 Dec 2020 06:51:59 +0000 [thread overview]
Message-ID: <D815C75C-CEE8-4C84-9410-83BB6383768D@britewhite.net> (raw)
In-Reply-To: <CABK=EDz7sWGPoNVqSBrpMmuwVucKE91T19OdzVOP22bson+JqQ@mail.gmail.com>
Have you tried selecting different CPU from the drop down list? Many cam detecting system are checking on the CPU type.
---Guy
(via iPhone)
> On 14 Dec 2020, at 06:47, David Martin <damart.vidin@gmail.com> wrote:
>
> Hi,
> Yes 300 proxmox servers with one virtual machine on each.
>
> Solidworks don't have a solution.
>
> Thank you.
>
> Best regards
>
>
>> Le jeu. 3 déc. 2020 à 17:41, Roland <devzero@web.de> a écrit :
>>
>> if solidworks is detecting proxmox and refusing to run on that, then
>> there is nothing proxmox community can do for you (besides recommending
>> using software which does not restrict users in such a way)
>>
>> playing tricks on their licensing server may bring you in trouble twice
>> - first you probably break licensing agreements second solidworks always
>> may change their code which may render your tricks ineffective
>>
>>> The problem is that we have 300 high schools with proxmox server.
>>
>> you mean you need to setup 300 license servers? omg ! 😂🙈 (i
>> understand your problem then and would recommend talking to solidworks
>> about that - otherwise i would bring that into public discussion, as
>> solidworks makes you burn additional public money...)
>>
>>
>>
>>> Am 03.12.20 um 15:48 schrieb David Martin:
>>> I try all solution who i found on internet.
>>>
>>> i 'm looking for solution to masquing hardware to deceive solidwork who
>>> detecting proxmox.
>>>
>>>
>>> Le jeu. 3 déc. 2020 à 15:45, David Martin <damart.vidin@gmail.com> a
>> écrit :
>>>
>>>> Solidworks run only windows server
>>>> i create windows 2016 server
>>>> When solidworks 2020 starting install, he detecting who run on proxmox
>> and
>>>> solidworks not run on proxmox.
>>>>
>>>> Prerequis is :
>>>> *Hyperviseurs (Environnements virtuels)*
>>>>
>>>>
>>>> SOLIDWORKS *2018*
>>>>
>>>> SOLIDWORKS *2019*
>>>> SOLIDWORKS *2020*
>>>> VMware vSphere ESXi 6.0 6.5 6.7
>>>> Station de travail VMware 9 14 15
>>>> Microsoft Hyper-V 2012 2016 2019
>>>> Parallels Desktop, Mac 10 14 14
>>>> Citrix XenServer 6.2 7.4 7.6
>>>> Not Proxmox...
>>>>
>>>> It's a big big problem for us
>>>>
>>>> Le jeu. 3 déc. 2020 à 15:23, Mark Adams via pve-user <
>>>> pve-user@lists.proxmox.com> a écrit :
>>>>
>>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Mark Adams <mark@openvs.co.uk>
>>>>> To: Proxmox VE user list <pve-user@lists.proxmox.com>
>>>>> Cc:
>>>>> Bcc:
>>>>> Date: Thu, 3 Dec 2020 14:22:44 +0000
>>>>> Subject: Re: [PVE-User] Solidworks 2020 refuse to help me
>>>>> Why is it not working? Does it refuse to run when Windows is detecting
>>>>> that
>>>>> it is virtualised?
>>>>>
>>>>> On Thu, 3 Dec 2020 at 14:20, David Martin <damart.vidin@gmail.com>
>> wrote:
>>>>>
>>>>>> Hi everybody,
>>>>>> I have been trying for 3 weeks to install and find a solution to make
>>>>>> solidworks 2020 license server work.
>>>>>> Solidworks software refused to help us !
>>>>>> The problem is that we have 300 high schools with proxmox server.
>>>>>> anybody have found a solution to install and run solidworks server
>>>>> license
>>>>>> 2020 on proxmox 6.2 ?
>>>>>>
>>>>>> I need information if it's possible (on 6.2) to masquing all
>> information
>>>>>> hardware on vm, is it possible ?
>>>>>> (i try different old solution who i found on google, but not work on
>> PVE
>>>>>> 6.2)
>>>>>>
>>>>>> ;-(
>>>>>>
>>>>>> Best regards
>>>>>> --
>>>>>> david martin
>>>>>> _______________________________________________
>>>>>> pve-user mailing list
>>>>>> pve-user@lists.proxmox.com
>>>>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Mark Adams via pve-user <pve-user@lists.proxmox.com>
>>>>> To: Proxmox VE user list <pve-user@lists.proxmox.com>
>>>>> Cc: Mark Adams <mark@openvs.co.uk>
>>>>> Bcc:
>>>>> Date: Thu, 3 Dec 2020 14:22:44 +0000
>>>>> Subject: Re: [PVE-User] Solidworks 2020 refuse to help me
>>>>> _______________________________________________
>>>>> pve-user mailing list
>>>>> pve-user@lists.proxmox.com
>>>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>>>
>>>>
>>>> --
>>>> david martin
>>>>
>>>>
>>
>
>
> --
> david martin
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2020-12-14 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 14:19 David Martin
2020-12-03 14:30 ` Roland privat
[not found] ` <mailman.110.1607005412.440.pve-user@lists.proxmox.com>
2020-12-03 14:45 ` David Martin
2020-12-03 14:48 ` David Martin
[not found] ` <mailman.113.1607007167.440.pve-user@lists.proxmox.com>
2020-12-03 14:58 ` David Martin
2020-12-03 16:41 ` Roland
2020-12-14 6:46 ` David Martin
2020-12-14 6:51 ` Guy [this message]
2020-12-15 3:14 ` Laurent Dumont
2020-12-03 14:46 ` Yannis Milios
2020-12-03 14:49 ` David Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D815C75C-CEE8-4C84-9410-83BB6383768D@britewhite.net \
--to=guy@britewhite.net \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox