NetSetMan Support

maartena

Member

Registered: 2017-03-20

Posts: 1

Message about commercial environment

Hello,

I use Netsetman to change network settings regularly for testing purposes. I have a ESXi Server at home with 8 VM's for testing (not for production), and part of it is a Windows Server domain environment. I have a MSDN license and am testing SCCM and Exchange in small lab environments. It's not a commercial domain of any kind, just a home setup.

I suspect that the free edition of NetSetMan detects a domain and automatically assumes that therefore it is a commercial environment. And while that might be true in most cases, it is not in mine. I already bought NetSetMan Pro at my actual office for my work laptop which of course is part of a domain, but my home machines are not commercial in any way or form.

Is there any way around this, or do I just have to purchase another one? I want to use it on 4 machines, 2 of my physical home PC's and 2 Windows Servers on MSDN license.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Message about commercial environment

Thank you for sharing your constellation and your concerns.
In case you didn’t follow the link from that message dialog yet, please make sure to read this first:
http://www.netsetman.com/en/commercialuse

Yes, a domain membership is one of the criteria that allows distinguishing between a private and a commercial environment. There are multiple reasons why we believe this is a clear indicator. The most obvious one is that by definition a network domain is an organizational structure. Using that privately is a rather odd constellation. We can’t think of any private use case that involves an ESXi Server with eight VMs - especially if you consider that each of those systems requires a Windows license (who pays for your MSDN subscription?). Speaking of Windows: domain membership isn’t available with Windows Home for a reason. It requires at least a Windows Pro version. Using a non-commercial software on a professional Windows version is quite contradictory.

No, we’re afraid, there is no way around this. This restriction would be quite useless if there would be a workaround. A system in a network domain is considered a commercial environment and therefore requires a Pro license. Even if we wanted to believe that your use case is purely private, it’s simply impossible to make user based exceptions.

I already bought NetSetMan Pro at my actual office for my work laptop

Just as a side note: We didn't find your email address in our database. Maybe your company purchased that license for you or you used a different email address. Notice, that one license is required per system.

Thank you for your understanding.