24 replies to this topic

[Unrealistic]

Alright, so while I don't like the solution for my personal issue, I think this should solve your issues.

It's very simple and I overlooked it on the first try. Create a Microsoft Account on Win8 and browse to the machine you want to access via \\computername.

Authenticate and check the remember password option. You should be set from then on out.

Attached Images

• 

[jakem1]

Unrealistic, on 11 August 2012 - 18:22, said:

Well right, but then you can't use the live services sync. I know I'm talking about a different thing, but it's still an issue.

I agree. It's a small issue but it's still an issue and it would have been nice if MS had given us the option to create local/AD accounts and link them to an MS account for syncing.

[xendrome]

Yeah that was my work around also, and to the other poster HomeGroup isn't good for permissions at a user level.

I wonder if when you join the system to a domain, does it remove the ability to convert to a "Microsoft Account"

[Anthonyd]

jakem1, on 11 August 2012 - 19:29, said:

I agree. It's a small issue but it's still an issue and it would have been nice if MS had given us the option to create local/AD accounts and link them to an MS account for syncing.

You can link your domain account (AD) with an MS account, and you can also block that with a GPO.

[+BudMan]

I still don't see what the issue is here?

There is not much difference between you logging in locally with billy and Password1 so it matches up with remote machine billy Password1 and accessing the share, via saving credentials to send billy Password1 when your logged in with susan@microsoft.id

Its not like your local account was sync'd in any way to the remote machines shares\account - if you changed the password on your machines local billy account, you would of failed to auth. So either you would have to had changed the account info on the remote machine or saved credentials.

It's not some other account logged into you local machine would have access to shares that billy does.

I don't see anything really different here other than saving credentials once vs them being what you logged in with. The method of access is still the same to the remote share - your authing with billy Password1. Be it thats what you logged in with, or what you saved as auth for that remote machine.

[jakem1]

Anthonyd, on 11 August 2012 - 20:09, said:

You can link your domain account (AD) with an MS account, and you can also block that with a GPO.

Ah, I didn't know that. Thanks.

So if you can do this to an AD account why can't you do it with a local account?

[Anthonyd]

jakem1, on 11 August 2012 - 20:22, said:

Ah, I didn't know that. Thanks.

So if you can do this to an AD account why can't you do it with a local account?

What would be the benefits from doing that with a normal local account?

[jakem1]

Anthonyd, on 11 August 2012 - 20:27, said:

What would be the benefits from doing that with a normal local account?

Compatibility with Windows Home Server.

[Anthonyd]

jakem1, on 11 August 2012 - 21:24, said:

Compatibility with Windows Home Server.

Care to detail it?
Because WHS is a dead product and I don't see how it's related to the discussion

[xendrome]

Anthonyd, on 11 August 2012 - 21:32, said:

Care to detail it?
Because WHS is a dead product and I don't see how it's related to the discussion

WHS 2011 is end of life in 2016, and is still being sold on systems today. So just because MS isn't making a successor to it, doesn't instantly mean it is dead.