Forum Discussion
Solved
WAC + Storage Migration Service: Source fails validation - SMB connection, access denied
Hi all, I'm brand new to WAC and Storage Migration Services. I'm trying to set it up so that I can copy data from SourceA server to TargetB server. SourceA is being migrated to TargetB machine, s...
Oh blimey!! I obviously had the conceptual nature of this down wrong.
During this first phase, setting up the Job, you will specify the 1 (or more) Source machines - you are NOT also setting up the Destination machine! There is a separate 2nd phase where you will set up the Destination machine. That was my flawed impression - I was setting up the Source and Destination machines during the same phase - thus only 1 UN/PW configured.
Bump. 🙂
- Maybe not specific answers - but does anyone have suggestions on how to troubleshoot this issue more?
I don't seem to see any entries in Event Viewer for this action. But the 'Events' view in WAC -> Storage Migration Services -> Admin -> Debug listed a few errors, but nothing that seemed to lead to anything that wasn't encompassed in the basic error message.
Installed some OS Updates. WAC warned me that SMB 1 was active on the Source machine, so I disabled that. Rebooted.- FYI - removing SMB1 and applying the OS updates didn't help at all. The WAC->SMS validation process throws the 'Access denied' error. And I went ahead and did the Inventory process as well - same kind of issues.
- Errrr.... well durn it. I swear I tried this before, and had got the same results.
So went through creating a Job again; I was trying to use a common Admin account that is shared amongs machines, but it was giving me errors about it. (I swear I had used that login before. Yes, I had the credentials correct. 🙂 ) So I instead specified the general Administrator account for the remote machine (SourceA in my description above). When I finished the basic Job setup and tried the Validate step, IT WORKED! At least for SourceA machine (the one that had been failing before). But it now is failing for the TargetB machine... because this one account is different on this machine.
So... two things:
1) Why the heck can't I specify a UN/PW per machine? This seems like a huge oversight for administering a bunch of different machines.
2) What special User setup/configuration/privilege do I need to specify on the common account so that it (WAC, SMS, etc) will work on these machines?
(Oh great - now I'm getting an authentication error from the MS Tech community site! 😞 )