- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Forum
- :
- Error when running Adoption Rules
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error when running Adoption Rules
Good day
We are receiving and error when running adoption:
Result of type 'TaskType_Adoption' on target '10.116.5.216':
<TaskStatus Result="Failed" StartDateTime="2020-04-09T05:00:39" Type="Adoption" Status="RemoteExecutionFailedReturnedNonZero" Duration="4.34">
<Step Result="Failed" Type="RPCCommand" Status="RPCExecutionOnRemoteHostReturnedNonZero" Duration="4.34" Credential="Windows NA Domain Account">
<CommandLine>\\beaconname\mgsRET$\Adoption\ndinstlr.exe -r "https://beaconname/ManageSoftDL/Packages/Flexera/Adoption/14.1.0/Rev1.0/Managed%20Device%20Adoption/Managed%20Device%20Adoption.osd" -o DeployServerURL="https://beaconname/ManageSoftDL" -o MsiInstallArgs="/L*v ManageSoft.msi.log DEPLOYSERVERURL=\"https://beaconname/ManageSoftDL\" ALLUSERS=1 REBOOT=ReallySuppress POLICYSOURCE=Server INSTALLMACHINEPOLICY=1 POLICYARGS=\"-o InstallDefaultSchedule=TRUE -o UserInteractionLevel=Quiet\"" -o INSTALLMACHINEPOLICY="1"</CommandLine>
<Parameter Index="0">1</Parameter>
</Step>
</TaskStatus>
All ports, accounts, rules, targets seem to be correct. Has anyone experienced these issues.
I have removed the beacon name for privacy.
regards
Manish
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
One good thing to verify is that the installation files really are located in that path. We had a strange error in our environment where the installation files was not replicated to the beacons, I did a manual fix by copying them from another beacon.
You can also review the log files on that beacon and also check on the test client.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Team,
I have also faced the same problem in my env. I am using latest onprem version.
I have verified packages in beacon & all are in place under adoption folder.
