NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HELP - Former ReadyCloud users cannot see shares after My.Netgear migration
Good morning,
ReadyCloud is effectively down and unusable for my client. Would appreciate any help you can provide ASAP!
The day of the dreaded My.Netgear migration arrived. I was able to successfully upgrade the core ReadyCloud user to a My.Netgear account, upgraded the firmware from 6.4.0 to 6.5.0, rebooted, and asked 20ish users to go through the ReadyCloud to My.Netgear account migration.
I found afterwards that they did not show up under ReadyCloud's Management page as being attached to any shares.
Although the My.Netgear account appeared to be correctly associated with ReadyCloud on the local admin console, I turned off ReadyCloud, and disassociated the account. I reassociated it and added one user to one share. This user had previously been a ReadyCloud account, but we transitioned her to a My.Netgear account before the disassociation.
Added user to the share via email address (same address as associated with her ReadyCloud and My.Netgear accounts) from the Management pane with Read/Write permissions. Afterwards, the user received the verification email from ReadyCloud, and the envelope icon showed up on the share in the Management pane. The user successfully verified and now the envelope icon is correctly changed to the person with the cloud icon, however if you log onto that user's My.Netgear account you see that no shares are available.
I repeated this process with my own email address, which had never been attached to ReadyCloud. I was correctly prompted to create a My.Netgear account, and I was able to add myself to the share with Read/Write permissions and see it while logged into my My.Netgear account with no issues.
I suspect the best solution would be to permanently wipe out the old ReadyCloud accounts associated with this client and have them build fresh My.Netgear ones, but I can't find any mechanism to do so. I am certainly not going to request the customer pay for support when the system is broken on Netgear's end!
Please let me know if there are any other steps I can try or any other insights you can provide.
Thanks!
Oscar
7 Replies
Replies have been turned off for this discussion
The binding of a ReadyCLOUD account to a NETGEAR account is considered a permanent merge. There is no 'undo' or 'swap' feature.
After your friends migrated their account, were they prompted to confirm their account via e-mail?
You can create new NETGEAR accounts directly from the readycloud.netgear.com sign in screen. Click "Create Account", but I think this is unnecessary.
Thank you kohdee. Apologies for the delayed response as I have been on holiday.
I figured that there was no way to revert, but perhaps we can arrange a purge of all ReadyCloud and My.Netgear accounts for this customer? If this is possible, I can PM you the details for the customer. This would let us build fresh new accounts in My.Netgear.
Beyond this, I appreciate any other ideas you may have.
Thanks,
Oscar
Hope you enjoyed your holiday.
Perhaps you should open a support case.
Hello FIT-OJanicki,
Welcome to the community!
Is the user entering the account name in an email format and in ReadyCloud web site? Are both email addresses in the same domain?
Regards,
Hello JennC,
Thanks for your help! So the original ReadyCloud accounts were a mishmash of usernames (similar to first.lastname) and email addresses (firstname@client.com). The one I have been doing the testing on was firstname.lastname.
The new My.Netgear accounts are all emails. I did notice that some of the oldest users had a clientname.org rather than a clientname.com email, and this one may have been one of those. The verification sometimes failed with those, but most went through (presumably because the .org account was forwarding to the new .com account, so they could still receive/reply to the verification email.). The ones I saw no email verification for I had manually set to Bind to New Email address or similar, pointing it to the current clientname.com domain.
I'd happily set all the old accounts to manually bind to a specified address in the .com domain, but I'm guessing that ship has sailed?
Hello FIT-OJanicki,
Try making the email addresses with .com, I heard that if the email addresses are not as simple as .com like .co.uk they get problems, I believe it is now being studied.
Regards,
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
