Scripting

You can start with the delete script from http://www.itninja.com/question/vbscript-to-search-for-and-delete-file to get rid of the old.url, run this from an msi as custom action and create the new url in a later action. 

It'd be easier to use your login script and run two command lines, one for each location to check.

"If exist 'oldX' xcopy 'newX' 'Location' /v/y"

Thanks for the advise. What I forgot to mention was that i had a mixture of Windows XP Pro SP3 clients and Windows 7 SP1 clients.

In my origional plan I created an sccm package which simply copied the below script 'replace.cmd' and 'example.url' to the root of the c: drive, I would run the 'replace.cmd' script which searchs the c: drive for example.url and replaces it with the newly copied one on the root. After the process completes i del the 'replace.cmd' and 'example.url' from the root. replace.cmd script looks like this;

_________________________________________________________________

for /F "tokens=*" %%P in ('dir /b /s "example.url"') do copy /Y .\"example.url" "%%P"

del /Q c:\example.url

del /Q c:\fileupdate.cmd

_________________________________________________________________

This package worked fine for XP machines but I found while testing that on Windows7 PC's with our current UAC it prompted me for elevated privileges even with local admin. 

So in the end I created a small sccm task sequence with Run Command Line, I added the package. For the command line I ran it as follows

cmd /c replace.cmd example.url

I ticked 'Run the step as the following account' and used my Domain Admin account.

Suppressed task sequence notification and deployed successfully.

Thanks again for the advise, N