Civil3d 2022 default template path

[Joe-Bouza]

Hello :

We are installing 2022 and I noticed on some users machines the template file location is :

C:\Users\%username%\AppData\Local\Autodesk\C3D 2022\enu\Template\_Autodesk Civil 3D (Imperial) NCS.dwt

and on other machines

C:\Users\%username%\AppData\Roaming\Autodesk\C3D 2022\enu\Template\_Autodesk Civil 3D (Imperial) NCS.dwt

not the end of the world but I typically send users a link to update some files and this is giving my batch file a hissy fit

Why is it different for some users? 

Is there something that can be done so they are all uniform

Users are installing from their accounts

[rkmcswain]

Interesting. %localappdata% vs %appdata%.......

I can't say I've ever seen this.

Does the folder %localappdata%\Autodesk\C3D 2022\enu\Template actually exist on the machines where it's specified? Because it does not here for me.

Here watching.....

[pendean]

User admin rights differences?

[Joe-Bouza]

I don't understand what you are saying

[Joe-Bouza]

could be? to my knowledge we all get admin writes. I will go to IT with this
Thanks

[rkmcswain]

Sorry, I am not sure how to make that any more clear.

Does the folder %localappdata%\Autodesk\C3D 2022\enu\Template actually exist on the machines where it's specified as the default template folder in Civil 3D?

You said that on some machines this path was being specified as the template folder path. On those machines, does this path even exist?

[Jeew-m]

@rkmcswain @Joe-Bouza Usually this 'AppData' folder is a hidden system folder. 

[Joe-Bouza]

Your use of %localappdata% through me off.
if %localappdata% = C:\users\%username%\appdata.... then yes, this is the issue

the folders are created by the installation. When I installed mine it created ...\local\.... and when others installed it created ...\roaming\...
Why?
I need an error trap in my bat file to check and then xcopy files from location A to the appropriate local or roaming path.

We modified _Autodesk Civil 3D (Imperial) NCS.dwt to our standards and I keep an updated version on the server. I send the batch file via email link to users to overwrite the OOTB copy.

I've gone through the changing install paths in a deployment to the server (PITA) and find it easier to install the software OOTB and xcopy standards files via xcopy

[Joe-Bouza]

Hi Jeewana

that's understood. Why does the installer create on one user==>  in ...\local\... and another user gets ==> ...\roaming\...

[rkmcswain]

@Jeew-m wrote:

Usually this 'AppData' folder is a hidden system folder. 

And?

Was there more to this that was omitted? Thanks.

[rkmcswain]

@Joe-Bouza wrote:

I've gone through the changing install paths in a deployment to the server (PITA) and find it easier to install the software OOTB and xcopy standards files via xcopy

We install from a single unaltered deployment, and then point them to the network paths at run time. No PITA at all.

[Jeew-m]

With some internet research, I found this.

Local stores data only on one PC. It's up to the developers what goes where, but generally, data in the Local folder is too large to sync or not worth syncing. For instance, you don't need to sync the giant thumbnails file or browser cache to a new PC -- it's just a waste of space and time.

In the end, Roaming and Local are functionally identical for a home PC running Windows. In a domain environment, data in the Roaming folder will stay with a user's profile if they move to a different computer.

So what I feel (I am no IT expert) is some users may be installing the software through a different PC (or server) which creates the template folder in the Roaming folder. 

[Joe-Bouza]

this may be the catch. I personally probably downloaded then executed the installer. The other users are most likely choosing "install now".

if they all get the same path its no trouble for me to change my standards file distribution

thanks