I fixed the link - the period at the end of the sentence was being interpreted as part of the URL.

I downloaded a copy of BGInfo. I created a simple configuration and saved it as "custom.bgi". From a command prompt, I ran
 Code:
bginfo.exe custom.bgi /timer:0 /accepteula
and verified that it worked as intended.

Next, I copied the custom.bgi and bginfo.exe files to my NetLogon share (\\MyDomain\NetLogon, logged on as a domain admin. From a regular user account, I performed the following:
 Code:
PATH=\\MyDomain\NetLogon;%PATH%
bginfo custom.bgi /timer:0 /accepteula
This verified that BGInfo.exe could be found, but it could not find it's config file. I got the same message you did, asking if I wanted to create a new file.

Next, I changed the command to
 Code:
bginfo.exe \\MyDomain\NetLogon\custom.bgi /Timer:0 /accepteula
and it worked.

Replace "MyDomain" in the examples with your actual domain name. Now, to translate the command that runs during testing to what the login config file needs.

PATH specifies the complete path and command to execute. If no path part is specified, it defaults to the NetLogon folder, so PATH=bginfo.exe will work just fine.

ARGS specifies all of the arguments that the command needs to function. PATH and ARGS are separate so that we can look for the command specified by PATH in multiple standard locations without being confused by the arguments. So, we must specify the ARGS parameter as
 Code:
ARGS=\\MyDomain\NetLogon\custom.bgi /Timer:0 /accepteula
and things should work. This change tells bginfo exactly where to find the file. If you put the Custom.BGI file in a BGInfo folder on the Netlogon share, you'll need to insert "BGInfo\" in front of the "custom.bgi" file name.

What version of ULS are you running? You are using a fairly old (like WinNT old!) method of defining unique shares for each user's home folder and manually mapping them rather than using deep mapping and AD Attribute to manage home folder mapping. Manual mapping will throw an error if a user logs in without a defined share. ULS 2.8.5 introduced the ERROR parameter to WARN or IGNORE mapping failures for these situations. "IGNORE" ignores the error and reports success (Green), while "WARN" reports the error in Yellow without stopping for the error. I'd recommend being at that version or higher and adding the ERROR=IGNORE parameter to your Personal resource.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D