windows XP vs Windows 7 and shared variables

[faustina]

 I have a stand-alone app I install onto 2 different PCs.  One PC runs Win XP and the other Win 7.  The application must deploy 3 shared variable libraries before the executable can run.  On the Win XP PC, I can be a user and accomplish this.  On the Win 7 PCI must be sys admin.  If I login as a user in the Win 7 PC, I must have the app set to run as sys admin otherwise the user cannot run the app.  What has changed?

[crossrulz]

Windows made things more secure by only allowing adminstrators to do certain things.  Apparently, whatever NI does to deploy shared variables are one of those.

[faustina]

Is there there any changes in the build instructions for the .exe or the installer that can compensate for these security changes?

[Skirpt]

Faustina,

I was unable to find anything. Is there a specific security threat that you are worried about?

[faustina]

No it's a matter of getting my work done efficiently.  Recently my organization increased security and my sys admin privledges went away.  Therefore creating stand-alone apps for my users, building shared variable libraries has become difficult.  The sys admin is not always available.  I was hoping that in creating the .exe or installer I could simplify the process.

[Skirpt]

Faustina,

I do not know of a good way around this. However I did find several links that I think should help. First here is information about what is going on http://digital.ni.com/public.nsf/allkb/E06C1800F5AFCCBF86257236006C9F2A?OpenDocument. Next as a workaround I would suggest setting the exe to run as admin you can find instructions for that here https://technet.microsoft.com/en-us/magazine/ff431742.aspx.

[faustina]

could you send new links.  I get errors when I try to follow them both from my work computer and home computer.

[SnowMule]

---

@faustina wrote:

could you send new links.  I get errors when I try to follow them both from my work computer and home computer.

---

Delete the "." at the end of both URL's.  Those get sucked into the URL-izer, but it's not part of the object so it barfs errors.

Always pad URLs posted on forums with whitespace.