From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Declined for reasons listed in AristosQueue's post:
"Microsoft documentation describes "My Documents" as the appropriate place for apps to install files that are meant to be user modified after installation. MS says this is supposed to be a writeable location that the current user (whoever is logged in) always has write access to. There's no other acceptable location for LV to use for such files under the MS rules of installation. If your IT department has made My Documents inaccessible for writing, that's a problem on your end."
When installing recent updates for LabVIEW 2018 an error message came up that said the installer needs access to "My Documents". However this location "file path" is not available. My company has a drive mapping package that has the my documents located on the server as well as my favorites so it is automatically backed up for recovery purposes. The installer keeps getting this error and forums state that the IT admins need to get involved every time to update & set my documents to local temporarily to install, then back to the server for automatic backups. This is very tedious and takes a lot of manpower. My colleague has the same issue with DIAdem 2018 as well. Looking to possibly have a fix where it gives the user a browse option to find the file path it needs for the install.
So your system cannot write to "My Documents". I suppose that certainly makes backups easier..... Why doesn't your IT implement things better. I also have "My Documents" on a server drive, but I can install no problem. I think the problem is with your system setup, not with NI.
@meisterplaceb Microsoft documentation describes "My Documents" as the appropriate place for apps to install files that are meant to be user modified after installation. MS says this is supposed to be a writeable location that the current user (whoever is logged in) always has write access to. There's no other acceptable location for LV to use for such files under the MS rules of installation. If your IT department has made My Documents inaccessible for writing, that's a problem on your end.
Declined for reasons listed in AristosQueue's post:
"Microsoft documentation describes "My Documents" as the appropriate place for apps to install files that are meant to be user modified after installation. MS says this is supposed to be a writeable location that the current user (whoever is logged in) always has write access to. There's no other acceptable location for LV to use for such files under the MS rules of installation. If your IT department has made My Documents inaccessible for writing, that's a problem on your end."
Declined for reasons listed in AristosQueue's post:
"Microsoft documentation describes "My Documents" as the appropriate place for apps to install files that are meant to be user modified after installation. MS says this is supposed to be a writeable location that the current user (whoever is logged in) always has write access to. There's no other acceptable location for LV to use for such files under the MS rules of installation. If your IT department has made My Documents inaccessible for writing, that's a problem on your end."