@theopenem_admin There is exception for this script, and unfortunately I used installation file that match with exception.
Documentation:
Setupact.log from ../Panther/UnattendGC
@theopenem_admin There is exception for this script, and unfortunately I used installation file that match with exception.
Documentation:
Setupact.log from ../Panther/UnattendGC
@theopenem_admin said in creating base image:
After you deploy the image, does the file exist at C:\Windows\Setup\scripts
Well, I was not sure either, because:
File "c:\windows\setup\scripts\setupcomplete" exists on my deployed machine.
@tomas-hook Just to be clear - I run "Toec Image Prep" without server connection. Simillar to older version when this feature was not present.
@theopenem_admin it's default (Toec Image Prep without server access because time server is not setup yet, but during sysprep later):
mkdir "%ProgramFiles%\Toec"
net stop toec /y >> "%ProgramFiles%\Toec\setupcomplete.log"
powercfg.exe /h off >> "%ProgramFiles%\Toec\setupcomplete.log"
copy NUL "%ProgramFiles%\Toec\setupcompletecmd_complete" >> "%ProgramFiles%\Toec\setupcomplete.log"
del /Q /F c:\windows\system32\sysprep\unattend.xml >> "%ProgramFiles%\Toec\setupcomplete.log"
del /Q /F c:\windows\panther\unattend.xml >> "%ProgramFiles%\Toec\setupcomplete.log"
REM ####### Driver install ###########
PowerShell ^
$Drivers = Get-ChildItem "C:\drivers" -Recurse -Filter "*.inf" ;^
ForEach($Driver in $Drivers) {;^
$args = \"/add-driver $($Driver.FullName) /install \";^
$p = (Start-Process -FilePath pnputil.exe -ArgumentList $args -NoNewWindow -Passthru);^
Wait-Process -Id $p.Id -Timeout 10 >> "%ProgramFiles%\Toec\setupcomplete.log";^
};^
%End PowerShell%
net start toec /y
Tomas
@theopenem_admin - I made many of reinstallation and tests, but the file "setupcompletecmd_complete" is never created on my machines. (image_prepped is present after imaging).
So, if I do "domain join" policy with condition on "setupcompletecmd_complete" policies are not started
and in opposite if I do test on "image_prepped" computer is joined to domain, and other following policies apply (include collect inventory), and finally "Image Prep Cleanup"
Other observation is: file c:\Windows\System32\Sysprep\Sysprep_succeeded.tag was created.
Tomas
@theopenem_admin Thank you for explanation.
Finally, I put that time server settings into unatended.xml file for sysprep. That works for me just fine.
For info how to call cmd script from sysprep:
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>c:\Windows\system32\cmd.exe /c c:\intel\synctime.cmd</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
Tomas
@mikespears check log on client side : c:\program files\Toem\logs\service.log and you can place it here as well.
I went through of that these days so maybe can help.
Tomas
Hi,
I created base image based on tutorial Universal image.
Once client deploy image from server I faced some troubles with client toec connection. All was caused by client machine time. Since we are using our time server and others are firewalled I must set our in universal image and refresh time after deploy.
My question is about timing of two files creation and deletion during init phase:
My concern is: if Toem server policy for join domain will be checking presence of this file after some process delete it it won't be triggered to run and join domain.
Thank you,
Tomas
@theopenem_admin said in Fresh install and PXE not working:
I'm confused with your proxy settings. In your initial post you say you are using the proxy but your images show that you are not using proxy.
My apologize, I didn't try proxy, only tested PXE with vSphere UEFI boot. And it was working.
@alext1024 said in Fresh install and PXE not working:
So VM PXE boot works for legacy bios VM. Seems UEFI VM won't work for Vsphere or Proxmox
Maybe I have to say I have older version of vSphere 6.0
I'm investigating how to work with Lenovo laptops and PXE, but it seems to me there is difference in some networking support.
Eg.: my older Lenovo laptop(i7-5600U) works well with grub or ipxe_efi64 (all TFTP uploads are fast), in contrast vSphere is able to use network and copy from TFTP but it is really slow (initrd.xz took about 30min)
and my newer LENOVO (11thgen i5-1135g7) is not able to work with PXE right now (I believe it is some kernel problem)
@alext1024 said in Fresh install and PXE not working:
So VM PXE boot works for legacy bios VM. Seems UEFI VM won't work for Vsphere or Proxmox
I'm able to boot EFI under Vsphere.