Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-11 > #16769 > unrolled thread

Problems with Microsoft account

Back to article view | Back to alt.comp.os.windows-11

Contents

  Problems with Microsoft account Fokke Nauta <fnauta@solfon.nl> - 2025-02-03 19:22 +0100
    Re: Problems with Microsoft account Fokke Nauta <fnauta@solfon.nl> - 2025-02-03 19:38 +0100
      Re: Problems with Microsoft account Graham J <nobody@nowhere.co.uk> - 2025-02-03 18:52 +0000
    Re: Problems with Microsoft account Andy Burns <usenet@andyburns.uk> - 2025-02-03 20:44 +0000
      Re: Problems with Microsoft account Fokke Nauta <fnauta@solfon.nl> - 2025-02-13 15:12 +0100
        Re: Problems with Microsoft account Andy Burns <usenet@andyburns.uk> - 2025-02-14 07:54 +0000
          Re: Problems with Microsoft account Fokke Nauta <fnauta@solfon.nl> - 2025-02-28 18:55 +0100
    Re: Problems with Microsoft account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-02-03 14:34 -0700
      Re: Problems with Microsoft account "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 23:33 +0100
        Re: Problems with Microsoft account Graham J <nobody@nowhere.co.uk> - 2025-02-03 23:09 +0000
      Re: Problems with Microsoft account Char Jackson <none@none.invalid> - 2025-02-03 19:46 -0600
    Re: Problems with Microsoft account Paul <nospam@needed.invalid> - 2025-02-03 20:26 -0500
      Re: Problems with Microsoft account ...w¡ñ§±¤ñ  <winstonmvp@gmail.com> - 2025-02-03 19:54 -0700
        Re: Problems with Microsoft account Paul <nospam@needed.invalid> - 2025-02-04 03:20 -0500
          Re: Problems with Microsoft account Java Jive <java@evij.com.invalid> - 2025-02-04 12:25 +0000
    Re: Problems with Microsoft account Fokke Nauta <fnauta@solfon.nl> - 2025-02-13 15:13 +0100

#16769 — Problems with Microsoft account

Hi all,

My wife and me bought both a time ago a laptop with a W11 account. I 
configured my account and I found out that my laptop was not accessible 
from our local network. It was a Microsoft account. I created a new non 
Microsoft account and deleted the MS account. Now was my laptop 
accessible from the network.
But this was a long time ago. Now I want to access my wife's laptop from 
the laptop, and while she still haves her MS account, I can't access her.
As it is quite a job to create a new non MS account, and set all things 
and software from her current MS account over to her new account, is it 
perhaps possible to change her MS account to a non MS account?
I'm curious to your answers.
Many thanks in advance.

With kind regards,
Fokke Nauta

[toc] | [next] | [standalone]

#16770

On 03/02/2025 19:22, Fokke Nauta wrote:
> Hi all,
> 
> My wife and me bought both a time ago a laptop with a W11 account. I 
> configured my account and I found out that my laptop was not accessible 
> from our local network. It was a Microsoft account. I created a new non 
> Microsoft account and deleted the MS account. Now was my laptop 
> accessible from the network.
> But this was a long time ago. Now I want to access my wife's laptop from 
> the laptop, and while she still haves her MS account, I can't access her.
> As it is quite a job to create a new non MS account, and set all things 
> and software from her current MS account over to her new account, is it 
> perhaps possible to change her MS account to a non MS account?
> I'm curious to your answers.
> Many thanks in advance.
> 
> With kind regards,
> Fokke Nauta

BTW, both laptops are W11 Pro.

[toc] | [prev] | [next] | [standalone]

#16772

Fokke Nauta wrote:
> On 03/02/2025 19:22, Fokke Nauta wrote:
>> Hi all,
>>
>> My wife and me bought both a time ago a laptop with a W11 account. I 
>> configured my account and I found out that my laptop was not 
>> accessible from our local network. It was a Microsoft account. I 
>> created a new non Microsoft account and deleted the MS account. Now 
>> was my laptop accessible from the network.
>> But this was a long time ago. Now I want to access my wife's laptop 
>> from the laptop, and while she still haves her MS account, I can't 
>> access her.
>> As it is quite a job to create a new non MS account, and set all 
>> things and software from her current MS account over to her new 
>> account, is it perhaps possible to change her MS account to a non MS 
>> account?
>> I'm curious to your answers.
>> Many thanks in advance.
>>
>> With kind regards,
>> Fokke Nauta
> 
> BTW, both laptops are W11 Pro.


None of this is easy.  Probably it is most sensible to copy the things 
you want to a memory stick and transfer it from one laptop to the other. 
  Or send via email.

But if you want to share things via your LAN you should start again from 
scratch and create identical local accounts on both laptops.  See below 
from Java Jive as posted in a.c.o.Windows-11 for how to do this, as follows:

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

Windows Sharing Instructions
============================

IMO, M$'s default sharing arrangements have always been dangerously 
insecure.  What follows is the comparatively secure
way that I've always set up sharing, ever since Windows 2000.

Note: These are W7 instructions only, other versions of Windows will
obviously be similar but not exactly the same, because of M$'
pointless and idiotic habit of hiding all the control levers in
different places with every new edition of Windows, thus forcing
people continually to relearn everything they've known for years. (Can
you imagine the catastrophic chaos that would result on the roads if
car manufacturers decided to do that?).

In what follows, I assume that you want to create shares on each PC
visible to others, and that none are work PCs authenticating to a domain
controller server.

On each PC:

1)    Go into ...
     Control Panel, All Control Panel Items,System,
     Advanced system settings, Computer Name, Change
... and ensure that name and workgroup are changed to something
memorable from the defaults, and that the latter is the same for all
the machines that you wish to share files together.

2)    Any user wishing to access a share on a PC must have a user
account on that PC, so set up the necessary accounts up on each PC,
giving them the same logon user id and password as they normally use on
their own PC.  (If on a particular PC you want a user only to be able
to access a share, but not be able to sign on to it, you still need
his/her account to exist, but then it must be added to a block list in
that PC's security policy  -  however, this may not be possible on
some lower cost editions of Windows, and is beyond the scope of these
notes).

3)    Go into ...
     Control Panel, All Control Panel Items,
     Network and Sharing Center, Advanced sharing settings
... and set the following:
     Network discovery
         Probably on, unless reason otherwise;
     File and printer sharing
         Probably on, unless reason otherwise;
     Public folder sharing
         Probably off, unless reason otherwise;
     Media streaming
         Probably off, unless reason otherwise;
     File sharing connections
         Use 128-bit, unless reason otherwise;
     Password protected sharing
         Turn on;
     HomeGroup connections
         Use user accounts and passwords.

4)    On each directory or drive of each machine that you want to
share, creating subdirectories for this as required ...
         <rt-click>, Share with,
             Advanced sharing, Advanced sharing;
         Select Share this folder;
         Type a suitable share name
             (Note:  ending it with a '$' will hide it from
             users casually browsing from other Windows PCs,
             but Linux users may still see it via Samba);
         Type a suitable comment, if required;
         Click Permissions, remove the relatively insecure
         default permissions offered, and then click ...
             Add, Advanced, Find Now
         ... and by <click>ing and <ctrl-click>ing select and add
         the following:
             Admininstrators
             System
             Authenticated Users
         ... and then give them the following permissions ...
             Admininstrators        Full Control
             System            Full Control
             Authenticated Users    Read or Read/Change
                             as required

5)    If necessary, but DO NOT DO THE FOLLOWING ON THE WINDOWS FOLDER OR 
OTHER SYSTEM FOLDERS (hopefully you're not trying to share these anyway, 
not normally recommended) including user folders but sub-directories of 
the latter that you've created especially to share are perfectly safe ...

<rt-click> the drive or directory being shared
and select ...
         Properties
         Security
... and ensure the above permissions are replicated on the drive or
folder itself.

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#16774

Fokke Nauta wrote:

> My wife and me bought both a time ago a laptop with a W11 account. I 
> configured my account and I found out that my laptop was not accessible 
> from our local network. It was a Microsoft account. I created a new non 
> Microsoft account and deleted the MS account. Now was my laptop 
> accessible from the network.
> But this was a long time ago. Now I want to access my wife's laptop from 
> the laptop, and while she still haves her MS account, I can't access her.
> As it is quite a job to create a new non MS account, and set all things 
> and software from her current MS account over to her new account, is it 
> perhaps possible to change her MS account to a non MS account?


Before proceeding ... If the machine is bitlocker encrypted, either make 
sure you have a backup of the recovery key which is NOT stored on the 
computer, or remove the encryption ... if it came encrypted from the 
factory, and it's Home, you might not be able to re-encrypt it (but I 
think the O/P said it was Pro)

settings,
Accounts,
Your Info,
under account Settings, there should be a button
[sign in with a local account instead]

[toc] | [prev] | [next] | [standalone]

#17040

On 03/02/2025 21:44, Andy Burns wrote:
> Fokke Nauta wrote:
> 
>> My wife and me bought both a time ago a laptop with a W11 account. I 
>> configured my account and I found out that my laptop was not 
>> accessible from our local network. It was a Microsoft account. I 
>> created a new non Microsoft account and deleted the MS account. Now 
>> was my laptop accessible from the network.
>> But this was a long time ago. Now I want to access my wife's laptop 
>> from the laptop, and while she still haves her MS account, I can't 
>> access her.
>> As it is quite a job to create a new non MS account, and set all 
>> things and software from her current MS account over to her new 
>> account, is it perhaps possible to change her MS account to a non MS 
>> account?
> 
> 
> Before proceeding ... If the machine is bitlocker encrypted, either make 
> sure you have a backup of the recovery key which is NOT stored on the 
> computer, or remove the encryption ... if it came encrypted from the 
> factory, and it's Home, you might not be able to re-encrypt it (but I 
> think the O/P said it was Pro)

It's not encrypted. And it is Pro indeed.

> settings,
> Accounts,
> Your Info,
> under account Settings, there should be a button
> [sign in with a local account instead]

But that would create a new account. She doesn't want to loose her 
current account.
So this won't work.

Fokke

[toc] | [prev] | [next] | [standalone]

#17055

Fokke Nauta wrote:

> Andy Burns wrote:
> 
>> settings,
>> Accounts,
>> Your Info,
>> under account Settings, there should be a button
>> [sign in with a local account instead]
> 
> But that would create a new account. She doesn't want to loose her 
> current account.
> So this won't work.
It doesn't create a new account, it converts the existing local account 
into a microsoft account (and the process is reversible the same way)

[toc] | [prev] | [next] | [standalone]

#17513

On 14/02/2025 08:54, Andy Burns wrote:
> Fokke Nauta wrote:
> 
>> Andy Burns wrote:
>>
>>> settings,
>>> Accounts,
>>> Your Info,
>>> under account Settings, there should be a button
>>> [sign in with a local account instead]
>>
>> But that would create a new account. She doesn't want to loose her 
>> current account.
>> So this won't work.
> It doesn't create a new account, it converts the existing local account 
> into a microsoft account (and the process is reversible the same way)

Thanks for your info.
I tried it, but it looked as I created a new account. I deleted it, and 
we now go further with her own account.

Thanks anyway.

With regards,
Fokke Nauta

[toc] | [prev] | [next] | [standalone]

#16775

Fokke Nauta wrote on 2/3/25 11:22 AM:
> Hi all,
> 
> My wife and me bought both a time ago a laptop with a W11 account. I 
> configured my account and I found out that my laptop was not accessible 
> from our local network. It was a Microsoft account. I created a new non 
> Microsoft account and deleted the MS account. Now was my laptop 
> accessible from the network.
> But this was a long time ago. Now I want to access my wife's laptop from 
> the laptop, and while she still haves her MS account, I can't access her.
> As it is quite a job to create a new non MS account, and set all things 
> and software from her current MS account over to her new account, is it 
> perhaps possible to change her MS account to a non MS account?
> I'm curious to your answers.
> Many thanks in advance.
> 
> With kind regards,
> Fokke Nauta

Configure both devices with at least the same account Windows logon.
  - i.e. both have the same MSFT account as a Windows logon *or* both 
have the same Local Account logons(username and password)

- Configure Network discovery for discovery and sharing
- Configure your router to assign a unique IP to each device(Lan and/or wifi)
- Configure each device with the same Workgroup name
- On each device, configure the desired folder for sharing in addition to 
the Public folders
- Ensure MSFT services(both Function Discovery, SSDP and UPnP) set to 
Automatic
- Windows credentials(both machines) add the common logon profile 
username/password.

-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#16778

On 2025-02-03 22:34, ...w¡ñ§±¤ñ wrote:
> Fokke Nauta wrote on 2/3/25 11:22 AM:
>> Hi all,
>>
>> My wife and me bought both a time ago a laptop with a W11 account. I 
>> configured my account and I found out that my laptop was not 
>> accessible from our local network. It was a Microsoft account. I 
>> created a new non Microsoft account and deleted the MS account. Now 
>> was my laptop accessible from the network.
>> But this was a long time ago. Now I want to access my wife's laptop 
>> from the laptop, and while she still haves her MS account, I can't 
>> access her.
>> As it is quite a job to create a new non MS account, and set all 
>> things and software from her current MS account over to her new 
>> account, is it perhaps possible to change her MS account to a non MS 
>> account?
>> I'm curious to your answers.
>> Many thanks in advance.
>>
>> With kind regards,
>> Fokke Nauta
> 
> Configure both devices with at least the same account Windows logon.
>   - i.e. both have the same MSFT account as a Windows logon *or* both 
> have the same Local Account logons(username and password)
> 
> - Configure Network discovery for discovery and sharing
> - Configure your router to assign a unique IP to each device(Lan and/or 
> wifi)
> - Configure each device with the same Workgroup name
> - On each device, configure the desired folder for sharing in addition 
> to the Public folders
> - Ensure MSFT services(both Function Discovery, SSDP and UPnP) set to 
> Automatic
> - Windows credentials(both machines) add the common logon profile 
> username/password.
> 


It must be possible to have different accounts, and set at least one 
directory accessible from the other computer. Somehow. Otherwise, this 
sillines breaks business usage.




-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#16779

Carlos E.R. wrote:

[snip]
>>
> 
> 
> It must be possible to have different accounts, and set at least one 
> directory accessible from the other computer. Somehow. Otherwise, this 
> silliness breaks business usage.
> 

No.  Business usage involves a "domain controller" where all user 
accounts are managed.  Shared filesystems have access permissions 
defined, if necessary differently for each user, by file and folder.

Each workstation is "joined" to the domain and managed from the domain 
controller.  The only account which is specific to any workstation, and 
essential, is the "local administrator" used to set up the connection 
with the domain controller.

A small business that does not use a domain controller will run into 
problems unless some care is taken in setting up file sharing and access 
rights.



-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#16782

On Mon, 3 Feb 2025 14:34:59 -0700, ...w¡ñ§±¤ñ  <winstonmvp@gmail.com>
wrote:

>Fokke Nauta wrote on 2/3/25 11:22 AM:
>> Hi all,
>> 
>> My wife and me bought both a time ago a laptop with a W11 account. I 
>> configured my account and I found out that my laptop was not accessible 
>> from our local network. It was a Microsoft account. I created a new non 
>> Microsoft account and deleted the MS account. Now was my laptop 
>> accessible from the network.
>> But this was a long time ago. Now I want to access my wife's laptop from 
>> the laptop, and while she still haves her MS account, I can't access her.
>> As it is quite a job to create a new non MS account, and set all things 
>> and software from her current MS account over to her new account, is it 
>> perhaps possible to change her MS account to a non MS account?
>> I'm curious to your answers.
>> Many thanks in advance.
>> 
>> With kind regards,
>> Fokke Nauta


I've apparently been doing it wrong for the past 25+ years. More below.

>Configure both devices with at least the same account Windows logon.
>  - i.e. both have the same MSFT account as a Windows logon *or* both 
>have the same Local Account logons(username and password)

I don't do that. I've never found it to be necessary.

>- Configure Network discovery for discovery and sharing

I don't do that, other than ensuring that each PC thinks its on a
Private network. My scenario is home use here.

>- Configure your router to assign a unique IP to each device(Lan and/or wifi)

I configure one or more static IPs on each PC, rather than letting the
router do it. Same result, but when you configure a static IP you can
then go back in and add any reasonable number of additional IP
addresses, if needed. If you use DHCP, you're limited to just one. For
most people, that won't be an issue.

>- Configure each device with the same Workgroup name

I don't do that.

>- On each device, configure the desired folder for sharing in addition to 
>the Public folders

I do that.

>- Ensure MSFT services(both Function Discovery, SSDP and UPnP) set to 
>Automatic

I don't check that.

>- Windows credentials(both machines) add the common logon profile 
>username/password.

I don't do that.

Seems like I don't do most of what is supposed to be done, but folder &
file sharing works just fine. I don't have any MSAs and I don't have any
dummy accounts that are used for sharing.

[toc] | [prev] | [next] | [standalone]

#16781

On Mon, 2/3/2025 1:22 PM, Fokke Nauta wrote:
> Hi all,
> 
> My wife and me bought both a time ago a laptop with a W11 account. I configured my account and I found out that my laptop was not accessible from our local network. It was a Microsoft account. I created a new non Microsoft account and deleted the MS account. Now was my laptop accessible from the network.
> But this was a long time ago. Now I want to access my wife's laptop from the laptop, and while she still haves her MS account, I can't access her.
> As it is quite a job to create a new non MS account, and set all things and software from her current MS account over to her new account, is it perhaps possible to change her MS account to a non MS account?
> I'm curious to your answers.
> Many thanks in advance.
> 
> With kind regards,
> Fokke Nauta

You don't have to do any of this. Stop right there.

                 +-------------------------------+
                 |                               |
                 |                               |
          folke@gmail.com  <=== login          wifey@gmail.com  <=== login
             bullwinkle                       bullwinkle        <=== a local account, purely for fileshare usage!

In this example, bullwinkle is just a local account. It is used to
establish a credential for file sharing, and that is its only purpose.

When you connect to the other machine for file sharing, you would
enter the made-up account "bullwinkle" and enter the password.
It's easiest to maintain file sharing, if all machines have the same
password for "bullwinkle" account.

When I connect to the other machine across the room from me, I am
logging in with "pauls@gmail.com" to my own machine. The other machine
does not have a gmail account, it does not have an MSA. The other
machine is using local login, and the file sharing still works, because
the other machine has the credential information for a match.

                 +-------------------------------+
                 |                               |
                 |                               |
          pauls@gmail.com  <=== login          bullwinkle  <=== login and fileshare purposes
             bullwinkle    <=== fileshare

What you log into the machine with, is a separate issue from
planning for fileshare.

*******

Let us say I am security-minded. I insist on each bullwinkle account having
a unique password.

                 +-------------------------------+
                 |                               |
                 |                               |
          folke@gmail.com  <=== login          wifey@gmail.com  <=== login
             bullwinkle                       bullwinkle        <=== a local account, purely for fileshare usage!
             PW=12345678                      PW=87654321

If I am sitting at the console of the left-hand machine,
and I see the "wifey" machine and I connect, I will be typing in

             username   bullwinkle
             oassword   87654321

I enter the password that is used on the foreign machine, as
the credential we are matching, is the credential the machine
on the right knows about. It only knows about the "87654321"
password, and that's what we will type in.

You will not be clicking the "bullwinkle" entry on the lockscreen.
You will not be logging into the computer as bullwinkle,
or running computer programs as bullwinkle. The bullwinkle
account exists only for filesharing purposes. If you want
to make all the bullwinkle accounts use "12345678", you can do that.

An example of a "rich" password is "Passw0rd!", as it contains
upper case, lower case, a number, and some punctuation. It is
an example of a "formulation method" that takes slightly longer
to crack :-) Don't use that particular example, just use it
as a template, as a way to make a better password than "12345678".

As far as I know, the Bullwinkle account does not need to belong
to the Administrator group. That's an unnecessary risk. But if you have
a bad habit of deleting the last administrator account on the PC, then
making the account belong to the administrator group, gives you one
more account that can be used for maintenance purposes (when you lose
the normal administrator account you would use).

   Paul

[toc] | [prev] | [next] | [standalone]

#16783

Paul wrote on 2/3/25 6:26 PM:

> When I connect to the other machine across the room from me, I am
> logging in with "pauls@gmail.com" to my own machine. The other machine
> does not have a gmail account, it does not have an MSA. The other
> machine is using local login, and the file sharing still works, because
> the other machine has the credential information for a match.
> 
>                   +-------------------------------+
>                   |                               |
>                   |                               |
>            pauls@gmail.com  <=== login          bullwinkle  <=== login and fileshare purposes
>               bullwinkle    <=== fileshare
> 
> What you log into the machine with, is a separate issue from
> planning for fileshare.
> 
> *******
> 

You're Windows logon is an email address?
  A Windows email address logon(Gmail) is linked and is a MSFT account.
  That MSA remains even if the logon is optionally switched to a Local 
Account.

  Another route to use a Gmail email as a Windows sign-in is available in 
the Microsoft Account's online features.
  - i.e. an alternate email address can be added to sign-in/logon to Windows.


-- 
...w¡ñ§±¤ñ

[toc] | [prev] | [next] | [standalone]

#16788

On Mon, 2/3/2025 9:54 PM, ...w¡ñ§±¤ñ  wrote:
> Paul wrote on 2/3/25 6:26 PM:
> 
>> When I connect to the other machine across the room from me, I am
>> logging in with "pauls@gmail.com" to my own machine. The other machine
>> does not have a gmail account, it does not have an MSA. The other
>> machine is using local login, and the file sharing still works, because
>> the other machine has the credential information for a match.
>>
>>                   +-------------------------------+
>>                   |                               |
>>                   |                               |
>>            pauls@gmail.com  <=== login          bullwinkle  <=== login and fileshare purposes
>>               bullwinkle    <=== fileshare
>>
>> What you log into the machine with, is a separate issue from
>> planning for fileshare.
>>
>> *******
>>
> 
> You're Windows logon is an email address?
>  A Windows email address logon(Gmail) is linked and is a MSFT account.
>  That MSA remains even if the logon is optionally switched to a Local Account.
> 
>  Another route to use a Gmail email as a Windows sign-in is available in the Microsoft Account's online features.
>  - i.e. an alternate email address can be added to sign-in/logon to Windows.

That's to symbolically indicate an MSA is involved.

Writing "MSA" everywhere isn't going to work, because I
have two identifiers to insert, Folke and Wife.

*******

Is there a way to remove an account from the login side bar in the lock screen ?
Such that no attempt is ever made to login on the lock screen to Bullwinkle ?
That might reduce the side effects of having a common account sitting
around for this usage.

Nevertheless, this is the kind of trick I use in the room here,
for file sharing. It does not cut any mustard on Linux, as Linux
has smbpasswd and keeps a separate set of credentials for SAMBA
connections. Just having a bullwinkle account in the main of Linux
did not help me, as I have to set a separate password using smbpasswd.
(That's if you want to log into a Linux share.)

But otherwise, I can reach everything with symbolic names, like
\\wallace\shared on Windows and //wallace/shared on Linux.
The common account in Windows, using the normal password mechanism
and the common account in Linux being held as smbpasswd.

But generally speaking, after a number of trials, the security behavior
seems to be all over the place. It does not inspire a lot of confidence.
Like, if I was trying to implement a "secure LAN", I would have to drop
file sharing entirely.

    Paul

[toc] | [prev] | [next] | [standalone]

#16792

On 2025-02-04 08:20, Paul wrote:
> On Mon, 2/3/2025 9:54 PM, ...w¡ñ§±¤ñ  wrote:
>> Paul wrote on 2/3/25 6:26 PM:
>>
>>> When I connect to the other machine across the room from me, I am
>>> logging in with "pauls@gmail.com" to my own machine. The other machine
>>> does not have a gmail account, it does not have an MSA. The other
>>> machine is using local login, and the file sharing still works, because
>>> the other machine has the credential information for a match.
>>>
>>>                    +-------------------------------+
>>>                    |                               |
>>>                    |                               |
>>>             pauls@gmail.com  <=== login          bullwinkle  <=== login and fileshare purposes
>>>                bullwinkle    <=== fileshare
>>>
>>> What you log into the machine with, is a separate issue from
>>> planning for fileshare.
>>>
>>> *******
>>>
>>
>> You're Windows logon is an email address?
>>   A Windows email address logon(Gmail) is linked and is a MSFT account.
>>   That MSA remains even if the logon is optionally switched to a Local Account.
>>
>>   Another route to use a Gmail email as a Windows sign-in is available in the Microsoft Account's online features.
>>   - i.e. an alternate email address can be added to sign-in/logon to Windows.
> 
> That's to symbolically indicate an MSA is involved.
> 
> Writing "MSA" everywhere isn't going to work, because I
> have two identifiers to insert, Folke and Wife.
> 
> *******
> 
> Is there a way to remove an account from the login side bar in the lock screen ?
> Such that no attempt is ever made to login on the lock screen to Bullwinkle ?
> That might reduce the side effects of having a common account sitting
> around for this usage.

See below ...

> Nevertheless, this is the kind of trick I use in the room here,
> for file sharing. It does not cut any mustard on Linux, as Linux
> has smbpasswd and keeps a separate set of credentials for SAMBA
> connections. Just having a bullwinkle account in the main of Linux
> did not help me, as I have to set a separate password using smbpasswd.
> (That's if you want to log into a Linux share.)
> 
> But otherwise, I can reach everything with symbolic names, like
> \\wallace\shared on Windows and //wallace/shared on Linux.
> The common account in Windows, using the normal password mechanism
> and the common account in Linux being held as smbpasswd.
> 
> But generally speaking, after a number of trials, the security behavior
> seems to be all over the place. It does not inspire a lot of confidence.
> Like, if I was trying to implement a "secure LAN", I would have to drop
> file sharing entirely.

Your method seems unnecessarily complicated to me.  Graham J has already 
kindly reproduced my own instructions in his first post to this thread, 
so I won't repeat them here, and perhaps mine seem equally complicated 
to others to set up, but you have to look on it as an investment in 
time, which pays back later by saving time thereafter.  They've worked 
for me, making suitable corrections to suit the particular control 
levers in particular versions of Windows, ever since Windows 2000.

I don't currently have an 11 build up and running  -  I'm working on 
that  -  but I have machines here running XP Pro, 7 mainly Pro but one 
Home Premium, and 10 Pro, and because the same user accounts with the 
same passwords exist on all PCs, I just click on where I want to go in 
Explorer's Network (formerly Network Neighbourhood) branch and I'm 
there; at worst, sometimes I may have to type ...
   '\\<ComputerName>\<ShareName>'
... into Explorer's address bar if the PC is newly powered up and hasn't 
yet picked up the local browsing data via the Computer Browser service, 
which some versions of Windows seem particularly sluggish about, 7 can 
be bad in this respect.

To prevent a particular account from logging on to a particular PC  - 
if, say, you want a child to be able to log on to a share on your PC so 
the child must have his user account credentials existing on the PC, but 
you don't want the child actually logging on to the PC itself  -  then 
you must be running a version of Windows that allows access to the 
Security Policy management console (from memory, Home versions do not, 
and note that I haven't needed to do this in quite a while, so I can't 
guarantee these instructions, but IMS they're correct):
   1  Get a Run dialog, say by <Win R>
   2  secpol.msc <Enter>
   3  Security Settings, Local Policies, User Rights Assignment
   4  Add particular username to 'Deny logon locally' list, Ok
        (by default this has only 'Guest')

To prevent logging on using an M$ account  -  this from searching for 
the above, haven't actually tried this for myself  -  again you need to 
get into the Security Policy management console:
   1  Get a Run dialog, say by <Win R>
   2  secpol.msc <Enter>
   3  Security Settings, Local Policies, Security Options
   4  Click 'Accounts: Block Microsoft accounts'
   5  Select from the drop-down list ...
        'Users can’t add or log on with Microsoft accounts'
      ... Ok

To allow XP and earlier to connect to more recent versions of Windows 
such as 10, or those between which are running Microsoft Security 
Essentials, you have to enable SMBv1.  To do this ...

Windows 10+: Run Powershell as Admin and enter the following:
   Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Windows 7-:  SMBv1 is enabled by default, so normally no change is 
needed, however, ISTR that installing Microsoft Security Essentials 
disables it, in which case you have to set or make a registry change to 
enable it, as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Registry entry: SMB1
REG_DWORD: 0 = Disabled
REG_DWORD: 1 = Enabled
Default: 1 = Enabled (No registry key is created)

Windows 8 versions:  I'm not sure about and cannot test here, but one or 
the other of the above should work.

In all versions of Windows, allegedly you have to reboot after making 
the changes, but perhaps restarting the service may suffice; again, as 
it's a while since I had to do this, I can't definitely say that this 
would work:
   net stop Server
   net start Server

HTHs

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]

#17041

On 03/02/2025 19:22, Fokke Nauta wrote:
> Hi all,
> 
> My wife and me bought both a time ago a laptop with a W11 account. I 
> configured my account and I found out that my laptop was not accessible 
> from our local network. It was a Microsoft account. I created a new non 
> Microsoft account and deleted the MS account. Now was my laptop 
> accessible from the network.
> But this was a long time ago. Now I want to access my wife's laptop from 
> the laptop, and while she still haves her MS account, I can't access her.
> As it is quite a job to create a new non MS account, and set all things 
> and software from her current MS account over to her new account, is it 
> perhaps possible to change her MS account to a non MS account?
> I'm curious to your answers.
> Many thanks in advance.
> 
> With kind regards,
> Fokke Nauta

It won't work. She doesn't want to loose her current account.
But thanks you all for your help.

With kind regards,
Fokke Nauta

[toc] | [prev] | [standalone]

Back to top | Article view | alt.comp.os.windows-11

csiph-web