Roaming Profile

[Dnixon]

I have a client whose IT department has them set up using roaming profiles with admin rights but the problem is when my AMS checks for an update using TU and it begins to download, the update tries to save the update file in a temp folder which is normally in their documents & settings.

The problem is with roaming profiles his documents and settings is on a network so when TU goes to save the VP it is redirected to a network and errors out the VP with a redirect error.

Is there a way to change where the temp files are being save through my AMS, VP or TU? Thanks.

[saurav]

From what I can infer, you want to update AMS and it is failing because of the Network temp folder. What you can do is temporarily change the location of the temp folder to somewhere local, do the update and change it back. To change the location of the temp folder you can change the Environment variables tmp and temp for the current user to somewhere local like c:\temp, which should then allow you to do the updates.

[Dnixon]

So you are saying to change it on the computer I am trying to update? The problem is it is one of my clients and he has multiple computers that will be updating and it could be updating more than once a week and would be a hassle for them to change it everytime. Is there a way I can change this in my TU or VP code?

[saurav]

you can change the g_PatchFileDest variable in the TU script.