Storage Migration Service Proxy fails to register

%3CLINGO-SUB%20id%3D%22lingo-sub-2887555%22%20slang%3D%22en-US%22%3EStorage%20Migration%20Service%20Proxy%20fails%20to%20register%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2887555%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20investigating%20the%20Storage%20Migration%20Service%20in%20Windows%20Admin%20Center%20as%20an%20option%20to%20migrate%20off%20a%20Server%202012%20file%20server.%20I%20have%20WAC%20and%20the%20services%20set%20up%20in%20a%20test%20environment%20and%20I'm%20running%20into%20an%20issue%20trying%20to%20get%20the%20destination%20proxy%20registered%20on%20the%20orchestration%20server.%20The%20account%20I'm%20using%20is%20a%20local%20admin%20on%20three%20servers%20involved%20and%20the%20firewall%20rules%20are%20open%20as%20required.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20fails%20to%20verify%20via%20WAC%20SMS%20interface%20(%22Warning%3A%20The%20destination%20proxy%20wasn't%20found.%22)%2C%20so%20I've%20dropped%20down%20to%20Powershell%20and%20using%20this%20command%20for%20testing%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3ERegister-SmsProxy%20-ComputerName%20%3CDESTINATION%20fqdn%3D%22%22%3E%20-force%3C%2FDESTINATION%3E%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EThis%20returns%3A%3C%2FP%3E%3CPRE%3ERegister-SmsProxy%20%3A%20Make%20sure%20the%20proxy%20service%20is%20installed%20and%20running%2C%20and%20then%20try%20again.%20The%20proxy%20isn't%3CBR%20%2F%3Ecurrently%20available.%3C%2FPRE%3E%3CP%3E%26nbsp%3BThe%20debug%20event%20logs%20on%20the%20destination%20has%201%20successful%20registration%20of%20the%20orchestrator%20host%20as%20orchestrator%2C%20then%20there%20are%202%20errors%20with%20'Access%20Denied'%20and%20a%20socket%20connection%20timeout.%20On%20the%20orchestrator%20server%2C%20the%20admin%20log%20for%20the%20StorageMigration%20service%20show%20%22Couldn't%20register%20the%20proxy%2C%20access%20is%20denied.%22%20and%20the%20debug%20log%20shows%20%22CreateJob%20request%20failed%2C%20Access%20is%20denied%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20suggestions%20for%20further%20troubleshooting%20or%20what%20I%20might%20be%20missing%20in%20the%20configuration%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETest%2FLab%20Environment%3A%3C%2FP%3E%3CP%3EWAC%2FOrchestration%20server%20is%20Server%202019%20with%20all%20updates%2C%20Storage%20migration%20service%20installed%3C%2FP%3E%3CP%3ESource%20server%20is%20Server%202019%20with%20all%20updates%3C%2FP%3E%3CP%3EDestination%20server%20is%20Server%202019%20with%20all%20updates%2C%20Storage%20Migration%20and%20Storage%20Migration%20Service%20Proxy%20service%20installed%3C%2FP%3E%3CP%3EWAC%20is%20v2103.2%2C%20Storage%20Migration%20Service%20extension%20is%20v1.143.0.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2887826%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20Proxy%20fails%20to%20register%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2887826%22%20slang%3D%22en-US%22%3E%3CP%3EPosting%20the%20solution%20to%20my%20own%20problem%3A%3C%2FP%3E%3CP%3EThe%20orchestrator%20server%20machine%20account%20needed%20to%20explicitly%20be%20a%20member%20of%20the%20local%20admins%20group%20on%20the%20destination%20server.%20Then%20the%20proxy%20was%20found%20on%20the%20destination%20server%20and%20it%20was%20used.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I'm investigating the Storage Migration Service in Windows Admin Center as an option to migrate off a Server 2012 file server. I have WAC and the services set up in a test environment and I'm running into an issue trying to get the destination proxy registered on the orchestration server. The account I'm using is a local admin on three servers involved and the firewall rules are open as required.

 

It fails to verify via WAC SMS interface ("Warning: The destination proxy wasn't found."), so I've dropped down to Powershell and using this command for testing:

Register-SmsProxy -ComputerName <destination FQDN> -force

This returns:

Register-SmsProxy : Make sure the proxy service is installed and running, and then try again. The proxy isn't
currently available.

 The debug event logs on the destination has 1 successful registration of the orchestrator host as orchestrator, then there are 2 errors with 'Access Denied' and a socket connection timeout. On the orchestrator server, the admin log for the StorageMigration service show "Couldn't register the proxy, access is denied." and the debug log shows "CreateJob request failed, Access is denied"

 

Any suggestions for further troubleshooting or what I might be missing in the configuration?

 

Test/Lab Environment:

WAC/Orchestration server is Server 2019 with all updates, Storage migration service installed

Source server is Server 2019 with all updates

Destination server is Server 2019 with all updates, Storage Migration and Storage Migration Service Proxy service installed

WAC is v2103.2, Storage Migration Service extension is v1.143.0.

1 Reply

Posting the solution to my own problem:

The orchestrator server machine account needed to explicitly be a member of the local admins group on the destination server. Then the proxy was found on the destination server and it was used.

We support Ukraine and condemn war. Push Russian government to act against war. Be brave, vocal and show your support to Ukraine. Follow the latest news HERE