Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
forticlient ems deployement doesn't work
Hi i'm trying to push the upgrade of forticlient on endpoints using forticlient ems and nothing happens on the endpoint
Labels:
- Labels:
-
FortiClient EMS
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem since I upgraded my installation to 7.2.
With EMS 7.0.x I was able to give some deployment credentials which were used for the deployment.
Now this option is gone and I really don't understand how the deployment should work without giving some administrative credentials.
So I'm also a bit lost here.
Additionally, when I'm looking into the deployment logfile I get this errors for every host which should be deployed.
Code: 0x80040E2F
Code meaning: IDispatch error #3119
Source: Microsoft OLE DB Driver for SQL Server
Description: Cannot insert the value NULL into column 'os_type', table 'FCM_Default.dbo.endpoint_deployment_schedule_states'; column does not allow nulls. INSERT fails.
460
[05-26 11:28:34][ ERROR]: Failed to add host=******* (device_id=171), policy_id=1, assignable_installer_id=7 into endpoint_deployment_schedule_states
[05-26 11:29:34][ ERROR]:
SET NOCOUNT ON
DECLARE @IdentityOutput TABLE(
[id] int
);
INSERT INTO dbo.endpoint_deployment_schedule_states (
endpoint_deployment_policy_id,
devices_id,
scheduled_upgrade_time,
upgrade_path,
sha256,
size_bytes,
deployment_method_id,
deployment_state
)
OUTPUT
INSERTED.id
INTO @IdentityOutput
VALUES (?, ?, ?, ?, ?, ?, ?, ?);
SELECT id FROM @IdentityOutput;
Code: 0x80040E2F
Code meaning: IDispatch error #3119
Source: Microsoft OLE DB Driver for SQL Server
Description: Cannot insert the value NULL into column 'os_type', table 'FCM_Default.dbo.endpoint_deployment_schedule_states'; column does not allow nulls. INSERT fails.
460
[05-26 11:29:34][ ERROR]: Failed to add host=******* (device_id=171), policy_id=1, assignable_installer_id=7 into endpoint_deployment_schedule_states
So I think thats an issue with 7.2.0 (so it is as everytime,... never install .0 releases)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem
