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

AutoLogon fails after OOBE

Scheduled Pinned Locked Moved
Windows Problems
2
5
2.5k
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.
  • P
    Psycholiquid Testers
    last edited by Psycholiquid Nov 2, 2015, 2:12 PM Nov 2, 2015, 8:12 PM

    I had my image made and have done this for years. Somehow my dummy self messed up and rebooted the image with the unattend.xml in the sysprep folder.

    Now the Administrator password is not blank and when I run OOBE it says “user name and password incorrect”

    Does anyone have any idea on how to get this back to blank.

    I have done the following:

    Reset and pressed OK with nothing there.
    Hit enter to just allow for a blank password
    Ran the NT Password Recovery disk and chose to blank the password form it.

    No dice on any of that. I have to be missing something, like a reg key or something. I have scoured the internet for days. I might need fresh eyes if anyone has any ideas.

    1 Reply Last reply Reply Quote 0
    • P
      Psycholiquid Testers
      last edited by Nov 2, 2015, 8:19 PM

      Forgot to add this is for Windows 7

      1 Reply Last reply Reply Quote 0
      • L
        Lee Rowlett Developer
        last edited by Nov 2, 2015, 11:47 PM

        add this code into /images/postscripts/fog.postdownload

        clearScreen;
        mkdir /ntfs &>/dev/null
        ntfs-3g -o force,rw $part /ntfs
        dots "Mounting Device";
        if [ "$?" = "0" ]; then
        	echo "Done";
        	. ${postdownpath}fog.ad
        	umount /ntfs;
        else
        	echo "Failed To Mount Device";
        	sleep 30;
        fi
        
        1 Reply Last reply Reply Quote 2
        • L
          Lee Rowlett Developer
          last edited by Nov 2, 2015, 11:52 PM

          then create a new file in the same location as fog.postdownload called fog.ad and you can edit the sysprep file however you would like - this changes the unattend.xml AFTER the machine is imaged and pulls the info for that host from fog, making the unattend.xml unique and set with the info for that host.

          using the below you could use sed command to edit the local admin password set in your unattend.xml to match what you want it to be, just follow how below works.

          #!/bin/sh
          
          hostadpwd="password-to-join-domain";
          panther="/ntfs/Windows/Panther/unattend.xml";
          if [ -f "$panther" ]; then
          	unattend="/ntfs/Windows/Panther/unattend.xml";
          else
          	if [ $osid == "9" ]; then
          		unattend="/ntfs/Windows/System32/Sysprep/unattend.xml";
          	else
          		unattend="/ntfs/Windows/System32/sysprep/unattend.xml";
          	fi
          fi
          
          if [ -f "$unattend" ]; then
          	dots "Writing Computer Name";
          	sed -i "/ComputerName/s/*/$hostname/g" $unattend
          	echo "Done";
          	dots "ComputerName Set To";
          	echo $hostname
          	dots "Set PC To Join The Domain";
          	if [ "$addomain" != "" ]; then
          		sed -i "/<JoinWorkgroup>/d" $unattend
          		sed -i -e "s|<Password></Password>|<Password>${hostadpwd}</Password>|g" \
          			-e "s|<Username></Username>|<Username>${addomain}\\\\${aduser}</Username>|g" \
          			-e "s|<MachineObjectOU></MachineObjectOU>|<MachineObjectOU>${adou}</MachineObjectOU>|g" \
          			-e "s|<JoinDomain></JoinDomain>|<JoinDomain>${addomain}</JoinDomain>|g" $unattend
          		echo "Done";
          	else
          		echo "Skipped";
          	fi
          

          fi

          1 Reply Last reply Reply Quote 2
          • P
            Psycholiquid Testers
            last edited by Nov 3, 2015, 11:59 AM

            I will take a look at this once I get it settled in the environment. The way I got around it for now was to create the SetupComplete.CMD file and put what I needed in there so it would start the FOG service once imaging was complete and it is working good now.

            I’m not a coder so it all looks like Greek to me but I know I can figure out what I am looking at. And thank you for the suggestion.

            1 Reply Last reply Reply Quote 1
            • 1 / 1
            1 / 1
            • First post
              4/5
              Last post

            196

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project