From a513936feb68ec32666ca681a2768f4ab7d84643 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Fri, 22 Nov 2019 12:08:48 +0500 Subject: [PATCH] Update usmt-hard-link-migration-store.md --- windows/deployment/usmt/usmt-hard-link-migration-store.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/usmt/usmt-hard-link-migration-store.md b/windows/deployment/usmt/usmt-hard-link-migration-store.md index 4b2d8385c2..d43c1fc21a 100644 --- a/windows/deployment/usmt/usmt-hard-link-migration-store.md +++ b/windows/deployment/usmt/usmt-hard-link-migration-store.md @@ -113,6 +113,9 @@ For example, a company has decided to deploy Windows 10 on all of their compute 3. An administrator runs the LoadState command-line tool on each computer. The LoadState tool restores user state back on each computer. +> [!NOTE] +> During the update of domain-joined computer, the profiles of the users which's SID cannot be resolved would not be migrated. In case of using Hard-Link Migration Store, it could cause the data lost. + ## Hard-Link Migration Store Details