uid0

You could try formatting it NTFS then using a junction, but you'd probably find thumb drives aren't an option because they're not fast enough to keep up, and would wear out quickly if they were. Couldn't you just copy files to it after recording? Alternatively, you might find mediaportal is more flexible.

I've not used this, but maybe <InstallToAvailablePartition>true expects a partition rather than a blank disk?

Rsync fits that budget, I doubt much else will...

Wouldn't dban or SecureErase or diskpart clean be enough?

I guess it's because 0 has a special meaning, like 1 and 2 are stdout and stderr. Jaclaz, any idea what 0 means?

It's messy, but you can poke entries into HKLM runonce from HKCU runonce, which get processed on the next reboot: SET KEY=HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce REG ADD %KEY% /V w /d "reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /V speak /d \"wscript %systemroot%\speak.vbs \\\"installation complete\\\"\" /f" /f REG ADD %KEY% /V z /D "shutdown.exe -r -f -t 60 -c \"1\"" /f

If you're trying to block outgoing ssh, you'd be better blocking the program - but win7 doesn't come with one... Likewise ftp will connect from a high random port number to the server port 21, so blocking outgoing port 21 isn't going to work either. If you say what you're trying to achieve, people can probably suggest better approaches.

Could try calling wmic from <FirstLogonCommands> ? wmic path Win32_UserAccount where Name="tripredacus" set PasswordExpires=false

I expect it's because security essentials is for businesses with up to 10 PCs, and MS don't expect these to use imaging, and want to sell them forefront instead. Happy to be wrong, though...

Don't let an unpatched server go near the internet, or any machines you don't trust.

Still absolutely no idea what reg tweak you're on about.

A bare .exe? What does it do, what's the licence, can we see the source?

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda Source: Neowin

procmon? http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

I had it called from runonceex, but I'm afraid I haven't used nlite or virtualbox for years. I'd test whether the /S switch still works first.

Oh, didn't notice we were in the nlite forum...

This was something I bodged a while ago, might still work, might not... Option Explicit Dim ws, strCmd, strComputer, objWMIService, colBIOS, colPC, objPC Set ws = WScript.CreateObject("WScript.Shell") strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colPC = objWMIService.ExecQuery("Select * from Win32_ComputerSystem") For Each objPC In colPC If Not IsNull(objPC.Model) Then If Left(objPC.Model,10) = "VirtualBox" Then strCmd = "VBoxWindowsAdditions-x86.exe /S" ws.Run(strCmd),0,True strCmd = "netsh interface ip set address name=" & chr(34) & "Local Area Connection" & chr(34) & " static 192.168.1.20 255.255.255.0" ws.Run(strCmd),0,True End If End If Next

Yep, and you'd have to have it match the disk signature and partition offset too. And if you'd created a partition already, setup will probably assign it c: anyway. Hmmm. I'd insist to whoever sets the rules that you need to be able to install from custom media - if they trust you to install stuff from your usb drive, they ought to trust you to build install media. You're bound to get a machine without a floppy drive at some point, so another approach will be needed.

You can set the drive letter using migrate.inf, but I suspect it might need to be in I386, which would break one of your rules...

Get the WAIK, let it build an autounattend.xml for you. You don't have to use an altered wim, $oem$ is deprecated but still works.

Sounds like it'll run fine on 64bit windows: http://forums.adobe.com/thread/460813 You'd only need to mess about if it had a 16bit installer, which is unlikely for newish software. You'd need two licences for two machines though I expect.

Yep. Run it from cmdlines during setup and it'll apply to the default user and all subsequent ones. Just showing you where to look in the registry. I found the location using Regshot.

"Mute sound on Windows boot up" is not the same as "stop the windows login sound from playing"... Just in case getting rid of some of the other sound effects becomes "URGENT" , here's a tweak with some clues: http://www.msfn.org/board/topic/116129-custamize-winxp-default-sounds-in-unattended-winxp/page__view__findpost__p__757122

If WPIW can run cmd files, you can use gsar: attrib -r -s -h %SystemDrive%\boot.ini gsar.exe -o -i -s:032:047bootlogo:032:047noguiboot -r %SystemDrive%\boot.ini gsar.exe -o -sfastdetect -rfastdetect:032:047bootlogo:032:047noguiboot %SystemDrive%\boot.ini attrib +r +s +h %SystemDrive%\boot.ini

I make it 2^32-1, at least for the administrator account. Not quite infinite, but pretty close <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Password> <Value>blah</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>4294967295</LogonCount> <Username>Administrator</Username> </AutoLogon> <RegisteredOwner /> <RegisteredOrganization /> <ComputerName>seven</ComputerName> <ShowWindowsLive>false</ShowWindowsLive> </component>