@quazz I remember in previous images, FOG would resize the images before capturing, then expand them during deployment. For whatever reason, it was not doing that this time around. As per my new post, upgrading to 1.4.4 may have helped… Or just a coincidence…
Posts made by lukebarone
-
RE: Windows 10 SysPrep not working
-
RE: Post Download Scripts not running / HDD not being resized
This feels much better!
Upgraded Fog to 1.4.4, and captured the image, deployed it, and was presented with my AD Login screen! It logged me in, then restarted… Then let me log in properly.
A couple things I need to change on the image, but over all, this is much better than where I was before! Thank you for the advice
-
RE: Post Download Scripts not running / HDD not being resized
OK, I’ll update, then report back. Thank you.
-
Post Download Scripts not running / HDD not being resized
Further to my SysPrep not working and Start Menu not loading correctly issue from before, I now have a new issue.
With my old Answer file, I would set the Administrator password, and I assumed it would enable it… Nope, it didn’t! And FOG did not automatically join my domain (the
C:\fog.log
file mentions NOTHING with the domain name, orhostname
, anywhere). So I created a new user in my answer file, and redeployed. The new user was created, but I couldn’t log in. After troubleshooting, I found out the hard drive partition/volume was still shrunk down to 29GB. I expanded it, rebooted, then I could log in.The FOG service is running. When I view the host in the Fog web page, Hostname Changer is enabled (as it should be), and I re-typed the username and password for the Domain section, just in case. No change. Fog is running at 1.3.4. The image type is Windows 10, disk type is “1 - Single disk, resizeable”
On the server, I have my storage set to
/images
(as per the default). I created the folderpostdownloadscripts/
inside there, permissions set to allow thefog
user access to do whatever:/images/postdownloadscripts# ls -lah total 24K drwxrwxrwx 2 fog img 4.0K Jan 11 15:00 . drwxrwxrwx 32 fog img 4.0K Jan 12 15:48 .. -rwxr-xr-x 1 fog img 2.5K Jan 15 09:34 fog.drivers -rwxr-xr-x 1 fog img 562 Jan 10 11:59 fog.log -rwxrwxrwx 1 fog img 233 May 31 2016 fog.postdownload -rwxr-xr-x 1 fog img 1.7K Jan 10 12:02 fog.postinstall
Where can I look for information on why the scripts are not running? Or why the hard drive partition is not being expanded automatically?
-
RE: Windows 10 SysPrep not working
OK, I booted the install drive I had for Windows, and loaded up
diskpart
. Apparently, the only had 29GB total, with nothing free! It also looked like mypostdownloadscripts
did not load, as the drivers didn’t appear in the Windows folder automatically.The new user profile loads, and the Start Menu is working - taskbar, not so much.
So my new issue (which I’ll open a new thread) is to figure out why FOG isn’t resizing the automatically like it did with Windows 7, and why the
postdownloadscripts
are not working. -
RE: Windows 10 SysPrep not working
So I thought it was successful, but apparently not. On my base image machine, I exported the Start Layout into the root of C:, as an XML (apparently, the
-As BIN
function is removed in Windows 10), and pointed the GPO at that. I rebooted the base image machine, and the start menu was locked down, and the taskbar looked perfect! I even went as far as dropping theunattend.xml
file into the%WINDIR%\Panther
folder instead.The issue now when deploying is that when I log in as the user that I had the answer file create, I get the cryptic error message
The User Profile Service service failed the sign in. User profile cannot be found
. I am skipping the User OOBE so that I can just get in with the Administrator account… But the Administrator account is not active for some reason. I cannot log in via Safe Mode (or else I don’t know how to get into it with Windows 10 without being able to log in), so I cannot pull the logs. I’ll probably be spending my morning trying to get the logs though.Thoughts?
-
RE: Windows 10 SysPrep not working
@george1421 So apparently, it worked this time for Sysprepping. No errors came up on my Hyper-V after the capture job was done.
Next is figuring out how to duplicate the Start Layout and Taskbar for every user… Which, as I failed to mention, was the original main show-stopper for me.
-
Windows 10 SysPrep not working
Re: Windows 10 1703 Image with strange issue
I have taken advice from all over the Internet, and I’m failing every time after the SysPrep has completed. I want to create an image (generic or specific to the hardware) with Windows 10, Office 2016, browsers and our regular applications. Part of what I want to do is also duplicate the Start Menu layout, but nothing is working.
The latest attempts will capture the image, then a message comes up on the same computer I built the image on saying
"Windows could not finish configuring the system. To attempt to resume configuration, restart the computer."
. I can click OK many times, and the computer just restarts and does the same thing.My
unattend.xml
file is here:<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="auditSystem"> <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"> <AuditComputerName> <Name>JMC-X-AUDIT</Name> </AuditComputerName> </component> <component name="Microsoft-Windows-Shell-Setup" 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"> <UserAccounts> <AdministratorPassword> <Value>REDACTED</Value> <PlainText>false</PlainText> </AdministratorPassword> </UserAccounts> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" 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"> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-CA</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" 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"> <DesktopOptimization> <GoToDesktopOnSignIn>true</GoToDesktopOnSignIn> <ShowWindowsStoreAppsOnTaskbar>true</ShowWindowsStoreAppsOnTaskbar> </DesktopOptimization> <OEMInformation> <SupportURL>https://jmc.sd57.bc.ca/~lbarone</SupportURL> </OEMInformation> <OOBE> <HideEULAPage>true</HideEULAPage> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> </OOBE> <WindowsFeatures> <ShowInternetExplorer>true</ShowInternetExplorer> </WindowsFeatures> <UserAccounts> <AdministratorPassword> <Value>REDACTED</Value> <PlainText>false</PlainText> </AdministratorPassword> </UserAccounts> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>C:\Windows\Setup\Scripts\SetupComplete.cmd</CommandLine> <Description>Run SetupComplete.cmd batch file</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> </component> <component name="Microsoft-Windows-WiFiNetworkManager" 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"> <DefaultAutoConnectOpenState>0</DefaultAutoConnectOpenState> <DefaultAutoConnectSharedState>0</DefaultAutoConnectSharedState> <WiFiSenseAllowed>0</WiFiSenseAllowed> <WiFiSharingFacebookInitial>0</WiFiSharingFacebookInitial> <WiFiSharingOutlookInitial>0</WiFiSharingOutlookInitial> <WiFiSharingSkypeInitial>0</WiFiSharingSkypeInitial> </component> <component name="Microsoft-Windows-WinRE-RecoveryAgent" 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"> <UninstallWindowsRE>true</UninstallWindowsRE> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-IE-InternetExplorer" 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"> <StartPages> <StartPage wcm:action="add"> <StartPageKey>1</StartPageKey> <StartPageUrl>https://www.sd57.bc.ca/school/cla/Pages/default.aspx</StartPageUrl> </StartPage> </StartPages> <SuggestedSitesEnabled>false</SuggestedSitesEnabled> <Home_Page>https://www.sd57.bc.ca/school/cla/Pages/default.aspx</Home_Page> <DisableOOBAccelerators>true</DisableOOBAccelerators> <DisableFirstRunWizard>true</DisableFirstRunWizard> <DisableAccelerators>true</DisableAccelerators> <CompanyName>School District #57 (Prince George)</CompanyName> </component> <component name="Microsoft-Windows-WwanUI" 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"> <NotInOOBE>true</NotInOOBE> </component> <component name="Microsoft-Windows-Shell-Setup" 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"> <CopyProfile>true</CopyProfile> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-SharedAccess" 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"> <EnableICS>false</EnableICS> </component> </settings> <cpi:offlineImage cpi:source="wim://tech-lbarone/users/luke/desktop/win10x64pro_workingdir/sources/install.wim#Windows 10 Pro Technical Preview" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
The latest take was done in Hyper-V, with the recommendation to make base images in a virtualized environment. Next step will be to figure out how to get it to work with FOG’s PXE boot mode, but that’s later.
Steps to reproduce:
- Use our Volume License media to install Windows 10, wiping the hard drive and letting Windows partition as necessary
- Go into Audit mode during Cortana setup screen
- Install Office 2016, AVG Anti-virus (disabled during testing and setup), Chrome / Firefox, Adobe Reader
- Apply Local Group Policy (no Active Directory domain setup)
- Install the FOG client from my FOG installation (Running Version 1.3.4, SVN Revision: 6064). Service is disabled in
services.msc
- Customize the Admin profile (i.e. desktop icons, Start Menu, background picture, etc)
- Restart system (still in Audit), verify everything looks good. Copy
SetupComplete.cmd
,Layout.ps1
, and our Wireless profile file toC:\Windows\Setup\Scripts
. Copy theunattend.xml
file toC:\Windows\System32\SysPrep
- Restart one more time for good measure.
- Run
sysprep /quiet /generalize /oobe /shutdown /unattend:unattend.xml
from the Command Prompt, in theC:\Windows\System32\SysPrep
working folder - Attempt to capture image
- System turns back on, and the error message appears.
Below is my
SetupComplete.cmd
file:sc config FOGService start= auto net start FOGService echo Installing Windows Product Key... cscript //b c:\windows\system32\slmgr.vbs /ipk REDACTED echo Activating Windows.... cscript //b c:\windows\system32\slmgr.vbs /ato netsh wlan add profile filename=Private-SD57-2.xml user=all Powershell.exe -NoProfile -Command "& {Start-Process PowerShell.exe -ArgumentList '-NoProfile -ExecutionPolicy ByPass -File ""%~dp0\layout.ps1""' -Verb RunAs}" rd /S /Q "C:\Users\Default\AppData\LocalLow" rd /S /Q "C:\users\Default\AppData\Local\Microsoft\Windows\WebCache" rd /S /Q "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache" del /F "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat" REM del /F C:\Windows\System32\Sysprep\unattend.xml REM del /F C:\Windows\Setup\Scripts\SetupComplete.cmd REM del /F C:\Windows\Setup\Scripts\Private-SD57-2.xml del /F c:\windows\system32\sysprep\panther\setupact.log del /F c:\windows\system32\sysprep\panther\setuperr.log del /F c:\windows\system32\sysprep\panther\ie\setupact.log del /F c:\windows\system32\sysprep\panther\ie\setuperr.log shutdown -r -t 60 -f
Where can I go to troubleshoot further?
-
RE: Installing FOG on Debian Stretch fails
@plegrand it works now, on version 1.4.3
-
Installing FOG on Debian Stretch fails
Server
- FOG Version: 1.4.0
- OS: Debian Stretch (9.0)
Description
Downloaded the latest tarball of the install. Extracted, ran the
installfog.sh
command. After confirming, I wait for it to install packages, and it fails to install php5 and its modules.Debian Stretch does not have php version 5 available anymore.
Is there a known fix to get the install script to run? Will it work with PHP 7? This is a brand new VM, no other changes made.
-
RE: Network Boot forgets Ethernet card exists after booting
@Sebastian-Roth Using
isc-dhcp-server
on a separate Debian Jessie server (192.168.0.1)@Wayne-Workman I’ll give that a try and report back. Because I never installed FOG’s DHCP server, I never knew about those lines.
Edit: I got this working. Issue with the switch, and I’m guessing, Auto-Negotiation. Turned it down to 100M Full Duplex, and it worked on the next boot! No change with the extra lines added to DHCP though.
-
RE: Network Boot forgets Ethernet card exists after booting
@Wayne-Workman Here it is:
authoritative; option domain-name "sd57.lan"; option domain-name-servers 192.168.0.1,199.175.16.2; option netbios-name-servers 192.168.0.3; option local-pac-server code 252 = text; option domain-search "sd57.bc.ca", "sd57.lan"; option routers 192.168.31.254; ddns-updates on; ddns-update-style interim; ignore client-updates; update-static-leases on; default-lease-time 3600; #1 Hr max-lease-time 28800; log-facility local7; include "/etc/dhcp/ddns.key"; zone sd57.lan. { primary 127.0.0.1; key DDNS_UPDATE; } zone 0.168.192.in-addr.arpa. { primary 127.0.0.1; key DDNS_UPDATE; } subnet 192.168.0.0 netmask 255.255.224.0 { authoritative; ddns-domainname "cla.sd57.bc.ca"; next-server 192.168.0.4; # FOG Server # filename "ipxe.pxe"; # filename "intel.pxe"; # filename "pxelinux.0"; filename "undionly.kpxe"; # The closest thing I have to something working # filename "undionly.pxe"; range 192.168.1.1 192.168.8.254; option subnet-mask 255.255.224.0; option broadcast-address 192.168.31.255; option routers 192.168.31.254; option netbios-name-servers 192.168.0.3; option netbios-node-type 8; }
-
RE: Network Boot forgets Ethernet card exists after booting
OK, I got it to use the correct filename. Now, the machines start the booting from the network, and when iPXE loads (1.0.0+ 26050), it goes to:
Configuring (net0 <MAC Address>)...... No configuration methods succeeded Configuring (net0 <MAC Address>)...... OK iPXE>
The advantage now is that the correct MAC address is attempting to boot; the unfortunate part is that the FOG menu is still not coming up
I also tried with a “dumb switch” just before the computers in question - no change. I know that STP is disabled on all my switches leading back to the FOG Server (when Googling other forums, this came up quite a bit to check for).
-
RE: Network Boot forgets Ethernet card exists after booting
@Tom-Elliott Well, this is awkward…
Captured a
tcpdump
from the DHCP server, and you’re right! It’s dishing outpxelinux.0
, not what I specified in the/etc/dhcp/dhcpd.conf
file! More investigating on my part now… Thanks for the direction to look in! -
RE: Network Boot forgets Ethernet card exists after booting
@Tom-Elliott OK, I can find the
ipxe.krn
file (notipxe.lkrn
) in my/tftpboot
folder. Assuming this is correct, why will the FOG menu not appear? Is there more work I can trace back to help? -
Network Boot forgets Ethernet card exists after booting
Server
- FOG Version: SVN 6063
- OS: Debian Jessie
Client
- Service Version: N/A
- OS: N/A
Description
PXE Booting is going to be the death of me! I need to image some computers, and then I learned that FOG is not working. So, I start the troubleshooting, and here’s what I found:
- The default menu appears for SOME clients (this is new to me, I’ve never seen it before. The only option is “fog”). After the zero second time out (where is it getting this info from?), it moves on to try to Network Boot the Wifi card, which fails.
- On the one I care about imaging right now, it starts the Network Boot, gets its IP address and info from the DHCP server, then starts to load the IPXE environment, which tries to boot the Wifi card, and does not seem to detect the Ethernet card that booted it.
I have tried to re-install the latest version from git, and the issue is still here. It seems like the IPXE kernel is not understanding the basic NIC in two different test machines - a VirtualBox machine, and an Asus EeePC.
DHCP options:
next-server 192.168.0.4;
filename “undionly.kpxe”;FOG server is located at 192.168.0.4, and the /tftpboot directory looks normal:
/tftpboot# ls -lah total 7.1M drwxr-xr-x 6 fog root 4.0K Jan 27 12:09 . drwxr-xr-x 25 root root 4.0K Jan 27 12:09 .. drwxr-xr-x 2 fog root 4.0K Jan 27 12:09 10secdelay -rw-r-xr-x 1 fog root 840 Jan 27 12:09 boot.txt -rw-r-xr-x 1 fog root 426 Jan 27 12:09 default.ipxe drwxr-xr-x 2 fog root 4.0K Aug 25 09:00 i386-7156-efi drwxr-xr-x 2 fog root 4.0K May 31 2016 i386-efi -rw-r-xr-x 1 fog root 195K Jan 27 12:09 intel7156.efi -rw-r-xr-x 1 fog root 216K Jan 27 12:09 intel.efi -rw-r-xr-x 1 fog root 92K Jan 27 12:09 intel.kkpxe -rw-r-xr-x 1 fog root 92K Jan 27 12:09 intel.kpxe -rw-r-xr-x 1 fog root 92K Jan 27 12:09 intel.pxe -rw-r-xr-x 1 fog root 921K Jan 27 12:09 ipxe7156.efi -rw-r-xr-x 1 fog root 959K Jan 27 12:09 ipxe.efi -rw-r-xr-x 1 fog root 846K Jan 27 12:09 ipxe.iso -rw-r-xr-x 1 fog root 337K Jan 27 12:09 ipxe.kkpxe -rw-r-xr-x 1 fog root 337K Jan 27 12:09 ipxe.kpxe -rw-r-xr-x 1 fog root 337K Jan 27 12:09 ipxe.krn -rw-r-xr-x 1 fog root 337K Jan 27 12:09 ipxe.pxe -rw-r-xr-x 1 fog root 121K Jan 27 12:09 ldlinux.c32 -rw-r-xr-x 1 fog root 184K Jan 27 12:09 libcom32.c32 -rw-r-xr-x 1 fog root 26K Jan 27 12:09 libutil.c32 -rw-r-xr-x 1 fog root 26K Jan 27 12:09 memdisk -rw-r-xr-x 1 fog root 29K Jan 27 12:09 menu.c32 -rw-r-xr-x 1 fog root 43K Jan 27 12:09 pxelinux.0 -rw-r-xr-x 1 fog root 43K Jan 27 12:09 pxelinux.0.old drwxr-xr-x 2 fog root 4.0K May 31 2016 pxelinux.cfg -rw-r-xr-x 1 fog root 195K Jan 27 12:09 realtek7156.efi -rw-r-xr-x 1 fog root 216K Jan 27 12:09 realtek.efi -rw-r-xr-x 1 fog root 93K Jan 27 12:09 realtek.kkpxe -rw-r-xr-x 1 fog root 93K Jan 27 12:09 realtek.kpxe -rw-r-xr-x 1 fog root 93K Jan 27 12:09 realtek.pxe -rw-r-xr-x 1 fog root 194K Jan 27 12:09 snp7156.efi -rw-r-xr-x 1 fog root 215K Jan 27 12:09 snp.efi -rw-r-xr-x 1 fog root 194K Jan 27 12:09 snponly7156.efi -rw-r-xr-x 1 fog root 215K Jan 27 12:09 snponly.efi -rw-r-xr-x 1 fog root 92K Jan 27 12:09 undionly.kkpxe -rw-r-xr-x 1 fog root 92K Jan 27 12:09 undionly.kpxe -rw-r-xr-x 1 fog root 374K May 31 2016 undionly.kpxe.INTEL -rw-r-xr-x 1 fog root 92K Jan 27 12:09 undionly.pxe -rw-r-xr-x 1 fog root 30K Jan 27 12:09 vesamenu.c32
Suggestions of where to look? The DHCP server is also Debian Jessie, but on a different server.
I ran a
tcpdump
on the interface, and looked at it through Wireshark, as suggested. The only errors I see is an unknown error at the top, and missing files, such aspxelinux.cfg/80833fa6-f091-4681-2969-485b39123be5
, then other weird ID numbers, until it findspxelinux.cfg/default
, and continues on. I can post the capture file if it would help futher -
RE: FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):"
@Tom-Elliott I updated to RC-11 with
git
. Ran the install, was using Kernel 4.7.3. Same issues as before. Switched back to 4.1.0 (another tech in the school district ran into the problem), and the systems are imaging. I’m still using the USB keyboard, as the built-in laptop keyboard is not working for registering.If it helps any, the BIOS version is A06 out of the box. I’ve tried with A08 (the newest), and no change.
-
RE: FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):"
@adukes40 said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
For our 3350’s you have to set
Host Kernel Arguments pci=noacpi
for each host. (maybe needs to be for 5520s as well??) We do not have any here, so I don’t know.
But I created a group, registered them all to the group, and mass updated all the host arguments.I think I may create a new post for this, but… How do I get them registered if I can’t type with the keyboards initially? Dell doesn’t send the MAC addresses in their packing slips. Once they’re registered, I can certainly do that (and I see no reason NOT to), but it is still not going to work initially, right?
-
RE: Cannot boot user off to rename host
@Tom-Elliott said in Cannot boot user off to rename host:
Aware and fixed for -10
Not fixed in my installation of RC-10
-
RE: FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):"
@Tom-Elliott said in FOG will not boot - "Failed to get an IP via DHCP! Tried on interface(s):":
@lukebarone has the keyboard on the laptop worked in the past with registering a host? What kind of keyboard is it? Does it detach or just isn’t recognizes? If you’re doing a tasking and unable to use the keyboard, this is normal.
Hi Tom,
It’s the built-in keyboard on the laptop of the Dell e3350. Plug in a USB keyboard, and it works fine. I’m thinking that Dell is just doing weird things to get everyone on to Windows 10 and their custom installs of it. The keyboard works in the menu, and logging in to FOG’s PXE boot menu. Once I select a task (i.e. Full Host Registration), it stops working. Plug in the keyboard, and I can type in the hostname and other options.