From: nospam@needed.invalid   
      
   On Mon, 12/15/2025 8:44 PM, Char Jackson wrote:   
   > On Mon, 15 Dec 2025 21:36:14 +0000, Graham J    
   > wrote:   
   >   
   >> Fokke Nauta wrote:   
   >>   
   >> [snip]   
   >>   
   >>>> Same Windows Logon username/pw on each device?   
   >>>   
   >>> No.   
   >>   
   >>   
   >> Then nothing will work.  You must have the same Windows Logon username   
   >> and password on each device   
   >   
   > I don't want to derail any progress being made, but I've never found a   
   > requirement to create matching user/pass on the destination PC. When   
   > prompted, I simply use credentials that already exist there.   
   >   
      
   This is a practicality situation.   
      
      laptop#1    timmy:12345678   
      laptop#2    ronald:87654   
      laptop#3    sally:forth   
      
   If instead, you do this   
      
      laptop#1    bullwinkle:12321   
      laptop#2    bullwinkle:12321   
      laptop#3    bullwinkle:12321   
      
   then, all you have to remember, is that one auxiliary account   
   you set up on each machine.   
      
   I expect there are other ways to do this, with Credential Manager,   
   or with setting up the accounts so they do not support a normal login,   
   but those are things you can look up if you want.   
      
   For example, TrustedInstaller, you can't log into that, it   
   doesn't have a Home Directory, it only exists as a "token" when   
   you elevate and impersonate it. That's one of the most baggage-free kinds of   
   account settings.   
      
   I *have* made the mistake of doing this.   
      
      laptop#1    timmy:12345678   
      laptop#2    ronald:87654   
      
   and I'm sitting at the Daily Driver, pounding in the timmy USER:PASS   
   and whining that it is rejecting my requests. Then after about   
   ten minutes of this, it occurred to me that "dammit, this old   
   machine was set up with ronald". And that's a little lesson   
   to myself, to clean up my act. That's where these rules of thumb   
   come from, embarrassing moments where you've forgotten a tiny detail.   
      
   People who run Password-less, yes, maybe at some level, the   
   software seems to support that. But just as easily, when the   
   26H1 Upgrade comes in, my Password-less setup could fail   
   to work. As a practical matter, you configure your systems   
   so you are not constantly treading on some knife-edge and   
   cutting yourself.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)