ATI2016 now seems to freeze
Ok, I think as long as your accounts are not a mix of MS and Local you should be able to get things working. Keep us posted of your progress.
In Windows Network and Sharing Center, does your network show as Private of Public? It should show as Private. if you click on Advanced sharing settings on the left side of screen you will see first, settings for your Private Network. You will see 3 settings. 1. Network Discovery, Turn on network discovery should be enabled for a Private Network so that connected devices can discover each other on the network. 2. File and Printer sharing, Should be on so that files can be shared on a Private network. 3. Homegroup Connections, If you are using the Homegroup network option you should have Allow Windows to manage homegroup connections. If your network is a Private network you might want to consider enabling the Homegroup feature on your computers. Given your objective and your current situation that just might be the best solution for you. If you enable Homegroup on all your machines and all machines have joined the Homegroup then access and sharing are much simpler.
In past versions of Windows it was common for the Network type to be set as Workgroup. Workgroups came about for networks where 1 or more Servers where connected and established the ground work for networking. Windows brought the Homegroup features into the picture as a way of managing a small home network without servers involved to allow for sharing across the small home network. If you enable Homegroup on your machines and join those machines to the created Homegroup your sharing would be much simpler to manage and fit your needs much better. I believe that your current Everyone settings on your drive settings would work if Homegroup were established on your network.
Regarding the Network and Sharing Center
- My desktop (aka S4) Private, Network Discovery On, File/printer sharing On, Allow windows
- My wife's laptop (aka Lenovo) private, Network Discovery On, File/printer sharing On, Allow windows
- My laptop (aka W700) private, Network Discovery On, File/printer sharing On, Allow windows
- The test laptop (aka Sony) private, Network Discovery On, File/printer sharing On, Allow windows
I thnk Homegroup is turned off, when I click on it in the filemanager nothing happens. To my knowledge I've never turned it on. I'll explore this a bit.
As for others whom connect to your network, These would be Guest or Public users. which brings us to the second part of the list of the Advanced sharing options in the Network and Sharing Center. There are two selections here. They are Network Discovery, obviously this should be turned on and File and Printer sharing, this should be turned on as well. These 2 settings will allow guest/public users to access your Homegroup.
I just checked and these options are all turned on. I've not looked into the homegroup yet.
The third part of the list of Advanced sharing options is for All Networks and sets the parameters for both Private and Public/Guest networks. You have 4 choices here. First is Public folder sharing. Obviously you want to turn this on so that sharing of the Public folders can work. Second you have Media Streaming which you can configure which media folders are allowed for media sharing. Third is File Sharing Connections which is where you would set Encrytion levels for networks which should be turned on for 128 bit encryption. Forth is Password Protected Sharing which you should select as turned off so as to allow access to those whom do not have an account on the network.
I checked on all systems and they were as you suggested.
This sorta takes me to the start of the circle. I'm going to review the dummies link and setup homegroup.
Gee wiz, I added 3-4 post to answer you questions and now I don't see the post.
Basically everything was correctly set on all systems and I started to review the dummies article. On my desktop I started to create a Homegroup and it states that my Sony laptop had created a Homegroup (I do not recall doing this but this is a VERY old laptop). I went to the Sony laptop Control Panel > Network and Internet > HomeGroup and it states "There is currently no homegroup on the network"
Now I need to determine how to get the other 3 systems to not see any homegroup and then create a new homegroup on my desktop and have the other system join it.
So far NONE of the systems have joined the homegroup that the Sony created and I cannot create a homegroup on the desktop because it thinks the Sony PC has already created such.
I'm researching but if you have a suggestion please.....
BTW, now I see the post I made.
Delete all home groups (check each system). Turn off all systems. Power up one (the main one). Create the homegroup on it and make sure it's complete. Then power up the next and join it to the newly created home group (hopefully). If successful, power up the next and repeat until all are done. Once they're all configured, should "stick" but homegroup is finicky when first joining and connecting them.
I should also note that you should do this via ethernet cable on all of them initially. I've had no luck joining home groups over wireless, but once connected, wireless networking works fine.
As a workaround I shut down the Sony laptop, created a HomeGroup on the desktop, joined the HomeGroup on my laptop (W700). Still I could not access the drives originally shared out on the desktop.
DARN!!!!!
Did you give the user "home group" modify access to the share too?
Bobbo - Everyone has full access.
However I think I have finally resolved the issue, at least on my laptop (W700), the Sony is powered off and is in the far end of the house. I'll work on it tomorrow. I'm getting tired and my puppy is driving me nuts, she wants to sit on my lap.
Solution:
First a little backgound - On all of the remote systems I had use my file manager to view the network > my desktop which then displayed all of the shared drives. I then right-clicked on a drive and mapped. On my laptops I used the same drive letter as on the desktop and used the drive label as the shared name. Example
On my desktop drive T has a label of S4-T-WDBlk6TB thus when I mapped it on the laptop it appeared as S4-T-WDBlk6TB (\\S4) (T:) in the file manager. Thus no matter what system I was using drive T was the same drive on all systems. So far so good, but on my laptop (W700) and the Sony eventhough the drives were mapped when I tried to access the shared drives I was told I did not have permissions. But the same mapping on my wife's laptop worked without issues.
On my laptop I opened a CMD window as Admin and here I used the "net use" CMD to display the mapped drives and it showed that I had mapped all of the drives on my desktop. Thus it seemed that all should work but it was not. The mapped drives were displayed correctly, example T: \\S4\S4-T-WDBlk6TB Microsoft Windows Network
Somewhere I read something about using the IP address and here is where I finally got my solution.
- First I used the "net use" CMD to delete all of the mapped drives, e.g. as follows
C:\WINDOWS\system32>net use /delete t:
t: was deleted successfully. - Then I mapped the drive as follows
C:\WINDOWS\system32>net use t: \\192.168.0.168\S4-T-WDBlk6TB /P:yes
The command completed successfully. - Thus when I now use "net use" for the T drive I see the following
OK T: \\192.168.0.168\S4-T-WDBlk6TB Microsoft Windows Network - I then access the drive in my file manager and I can create and delete things on the T drive.
- I then kicked off my data backup utility (SyncBack Pro) that uses the network T drive and it ran will success.
Gee Wiz - this was a bitch to resolve!
Now I just need to resolve the ATI2016 issue on my wife's laptop.
I forgot to mention my desktop has a static IP address. Without a static IP address the mapping as performed would fail when the IP address of the desktop changed.
On my wife's laptop I modified the script to include the IP address instead of the original:
\\S4\S4-Q-WDBlk6TB-BU\BU\Acronis\Lenovo-Z580\Incremental\@task@.tib
It was changed to
\\192.168.0.168\S4-Q-WDBlk6TB-BU\BU\Acronis\Lenovo-Z580\Incremental\@task@.tib
Still I get the failure.
As a workaround I have a USB external 3TB drive that I'm backing up to.
Did you join the Homegroup on your wifes laptop? Joining the homegroup will get you on the same network as your desktop and your laptop.
I would say you are almost there, just need to resolve the wifes laptop. I would follow Bobbo's suggestion to attach via ethernet cable if possible to get the Sony setup. It should work straight away once you join the Homegroup you created on the desktop.
I'd also point out to be sure that your wife's laptop and/or the Sony need to leave the old home group and reboot first if that hasn't been done yet.
You also need to disconnect the old "mapped drives" and re-add them again and should do that for all of the systems (even if they seem to be working now - I'd recommend it, if this hasn't been done yet). If they were mapped with different network settings previously (non homegroup), whatever authentication they originally used is old.
You want them mapped NEW after joining the new homegroup (to rule out any other background network issues).
Finally, wherever the source of the shares is at, you want to go into the share permissions and give "homegroup" READ/WRITE access. That should allow any system in the homegroup to do whatever it needs. Perhaps not the most secure, but that is the way Homegroup is designed to work so that network and sharing is "simpler" (when it works).
Did you join the Homegroup on your wifes laptop? Joining the homegroup will get you on the same network as your desktop and your laptop.
I would say you are almost there, just need to resolve the wifes laptop. I would follow Bobbo's suggestion to attach via ethernet cable if possible to get the Sony setup. It should work straight away once you join the Homegroup you created on the desktop.
With the Sony powered off, on my laptop I disconnected all the shared drives, I joined the HomeGroup (not sure if I rebooted) but still I could not access the shared drives. Posssibly it was just me doing something wrong. At this point I gave up on the HomeGroup and went back to the "net use" CMD and used the desktop static address to map the drives.
I'd also point out to be sure that your wife's laptop and/or the Sony need to leave the old home group and reboot first if that hasn't been done yet.
You also need to disconnect the old "mapped drives" and re-add them again and should do that for all of the systems (even if they seem to be working now - I'd recommend it, if this hasn't been done yet). If they were mapped with different network settings previously (non homegroup), whatever authentication they originally used is old.
You want them mapped NEW after joining the new homegroup (to rule out any other background network issues).
Finally, wherever the source of the shares is at, you want to go into the share permissions and give "homegroup" READ/WRITE access. That should allow any system in the homegroup to do whatever it needs. Perhaps not the most secure, but that is the way Homegroup is designed to work so that network and sharing is "simpler" (when it works).
None of the systems had ever accessed the old HomeGroup. I powered the Sony off, this removed the old HomeGroup from the desktop, my wife's laptop and my laptop. It was then I attempted to create the HomeGroup on my desktop and join it on my laptop (see previous post) and this did not allow me to use the shared drives.
I did NOT remap the drives after joining the HomeGroup on my laptop.
Finally, wherever the source of the shares is at, you want to go into the share permissions and give "homegroup" READ/WRITE access.
This I did not do I had assumed that if I granted full permissions to Everyone it would not be necessary to grant permissions to any other users.
On all three laptops I use the NET USE in an Admin CMD window and used the IP address as the Device Name all three laptop have full access to the shared drives, except the Sony currently has a problem with two of the drives.
In that the drive access is now working I'm not sure if I want to continue down this path, however I still cannot get my wife's laptop to BU to the shared drive on the desktop (it is backing up to a USB drive that I attached to it). At this time I have NOT tried the Sony with ATI. Hopefully I can try this later tonight. Also I will retest my laptop, currently ATI2016 on that laptop is backing up to attahced USB drives.
Once you joined the Homegroup that basically just establshes a networked connection between the machines involved. In order to share over that netwrked connection you then need to establish/grant permissions to the content on each device you wish to share.
As Bobbo pointed out you would need to navigate to the drive you wish to share Properties, Security tab and set permissions for User Homegroup with Read, Write, and Modify permissions. That shoul give you access to the drive.
I think your use of the netuse commands will not be persistent, in other words they are settings that will only last for the current network session. When that session ends so will the connections. Network sessions end upon reboot, shutdown/restart, loss of connection, or other interuption of the connection.
And NetUse is establishing a new session each time as well. That was something that seems to have been missed with the homegroup. Basically, when you create a new homegroup, new shares need to be configured as well and also need to make sure the "home group" users have been set for read/write after that. If that is done on each machine, all network shares should work fine with home group.
And NetUse is establishing a new session each time as well. That was something that seems to have been missed with the homegroup. Basically, when you create a new homegroup, new shares need to be configured as well and also need to make sure the "home group" users have been set for read/write after that. If that is done on each machine, all network shares should work fine with home group.
I was under the assumption that the /P:yes would ensure the drive(s) would be available after a reboot but it is not (as you stated). I just tested by rebooting my desktop, the W700 and Sony. None of the "net use" mapped drives are available. In the Win 10 forum (see http://www.tenforums.com/network-sharing/22613-network-drive-not-showin…) a users stated that the /P:yes only works "if" it was issued in a normal CMD prompt and will not if it was issued in an Admin CMD prompt.
A bit more testing. I've not changed anything at this time and just noticed that scheduled BU applications that use the shared drives on the desktop ran with success. On my laptop (W700) I opened my file manager (xplorer2) and noticed that the drive mappings no longer show on the drive bar but if I click on the drive in the nav pane under Network > S4 I correctly access the drive. See the image.
Not sure what to make of the Win 10 Forum statements. Really doesn't matter. True Image must be run as an administrator just so you know.
You seem to have some misconceptions about permissions. When you allow everyone on your desktop permissions to a drive, folder, or file that establishes permissions for anyone whom has an account on your desktop. Do your other machines has user accounts on your desktop? If so to me it begs the question why? It is much simpler and safer to establish a homegroup network that at least will provide albeit a low level of security for the network. If you setup the homegroup correctly you will not have to map drives, you simply apply permissions for the homegroup and any member of the group will have access. If you have drives you do not want members of the homegroup to have access to you simply do not establish such permissions and those drives, folders, files become off limits. This works in reverse order as well if you want to have access to content or drives on one or more of your laptops from the desktop.
When it comes to others (visitors) whom you want to connect to share content all you would need to do in the homegroup is place such content in the Public folder on the desktop and they will have full access to it. This gives you a level of control over access which I cannot understand that you would not want. It makes things much easier to administer as well which is a big deal in itself.
The choice is yours with all of this so you be the judge but if it were me I would setup the homegroup just to keep it simple if for no other reason.
Finally, wherever the source of the shares is at, you want to go into the share permissions and give "homegroup" READ/WRITE access. That should allow any system in the homegroup to do whatever it needs. Perhaps not the most secure, but that is the way Homegroup is designed to work so that network and sharing is "simpler" (when it works).
OK I'm back to trying the HomeGroup. When I attempt to grant permissions for HomeGroup I get an error "An object named "homegroup" cannot be found. Check the selected object types and location for accuracy and ensure that you typed the object name correctly, or remove this object from the selection."
Maybe this article can help you in setting things up:
http://www.windowscentral.com/how-setup-and-manage-windows-10-homegroup…
It mgiht be "HomeUsers"
On your shared folder, right click and go to properties. Second tab is "sharing" Don't use the advanced sharing. Use the top "share" button and click the drop down. One of the options should be either HomeGroup or HomeUsers. You want that one (or both if available) and make sure teh Permission level is set to READ/WRITE.
Not sure what to make of the Win 10 Forum statements. Really doesn't matter. True Image must be run as an administrator just so you know.
You seem to have some misconceptions about permissions. When you allow everyone on your desktop permissions to a drive, folder, or file that establishes permissions for anyone whom has an account on your desktop. Do your other machines has user accounts on your desktop? If so to me it begs the question why? It is much simpler and safer to establish a homegroup network that at least will provide albeit a low level of security for the network. If you setup the homegroup correctly you will not have to map drives, you simply apply permissions for the homegroup and any member of the group will have access. If you have drives you do not want members of the homegroup to have access to you simply do not establish such permissions and those drives, folders, files become off limits. This works in reverse order as well if you want to have access to content or drives on one or more of your laptops from the desktop.
When it comes to others (visitors) whom you want to connect to share content all you would need to do in the homegroup is place such content in the Public folder on the desktop and they will have full access to it. This gives you a level of control over access which I cannot understand that you would not want. It makes things much easier to administer as well which is a big deal in itself.
The choice is yours with all of this so you be the judge but if it were me I would setup the homegroup just to keep it simple if for no other reason.
I agree I'm totally confused with the networking and permissions settings.
Maybe this article can help you in setting things up:
http://www.windowscentral.com/how-setup-and-manage-windows-10-homegroup…
This was very helpful. I was also reading the comments and one user stated to ensure that my router had IPv6 enabled. I checked my router and it is disable and there are several options. At this point I'm lost and have not made a lot of progress.
Gee wiz guy I'm sure I'm driving you nuts and I really appreicate your help.
I would check the Use DHCP Server for IPv6, this will allow the router to assign an address.
Auto Detect / use dhcp server should be fine. I don't think it's necessary for home groups though. I do have it on my router, but only recently. Prior to that, homegroups were still working for me. I wanted to post a screenshot of my homegroup settings on a typical "open" homegroup share as well.
It mgiht be "HomeUsers"
On your shared folder, right click and go to properties. Second tab is "sharing" Don't use the advanced sharing. Use the top "share" button and click the drop down. One of the options should be either HomeGroup or HomeUsers. You want that one (or both if available) and make sure teh Permission level is set to READ/WRITE.
It is HomeUsers and the setup is much different (at least for me) than you suggested. I "think" I now have it setup for one drive. I want to share the entire drive(s) not just a folder on it and I want the users to have full access to the drive(s). After setting it up on my desktop I went to my laptop and I'm not sure what to do to access the drive(s).
On each of my laptops I will be running ATI2016 and at least SyncbackPro to run various backups (most likely I will be using other BU applications as well). ATI will be backing up to the boot drives to my desktop shared drives. SyncbackPro not only backs up but also syncs various folders. Can I do this with the HomeGroup?
Attached is a PDF with the images I captured when assigning HomeUsers permissions to one of my drives on my desktop.
OK I picked DHCP and for the LAN I picked auto config, see the image.
Because of my limited knowledge in this area (networking in general) I'm having touble connecting the dots.
It is HomeUsers and the setup is much different (at least for me) than you suggested. I "think" I now have it setup for one drive. I want to share the entire drive(s) not just a folder on it and I want the users to have full access to the drive(s). After setting it up on my desktop I went to my laptop and I'm not sure what to do to access the drive(s).
To access the drives, you would go to "this pc" >>> expand network >>> Look for the name of your networked device (pc name). Should see it there. Double click on it. Any shares that are accessible should show up. Click on the share and you should be able to access without any additional credentials. You can also map the drive or create a shortcut.... example: \\PC1-NAME\SHARE-NAME
On each of my laptops I will be running ATI2016 and at least SyncbackPro to run various backups (most likely I will be using other BU applications as well). ATI will be backing up to the boot drives to my desktop shared drives. SyncbackPro not only backs up but also syncs various folders. Can I do this with the HomeGroup?
Attached is a PDF with the images I captured when assigning HomeUsers permissions to one of my drives on my desktop.
I don't see why not. The homegroup is just a way of managing permissions. As long as the software can access the shares via the accounts in the homegroup, it should work. I don't now if SynbackPro has a place to enter credentials or not, but if it does, once your sharese have already been created, give it credentials for any account on any machine in your homegroup (probably the one on the machine your're running the application on though.
You can share an entire drive by selecting it from "this pc" and clicking permissions on it as well. For some reason, when you setup your share in your screenshot, you had to go through the "advanced" permissions setup. If you create a new folder on your drive - then refresh the screen, then go to properties/shares, are you not able to click on the top share button?
You can share an entire drive by selecting it from "this pc" and clicking permissions on it as well. For some reason, when you setup your share in your screenshot, you had to go through the "advanced" permissions setup. If you create a new folder on your drive - then refresh the screen, then go to properties/shares, are you not able to click on the top share button?
I just discovered that if you select properties on a drive vs properties on a folder the resulting window is different. I assume you had selected a folder thus the 2n tab was Security whereas I was selecting a drive and had two rows of tabs and to set the permissions I had to use "advanced" permissions.
I can confirm what you went through on my system as well. Doing that - since you want all systems to connect without issue, I'd give "users, homeusers and homegroup$" full access. Of course, this is not very secure, but will give you the results you're looking for.
To access the drives, you would go to "this pc" >>> expand network >>> Look for the name of your networked device (pc name). Should see it there. Double click on it. Any shares that are accessible should show up. Click on the share and you should be able to access without any additional credentials. You can also map the drive or create a shortcut.... example: \\PC1-NAME\SHARE-NAME
AH this is the way I was doing it for the simple networking. I now have all four pcs in the homegroup. I've mapped all of the shared drives on the desktop on each laptop
- From my laptop (W700) I can access all of the shared drives, add a folder to the shared drive and delete the folder.
- From my wire's laptop (Lenovo) I can access all of the shared drives, add a folder to the shared drive and delete the folder.
- From my test laptop (Sony) I canNOT access all of the shared drives, add a folder to the shared drive and delete the folder. Three of the drives (P, Q, T) tell me I don't have permissions and to contact my network admin.
The Sony laptop is an upgrade to Win10 from Win8.1 which was an upgrade fromWin8 which was an upgade from Win7. Is it possible that there is some issue on this laptop. If I have to I can live without the access to these three drives on this laptop but if it is not going to take me hours to resolve I'd like to resolve it.
At this time I assume that SyncbackPro will correctly function now that the drives are mapped on each laptop. I can easily kick off the profiles that access the desktop drives and see if any issues pop up
I just attempted to run ATI on my wife's laptop to BU to the desktop drive. The run is in a que. I don't see any other ATI task running. I'm rebooting her PC.
PC is backup and I kicked off the run but it failed with the same issue that started this thread.
Today I received a Thermaltake USB3 Max 5G enclosure. I mounted a 3TB drive in it for my wife's PC and started to test. One of the two 80mm fans in the unit makes a LOT of noise. This is unacceptable and I'm trying to setup an exchange.
Isn't the Sony laptop the one that you stated earlier was complaining that it was already part of a homegroup? Did you or where you successful in resolving that issue on the Sony?
I am going to assume the answer to the above is Yes at this point. If not you need to resolve that issue before you go looking at the steps below.
The homegroup requires a number of sevices to be running to function correctly. You should insure that they are all working. The steps below should be followed to do that:
The services that need to be turned on are listed below:
• DNS Client
• Function Discovery Provider Host
• Function Discovery Resource Publication
• HomeGroup Provider
• HomeGroup Listener
• Peer Networking Grouping
• SSDP Discovery
• UPnP Device Host
Let us try to start the service manually, you can turn on the services by following the steps given below.
- Press Windows Key + R Key.
- Type services.msc and hit enter, you will see list of services.
- Right Click and Click on Properties.
- Set the Service Status as Start.
- Restart your computer.
Make sure the Startup type is set to Automatic and click Start to turn on the service. To do that right click on the service and select properties and select Automatic in the drop down menu field.
Agree with Enchantech - did you leave the homegroup on the Sony, reboot and try to connect to the new one - if not, that is a must, but if services are not running correctly, it will never happen.
If it just isn't happening, as atest, take an image of it for posterity so you can roll back if you want. Then, "refresh" Windows 10 and keep your data (your apps will be gone and your settings), but that should bring Windows to a pristine state. At that point, try connecting to the homegroup and see if it works. If it does, but not in the original version, we can assume something from all of the upgrades has broken networking to some extent and a refresh may actually be a good thing at this point.
As for your backup still not running... now that homegrouop is working on the 4 other systems. Create a NEW backup task and enter credentials for the share when prompted in Acronis. Your old backup task may still be using some old credentials or something from your earlier shares that no longer jives with the homegroup so creating a new task should alleviate that. What happens then?
Isn't the Sony laptop the one that you stated earlier was complaining that it was already part of a homegroup? Did you or where you successful in resolving that issue on the Sony?
Originally when I started working with the HomeGroup on my laptop (W700), my wife's laptop (Lenovo) and my desktop (S4) all showed that the Sony had created a HomeGroup but when I went to the Sony > HomeGroup it stated that no HomeGroup existed. I looked for ways to eliminate the phantom HomeGroup but did not find anything. I then powered off the Sony (at this point the other three systems did not see an existing HomeGroup) and created the HomeGroup on S4 and did my inital test which was somewhat of a failure for me. After additional post from you and others I finally got the HomeGroup working. At this point I powered on the Sony and let it join the HomeGroup.
I'll follow up with your other suggestions and see if something eliminates the existing issue of not being able to access three of the shared drives on the desktop.
Agree with Enchantech - did you leave the homegroup on the Sony, reboot and try to connect to the new one - if not, that is a must, but if services are not running correctly, it will never happen.
See the answer to Enchantech, I could not find a way to ensure it was removed from the Sony.
If it just isn't happening, as atest, take an image of it for posterity so you can roll back if you want. Then, "refresh" Windows 10 and keep your data (your apps will be gone and your settings), but that should bring Windows to a pristine state. At that point, try connecting to the homegroup and see if it works. If it does, but not in the original version, we can assume something from all of the upgrades has broken networking to some extent and a refresh may actually be a good thing at this point.
As for your backup still not running... now that homegrouop is working on the 4 other systems. Create a NEW backup task and enter credentials for the share when prompted in Acronis. Your old backup task may still be using some old credentials or something from your earlier shares that no longer jives with the homegroup so creating a new task should alleviate that. What happens then?
I need to install ATI2016 on the Sony and test.
When I upgraded all system (a few days ago) to WIn10 10586.164 I picked the option to install Win10 and keep my apps and settings. This was before doing anything with the HomeGroup. I don't recall having the Sony create a HomeGroup, if I did (I must have) it would have been at least 2-3 years ago.
I was planning to use the Sony to monitor my solar and had trouble getting the app installed. The app is now installed but I have not collected anything from the solar.
Great suggestion about creating a new task in ATI. I'm braind dead at this point and did not think of it. I'll let you know the results but it will not be until tomorrow. Taking the wife out for her 70th birthday.
Quick update, hopefully I correctly state the current status.
- On the desktop I ensured all the drives I wanted to share also included HomeUsers with full permissions.
- The HomeGroup was created on my desktop (S4) and the other three laptops have joined the homegroup (Sony (the system to monitor my solar), the wireless BTW it was able to join with the wirless connection, Lenovo (my wife's laptop), W700 (my laptop))
- On each of the three laptops I expanded Network and mapped the desktop shared drives. On each laptop after all of the drives were mapped I created/deleted a folder on each shared drive. In the past I had troubles connecting to some of the drives from the W700 and Sony systems. At this time I think all of the drives are working without issues as far as normal usage.
- I've also checked the SyncbackPro profiles where they access a shared drive on the desktop. The past two nights all profiles have run successfully.
- On my wife's laptop (Lenovo) I created a new task to create an incremental BU to the desktop shared drive. It failed in the same fashion as I initially reported. Just as a reminder on 3/19 Macrium successfuly created a BU to the same shared drive.
- On the Sony laptop, I installed ATI2016, created a task to create an incremental BU to the desktop shared drive and started the BU. It failed in the same fashion as the Lenovo. Thus with respect to ATI I'm back to where I started when I created this thread.
- Tomorrow if time permits (I have guest from out of town visiting) I will install a empty HD in the laptop and start a clean install of Win10 10586.164. I just checked and this is still the latest version that MS has released. To expidite the install I will connect the PC to my LAN and place it in my home office where I normally work on the PC. After installing Win10 and what I consider my critical apps I will then ensure I have joined the HomeGroup, mapped the desktop drives, test the shared drive connections, install ATI2016, create a task and test it. Thus it may be a few days before I have an update. One of the possibilities I'll be able to test is ATI on an upgraded Windows system vs a clean install system.
Now that you have the network connection problems sorted it should be easier to figure out why ATI is having issue.
In 5 above the new task you created, was that task pointed to a new folder on the destination disk?
Same question for 6?
If not you should do that.
Any machine that has TI 2016 installed as an upgrade should have the app unintsalled, the cleanup tool found at the link below and then reinstall the application. This will remedy most problems with upgraded installs:
http://kb.acronis.com/content/48668
Now that you have the network connection problems sorted it should be easier to figure out why ATI is having issue.
OK I installed a empty HD in the Sony, Installed Win10 10586.164, installed kaspersky Total, malwaebytes Pro, SuperAntiSpyware Pro, downloaded the updates for the AV apps, ran scans. Joined the HomeGroup, mapped all of the shared drives on the desktop, Installed ATI2016, created a task to BU to the desktop K 3TB drive (this is a drive that was totally empty and had NOT been used by any system for ATI. As with the previous failures, it failed, I see at the bottom of the ATI window "Backing up... 31mb" and never seen any other update to the window. I do see after several minutes the ATI window telling me th BU has failed.
Thus the clean install of Win10 did NOT resolve the issue.
In 5 above the new task you created, was that task pointed to a new folder on the destination disk?
I just created another task and ensured it was backing up to a different drive (I picked the K drive as I did for the Sony), again it failed with the same symptoms as the Sony.
Same question for 6?
If not you should do that.
With the previous test I did try to the same drive as I had been using but with the test tonight I did use a different drive.
Any machine that has TI 2016 installed as an upgrade should have the app unintsalled, the cleanup tool found at the link below and then reinstall the application. This will remedy most problems with upgraded installs:
On one of my systems I did try the cleanup tool and this created a lot of problems for me. I don't recall the problems, I think I mentioned this in a previous post in this thread. After the mess it created I went through a LOT of effort using Revo and Everything attemptiong to remove all traces.
On the Sony tonight ATI2016 was a fresh install. Other than windows and my AV stuff NOTHING else was installed on the system.
IMHO Acronis has a serious issue with Win10 and I think it is time for them to step up to the plate and resolve the issue. I don't know what else to do to get ATI working. At this time I'm tried and very discouraged. Previously I tested with v5.3 of Macrium Reflect on my wife's laptop using the desktop shared drive as the target for the BU and it worked.
All four of my systems are signing in with my MS account.
On your machines that work, were you required to or asked for Windows Credentials either when selecting the destination during the backup creation process or when you selected to proceed with the backup?
If yes, what credentials did you enter?
Is the Kapersky app installed on the other machines that you have working? In some cases Anti-virus applications will block the services of True Image from running. To address this problem it is necessary to add the services to the anti-virus exceptions/whitelist. TI 2016 Processes and services can be found at the link below
https://kb.acronis.com/content/56697
Did you run the TI 2016 installer as administrator on the Sony installation?
Can you provide the log files for the failed backups on the Sony here? At this point we need to discover what the failure is. The log files would be helpful in doing that.
I understand your frustrations. The above are the common things that cause backup failure. If this machine is on a wireless connection and that connection is not a very good connection that could be an issue here but not that likely.
I might also suggest that you take the time to submit the issue using the feedback features available. There is an option within the application that allows for you to submit a system report along with the the feedback in the application in the Help section (open book icon on left of GUI screen). When submitting feedback reference this forum thread by copy and paste link.
jg1942. If at all interested, we could setup a webex where I could take control (or just view while you drive) to double check some settings in Acronis and your home group shares. It seems like the homegroup is all setup correctly now, but just to verify. If you'd like to take me up on the offer, shoot me a PM.
On your machines that work, were you required to or asked for Windows Credentials either when selecting the destination during the backup creation process or when you selected to proceed with the backup?
If yes, what credentials did you enter?
Yes I was prompted. All of my PCs now use my MS account, thus I have the same ID on all systems. When I used earlier versions of windows (XP, Win7, Vista, Win8, Win8.1) this made it super simple for me to connect the PCs on my LAN. May not have been the best move but I could not get the shares working correctly otherwise. Since then I think I have figured this out but continued to use the same IDs on each system (most of the time).
Is the Kapersky app installed on the other machines that you have working? In some cases Anti-virus applications will block the services of True Image from running. To address this problem it is necessary to add the services to the anti-virus exceptions/whitelist. TI 2016 Processes and services can be found at the link below
Kaspersky Total is installed on all of my PC. I'll look at the KB a bit later, it is now supper time.
Did you run the TI 2016 installer as administrator on the Sony installation?
I'm not sure but normally I don't install as admin, e.g. right-click and select admin. However my ID has Admin rights. I don't know if having the admin rights is the same thing as right-clicking and selecting install as admin.
Can you provide the log files for the failed backups on the Sony here? At this point we need to discover what the failure is. The log files would be helpful in doing that.
Yes - all logs are attached in a zip file
I understand your frustrations. The above are the common things that cause backup failure. If this machine is on a wireless connection and that connection is not a very good connection that could be an issue here but not that likely.
I might also suggest that you take the time to submit the issue using the feedback features available. There is an option within the application that allows for you to submit a system report along with the the feedback in the application in the Help section (open book icon on left of GUI screen). When submitting feedback reference this forum thread by copy and paste link.
Currently all systems are connecte via wired connection. When I replaced the Sony HD and performed a clean install of Win10 I connected it via wire to my network.
Good idea on submitting the feedback.
Just a quick note on "run as administrator". I'd recommend using it always for installation of applications. Even when logged in as "administrator" on a computer, you do not have full admin credentials unless you've enabled the default "hidden" admin account. It's widely thought that this is only for UAC, but not entirely true. You can test this simply by opening command prompt (like you normally would) and trying to run:
nbtstat /R
reference for what the command does... https://technet.microsoft.com/en-us/library/cc957823.aspx
it will fail with "Failed to Purge the NBT Remote Cache Table."
Then run command prompt with "run as administrator" and type the same command and it will be successful with "Successful purge and preload of the NBT Remote Cache Name Table."
This particular command requires elevated rights above the "regular" administrator access. Some applications do not get full access to system resources during installation unless they have the "run as administraor" option at runtime.
Just a quick note on "run as administrator". I'd recommend using it always for installation of applications. Even when logged in as "administrator" on a computer, you do not have full admin credentials unless you've enabled the default "hidden" admin account. It's widely thought that this is only for UAC, but not entirely true. You can test this simply by opening command prompt (like you normally would) and trying to run:
nbtstat /R
reference for what the command does... https://technet.microsoft.com/en-us/library/cc957823.aspx
it will fail with "Failed to Purge the NBT Remote Cache Table."
Then run command prompt with "run as administrator" and type the same command and it will be successful with "Successful purge and preload of the NBT Remote Cache Name Table."
This particular command requires elevated rights above the "regular" administrator access. Some applications do not get full access to system resources during installation unless they have the "run as administraor" option at runtime.
As you stated, it failed in a normal CMD window and ran with success when I started CMD as admin.
I've updated my install notes with your suggestion. In an attempt to make life easy for me several years ago I create an installation document and as I've moved to different windows releases I've attempted to update the document. Most of the applications I've installed are also documented (I sometimes forget to update it) and it has saved me many times.
If I modify the shortcut to Run as Admin (right-click on shortcut, select Properties, click on Shortcut tab, click the Advance button, check the box for Run as administrator. Will the accomplish almost the same thing. Or should I just reinstall as admin?
Late Dec 2015 I was forced to perfrom a clean install on my desktop because the upgrade attempt failed to run. Most of the applications I have installed I just ran the install under my account, e.g. not as admin. It would not be a huge task to just reinstall as admin.
Is the Kapersky app installed on the other machines that you have working? In some cases Anti-virus applications will block the services of True Image from running. To address this problem it is necessary to add the services to the anti-virus exceptions/whitelist. TI 2016 Processes and services can be found at the link below
I have Kaspersky Total Security v16 installed. It was difficult finding all of the files listed in the KB article and some I could not find. However KTS v16 seem to be allowing ATI2016, there are numerous entries in KTS for Acronis and everything was set to "Allowed".
I did NOT see anything is the High Restricted section for Acronis.
This is not to say something critical is blocked, I just did not see it if it is.
jgt1942,
Since you did not install the application as admin I would advise that you uninstall the app, run the cleanup tool again, then reinstall again as administrator. This will insure that admin rights are used in all features of the application. This is necessary as those features of the app which require low level disk access must run at the admin level.
Next, I had a look at your log file, thanks for providing it and rest assured I will delete it from my system once you are squared way here. Your error indicates that, "Access to the file or folder is denied." "Error: The backup has failed. Please close the application that may currently use the file: \\S4\s4-k-h3tb\BU\Acronis\Sony\Incremental\Entire PC (SONY-VAIO)_full_b1_s1_v1.tib."
This error is a bit misleading as what it indicates is the following:
Most probably the issue occurs due to not having permission to the folder or using wrong credentials and not because of another application using the file.
To delete the stored credentials (if you wish you may try steps 4 to 6 first) and provide them again here is what to do:
1. Please run "regedit" as an Administrator.
2. Locate the path "HKEY_CURRENT_USER\SOFTWARE\Acronis\Connections"
3. Deleting the Key "Connections" removes the stored credentials for listed connections, you may try to delete only the ones for failing location if you manage to identify them.
4. If the Network share drive is connected via Router then, please check if you are allowed to copy paste files/folders within the destination directory.
5. Create a backup in the Public folder and check if the backup works. If yes, then please check if the actual destination folder is granted with full permissions.
6. If yes, then create a test backup by creating a new Share on the Network drive and create the backup.
The above in italics is an excerpt from a reply to me from Acronis Support for myself having the same issue/error. My recommendation is that once you have the app reinstalled as admin follow steps 4 and 5. If this proves successful which it should then you have sufficient access in Windows to access and write to the share/drive. We already know that step 6 fials so no sense in going there.
After that please follow steps 1 through 3. The clean install may have already removed the "Connections" registry key. if it has or if there are no other keys below that key then simply close out the registry editor as no action is required.
Next, create a new backup task. When you get to the destination step instead of browsing to the destination folder look to the top of the GUI screen and you will see a path box. Enter the path to the destination drive/folder in the following format:
Example: \\S4\s4-k-h3tb\BU\Acronis\Sony\Incremental\
Now look to the right at the end of the box and you will see a carat that looks like this > Click on that carat and a popup credentials box should appear. In this credentials popup enter the Homegroup username and the homegroup password, then click on the test connection button. You should get a confirmation that connection has been made. Once you have that the backup should run.
I know that the popup credentials box will ask for your Windows password but that is not what you need to enter. That is a shortcoming in the product and should be soon corrected. What is needed is the network credentials for access to the shared drive.
These steps should remedy your issue.