• Patch Lady – can you set up a local – no Microsoft account on 2004?

    Home » Forums » Newsletter and Homepage topics » Patch Lady – can you set up a local – no Microsoft account on 2004?

    Author
    Topic
    Viewing 12 reply threads
    Author
    Replies
    • #2260031

      These user hostile interface designs by Microsoft are not scoring any points with me, especially as a blind user. Today I helped mom set up Zoom on her Chromebook, and we used it between the Chromebook and my Linux laptop, and it worked great.

      It is so satisfying to see Zoom eating Google and Microsoft’s lunch; you don’t even need to sign up for a Zoom account to join in a meeting, only to host one. Google and Microsoft have offered video conferencing for years, but the key to success, is to make it as painless as possible for the end user to just get going right now. No need to navigate dialog boxes, no carefully monitoring installers. And Zoom really treats every platform equally, since they don’t make an operating system or have a huge ecosystem to lock consumers into.

    • #2260040

      Simple way – during install don’t attach LAN cable.

      Sometimes with attached LAN cable there is no option for local account, even in corners, checked for several installations. Then create online account, after installation ends create new local account and delete this account.

      1 user thanked author for this post.
    • #2260062

      I guess it is only me but I despise those cartoon graphics MS uses. Hate the ones Google uses too. Can we have a clean simple interface with the essentials and nothing cluttering up the screen. Probably not. Goes with having a clean and simple experience setting up your own account on a computer and not one of theirs too.

    • #2260076

      I assume this only applies to Home?

      On Pro you can always create a local account during setup (even with the Ethernet cable connected) by choosing Set up for an organisation and then “Domain join instead”. You don’t have to join it to a domain, it just skips the Microsoft account setup.

    • #2260087

      Have never had anything but an OEM Win License via new computer purchase at (ie) Best Buy, AND know that my W10 HOME License is Digitally Registered to my MS Account – BUT – since the 2/19 setup it’s been a LOCAL ACCT with All Ver upgrades accommodating that fact – no change or popups.

      Any idea If Home users will see these Same Screens, or this is a Pro-Only post as is often the case?

      W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / HP Envy Desk-Ethernet - SSD-HDD/ i5(8th Gen) 12GB / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU=0

      • #2260092

        The screens are first-time OEM setup or clean install setup for Win10 Home. You DO NOT have to create an MS account and register the computer with them. You can create a Local account ONLY.

        But they make it difficult and obscure.

        • #2260292

          I know that I did a test install of 1903 Pro on a VM about a year ago, and had no problems with getting a local account on a LAN-connected system.  My impression is that this issue seems to be predominantly an issue with Home installations.

          To me, that makes sense.  Although Microsoft *really* wants everybody doing cloud IDs, there’s a lot more compelling for a user with Pro to have a local ID than a Home user.

          Yet another reason to prefer Pro over Home.

        • #2260727

          Thank you PKCano for describing the underlying process that Susan was doing & the O/S version. She didn’t mention them & they weren’t obvious to someone who hasn’t installed Windows 10.

    • #2260088

      I figure Microsoft will eventually lock out users that use Home or Pro versions to the local account option. Were already at a point that we need to circumvent the setup to access the local option. Here I thought when Ballmer left we would see a kinder gentler Microsoft and instead I see more and more this is not the case at all.

      • #2260097

        My guess is that Windows will eventually become Microsoft365 (requiring an MS account/login) with the OS resident on the MS servers and a Click-to-run setup on the PC.
        The rental price will be based on how many added “Features,” for which you will pay extra.

         

    • #2260096

      I received this reply to one of my questions:

      We usually recommend passing up the C/D week patches and sticking with just the Security CUs issued on Patch Tuesday.

      Because I am deficient in this sort of stuff I am asking what are the C/D week patches and Security CUs?

      Not understanding those terms is a major reason why I dont upgrade to the advanced newsletter.  If I am lost on the basic newsletter I doubt I would understand the upgraded newsletter.

      • #2260100

        Security updates are released by Microsoft on Patch Tuesday (the second Tues. of the month, or “B” week).
        The updates released later in the month (third/fourth weeks = “C”/”D” weeks) are Install-optional non-security patches meant for testing coming changes. We do not recommend installing them outside a testing environment.

        1 user thanked author for this post.
    • #2260104

      If this is for Home, then they seem to have made the process easier this time around. In previous versions of Windows 10 Home, you had to actually disconnect the computer from the Internet (and keep it disconnected) in order to force Windows to let you create a local account. If your computer was connected to the Internet via cable, that meant physically yanking the cable out.

      I run Windows 10 in virtual machines and I always create local accounts for them. At least with a virtual machine it’s very easy to disconnect a machine from the Internet. It’s always a good idea to keep the machine disconnected from the Internet during the installation process; that way, once Windows 10 finishes installing, it won’t immediately try and download a whole bunch of UWP apps; the bloatware apps will appear as download icons in the start menu and can be eliminated. Only reconnect the computer to the Internet when you’ve gotten rid of those bloatware apps (unless you actually want them).

    • #2260106

      Like real issues, I am sure Microsoft will eventually get around to “fixing” this “issue”.

      Byte me!

    • #2260120

      I only do a clean install on purpose-built bare metal; everything else is a Windows version update.  I also stopped using VM’s a few years ago, as the performance of a VM cannot match the performance of the same OS on bare metal; too much of an apples-to-oranges sort of thing.

      I also dual boot, so I can get a direct comparison between two setups on exactly the same hardware.  That’s the main reason I haven’t found a Linux distro I could tolerate for very long.

      Nor do I see a subscription model of Windows 10 any time soon.  Some larger businesses are still using a Windows 7 Enterprise backbone that they have thoroughly locked down.  I don’t much foresee such businesses opening a back door for Microsoft into their business domains.  As I see it, such a fork would be required in the OS in order to appease businesses  that it wouldn’t be worth the effort.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

      • #2260124

        This is already happening.
        Businesses are running the Windows OS in Azure VMs, Citrix, etc.
        And MS is financially punishing businesses for running Windows and MS Apps in VMs on other than MS Web Servers.

        • #2260205

          Businesses are running the Windows OS in Azure VMs, Citrix, etc. And MS is financially punishing businesses for running Windows and MS Apps in VMs on other than MS Web Servers.

          Small businesses, maybe.  Before I retired at the end of May, 2019, I was a contract Geologist for a multi-national mining company that traces its roots back to 1904.  They were using their own cloud before “the cloud” was a thing.  Their databases are in multi-petabytes.  They have multiple redundant server farms in a number of locations.

          They have local server farms at each mining location to run control systems.  There would be way too much lag to run these control systems from the cloud.  They have literally thousands of workstations/desktops/laptops.  They transitioned from IBM mainframes/dumb terminals to Windows NT4 to Windows 7, building out their server farms along the way, skipping every other Windows version in between.

          They are still on Windows 7, and just now beginning the rollout to Windows 10, which will take about 3 months.  They won’t be using Azure, or any other commercial cloud, and they won’t be running any VM’s.  Their connections between locations are fibre-optic, much of which was installed by contractors, not the phone company.  Only their international connections run through commercial trunk lines.

          I was recently talking to a friend who works in Mine Planning, and he told me he was assigned the task of coordinating the Windows 10 transition with the IT department.  IT’s policy is to swap out computers.  Mine Planning’s policy is to make sure the new computer does every little thing that needs to be done on par with the Windows 7 machines first, so they won’t give up the Windows 7 machines until the Windows 10 machines have proven themselves to be rock-solid.

          That little disagreement got pushed up the chain of command a couple of levels.  Mine Planning won the battle, because they provide the data upon which nearly every other department in the entire organization relies.

          The company employs ~12,000 people, and probably half (or very nearly) of those employees use a desktop/workstation/laptop for their job.  They’re all getting new machines (by the truckload) in the transition to Windows 10.

          I somehow doubt that Microsoft will have any footing from which to punish them for doing things their own way, running Windows in hardware, not VM’s, using their own cloud, and not a commercial service.

          Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
          We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

          1 user thanked author for this post.
      • #2260174

        regarding a possible “subscription model” for Win10, read this article by Ed Bott:
        https://www.zdnet.com/article/windows-10-five-years-later-almost-nothing-turned-out-as-planned-and-thats-ok/

        The free upgrade offer was a trap, they insisted. After Microsoft had lured in a few hundred million suckers with that offer, they were going to start charging for subscriptions. Five years later, that still hasn’t happened.

    • #2260178

      Even adding a local User under Accounts in the Win 10 Settings screen is annoying. It demands multiple answers to security questions as well as the classic “hint”. Given the activation info is stored online it is not a stretch that they are creating most of a Microsoft Account with this personal info and using it for tracking and telemetry.

      At least the classic CMD method still works with none of the above required.

      Open CMD as Admin:

      net user “username” “password” /add

      if want it as Admin level:

      net localgroup administrators “username” /add

      Yes the ”  ” are required.

       

      1 user thanked author for this post.
    • #2260237

      I’m going to go against the grain here and say this:  go ahead and create a MS account and install windows using it.  Use a throwaway email if you like.  Once you’re logged in, it’s just a couple seconds to convert that to a local account in the User control panel.  Alternately, you can create a second offline admin account, log in on that, then remove the online account.

      The reason for this is for ease of licensing.  Your system hash along with your Win10 license sits on MS servers.  Once you install once and tie that to your MS account, licensing on OS reinstalls is automatic and painless.

      This gives you the best of both worlds – a more convenient way to activate windows, and a continued ability to rely on local only accounts, starving them of the economic metric tracking they obviously want so badly.

      • #2260284

        The reason for this is for ease of licensing. Your system hash along with your Win10 license sits on MS servers. Once you install once and tie that to your MS account, licensing on OS reinstalls is automatic and painless.

        The Windows 10 license is tied to the PC, not to the MS account.  I have 5 installations, all local updates (one was a clean install on my NAS), not one has ever had a Microsoft account user at any time.

        I have a Microsoft account for OneDrive, but that’s all it’s affiliated with.  I have a phone and two PC’s that sync that same OneDrive account, but none of them have a Microsoft user account.

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

    • #2260379

      Does 2004 still let you avoid the security questions if you create a offline account without a password? I have been skipping the security question for my VM test machines that way. After I get to the desktop I then change the password from no password to my test password.

    Viewing 12 reply threads
    Reply To: Patch Lady – can you set up a local – no Microsoft account on 2004?

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: