none
Image Backup and Restore For Windows 10 Professional RRS feed

  • Question

  • Hello:

    I though I remembered reading there were issues with the image backup and restore of Windows 10 Pro workstations using Windows Server 2016 Essentials.

    Does anyone have experience doing successful image backup/restores for a Windows 10 Pro workstation on Server 2016 Essentials?

    Thanks,


    Rich Locus, Logicwurks, LLC

    http://www.logicwurks.com

    Monday, April 22, 2019 12:25 AM

Answers

  • hi,
    1 can you share the problem link to me ? it seems that there is no backup problem for win10pro 1709 on server 2016 essentials in my lab. like picture
    2 Windows Server Essentials
    This section applies to a server running Windows Server Essentials. The following computer operating systems are supported:
    Windows 10 Pro
    https://docs.microsoft.com/en-us/windows-server-essentials/use/get-connected-in-windows-server-essentials
    3 if we occur computer backup and restore errors issue ,we can refer below document to do troubleshoot
    Troubleshoot computer backup and restore errors in Windows Server Essentials
    https://docs.microsoft.com/en-us/windows-server-essentials/support/troubleshoot-computer-backup-and-restore-errors-in-windows-server-essentials

    For more information, see Manage Client Backup and Restore a full system from an existing client computer backup.
    https://docs.microsoft.com/en-us/windows-server-essentials/manage/manage-backup-and-restore-in-windows-server-essentials


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, April 22, 2019 3:32 PM
    Moderator
  • Hi Rich, I run several Windows 10 Pro workstations with my WSE 2016 server.  Most are running 1809, but I just updated one to 1903. They all back up just fine. 

    I saw on another post that you said you were migrating from WHS 2011.  In that case, you should be aware that it is possible to connect your workstations to the WSE 2016 server without joining them to the domain. Follow the official Microsoft instructions here: 

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/aa40963c-7235-40f7-85f5-8f8d030a7c13/how-to-skip-domain-joining-during-client-deployment-in-a-windows-server-2012-essentials-network

    You may find that DNS settings become an issue for non domain-joined clients. There is a lot of information in the 2012 and 2016 Essentials forums that can help you navigate this successfully. Do a search for more. 

    Finally, unlike WHS 2011, there is no way to persistently save passwords so that the Launchpad can run at start and log non-domain joined users into the server automatically. Worse, if you do log in via the Launchpad, any existing saved credentials are overwritten with session-level credentials that disappear at log off. (It's complicated to explain, but basically it means that users must actively log into the Launchpad each time in order to access server folders.)

    For this reason, you may find it best to not use the Launchpad at all. You can save persistent credentials for each user using Windows Credential Manager. This gives them access to shared folders while using Windows without having to use the Launchpad at all. (These credentials will need to be recreated if the Launchpad is used.)

    Good luck.

     

    • Marked as answer by RichLocus Wednesday, April 24, 2019 4:05 PM
    Wednesday, April 24, 2019 12:01 AM

All replies

  • hi,
    1 can you share the problem link to me ? it seems that there is no backup problem for win10pro 1709 on server 2016 essentials in my lab. like picture
    2 Windows Server Essentials
    This section applies to a server running Windows Server Essentials. The following computer operating systems are supported:
    Windows 10 Pro
    https://docs.microsoft.com/en-us/windows-server-essentials/use/get-connected-in-windows-server-essentials
    3 if we occur computer backup and restore errors issue ,we can refer below document to do troubleshoot
    Troubleshoot computer backup and restore errors in Windows Server Essentials
    https://docs.microsoft.com/en-us/windows-server-essentials/support/troubleshoot-computer-backup-and-restore-errors-in-windows-server-essentials

    For more information, see Manage Client Backup and Restore a full system from an existing client computer backup.
    https://docs.microsoft.com/en-us/windows-server-essentials/manage/manage-backup-and-restore-in-windows-server-essentials


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, April 22, 2019 3:32 PM
    Moderator
  • Andy:

    I think the quote I read regarding a problem with Windows 10 Pro backups on Server 2016 essentials was a user who posted an incorrect post.  I couldn't locate it, so I will assume that there is no problem with Windows 10 backups.

    Thanks for the information you presented.

    Regards,


    Rich Locus, Logicwurks, LLC

    http://www.logicwurks.com

    Monday, April 22, 2019 4:03 PM
  • Hi Rich, I run several Windows 10 Pro workstations with my WSE 2016 server.  Most are running 1809, but I just updated one to 1903. They all back up just fine. 

    I saw on another post that you said you were migrating from WHS 2011.  In that case, you should be aware that it is possible to connect your workstations to the WSE 2016 server without joining them to the domain. Follow the official Microsoft instructions here: 

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/aa40963c-7235-40f7-85f5-8f8d030a7c13/how-to-skip-domain-joining-during-client-deployment-in-a-windows-server-2012-essentials-network

    You may find that DNS settings become an issue for non domain-joined clients. There is a lot of information in the 2012 and 2016 Essentials forums that can help you navigate this successfully. Do a search for more. 

    Finally, unlike WHS 2011, there is no way to persistently save passwords so that the Launchpad can run at start and log non-domain joined users into the server automatically. Worse, if you do log in via the Launchpad, any existing saved credentials are overwritten with session-level credentials that disappear at log off. (It's complicated to explain, but basically it means that users must actively log into the Launchpad each time in order to access server folders.)

    For this reason, you may find it best to not use the Launchpad at all. You can save persistent credentials for each user using Windows Credential Manager. This gives them access to shared folders while using Windows without having to use the Launchpad at all. (These credentials will need to be recreated if the Launchpad is used.)

    Good luck.

     

    • Marked as answer by RichLocus Wednesday, April 24, 2019 4:05 PM
    Wednesday, April 24, 2019 12:01 AM
  • Thanks Gary!

    Regards,


    Rich Locus, Logicwurks, LLC

    http://www.logicwurks.com

    Wednesday, April 24, 2019 4:05 PM