• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Windows (Powershell) / Username=Computername

    Scheduled Pinned Locked Moved Solved
    General Problems
    6
    14
    4.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tywyn @Tom Elliott
      last edited by

      @tom-elliott said in Windows (Powershell) / Username=Computername:

      Pretty sure the computer names aren’t allowed to be the same as usernames. I don’t know why, I think it’s because of domain issues

      When I add a user via the UAC with the same username as the computername it works fine (at least under Win 7 64bit. Did not try it with win 10 though)

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Tywyn
        last edited by george1421

        @tywyn In your PS script, add a text literal to the computer name (to just change it slightly as a test) when you create the user account. See if that works. That test will give you an idea if the computer name and user name can be the same.

        Right now you need to basically take the approach of divide and concur. (find out where the problem isn’t so you can narrow down where it is).

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        T 1 Reply Last reply Reply Quote 0
        • T
          Tywyn @george1421
          last edited by

          @george1421 said in Windows (Powershell) / Username=Computername:

          @tywyn In your PS script, add a text literal to the computer name (to just change it slightly as a test) when you create the user account. See if that works. That test will give you an idea if the computer name and user name can be the same.

          My tests said, that you cannot have the same names, when you use Powershell, but you can have he same names, when you use the UAC 🙂

          1 Reply Last reply Reply Quote 0
          • AvaryanA
            Avaryan
            last edited by Avaryan

            Worked for me when I ran it locally on a Windows 10 Enterprise x64 computer. Will run as snapin soon to test.

            Here is my code:

            $Hostname = (Get-WmiObject -Class Win32_ComputerSystem).Name
            $Password = "password" | ConvertTo-SecureString -AsPlainText -Force
            New-LocalUser -Name $Hostname -Password $Password -Description "Local user." | Add-LocalGroupMember -Group "Users"
            

            edit: Did not work when ran as a FOG snapin.

            T 1 Reply Last reply Reply Quote 0
            • AvaryanA
              Avaryan
              last edited by

              Why not just create the local user doing sysprep?

              1 Reply Last reply Reply Quote 1
              • x23piracyX
                x23piracy
                last edited by x23piracy

                Batch!:

                net user /add USERNAME PASSWORD
                net localgroup GROUPNAME USERNAME /add
                

                @avaryan said in Windows (Powershell) / Username=Computername:

                $Password = “password” | ConvertTo-SecureString -AsPlainText -Force

                It does not make sense to encrypt the password within the same script. 😄
                You need to use the encrypted string and don’t encrypt it within the same script 🙂

                @Tywyn like @Avaryan said why not use unattend.xml to create local users?

                ║▌║█║▌│║▌║▌█

                AvaryanA T 2 Replies Last reply Reply Quote 1
                • AvaryanA
                  Avaryan @x23piracy
                  last edited by

                  @x23piracy said in Windows (Powershell) / Username=Computername:

                  It does not make sense to encrypt the password within the same script. 😄

                  PowerShell doesn’t allow you to do passwords in plain text. For testing purposes, it was fine. 🙂

                  1 Reply Last reply Reply Quote 0
                  • Q
                    Quazz Moderator
                    last edited by

                    When you try to create a user with the same name as the Computername in command prompt, it will say that the two cannot be the same.

                    So likely when you create it in UAC, it does some magic behind the scenes to distinguish the 2.

                    1 Reply Last reply Reply Quote 0
                    • T
                      Tywyn @Avaryan
                      last edited by

                      @avaryan said in Windows (Powershell) / Username=Computername:

                      Worked for me when I ran it locally on a Windows 10 Enterprise x64 computer. Will run as snapin soon to test.

                      Here is my code:

                      $Hostname = (Get-WmiObject -Class Win32_ComputerSystem).Name
                      $Password = "password" | ConvertTo-SecureString -AsPlainText -Force
                      New-LocalUser -Name $Hostname -Password $Password -Description "Local user." | Add-LocalGroupMember -Group "Users"
                      

                      edit: Did not work when ran as a FOG snapin.

                      This code worked for me as well now.
                      Interesstingly, when I have the Add-LocalGroupMember in a separate line, it does not work.

                      This is what I tried (did not work):

                      New-LocalUser $UserName -Password $UserPasswordEnc 
                      Add-LocalGroupMember -Group "Benutzer" -Member $UserName 
                      

                      Thank you gentlemen!

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tywyn @x23piracy
                        last edited by

                        @x23piracy said in [Windows (Powershell) / Username=Computername]

                        @Tywyn like @Avaryan said why not use unattend.xml to create local users?

                        Having a Powershell-script, that does more, for example, set ip-addresses, active office/windows, sets the correct time, etc.

                        AND: I have no idea how to use unattend.xml 🙂

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post

                        184

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.4k

                        Posts
                        Copyright © 2012-2024 FOG Project