Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mandrake

Profile Information

  • OS
    none specified
  1. Even though this post is almost 6 years old I still found it and had the same problem (but with Win7). My RunOnceEx process contains a bunch of reboot command, and the only reliable way of doing it for me was to: Add Flags = 0x3 (run synchronous and delete entry after run) And then run shutdown command that also kills the RunOnceEx process The shutdown command is crucial since if shutdown process exits the next item on the RunOnceEx list will be processed and interruped in the middle of an item, since a shutdown is in progress. The solution I found was to execute a kill command of the RunOnceEx process and then shutting down Windows. That's the only reliable way of doing it. One would think that just executing shudown and then pausing: shutdown /r /t 0 /f & pause would also do the trick. But noo. If Windows terminates the shell that executes that command before the RunOnceEx process, then it will stop waiting for the process to finish (since it was killed) and continue to the next. Bottom line, kill it first and then shut down: taskkill /im rundll32.exe /f & shutdown /r /t 0 /f Since it needs to be run in a shell the RunOnceEx entry will look something like this: REG ADD %KEY%\001 /V 1 /D "cmd /k taskkill.exe /im rundll32.exe /f & shutdown /r /f /t 0" /f In XP the taskkill might not be available, try tskill instead.
  2. CMD Update install problem

    Might just be that "/quite /norestart" should be "/quiet /norestart" :~
  3. When I add local users in oobeSystem (for Win7 PRO) the password field seems to be ignored. When logging in one can just log on without ever being prompted for a password. Have anyone ever experienced that problem? This is the relevant section of the answer file (created in WSIM): <settings pass="oobeSystem"> ... <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>UABjJAJkfl8AAkfka==</Value> <PlainText>false</PlainText> <Password> <Description>Local User</Description> <Group>Users</Group> <Name>Localuser</Name> <DisplayName>Local user</DisplayName> </LocalAccount> </LocalAccounts> </UserAccounts> ... </settings> What I don't show here is that I also have autologin for administrator with count=1 to make the FirstLogonCommands run unattended. But that shouldn't affect localuser.
  4. Awsome, it works perfectly! We are creating this account via sysprep and assigning a default password to that user.. We need the system to flag the account to reset the password on first logon. EDIT: it looks like we just got it to work... At first I was calling "net user <username> /logonpasswordchg:yes" and this was not working.. After further research it appears since the flag was set that the password will never expire this was doing nothing.. So in my setup complete now I have an extra entry "WMIC.EXE Path Win32_UserAccount Where Name="<username>" Set PasswordExpires="TRUE"" Which clears the "password never expires checkbox" then I run the "net user <username> /logonpasswordchg:yes" and everything works as expected.. thanks for the feed back..
  5. As soon as I left out the audit passes, everything started to make sense. And settings in the answer file was actually executed and applied! Yay! Thanks! Too bad Synchronous commands in specialize pass didn't work as expected. The installation kind of looses the professional feeling when you have to make installation in FirstLogonCommands. I wouldn't say so, you are just not approaching it right. My example of using multiple XML won't work for you, as it does for me. Install your programs (like Acrobat) using FirstLogonCommands. I would just ignore Audit Mode/Pass all together since you probably don't need to use it and you seem to be mixed up about how to use it. You should not run an OS in Audit Mode for more than 30 days.
  6. Do you run the Audit passes as well? If that's the case, how does that work with only one unattend file? My understanding this far is that if you're going into audit pass via oobeSystem|Reseal[mode=audit] then the rest of oobeSystem pass is ignored and marked as "hasProcessed" in the cached answer file in Panther dir. When revisited next time it's ignored since it's marked as been processed? I've tried doing everything in one file but all my goodies in oobeSystem was ignored after auditUser. If, however the audit passes are skipped, then it works with one file since no pass is revisited twice. How does your answer file look like?
  7. I'd love to just have everything installed during specialize and skip the audit pass. But some software can't be installed during specialize pass for some reason (like adobe reader, that just disappears after reboot to welcome). Therefore I had to switch to audit mode and install. Also adding group policies during specialize fails. But what happens if I never reseal to oobe? Doesn't the installation stay in audit mode in perpetuity? At one point I left out the reseal /oobe in auditUser, but then the sysprep GUI poped up after being logged in, asking me if the system should be generalized and/or audited or oobe. Also, could you elaborate what you mean with several unattend files? I'm not sure how to do that with scripts. If I add like a runSynchrous command that executes sysprep with /unattend option, that will fail since the sysprep gui is already running (started by the installer). The only option I found was to add an answer file named oobe.xml in /System32/oobe/info/ or something like that. If that one exist it seems to be executed after a reseal to oobe. I just can't wrap my head around how this is supposed to work in my scenario. It's just so unintuitive. Like going into audit mode by adding reseal audit in oobeSystem... :/
  8. Windows setup searches for the autounattend.xml on your DVD as well. So go ahead and create an ISO and burn a new Windows installation media with the answer file on the root. Using WAIK you can create the iso with oscdimg -n -m -b"iso\boot\etfsboot.com" iso\ myinstallation.iso where .\iso\ contains all the files from the windows installation cd + answer file.
  9. I assume you wish to do that as an admin? If that's the case it's my understanding that you must get the automatic logon as an admin user to work during oobeSystem pass a.k.a "Welcome". If you can get that to work then it should be a matter of adding Microsoft-Shell-Setup|FirstLogonCommand|SynchronousCommand|Path=regedit /s <path to your reg-file> ... in oobeSystem pass. But that only works if the oobeSystem pass runs at all. In my case it doesn't for some reason I don't know. Good luck.
  10. Hi! First off: awsome forum! It has been the best source of information for me the last week. I've spent all my time trying to create an unattended windows 7 installation that does the following: Everything on 1 DVD Completly unattended (no EULA, no product-key forms to fill et.c.) Installs 3rd party software Installs GPOPacks (created with Microsoft SCM). Make the OOBE (Welcome) unattended. I'm not sure I'm doing this the right way. But to enter audit, the only way I've gotten it to work is by having Reseal|Mode=Audit in oobeSystem. But when I finish the audit and do a Reseal|Mode=oobe it seems like the other setttings in the oobeSystem pass in my autounattend.xml is ignored. How can I run both audit and oobe system unattended? Must I create a new unattend file and run sysprep /oobe /unattend:<file> or what? Have any of you done that? Help is much appreciated!