Posts made by icxnelly

@icxnelly I just realized this is because COM2 uses the Database on COM1.... Is there a way to make both COM servers replicate the database like how it is done with storage?

So I have 2 com servers on the same network, I set them up following the setup video on YT.

Anyway, As a test:

1. I disconnected com server 1 from the network.
2. OK, PXE booting still works via COM Server 2 but once I get to the login screen, I try to login with the same creds I use on COM Server 1 (Same creds whether its web UI or PXE Login) and I get an "incorrect Login" returned.

If COM1 and COM2 are online, this issue does not occur and I am able to authenticate into the On Demand Imaging Screen.

I've been using this Win 10 22H2 Image for deployment without issues until today.. I deployed to a machine today & after 10 minutes it was not under Active Computers, I checked the imaging logs and there is no error that I could identify (attached)

Logged into the machine as local admin, opened a Admin PS prompt and from C:\Program Files\Toec, I ran the --resetPartial and again, the --resetFull option 10 minutes apart with no change (machine never checks in) ... So I went ahead and pre-provisioned it again via TOEMS Web UI & re-ran the --resetFull. I went ahead and joined my domain and rebooted. Still no change as of 10 minutes later (at time of typing this)

As I am typing this, the machine actually did show up under active computers with a successful check-in. My question is, why/what could cause this?

I'll also mention that the image used, is meant to be universal based of the universal image YT video.

MP-PHONE-REP-6_03-14-2023_10_09-modelmatchdeploy.txt

@icxnelly Hi guys I just needed to change the boot mode, IDK why I didn't think of that..

THANKS!!!!

Alright, so I have a Windows 10 22H2 image that I built that i've had no issue deploying to other Lenovo M710q SFF 10AY's(along with other profiled images for diff models) but on one of them, I'm having issues.

So deployment goes fine, then -- Upon boot up, I get a 'booting from local disk...' then 'boot error'. I've tried deploying this image via LEGACY & UEFI with both failing to boot.

My question is, is this something from my end? (I've installed the 10AY profiled image on other 10AY models without issues.) OR could this be something like the hard disk being bad?

I've included the Deploy log(s) as well below.

TELL4-W10_01-31-2023_13_52-onddeploy (1).txt