Computing space requirementsĪction ended 22:41:42: CostFinalize.
Return value 1.Īction 22:41:42: CostFinalize. Computing space requirementsĪction ended 22:41:42: FileCost. Return value 1.Īction 22:41:42: FileCost. Computing space requirementsĪction ended 22:41:42: CostInitialize. Return value 1.Īction 22:41:42: CostInitialize. Return value 1.Īction start 22:41:42: ValidateProductID.Īction ended 22:41:42: ValidateProductID. Evaluating launch conditionsĪction ended 22:41:42: LaunchConditions. Return value 1.Īction 22:41:42: LaunchConditions. Searching for installed applicationsĪppSearch: Property: UNBOMGAR_LOCATION, Signature: UnbomgarSearchHKLMĪppSearch: Property: UNBOMGAR_LOCATION, Signature: UnbomgarSearchHKCUĪppSearch: Property: UNBOMGAR_LOCATION, Signature: UnbomgarSearchHKLM64ĪppSearch: Property: UNBOMGAR_LOCATION, Signature: UnbomgarSearchHKCU64Īction ended 22:41:42: AppSearch.
#Bomgar jump client ports install
I've been running a simple command to to test install first.Īction 22:41:42: AppSearch. I then started logging it, it shows to either install or reconfigure in the log file each time it runs. It runs appears to install, but the client never shows up on the machine or the bomgar console. I could not find anything in any of the Bomgar Documentation.Īfter that occurrence i went for using an MSI, i have made several attempts at this point to get it to install through MSIEXEC. I cannot use an EXE to script in if it disappears after one use, I'm not sure if this in normal behavior or not. I then uninstalled from the console as I have it set to not be able to be removed by the end user. The age of installer was set to expire after a year. I created an EXE the first time around, it ran and installed. I'm hoping someone can shed some more insight on the situation. However, my bench testing on my workstation is yielding odd results.
#Bomgar jump client ports upgrade
I have no idea why the 2006 upgrade broke that Requirement on the Deployment Type, but hopefully that helps someone else that runs into this issue.Well i've been tinkering with doing a mass deployment of jump clients on our network. Once I did that, my issue was resolved and I was able to run the Task Sequence again without it failing on that Application install. I deleted this and recreated it without changing anything, Applied my changes, and Updated the Content on the Deployment Type (just for good measure). Noting that it was complaining about a setting on the application, I went into the Office application and saw that there was a Requirement related to Office 365 Intune Management. However, I did see the following error:ĭTS job _2.zip with error 0x80190194 This environment isn't configured for HTTPS communication and I wasn't receiving the error noted in the article Jason provided. Verifying that 2006 shows as installed and the upgrade completed successfully in the CMUpdate.logīased on the note above from Jason I checked the DataTransferService.log file. Verifying that both the pilot and production version of the ConfigMgr client have been promoted and are currently running version. Unchecking "Allow this application to be installed from the Install Application task sequence action without being deployed", clicking Apply, re-checking the option, clicking Apply, and retesting My logs look identical to those posted above, with error the same "Policy Evaluation failed, hr=0x87d00267" error.
The Task Sequence in question was working and successfully tested yesterday just prior to the upgrade to 2006. This started occurring yesterday immediately following an upgrade to 2006. I was experiencing the same behavior described above by ConfigConfuse-9352, but was able to resolve it.
0 kommentar(er)
