Special considerations when installing on multiple desktops for classroom use?

Are there any special instructions that have to be followed to install Arduino on multiple desktops for classroom use? My 12/9 post talks about a compile error on installations of Arduino from our network. Only the first install seems to work.

Thank you.

Have you tried the advise in your other thread (Compile error: exec: "{runtime.tools.ctags.path}/ctags": file does not exist - Installation & Troubleshooting - Arduino Forum)?

Is there a difference in all those machines? Different versions of OS?

BTW: you could have continued in your original thread instead of starting a new one :wink:

I'm wondering if it is because I passed along instructions to tech to:

click "Windows ZIP file for non admin install"

That's what I did on my laptop and desktops at home.

Could this problem be the result of not asking our tech group to:

click "Windows Installer" ?

Before I ask the tech group to reinstall on 30 desktops - I would appreciate any/all input.

Thanks so much

You're asking detailed questions about a unique situation that most of us have no experience in.

Sounds like you need to work closer with your tech team. Hopefully they have experience with configuring software to work in your environment.

Thank you for your responses - but it would really be helpful if someone could clarify for me when one would use "Windows Installer" vs "Windows ZIP file for non admin install" that would be great!

Thank you.

UPDATE: looking through older posts - found one from May 2015 which has a reply to someone else asking about the difference between the 2 windows install options - so I'm going to ask our tech group to install arduino using the "Windows Installer" option.

Yes I am a Newbie.

If you maintain computers then you should know the difference between a installer and a non installer right? The "Windows ZIP file for non admin install" does not install anything. You extract it to wherever you can and just run it.

Use the installer - the zip file version also doesn't install the drivers or anything. It's for people who need more control over how it's installed, or need to avoid running an installer due to not being able to get admin privs (though I wouldn't expect it to have compiling problems - maybe upload problems due to it not installing the drivers)

The real problem here is that the people on the Arduino forum are maker-hobbyists. Very few of us are using Arduino on a locked down environment; in fact, I think most of us have probably cranked UAC all the way back.

Recent versions of windows have made security much more confusing, and Microsoft doesn't feel a need to produce a proper technical reference for this material. I can see in the 1.5.x and 1.6.x versions, the Arduino team has been exerting a considerable effort to navigate the windows security tar pit. There's a general dearth of good, practical information on how to make things play well with the new windows security model, probably in part because nobody enjoys dealing with it, so outside of companies (where people are paid to do it), people don't deal with it - Unlike many topics, it's not something that is exciting and motivates people to dive in, put the effort into understanding it, and write and post detailed information (and the people doing it for work aren't going to go around writing it up and posting it publically). And that's just the default behavior - there are hundreds of obscure settings that can be configured through group policy, in addition to the normal settings.

I think you're going to need to work more closely with your technical team - I would be inclined to say that they should install it on one system, and verify that it compiles blink, even when logged in from a student account. Further adjustment of security settings may be required, depending on how tightly it's locked down.