Thanks for your input.
Although we have full access (it guy and myself), we were not able to change the file location via solid edge.
We had to change the location via regedit on my pc.
What could have been done to prevent me from changing it via SE.
If the options.xml file has entries set to not allow overides that will prevent changing them in file locations.
Hmm. Strange. IDK. I guess I just have to ask if that is the .xml file pointed to in the Solid Edge Admin entry. (Sort of like asking if the machine is plugged in. Sorry)
You mean there is more than one xml file.
I don't know where the other xml file will be.
How do I know which one I should change?
In your SE options file locations what is the file pointed to by Solid Edge Admin? The very first line.
It does create an updated copy called options.xml in the local machine's SE preferences folder. Maybe you could try deleting that and run Update on "Solid Edge Admin" in file locations.
That is the image I posted earlier.
??? If you mean the image of the options.xml file that doesn't tell me anything about what's in the file locations setting for Solid Edge Admin.
FYI in seadmin if the option to allow override is originally set to No and then that options file is deployed, if you then change the options file to allow the override and redeploy the options, the Solid Edge client will not pick up the override change -- it will remain set to No and will not allow the override. The only way around this is to remove the user's Solid Edge registry and then re-read the options again.
@uk_dave, Maybe I'm not fully understanding but as a test I changed our options file to allow override on the reports entry. It worked immediately when I allowed it then didn't work when I disallowed it.
The options file is deployed from a server location. The date on the local options.xml in preferences also changed.