@theopenem_admin Hey, just following up. Is there a fix for this?
Posts made by cracking.skulls
-
RE: Deleted image not replicated to COM servers
-
RE: Deleted image not replicated to COM servers
@theopenem_admin OK. Great, thank you!
-
RE: Deleted image not replicated to COM servers
@theopenem_admin Yes. I've updated the images in the prior weeks and working consistently well in terms of replicating. The image deletion was performed over a month ago. I just noticed it after reviewing storage space on the dashboard and remoted in to confirm the deleted image is still there.
-
Deleted image not replicated to COM servers
Hello. When deleting an image, Action -> Delete Selected Images, didn't replicate to the COM servers. Is there a setting that I'm missing? Thank you.
-
Passing variables in script modules
Hello. Attempting to use the %username% variable in a script module with no success.
cd\ xcopy C:\ApplyThese\start2.bin "C:\Users\%username%\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\LocalState" /D /C /Y
However, it works fine if I specify the exact path. Is there a workaround or setting I'm missing? Thanks.
cd\ xcopy C:\ApplyThese\start2.bin "C:\Users\administrator\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\LocalState" /D /C /Y
-
RE: Script Module Issue
@theopenem_admin Thought you might find this of interest. There is a tool called PsExec that can remotely call up gui applications via command line. Can be downloaded from https://learn.microsoft.com/en-us/sysinternals/downloads/psexec. Below are some examples:
psexec \\computername -u domain\username -p password -i 1 -d notepad psexec \\computername -u username -p password -i 1 -d C:\Windows\System32\DisplaySwitch.exe 2
Perhaps this can be integrated into TOEMS?
-
RE: Script Module Issue
@cracking-skulls The batch file is created in the AppData directory. Double clicking the batch runs fine.
-
RE: Script Module Issue
@cracking-skulls The log file doesn't show any errors.
2023-02-09 13:43:29,407 INFO [39] PolicyExecutor - Executing Policy c2eed9b0-43fb-413c-be49-76ae18bc54c3 (Instant Module )
2023-02-09 13:43:29,407 DEBUG [39] PolicyExecutor - Evaluating Conditions For Instant Module
2023-02-09 13:43:29,407 DEBUG [39] PolicyExecutor - No Conditions Found For Module
2023-02-09 13:43:29,407 DEBUG [39] PolicyExecutor - Evaluating Conditions For SB-CloneDisplay-Resolution-1024x768
2023-02-09 13:43:29,407 DEBUG [39] PolicyExecutor - No Conditions Found For Module
2023-02-09 13:43:29,407 INFO [39] ModuleScriptManager - Running Script Module: SB-CloneDisplay-Resolution-1024x768
2023-02-09 13:43:29,407 DEBUG [39] ServiceImpersonationTask - Starting Impersonation Task
2023-02-09 13:43:29,423 DEBUG [39] ApiRequest - ProvisionedComm/Policy/GetImpersonationAccount/
2023-02-09 13:43:29,595 DEBUG [39] ServiceProcess - Starting Command: cmd.exe /c "net localgroup "backup operators" domain\username /add"
2023-02-09 13:43:35,209 DEBUG [39] ServiceProcess - Starting Command: cmd.exe /c "net localgroup "backup operators" domain\username /delete"
2023-02-09 13:43:35,319 INFO [39] ModuleScriptManager - 0
2023-02-09 13:43:35,319 INFO [39] ModuleScriptManager - Script Module: SB-CloneDisplay-Resolution-1024x768 Finished
2023-02-09 13:43:35,319 INFO [39] PolicyExecutor - Finished Executing Policy c2eed9b0-43fb-413c-be49-76ae18bc54c3 (Instant Module )
2023-02-09 13:43:35,319 INFO [39] PolicyRunner - Policies Complete. Starting Policy Cleanup.
2023-02-09 13:43:35,319 INFO [39] PolicyRunner - Submitting Policy Results
2023-02-09 13:43:35,350 DEBUG [39] ApiRequest - ProvisionedComm/Policy/AddHistory/
2023-02-09 13:43:35,491 INFO [39] PolicyRunner - Completed Submitting Policy Results
2023-02-09 13:43:35,506 INFO [39] PolicyRunner - Cleaning Policy Cache
2023-02-09 13:43:35,506 DEBUG [39] ServiceFileSystem - Deleting Directory C:\Program Files\Toec\AppData\1fe4bf9f-815d-40ee-bc66-6546eb987e72 -
RE: Script Module Issue
@theopenem_admin If I leave a batch file on the C drive of the computer can I run it from a certain module type?
-
Script Module Issue
Hello. I created a batch script module attempting to change extended display to cloned display with command
displayswitch.exe 2
with no results. Running a batch on the device works fine though. Any ideas how to resolve? Thanks. -
RE: Join Domain Issue
@theopenem_admin I have a Windows 11 Education VM. I installed Toec and issued Toec.exe --prepareImage command in powershell. Placed unattend.xml sysprep file in C:\Windows\System32\Sysprep. I left it in audit mode. I know, it's sloppy, but I was just testing.
-
RE: Join Domain Issue
@theopenem_admin Didn't use either. If it's dependent on this then yes it's my issue. I will test again with it syspreped.
-
Join Domain Issue
Hello. After imaging completes, Toec fails to join domain. However, after fail, forcing a check in works.
2023-01-11 11:57:55,948 DEBUG [4] PolicyExecutor - Evaluating Conditions For Join Domain 2023-01-11 11:57:55,964 DEBUG [4] PolicyExecutor - No Conditions Found For Module 2023-01-11 11:57:55,995 DEBUG [4] ApiRequest - ProvisionedComm/Policy/GetDomainJoinCredentials/ 2023-01-11 11:57:56,145 ERROR [4] ApiRequest - Invalid Reponse, Signature Missing: ProvisionedComm/Policy/GetDomainJoinCredentials/ 2023-01-11 11:57:56,145 DEBUG [4] ServiceDomain - Could Not Obtain Credentials To Join The Domain. 2023-01-11 11:57:56,161 ERROR [4] PolicyRunner - Aborting All Remaining Policies 2023-01-11 11:57:56,161 INFO [4] PolicyRunner - Policies Complete. Starting Policy Cleanup. 2023-01-11 11:57:56,161 INFO [4] PolicyRunner - Submitting Policy Results 2023-01-11 11:57:56,192 DEBUG [4] ApiRequest - ProvisionedComm/Policy/AddHistory/ 2023-01-11 11:57:56,416 INFO [4] PolicyRunner - Completed Submitting Policy Results 2023-01-11 11:57:56,416 INFO [4] PolicyRunner - Cleaning Policy Cache 2023-01-11 11:57:56,431 INFO [4] ServiceTriggerAction - Check In Time Set To 60
After forced check in.
2023-01-11 11:57:56,431 INFO [4] ServiceTriggerAction - Trigger Action: Startup. Complete. 2023-01-11 12:05:32,935 INFO [30] ServiceTriggerAction - Manual Checkin Request Received 2023-01-11 12:05:32,935 INFO [30] ServiceTriggerAction - Checking For Checkin Policies 2023-01-11 12:05:33,278 INFO [30] PolicyExecutor - Executing Policy 9aff4a1a-26d0-4568-b897-25108e600b8d (Join Domain) 2023-01-11 12:05:33,278 DEBUG [30] PolicyExecutor - Evaluating Conditions For Join Domain 2023-01-11 12:05:33,278 DEBUG [30] PolicyExecutor - No Conditions Found For Module 2023-01-11 12:05:33,305 DEBUG [30] ApiRequest - ProvisionedComm/Policy/GetDomainJoinCredentials/ 2023-01-11 12:05:33,463 INFO [30] ServiceDomain - Joining Domain 2023-01-11 12:05:33,479 DEBUG [30] ServiceDomain - Username: 2023-01-11 12:05:33,479 DEBUG [30] ServiceDomain - OU: 2023-01-11 12:05:49,595 INFO [30] ServiceDomain - Successfully Joined Domain
-
RE: Duplicate records after reimaging
@theopenem_admin Oh, wasn't aware. That would work. Awesome. Thank you for your support. Again an amazing product!
-
RE: Duplicate records after reimaging
@theopenem_admin We have over 10000 computers so not a practical solution.
-
RE: Duplicate records after reimaging
@theopenem_admin Just an update: I manually renamed the PC and after a restart I was able to perform a reset request in Theopenem. If this could be automated would be a really cool feature and speed things up. If you are interested and need some details we can set up some time so you can view the FOG interface remotely or make a VM yourself. Thank you for your consideration and thanks for making this amazing platform!
-
RE: Duplicate records after reimaging
@theopenem_admin Understood. Any chance future releases of TOEC could match existing records in Theopenem database and force a rename and domain join without the sysprep answer file? FOG had that feature by matching the MAC which facilitated the annual imaging process.
-
RE: Duplicate records after reimaging
@theopenem_admin Yes it is sysprepped but doesn't perform the rename task. The FOG client/server had that role.
-
RE: Duplicate records after reimaging
@theopenem_admin Hey. Thanks for getting back to me. Yes, I did collect the inventory. To give you a bit of history, the image I used was created with FOG. I migrated these to Theopenem. Because I'm in the migration/testing stage I didn't create a new image and preinstall TOEC. Instead after imaging completes I removed the FOG client and then manually installed TOEC. This process generates a new instance with a new installation ID but I was hoping it would identify via MAC then rename, join domain and implement policies after it consolidated duplicate records.
-
Duplicate records after reimaging
Hello. I have a question concerning the image/re-image process, TOEC installation ID and AD integration. First i have LDAP configured correctly and working. The image process is flawless as well. My only concern is after the device is imaged/re-imaged and boots to the Windows desktop environment TOEC creates a new record and a new installation ID in the database. Collecting inventory with TOEC doesn't seem to prevent this. Can TOEC identify the computer via a unique identifier such as MAC address or some other means to prevent duplicate records? Note: PreProvision, New Computer Provision and PreProvision Approval are disabled.