# We initialize a few things that are needed by this script - there are no other requirements. # You need to have downloaded the Chocolatey package as well.
Download Chocolatey Package and Put on Internal Repository # # repositories and types from one server installation.
# are repository servers and will give you the ability to manage multiple
# Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they # generally really quick to set up and there are quite a few options. # You'll need an internal/private cloud repository you can use. Internal/Private Cloud Repository Set Up #
What SLA does AutoDesk provide for the service? How do you measure "uptime"? What happens if you don't meet your promise? I know you said there's a lot of incentive to make it reliable, but a SLA would tell customers up front what reliability really means to AutoDesk.Īlso, I don't know if AutoDesk recently changed things or this is a typo, but on this page: under the FAQ section, it says we only need to connect every 30 days for the license check not every 14 days like I've heard on this forum.# Here are the requirements necessary to ensure this is successful. I've also worked at a variety of companies where we had similar SLA agreements with our customers/vendors, so this seems to be a pretty common industry standard when providing a service. I tried looking in the new license agreement to see if AutoDesk had an SLA, but I couldn't find the agreement on your website. When my cable (Comcast) goes out or they show up late to my house to do work, their SLA (service level agreement) says they refund me a portion of my bill.
So taking your analogy about cable service. At worse, it causes some customers serious problems. This isn't here to help us and does us no good, nor does it provide us any value. Realize, nobody outside of AutoDesk was asking for this change. So when we see something we pay for intentionally designed to fail, all we see is more problems. And as I said, there's Murphy's Law which says these kinds of problems always seem to happen at the worst possible time. But they add up over time and make us less efficient and cause us stress and all kinds of problems (even possible financial implications). Some like bugs or a down license server are. We got to deal with all kinds of problems which hurt productivity. But it's a cumulative problem for the end user. that'll never happen! Or happen so so rarely that "it's not a big deal". And that even if you were perfect, there are other people/services/companies which can break things just as badly (my ISP going down for example). But the simple fact is you can't/won't guarantee that your "AutoDesk" service will never go down because we all understand that things happen in life and nobody is perfect. There are dozens of other reasons other then "I went on vacation" which might prevent Eagle from calling home for 14 days.Īnyways, yes, I get it that this was about the "CadSoft" servers and those are different from the "AutoDesk" servers.
Like I said, if I go on vacation for 14 days (my computer is turned off because we like saving power/the environment but your licensing server is running) and then on the 15th day try to use Eagle when the server is offline then I'm SOL until you fix it. Your servers only need to be off line when I need to refresh my 14 day window. Generation of Footprint from Schematic 1Īlso keep in mind that EAGLE has a 14 day heartbeat, so Autodesk servers would have to be out of comission for 14 days for anyone to be unable to work.creating new part from existing library part 1.