Deployment not completing

Greg_E

Still banging my head against the wall on this, not sure why I'm not able to understand this.

Using the standalone generated WIE boot image.

Install Win11 25h2 OS, updates, etc., install TOEC and let it check in.

Run the TOEC imagine prep, using the bare minimum setup completion and unattend that you provide in the documentation copied to the server and loaded into the TOEC prep tool.

Boot from USB WIE and capture image.

Grab a second computer that is the same hardware. Boot from HBCD and wipe the drive. Boot from usb WIE type in computer name, deploy image. *I've shut off all the security for now, want to make sure that doesn't get in the way while I'm still trying to figure this out.

PC reboots, comes up to a Windows logo, I see an update message and then it tries to reboot, and I get the attached image. I let this wait overnight to see what would happen, but all it did was go into hibernate.

I can get logs, but they might be kind of worthless, I did a lot of clicking around and it seemed to fill up some of them.

I have both from the TOEC before I messed with things:
Service

2025-11-24 10:50:53,127 INFO [7] Host - Starting Toec Service 2025-11-24 10:50:54,054 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-24 10:50:57,836 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-24 10:50:57,836 INFO [4] ServiceInitialize - Provision Status: 0 2025-11-24 10:50:57,839 INFO [4] ServiceInitialize - Installation ID: 3be7b004-0e1a-4ee9-af59-db6440ad3246 2025-11-24 10:50:57,839 INFO [4] ServiceInitialize - Verification Complete 2025-11-24 10:50:58,691 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 21 Seconds. 2025-11-24 10:51:19,692 INFO [4] ServiceProvision - Verifying Client Provision Status 2025-11-24 10:51:19,723 INFO [4] ServiceProvision - Verification Complete 2025-11-24 10:51:20,186 INFO [4] ServiceAD - AD Computer Guid: 486f489b-b2ea-4607-b4c9-91b1d9e0dec0 2025-11-24 10:51:29,515 INFO [4] ServiceTriggerAction - Checking For Startup Policies 2025-11-24 10:51:29,936 INFO [4] PolicyRunner - No Policies For Trigger Startup Were Found For This Computer 2025-11-24 10:51:29,936 INFO [4] ServiceTriggerAction - Check In Time Set To 60 2025-11-24 10:51:29,936 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete. 2025-11-24 10:59:18,650 INFO [7] Host - Starting Toec Service 2025-11-24 10:59:18,724 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-24 10:59:22,286 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-24 10:59:22,288 INFO [4] ServiceInitialize - Provision Status: 8 2025-11-24 10:59:22,288 INFO [4] ServiceInitialize - Installation ID: 3be7b004-0e1a-4ee9-af59-db6440ad3246 2025-11-24 10:59:22,288 INFO [4] ServiceInitialize - Verification Complete 2025-11-24 10:59:22,831 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 73 Seconds. 2025-11-24 11:00:35,845 INFO [4] ServiceProvision - Verifying Client Provision Status 2025-11-24 11:00:35,879 INFO [4] ServiceProvision - Verification Complete 2025-11-24 11:00:37,332 INFO [4] ServiceTriggerAction - Checking For Startup Policies 2025-11-24 11:00:37,635 INFO [4] PolicyRunner - No Policies For Trigger Startup Were Found For This Computer 2025-11-24 11:00:37,635 INFO [4] ServiceTriggerAction - Check In Time Set To 60 2025-11-24 11:00:37,635 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete. 2025-11-24 16:32:46,696 INFO [7] Host - Starting Toec Service 2025-11-24 16:32:47,073 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-24 16:32:50,811 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-24 16:32:50,811 INFO [4] ServiceInitialize - Provision Status: 0 2025-11-24 16:32:50,811 INFO [4] ServiceInitialize - Installation ID: 2025-11-24 16:32:50,811 INFO [4] ServiceInitialize - Generating New Installation ID 2025-11-24 16:32:50,826 INFO [4] ServiceInitialize - Verification Complete 2025-11-24 16:32:51,842 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 90 Seconds. 2025-11-24 16:34:22,212 INFO [7] Host - Starting Toec Service 2025-11-24 16:34:22,258 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-24 16:34:25,891 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-24 16:34:25,906 INFO [4] ServiceInitialize - Provision Status: 0 2025-11-24 16:34:25,906 INFO [4] ServiceInitialize - Installation ID: cefb821d-5d47-410b-ab92-eb7a3ff86e7f 2025-11-24 16:34:25,906 INFO [4] ServiceInitialize - Verification Complete 2025-11-24 16:34:26,350 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 64 Seconds. 2025-11-24 16:34:29,517 INFO [7] Host - Starting Toec Service 2025-11-24 16:34:29,549 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-24 16:34:32,151 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-24 16:34:32,151 INFO [4] ServiceInitialize - Provision Status: 0 2025-11-24 16:34:32,161 INFO [4] ServiceInitialize - Installation ID: cefb821d-5d47-410b-ab92-eb7a3ff86e7f 2025-11-24 16:34:32,161 INFO [4] ServiceInitialize - Verification Complete 2025-11-24 16:34:32,579 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 71 Seconds. 2025-11-24 16:35:43,600 INFO [4] ServiceProvision - Verifying Client Provision Status 2025-11-24 16:35:43,614 INFO [4] ServiceProvision - Verification Complete 2025-11-24 16:35:43,774 ERROR [4] ServiceAD - Active Directory Search Failed: 2025-11-24 16:35:43,774 ERROR [4] ServiceAD - Current security context is not associated with an Active Directory domain or forest. 2025-11-24 16:35:47,842 INFO [4] ServiceTriggerAction - Checking For Startup Policies 2025-11-24 16:35:48,150 INFO [4] PolicyRunner - No Policies For Trigger Startup Were Found For This Computer 2025-11-24 16:35:48,150 INFO [4] ServiceTriggerAction - Check In Time Set To 60 2025-11-24 16:35:48,150 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete. 2025-11-25 09:06:51,682 INFO [89] ServiceSocket - Could Not Connect To Web Socket 2025-11-25 09:06:51,682 ERROR [89] ServiceSocket - System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable host 172.30.0.40:8888 at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult) at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar) --- End of inner exception stack trace --- 2025-11-25 09:06:51,683 INFO [89] ServiceSocket - Server Push Events Will Not Be Available 2025-11-25 09:08:21,640 INFO [7] Host - Starting Toec Service 2025-11-25 09:08:21,708 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-25 09:08:24,491 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-25 09:08:24,494 INFO [4] ServiceInitialize - Provision Status: 8 2025-11-25 09:08:24,494 INFO [4] ServiceInitialize - Installation ID: cefb821d-5d47-410b-ab92-eb7a3ff86e7f 2025-11-25 09:08:24,494 INFO [4] ServiceInitialize - Verification Complete 2025-11-25 09:08:25,126 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 48 Seconds. 2025-11-25 09:09:13,136 INFO [4] ServiceProvision - Verifying Client Provision Status 2025-11-25 09:09:13,152 INFO [4] ServiceProvision - Verification Complete 2025-11-25 09:09:15,186 INFO [4] ServiceTriggerAction - Checking For Startup Policies 2025-11-25 09:09:15,630 INFO [4] PolicyRunner - No Policies For Trigger Startup Were Found For This Computer 2025-11-25 09:09:15,632 INFO [4] ServiceTriggerAction - Check In Time Set To 60 2025-11-25 09:09:15,632 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete. 2025-11-25 09:10:06,621 INFO [7] Host - Starting Toec Service 2025-11-25 09:10:06,688 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-11-25 09:10:09,338 INFO [4] ServiceInitialize - Verifying Installation ID 2025-11-25 09:10:09,338 INFO [4] ServiceInitialize - Provision Status: 8 2025-11-25 09:10:09,338 INFO [4] ServiceInitialize - Installation ID: cefb821d-5d47-410b-ab92-eb7a3ff86e7f 2025-11-25 09:10:09,338 INFO [4] ServiceInitialize - Verification Complete 2025-11-25 09:10:09,574 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 76 Seconds.

tray

2025-11-24 10:59:39,960 INFO [1] Program - Tray App Started 2025-11-24 10:59:39,967 INFO [1] Program - Current User: greg 2025-11-24 10:59:44,470 ERROR [1] ApiRequest - Error Retrieving API Response: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:1415 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at RestSharp.Http.<ExecuteRequest>g__GetRawResponse|185_1(WebRequest request) at RestSharp.Http.ExecuteRequest(String httpMethod, Action1 prepareRequest)
2025-11-24 10:59:58,521 ERROR [1] ApiRequest - Error Retrieving API Response: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:1415
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at RestSharp.Http.<ExecuteRequest>gGetRawResponse|185_1(WebRequest request)
at RestSharp.Http.ExecuteRequest(String httpMethod, Action1 prepareRequest) 2025-11-24 11:00:12,571 ERROR [1] ApiRequest - Error Retrieving API Response: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:1415 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at RestSharp.Http.<ExecuteRequest>g__GetRawResponse|185_1(WebRequest request) at RestSharp.Http.ExecuteRequest(String httpMethod, Action1 prepareRequest)
2025-11-24 11:00:26,624 ERROR [1] ApiRequest - Error Retrieving API Response: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:1415
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at RestSharp.Http.<ExecuteRequest>gGetRawResponse|185_1(WebRequest request)
at RestSharp.Http.ExecuteRequest(String httpMethod, Action1 prepareRequest) 2025-11-24 11:00:37,111 INFO [1] ServiceTriggerAction - Checking For Login Policies 2025-11-24 11:00:37,396 INFO [1] PolicyRunner - No Policies For Trigger Login Were Found For This Computer 2025-11-24 11:00:37,396 INFO [1] ServiceTriggerAction - Trigger Action: Login. Complete.

Any other logs I can get? I've tried with both secure boot on, and secure boot off to see if that was getting in the way.

I'm also getting another problem that might be related. When I wipe the drives, the deployment comes up with a big red warning about the drives being unformatted (or something), it then seems like it goes through and creates the partitions, but it fails copying the files and reboots. Second time around it is able to complete the partitions and copying the files.

I'm probably going to get the LIE configured and make a fresh client install and see what happens. I'm guessing some of this might be a Win11 25h2 issue, but some of this is me not understanding something and I'm just not getting it. I've watched the videos at least 3 times, and been through the documents more than that.

Greg_E

Same happens if I use the LIE or if I just reboot the computer.

I tested just sysprep with the same unattend.xml file, and it worked fine, a final reboot just after the checking for updates. Somewhere, for a reason I can't find, TOEC is getting tripped up at this point. The completion file is written and it seems like it is trying to move on to another step. I'm guessing it has something to do with the bold text in the log above. And this probably points to some kind of configuration mistake I made when setting up the server. Going to go back through the settings today and see if I can find where I missed something.

Thankfully I got smart and made a Clonezilla backup of the workstation, it's a lot faster to go back to this state, just before TOEC is installed. Clear out the server, install latest TOEC configuration, and start the process over.

Greg_E

Haven't had time to get back to this, going to go through the install and config procedures and make sure I didn't miss something.

Not really sure where to go from here or what to look at to try and figure this out.

theopenem_admin

Did you make a cleanup policy in the first run group? You also don't need to the image prep tool, sometimes it makes things harder, you can just use a sysprep answer file, to join the domain etc, and just skip all that, as long as Toec is on the image and it's install ID is reset before you capture it, it will work fine.

Greg_E

I have not yet made a clean up policy, need to do that. I also see a section of the setupcomplete file that I need to comment out, I don't need/want it loading drivers so I need to comment that section out.

Let me look those up and see how far I get.

Greg_E

OK, looking better (sort of). It looks like I have a stumbling block again. TOEC client can not find the log in credentials for joining the domain. This was before image prep and deploy, just wanted to make sure this part worked before prepping and deploying. Log and screenshot below:

2025-12-02 15:29:55,172 INFO [7] Host - Starting Toec Service 2025-12-02 15:29:56,219 INFO [4] ServiceInitialize - Toec Version: 1.5.7.0 2025-12-02 15:29:59,485 INFO [4] ServiceInitialize - Verifying Installation ID 2025-12-02 15:29:59,503 INFO [4] ServiceInitialize - Provision Status: 0 2025-12-02 15:29:59,503 INFO [4] ServiceInitialize - Installation ID: df36c84c-d797-479f-9373-5015dd3caf97 2025-12-02 15:29:59,503 INFO [4] ServiceInitialize - Verification Complete 2025-12-02 15:30:05,529 INFO [4] ServiceInitialize - Threshold Window Enabled. Delaying For 54 Seconds. 2025-12-02 15:30:59,539 INFO [4] ServiceProvision - Verifying Client Provision Status 2025-12-02 15:30:59,546 INFO [4] ServiceProvision - Verification Complete 2025-12-02 15:30:59,905 INFO [4] ServiceAD - AD Computer Guid: 86285462-853a-40eb-82f7-744d51351569 2025-12-02 15:31:07,505 INFO [4] ServiceTriggerAction - Checking For Startup Policies 2025-12-02 15:31:08,052 INFO [4] PolicyExecutor - Executing Policy d7e057f5-736b-4dee-84b6-5d97a83dbdbe (cleanup) 2025-12-02 15:31:08,052 DEBUG [4] PolicyExecutor - Evaluating Conditions For cleanup 2025-12-02 15:31:08,052 DEBUG [4] PolicyExecutor - No Conditions Found For Module 2025-12-02 15:31:08,068 DEBUG [4] ApiRequest - ProvisionedComm/Policy/RemoveFromFirstRunGroup/ 2025-12-02 15:31:08,315 INFO [4] PolicyExecutor - Finished Executing Policy d7e057f5-736b-4dee-84b6-5d97a83dbdbe (cleanup) 2025-12-02 15:31:08,316 INFO [4] PolicyRunner - Policies Complete. Starting Policy Cleanup. 2025-12-02 15:31:08,320 INFO [4] PolicyRunner - Submitting Policy Results 2025-12-02 15:31:08,375 DEBUG [4] ApiRequest - ProvisionedComm/Policy/AddHistory/ 2025-12-02 15:31:08,663 INFO [4] PolicyRunner - Completed Submitting Policy Results 2025-12-02 15:31:08,663 INFO [4] PolicyRunner - Cleaning Policy Cache 2025-12-02 15:31:08,663 INFO [4] ServiceTriggerAction - Check In Time Set To 60 2025-12-02 15:31:08,663 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete. 2025-12-02 15:31:37,101 INFO [23] ServiceTriggerAction - Manual Checkin Request Received 2025-12-02 15:31:37,103 INFO [23] ServiceTriggerAction - Checking For Checkin Policies 2025-12-02 15:31:37,422 INFO [23] PolicyExecutor - Executing Policy b4cfd58a-aca2-4269-9950-abf7ff1b4fef (Domain join) 2025-12-02 15:31:37,422 DEBUG [23] PolicyExecutor - Evaluating Conditions For Domain join 2025-12-02 15:31:37,422 DEBUG [23] PolicyExecutor - No Conditions Found For Module 2025-12-02 15:31:37,438 DEBUG [23] ApiRequest - ProvisionedComm/Policy/GetDomainJoinCredentials/ 2025-12-02 15:31:37,592 ERROR [23] ApiRequest - Invalid Reponse, Signature Missing: ProvisionedComm/Policy/GetDomainJoinCredentials/ 2025-12-02 15:31:37,594 DEBUG [23] ServiceDomain - Could Not Obtain Credentials To Join The Domain. 2025-12-02 15:31:37,596 ERROR [23] PolicyRunner - Aborting Current Policy 2025-12-02 15:31:37,597 INFO [23] PolicyRunner - Policies Complete. Starting Policy Cleanup. 2025-12-02 15:31:37,598 INFO [23] PolicyRunner - Submitting Policy Results 2025-12-02 15:31:37,605 DEBUG [23] ApiRequest - ProvisionedComm/Policy/AddHistory/ 2025-12-02 15:31:37,822 INFO [23] PolicyRunner - Completed Submitting Policy Results 2025-12-02 15:31:37,822 INFO [23] PolicyRunner - Cleaning Policy Cache 2025-12-02 15:31:37,822 INFO [23] ServiceTriggerAction - Trigger Action: Checkin. Complete.

Inside the admin --> TOEC settings:

So it checks in, it ran the clean up policy, and then choked on the domain credentials. I've tried with DC=lab,DC=lan and tried with and without the lab/ for the user name. I have used the toems user to manually join the test computer to the domain and it works, but is there a different toems user that got created and I'm being stupid? I can certainly make another user account with enough privileges to join a computer to the domain if this is an issue.

At least this time it doesn't give me the can't connect 127.0.0.1:1415 error I was getting before.

theopenem_admin

Did you enable impersonation access?
https://youtu.be/ZmMzStsFnEI?t=1053

Greg_E

Nope, I didn't. I also see how the join domain script is different from trying to build it through the gui.

I'll have to try this tomorrow after I watch that video again. I may not have watched that one completely because I wasn't trying to make a universal image yet, but obviously I need to be more thorough because the answers are right there.

I also need to fix the TOEC domain info, I made a change and updated the client to see if I could cause it to try and log in, need to change it back to lab.lan

The Tray is still giving the can't connect to 127.0.0.1:1415 on the "master" computer before imaging, I must have something configured wrong and will have to get back to that. But if it only prevent the tray icon/app for doing things, but forms still can function, I'm not really sure I can that much. Rarely will I want to do things from the client side.

Greg_E

Sorry to be such a pain.

Small step forward, I now get a completed deployment with a very basic image. More like a half step.

But it does not join the domain after importing the script, then assigning the policy to the image first run group (and activating the policy).

The pages for the policy settings is significantly different from in the video, so I am having some confusion about where the "join domain" flag needs to get turned on, and where the domain and user/pass get set.

If I turn on the flag within this policy, and update the policy, then try to active it, I get the following error:

And here is what the client processed:

So small half a step, but I'm still not getting something. Going to go back to the video and see if I can find the mistake in my policy, or create the same from scratch. Or I may look into joining the domain through the unattend file, I just like the thought of this step happening within the management tool.

All of the above is done with a system that follows:

TOEMS single server, a VM running in XCP-ng 8.3 LTS, Server 2022 eval fully patched, member server in the domain

Clients are HP Prodesk 600 gen6, i5 10500 and built in Intel NIC (fully supported in Windows)
Trying to use Windows 11 25h2 eval fully patched

AD server is another Server 2022 eval fully patched running AD DS, DNS, DHCP on a small physical computer

I exported the policy, but it won't let me attach it. Ugly but let me copy/pasta:

{"Name":"domain join test","Description":"The test domain join that I'm using","Instructions":"","Requirements":"","Guid":"9aff4a1a-26d0-4568-b897-25108e600b8d","Hash":null,"Frequency":1,"Trigger":0,"SubFrequency":0,"CompletedAction":1,"RemoveInstallCache":false,"ExecutionType":0,"ErrorAction":1,"IsInventory":0,"IsLoginTracker":false,"IsApplicationMonitor":false,"IsWingetUpdate":false,"WingetUseMaxConnections":false,"FrequencyMissedAction":0,"LogLevel":0,"SkipServerResult":false,"CommandModules":[],"FileCopyModules":[],"PrinterModules":[],"ScriptModules":[{"DisplayName":"Sysprep Setup Completed","Arguments":"","Order":0,"Timeout":0,"RedirectOutput":false,"RedirectError":false,"ScriptType":0,"SuccessCodes":"-1","AddToInventory":false,"IsCondition":true,"WorkingDirectory":"","ScriptContents":"if($(Test-Path -Path \"c:\\program files\\toec\\setupcompletecmd_complete\" -PathType Leaf)) { exit -1 }\r\n","Description":"Added Via Policy Template Join Domain On 12/4/2025 2:54:09 PM\r\n","Guid":"f79019c0-3b7f-46b1-8809-f29f548dff86","ConditionFailedAction":0,"ConditionNextOrder":0,"Condition":null}],"SoftwareModules":[],"WuModules":[],"WingetModules":[],"MessageModules":[],"WuType":0,"ConditionFailedAction":3,"Condition":{"DisplayName":"Sysprep Setup Completed","Arguments":"","Order":0,"Timeout":0,"RedirectOutput":false,"RedirectError":false,"ScriptType":0,"SuccessCodes":"-1","AddToInventory":false,"IsCondition":true,"WorkingDirectory":"","ScriptContents":"if($(Test-Path -Path \"c:\\program files\\toec\\setupcompletecmd_complete\" -PathType Leaf)) { exit -1 }\r\n","Description":"Added Via Policy Template Join Domain On 12/4/2025 2:54:09 PM\r\n","Guid":"f79019c0-3b7f-46b1-8809-f29f548dff86","ConditionFailedAction":0,"ConditionNextOrder":0,"Condition":null}}

Greg_E

OK, I think I found the error:

admin settings --> TOEC --> I didn't have the user as lab\toems

I won't be able to check until Monday.

This does bring up a question, will I need to export a new TOEC client for this to work? If so I may need to start from the beginning with the client again, which is OK for what I'm doing.

Assuming this works now, I'll have to move on to injecting the drivers and installing those. And then uploading and installing a whole bunch of applications, including the Adobe Creative Cloud package I mentioned in another thread. I did export the drivers and zip them up, so that part is ready for upload once I get that far.

And again, sorry to be such a pain, I think I'm finally getting some of this, it's just a lot of settings to keep track of for an application I've never used before. the way my production system is run, I'm not part of the bigger college system, so don't have access to Config Manager or Intune or AutoPilot, all of which are pretty complex

Greg_E

OK, the changes I made Friday night are working, it's coming up joined to the domain. Now I need to go back through the video and watch then perform the same steps you did to inject the drivers and I'll be moving along.

Need to gather a list of applications and test their silent installs (most will be exe) and get moving. Or I need to bake them into the image like I have been doing for the past 10+ years. Probably going to punt on some of the applications, because I know it works, just makes bigger and more specific images, but I only have about 4 different configurations to worry about.

Greg_E

Well, trying to add the drivers causes an error right after they are unzipped, and then the join domain policy aborts. I'm not finding any obvious errors in the logs.

I think I'm just going to persist them in the registry and move on to trying to install some applications.