Keep getting "Uploading USMT to: ##### followed by The network name cannot be found.

[ChrisFromIT]

Describe the bug A clear and concise description of what the bug is.

Hi I am starting on the process of migrating users from a Windows 10 to W11 environment and thought I would try using your tool. Unfortunately, I am getting the error "The network name cannot be found." "Error uploading USMT to: 8TB17D3"

SuperGrate is able to locate the computer, and identify the users (local and Domain) - it will even do the Size Calculations on the selected users (All domain) but then this error occurs.

I attached a screen shot of the error.

All drives are shared to Everyone R/W (for testing)

To Reproduce Do what I said above.

Expected behavior I expected the tool to copy the USMT to the network computer, run scanstate, copy USMT to the new computer and run loadstate.

Screenshots If applicable, add screenshots to help explain your problem.

Logs

**IMPORTANT**

To retrieve the logs, click "File", the select "Save log..." Copy the contents of the log file and paste it here.
Refrain from copying and pasting the log from the console since it does not output verbose information.

[SUCCESS]<2:29:17 PM> Config loaded!
[SUCCESS]<2:29:17 PM> Welcome to Super Grate! v1.3.5.1
[INFO]<2:29:17 PM> Enter some information to get started!
[INFO]<2:29:21 PM> Getting list of users on: 8TB17D3...
[VERBOSE]<2:29:21 PM> Found: WICHE_NET\username
[VERBOSE]<2:29:21 PM> Found: 8TB17D3\Administrator
[VERBOSE]<2:29:21 PM> Found: NT AUTHORITY\NETWORK SERVICE
[VERBOSE]<2:29:21 PM> Skipped: S-1-5-20: NT AUTHORITY\NETWORK SERVICE.
[VERBOSE]<2:29:21 PM> Found: NT AUTHORITY\LOCAL SERVICE
[VERBOSE]<2:29:21 PM> Skipped: S-1-5-19: NT AUTHORITY\LOCAL SERVICE.
[VERBOSE]<2:29:21 PM> Found: NT AUTHORITY\SYSTEM
[VERBOSE]<2:29:21 PM> Skipped: S-1-5-18: NT AUTHORITY\SYSTEM.
[SUCCESS]<2:29:21 PM> Users listed successfully.
[INFO]<2:29:23 PM> Retrieving user properties...
[VERBOSE]<2:29:23 PM> Found: WICHE_NET\username
[INFO]<2:29:23 PM> Calculating profile size for: WICHE_NET\username...
[WARNING]<2:29:25 PM> Canceling current task...
[INFO]<2:29:25 PM> Canceled.
[INFO]<2:29:27 PM> Reading OS Architecture...
[INFO]<2:29:27 PM> OS Architecture is: X64.
[INFO]<2:29:27 PM> Uploading USMT to: 8TB17D3
[ERROR]<2:29:27 PM> The network name cannot be found.
[VERBOSE]<2:29:27 PM> ERROR
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
   at SuperGrate.IO.FileOperations.CopyFolder(String Source, String Destination)
   at SuperGrate.USMT.<>c.<<CopyUSMT>b__13_0>d.MoveNext()
[ERROR]<2:29:27 PM> Error uploading USMT to: 8TB17D3
[INFO]<2:29:27 PM> Done.
[INFO]<2:29:31 PM> Writing log to: .\LOGS...

Additional context

Added the XML File:

<?xml version="1.0" encoding="utf-8"?>

D:\SuperGrate\USMT5 F:\DeploymentShare\Tools\x86\USMT5 D:\SuperGrate D:\SuperGrate\SGUser_Store /config:Config.xml /i:ExcludeDrives_D_to_Z.xml /i:ExcludeSystemFolders.xml /i:ExcludeOneDriveRedirFolders.xml /i:MigApp.xml /i:MigUser.xml /i:Win10.xml /i:Win11.xml /i:custom.xml /c /r:3 /o /config:Config.xml /i:ExcludeDrives_D_to_Z.xml /i:ExcludeSystemFolders.xml /i:ExcludeOneDriveRedirFolders.xml /i:MigApp.xml /i:MigUser.xml /i:Win10.xml /i:Win11.xml /i:custom.xml /c /r:3 /lac /lae false false true false .\LOGS 0,3,9 0,1,5,6,4 1 8TB17D3 None Tls12

[krisdb2009]

Does the client's PC have a C$ share enabled?

[ChrisFromIT]

Hi @krisdb2009 - thanks for the response - I just looked at the shares on all of our systems and C$ is shared "for administrative purposes". I thought it was strange that the system is able to scan and provide the size of the info to be copied - and the users on that device (it was a long term loaner), but it can't find it when the initial Copy of USMT is being done... Chris

[krisdb2009]

Chris,

Check and see if you can access the C$ share directly in file explorer \\PCNAME\C$ I am thinking your account doesn't have access to this for some reason and that's why you are getting that "cannot find" error. The stack trace in your log is indicating its failing to create a directory at C$, so with your same account try to make a folder to see if your account has permissions to do so.

[ChrisFromIT]

Hi - I was able to link and create a folder without any issues.

[krisdb2009]

Is "8TB17D3" really the PC name being used? I would like to try on my own PC with the same name to try to re-produce.

[ChrisFromIT]

Yes it is the name - we use the Dell Service Tag as the naming convention for the systems.
It failed on others also - JMRZJR2, C7M6KR2 are a couple more of them.

[ChrisFromIT]

I should also mention that these are all domain connected devices, they are named WICHE_NET\name on the domain Wiche.edu. If you just ping the name though, you get a response so I don't think that matters. I am able to connect to, for example, 8TB1TD3\C$ directly with no password needed - and I was able to create a folder, and a file on that machine. I appreciate your help with this... Chris

On Mon, Apr 3, 2023 at 1:12 PM Dylan Bickerstaff @.***> wrote:

Is "8TB17D3" really the PC name being used? I would like to try on my own PC with the same name to try to re-produce.

— Reply to this email directly, view it on GitHub https://github.com/belowaverage-org/SuperGrate/issues/75#issuecomment-1494840033, or unsubscribe https://github.com/notifications/unsubscribe-auth/A64NK57ZT5TO7WTVPDT6QSDW7MOI7ANCNFSM6AAAAAAWPDV7V4 . You are receiving this because you authored the thread.Message ID: @.***>

[krisdb2009]

Can you upload a copy of your SuperGrate.xml again? It didn't come through correctly in the initial post.

[krisdb2009]

In particular, I am interested in what "SuperGratePayloadPath" is set to.

[ChrisFromIT]

Hey - Sorry for the delay - and thanks for looking at this again. Had to make it TXT format because it kept removing all of the tags -

SuperGrate.txt

I decided to try running SuperGrate from the C: drive - that worked to a point - now it will run the USMT Copy but won't start the ScanState program... Here are those results starting from the last copy into the SuperGrate folder on the machine it's copying from. I also tried the USMT folder on the C drive, and D drive (updating the XML) to see if that made any difference - it didn't.

10:34:16 AM> D:\SuperGrate\USMT5\ReplacementManifests8\WindowsSearchEngine\WSearchMigPlugin.dll => \8TB17D3\C$\SuperGrate\ReplacementManifests8\WindowsSearchEngine\WSearchMigPlugin.dll 10:34:16 AM> USMT uploaded successfully. 10:34:16 AM> Capturing user state: 'WICHE_NET\ccartwright' on '8TB17D3'... 10:34:16 AM> Waiting for scanstate to finish... 10:34:16 AM> Couldn't connect to remote machine. 10:34:16 AM> ERROR at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine) at System.Diagnostics.Process.GetProcesses(String machineName) at System.Diagnostics.Process.GetProcessesByName(String processName, String machineName) at SuperGrate.Remote.<>c__DisplayClass2_0.<b__0>d.MoveNext() 10:34:16 AM> Couldn't get process information from performance counter. 10:34:16 AM> ERROR at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library) at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName, Boolean isRemoteMachine) 10:34:16 AM> Failed to check if scanstate is still running. 10:34:19 AM> Removing USMT from: 8TB17D3... 10:34:20 AM> USMT removed successfully. 10:34:20 AM> Done.

[ChrisFromIT]

I did a bit more digging and thought that this error was coming because I am RDP's into the Server that I'm running it on - -but I tried by logging in directly and I am not getting any different results. It took me a bit to realize that the "Payload" is the location where SuperGrate is COPYING the data to on the remote machine - yes, the C$ drive makes more sense in this case. I also checked the RPC Services, including DCOM to make sure it is running - it is.

[krisdb2009]

Yea I was about to say, I'm guessing you set <SuperGratePayloadPath>D:\SuperGrate</SuperGratePayloadPath> back to C:\SuperGrate ?

Did it resolve your issue?

[ChrisFromIT]

HI Dylan - It almost did... I added the Verbose Log from what happened next - it was able to copy the files over, then it said it could not connect. I added some more info in the Github space for you. I tried moving the USMT out of the SuperGrate folder - it copied, but then could not connect. I killed the task before it was done copying and it did actually do the copy now - but still no connect. Let me know if you need more info - I'm a programmer also so I can do whatever you need. Chris

On Tue, Apr 4, 2023 at 12:46 PM Dylan Bickerstaff @.***> wrote:

Yea I was about to say, I'm guessing you set

D:\SuperGrate back to C:\SuperGrate ? Did it resolve your issue? — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ChrisFromIT]

Yes it does...

On 3/31/2023 7:09:08 PM, Dylan Bickerstaff @.> wrote: Does the client's PC have a C$ share enabled? [image] [https://user-images.githubusercontent.com/8226974/229258314-028ae89f-26d4-4d4d-9241-c47b8df440e5.png] — Reply to this email directly, view it on GitHub [https://github.com/belowaverage-org/SuperGrate/issues/75#issuecomment-1492771469], or unsubscribe [https://github.com/notifications/unsubscribe-auth/A64NK53VVN7L6SUWNUQL4JTW6553HANCNFSM6AAAAAAWPDV7V4]. You are receiving this because you authored the thread.Message ID: @.>

[krisdb2009]

So that new error you are getting might be because the remote registry service is not running on your client PCs. You can push to enable via GPO. I want to remove this requirement (I honestly thought I did already) and use WMI to get the remote process list.

[ChrisFromIT]

I'll take a look at that ... thanks! I ended up reverting to a PowerShell program that did the same thing but I would like to use this tool - it is a great option.

PS: I sent you a 6-pack for the help ..

[krisdb2009]

Oh wow thank you!