It needs a path it can write to before next button is enabled. That's why I said it needs \\server\share\rest_of_the_path
Typing just \\server does not the trick.
I have tried \\server\share\rest_of_the_path
It needs a path it can write to before next button is enabled. That's why I said it needs \\server\share\rest_of_the_path
Typing just \\server does not the trick.
Then I guess this is a credentials issue. It is better to have the admin account running the program allowed to access the share.I have tried \\server\share\rest_of_the_path
There is a very minor bug regarding the Next button on the Backup Data screen that I've noticed a few times. It's so minor I haven't reported it:I just can not click next unless the backup path is local
Well, so far, I am not able to reproduce this. As soon as a user name is selected and the backup path is valid, I do not get this behavior.There is a very minor bug regarding the Next button on the Backup Data screen that I've noticed a few times. It's so minor I haven't reported it:
If you set the backup location path, then go up and change a selection in step 1 or 2, the next button is disabled, even though the backup location in step 3 is still valid. The workaround is to modify the backup location path (e.g. add space or remove trailing backslash).
It probably isn't the problem in this case but I thought I'd mention it in case.
Does the last folder in the path exist on your server? If not, then it's normal. Create it and see what's nextWell, here are screenshots where to show. It's not the end of the world, but maybe something that can be fixed.
View attachment 9969 View attachment 9970
Does the last folder in the path exist on your server? If not, then it's normal. Create it and see what's next
That's weird it works on one and not another. Does your share require credentials to be accessed? If so, since you can access it from Windows explorer, are you running Fab’s AutoBackup with the same credentials or are you prompted for administrator login information?Yes, it does exist. This happens on the customer's laptop but not another PC that I tested.
This will be in the next update. The program will look in the registry for default browser and default email client and add them to the installed software html report, user per user since this is not defined at machine level but user level :Which is why I'm suggesting that the default browser is logged in the Installed Software List report. Then the tech can manually set the default after installing the browser.
Thankyou!The program will look in the registry for default browser and default email client and add them to the installed software html report, user per user since this is not defined at machine level but user level
Redirected folders are not an issue. Entire profiles moved elsewhere are.Some people move too much from the system drive to save space on the system drive. I have no issues with the last upgrade or using Fab's to back up data when I set up a dual drive system.
Usually, this is not an issue. In this particular case, the program put the stuff back in the default location, so it would have been better to install and set steam before restore.Better to install programs first or restore first?
Had odd situation where customer wanted his Steam stuff moved to his other drive not with Windows, but this program didn't move the Program Files (x86)\Steam\SteamApps folder. I guess this was to be expected due to different location. His Steam stuff was originally on the C drive before intake and wanted Windows reinstall.
Do you mean not an an issue for Fabs AutoBackup? There was a discussion a couple of weeks ago about Fabs handling redirected profile folders, I can't remember if that was implemented. I think we can all safely ignore the possibility of the entire user profile being relocated as that isn't a documented feature of the OS, or is it?Redirected folders are not an issue
Yes, that's what I mean. I use folder redirection for "My documents', "My music" and "Downloads" and there's no problem for Fab's AutoBackup to find and back them up. As soon as it has been done the right way using their properties through windows Explorer, it is a breeze.Do you mean not an an issue for Fabs AutoBackup?
Since redirected folders are already handled (folders paths are grabbed from registry, so I get their real path), no need to change anything for them. Entire profiles location change is a pain to do, so, people doing that know what they are doing, so, I think it can be ignored. In worst case, a disk image of the client's computer before starting anything on them is the base trick to CYA.There was a discussion a couple of weeks ago about Fabs handling redirected profile folders, I can't remember if that was implemented. I think we can all safely ignore the possibility of the entire user profile being relocated as that isn't a documented feature of the OS, or is it?
Well, this deserved to be well implemented to not complicate program's use. Like looking for real folder paths, compare them with default path and is there is a difference, include default location too. The thing that disturbs me is : when it comes to restore, how do I choose which file to keep if there is a conflict? Or do I put them in a special sub folder like "@Recovered" so the client can decide by himself. This one would be the best option IMHO.Maybe Fabs AutoBackup should save the redirected profile folders PLUS the default folders if they still exist, as the Windows 10 upgrade process will now apparently do in future. Otherwise the previously requested feature of saving non-standard profile folders could solve this.