Posts made by Jason Cline

@theopenem_admin I'm thinking it has something to do with the ISO I'm using to install. Going back to the drawing board on that. I'll update when/if I figure it out.

@theopenem_admin Not yet, and now with the newest version of Win 11, I can't run the TOEC installer because it's telling me the system administrator has set a policy to prevent it. This is while in admin/audit mode.

@theopenem_admin I'm not familiar with the setupcomplete file. What might I need to do with that? I've never messed with it beyond the defaults.

Here's exactly what I'm doing. I've tried this on multiple systems now.

Installed new Windows 11 on PC via USB. At country selection use Ctrl-Shift-F3 to go into audit mode. Run all updates, use ninite.com to install Chrome, VLC Player, Google Drive, and WinDirStat. Install toec. Wait for toec to register with com server (which sometimes fails, unsure why).

Then run Toec-Sysprep, connect to com server, select the unattend file, and then sysprep.

If I boot THAT machine after uploading the image (or before uploading it), it tells me "Windows could not complete the installation. To install windows on this computer, restart the installation."

I'm at a loss. I'm not sure if something about the toec portion of imageprep is removing something that's needed, or if there's something wrong with my install media (A theory I'm going to test right now)

@theopenem_admin This is with the newest 22H2 image, by the way. And I had to use the Windows Installation Media creator to get the installer to recognize the hard drives on this device.

I'm getting a terribly helpful message from Windows 11 after deploying a newly created image. "Windows could not complete the installation. To install windows on this computer, restart the installation."

Clicking Ok reboots the PC, and leave the "finalizing" screen as the background, but does not join the computer to the domain or finish setup. I used the same unattend I've used for countless Win 10 installs, and also tried creating a new one.

Has anyone else run into this, or has anyone spotted a fix for this? I'm desperate, as we've got a very tight window for re-deploying our fleet this summer.

@theopenem_admin 1.4.8/1.4.5 client

Ok, so I think this topic can be safely ignored. I think I was being plagued by two separate small issues.

Is there any string validation on the device name when you first boot into TheOpenEM with a device? One of our culprits was an erroneous "=" in place of a "-", Windows choked hard on that when it found it in the unattend file. And kept doing so because the name stayed in the background, out of sight, for multiple deploy (and upload) attempts

@theopenem_admin Ok, I'm going to start over and try both methods, because I honestly don't remember which is which. There are about 30 logs in the last 3 days. So, I'll send them, but it'll be a bit.

@theopenem_admin Could you remind me where I might find the deploy log?

Also, I've been trying with a universal image (which has worked wonderfully in the past). But now I'm trying to make an image on the machine in question. I get it updated, and use toec_sysprep to prep it, and something is happening. If I try to upload the image, toems fails saying the drive needs checked, but if the machine boots, it gives an unexpected error and prompts for reboot. If I go in with an installer and chkdsk with command prompt, I still get the error, and can do nothing but reboot.

I have uploaded the image after such a chkdsk, but any deployments made from it have the same unexpected error reboot.

I'm installing Windows 10 Pro.

Would love to be able to search by user on the Computer list, now that it's included in the display.

Just wanted to let you know that I've not been able to send a message via the contact form regarding support plans for some time. I fill everything out, and get a "something went wrong" tooltip when submitting.

We've got a few new HP all in ones that we had trouble booting into TheOpenEM with, but have gotten past that. They will deploy properly, copy drivers, restart, but no matter the arrangement of settings (different kernel, AHCI vs RAID in the BIOS, different deploy settings with Dynamic, Standard, Original partition schemes. Secure boot doesn't even seem to be an option. It's greyed out and disabled.), it won't boot after deploy. Just says there's no boot device.

I'm guessing that whatever boot loader is being copied during the image process is just unrecognizable to the All In One, but I'm hoping someone may have found a workaround.

Hope that makes sense.

@grolsch I had to set the TOEC API config file's logging setting to debug from info. Then I got the cause of my issue (Which WAS a time zone problem)

@theopenem_admin Ok, perfect. That's the step I was missing, thanks.

Where is the remote access ID stored on the client? I'm trying to fix a few dozen devices that are deployed, that all have the same remote access ID. I know what caused it and can prevent it in the future, but so far ininstalling remotely and/or toec is not clearing out that Remotely access ID.

@theopenem_admin It loads several HBA and SCSI drivers, but I don't see any errors related to the hard drive, or any reference to the hard drive, for that matter. Trying to find a place I can SFTP the dmesg output file to. I'll reply as soon as I have it.

Good morning,

I've had trouble with newer Acer laptops. Here's my current issue: We get through PXE boot, identify the device, select deploy, pick the image, and then it fails to find a hard drive on the PC. It suggests to try a different kernel. I've tried 4.20.10 (too old) 5.6.4, 5.10.11, 5.11.10, and 5.14.12. The device only supports UEFI, secure boot is not on, fast boot is not on. Can anyone think of anything else I should try?

Was thinking about this. Could you prompt the user for a domain admin name and password to pass to the netdom renamecomputer command?

I've not successfully created a web task yet. I've set the image and the profile for the device, then created the deploy task. Restarted the PC. It bypasses the boot to local or theopenem menu, but then says no active imaging tasks, and prompts for a login, then taking one to the On Demand menu. If I check the tasks after I start an on-demand deploy, it shows the name with :06-29-2021_23_38 behind it, which is the timestamp of the first time I registered the PC with TheOpenEM.

Am I missing a step to creating deploy tasks from the web interface?