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

Groups > alt.comp.os.windows-11 > #16792

Re: Problems with Microsoft account

Show all headers | View raw

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

Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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

csiph-web