How does Windows 7 setup know there is a unattend.xml file available?

After creating our answer files, the question came about as to how Windows knows to use this answer file. Our deployments took off after a reboot without us designating an answer file. Windows setup will use an answer file either explicitly, or implicitly.
The explicit method of user an answer file is by running the following command from the installation media: Setup.exe /unattend:filename. This will launch windows setup and will take answers from your unattend.xml file that you created with Windows System Image Manager (Windows SIM).

Windows setup also has some implicit ways of recognizing that you have an answer file. Windows setup will automatically look for an answer file in the following locations:
1. HKLM\System\Setup!UnattendFile
2. %WINDIR%\Panther\Unattend
3. %WINDIR%\Panther
4. Removable read/write media in order of drive letter, at the root of the drive.
5. Removable read-only media in order of drive letter, at the root of the drive.
6. windowsPE and offline Servicing passes:
• \Sources directory in a Windows distribution
All other passes:
• %WINDIR%\System32\Sysprep
7. %SYSTEMDRIVE%

Reference: http://technet.microsoft.com/en-us/library/cc749415(WS.10).aspx

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog