@TheDiskDrive said in Create UEFI ISO and prepare Surface go deployement.:
Fatal Error: unknow request type :: Null
Kernel Variables and settings:
Sorry I didn’t see this til now. The issue with the unknown user request is listed in the caveats. You MUST schedule the task in FOG BEFORE you select option 1 from the menu.
@UWPVIOLATOR said in Dell Precision 5530 Compatibility:
FOG images it but it wont boot to HD.
Can you check in the firmware to see if you need to change the boot order to the hard drive first??
@UWPVIOLATOR Ok since you have a 3530 (I still don’t have my allocations yet) does it have a built in ethernet adapter, or do you have a usb-c/usb-a adapter that is uefi pxe boot compliant?
Are you running the latest release of FOG and its kernels?
@UWPVIOLATOR Fair enough. The WD15 is Dell’s usb-c port replicator hub.
https://www.dell.com/en-us/shop/dell-business-dock-wd15-with-180w-adapter/apd/452-bddu
It has a built in network adapter that is uefi/pxe boot compliant.
@UWPVIOLATOR Do you have the WD15 port replicators you can test with?
Hello,
You really didn’t give us any information to help you.
If you can post a clear picture of the error you see taken with a mobile phone. Post the picture in this thread.
Its not clear at this time if fog is doing this or Windows playing with the boot order. I know in uefi mode windows can do this, but not in bios mode.
What I want you to do is set the boot order like you want it then schedule a deploy to this computer but tick the checkbox to shutdown after deployment.
Go ahead and deploy to this computer.
After the computer shuts down, power it up and immediately go into the firmware and confirm the boot order before the deployed OS boots the first time.
With that info we can think about the next steps.
Also what version of FOG are you running, that may have an impact on the next steps.
@dooleyrd Was the FOG Client service enabled in your golden image?
For others that might find this thread: https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep
@maouu Here is how we deploy with PDQ Deploy (sorry I don’t use snapins but the install function is similar:
@Echo Off
start /wait dfmirage-setup-2.0.301.exe /verysilent /norestart
REM Hack to determine arch of this system
IF EXIST C:\Windows\SysWOW64\diskpart.exe GOTO :x64
:x86
msiexec /i tightvnc-2.7.10-setup-32bit.msi /qn /norestart ADDLOCAL="Server" SERVER_REGISTER_AS_SERVICE=1 SERVER_ADD_FIREWALL_EXCEPTION=1 SERVER_ALLOW_SAS=1 SET_USEVNCAUTHENTICATION=1 VALUE_OF_USEVNCAUTHENTICATION=1 SET_PASSWORD=1 VALUE_OF_PASSWORD=<SetMe!!> SET_USECONTROLAUTHENTICATION=1 VALUE_OF_USECONTROLAUTHENTICATION=1 SET_CONTROLPASSWORD=1 VALUE_OF_CONTROLPASSWORD=<SetMe2!!> SET_IPACCESSCONTROL=1 VALUE_OF_IPACCESSCONTROL="192.168.0.0-192.168.255.255:2,0.0.0.0-192.167.255.255:1,192.169.0.0-255.255.255.255:1" SET_REMOVEWALLPAPER=1 VALUE_OF_REMOVEWALLPAPER=1
:x64
msiexec /i tightvnc-2.7.10-setup-64bit.msi /qn /norestart ADDLOCAL="Server" SERVER_REGISTER_AS_SERVICE=1 SERVER_ADD_FIREWALL_EXCEPTION=1 SERVER_ALLOW_SAS=1 SET_USEVNCAUTHENTICATION=1 VALUE_OF_USEVNCAUTHENTICATION=1 SET_PASSWORD=1 VALUE_OF_PASSWORD=<SetMe!!> SET_USECONTROLAUTHENTICATION=1 VALUE_OF_USECONTROLAUTHENTICATION=1 SET_CONTROLPASSWORD=1 VALUE_OF_CONTROLPASSWORD=<SetMe2!!> SET_IPACCESSCONTROL=1 VALUE_OF_IPACCESSCONTROL="192.168.0.0-192.168.255.255:2,0.0.0.0-192.167.255.255:1,192.169.0.0-255.255.255.255:1" SET_REMOVEWALLPAPER=1 VALUE_OF_REMOVEWALLPAPER=1
:Exit
REM Install done, errors generated by msi will be reported to installer
net stop "TightVNC Server"
net start "TightVNC Server"
rmdir /s /q "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\TightVNC\"
I’m pretty sure if you reinstall with the new parameters they will overwrite what is in the registry. I know this ISN’T what you are looking for, but it works for us.
@maouu I know tightvnc, so I’m going to ask what is your goal here. Do you want to preset these values using regedit? If so there is a different way to go about this that we use.