AndyGilly Posted March 26, 2020 Share Posted March 26, 2020 Hi we are trying to get our first 'add user to AD group' automation happening I get an error on the IT Automation node. I am struggling to understand why, can anybody help?? thanks Andy Link to comment Share on other sites More sharing options...
Steve G Posted March 26, 2020 Share Posted March 26, 2020 Hi @AndyGilly, This would usually mean there are no managed assets in the list that you have selected against the node in the workflow: And the list: If you're adding users to a group using the node, you should only really select one target machine though, otherwise the job will be executed on each machine in the list. So the node should be configured as so: Cheers, Steve Link to comment Share on other sites More sharing options...
AndyGilly Posted March 26, 2020 Author Share Posted March 26, 2020 @Steve G thanks for coming back quickly. after reading the Wiki I can see I would need to discover and set as amanged the SIS server. My inventory is currently empty. How do I start the discovery process? Link to comment Share on other sites More sharing options...
Ricky Posted March 26, 2020 Share Posted March 26, 2020 Hi @AndyGilly A Discovery Job can be initiated from the Job Queue, however before this you will most likely need to create a Credential using Hornbill KeySafe of type Username + Password, within the Hornbill Administration Site. The username must have rights to access WMI on the discovered computers in order to pull the inventory. Information on creating a Credential here: (https://wiki.hornbill.com/index.php/Hornbill_KeySafe). From within the ITOM Job Queue, you will need to do the following: Select Create New > Discovery Job Set Discovery Mode to: "Active Directory" Set the Container to the domain that you wish to discover computers Set the Admin Credentials created in the Hornbill KeySafe Click Create The Job should start immediately and all output should be visible via the Monitor. (see: https://wiki.hornbill.com/index.php/Discover_Job) Once completed the Discovered devices will be visible in the ITOM Inventory within the Unmanaged list. Regards, Ricky Link to comment Share on other sites More sharing options...
AndyGilly Posted March 27, 2020 Author Share Posted March 27, 2020 @Ricky guidance much appreciated. I will get the team on this. thanks Andy Link to comment Share on other sites More sharing options...
AndyGilly Posted March 27, 2020 Author Share Posted March 27, 2020 @Ricky I have that all working now and the IT Automation node has complete in the BPM but the AD group has not been added. Are you able to point me at the logs that will tell me why?? thanks Andy Link to comment Share on other sites More sharing options...
Ricky Posted March 30, 2020 Share Posted March 30, 2020 Hi @AndyGilly In the Job Queue you should see an entry for the AD Job added to the list opening the Jobs properties should provide a monitor, Console and Debug Log. These will contain the outputs from the actual package that was used. There is also a log located on the SIS Server: %PROGRAMDATA%\Hornbill\Site Integration Server\log\EspSisService.log This log will show the execution of the package by the SIS. I will have a look at the process and see if there is any further information I can provide and get back to you. Regards, Ricky Link to comment Share on other sites More sharing options...
AndyGilly Posted March 30, 2020 Author Share Posted March 30, 2020 @Ricky thanks for the reply, when I access the job properties I get a blank page, am I in the correct place??? Link to comment Share on other sites More sharing options...
Ricky Posted March 30, 2020 Share Posted March 30, 2020 @AndyGilly Yes this is the correct location however it should not be blank, I will talk to the development guys and see what they come up with and get back to you. Link to comment Share on other sites More sharing options...
Steve G Posted March 30, 2020 Share Posted March 30, 2020 Hi @AndyGilly, Are there any error messages in your browser console when attempting to load that page? Thanks, Steve Link to comment Share on other sites More sharing options...
AndyGilly Posted March 30, 2020 Author Share Posted March 30, 2020 Hi @Steve G no errors in the browser whilst loading I am afraid Link to comment Share on other sites More sharing options...
AndyGilly Posted March 30, 2020 Author Share Posted March 30, 2020 @Ricky, @Steve G looks like it is an Edge issue, Chrome works fine Link to comment Share on other sites More sharing options...
Guest Bauti Posted March 30, 2020 Share Posted March 30, 2020 @AndyGilly I was just about to reply that, seems you are using old version of edge, while this is a Hornbill supported browser, old Edge does not support JavaScript ES6 so we are still working on I.E/Edge compatibility. I.E and Edge is and will be available for ITOM, but during this preview period, we are still working on some issue you may not find if using chrome/firefox/new edge. We already identified the issue with the Job Details page, and we are working to resolve it for the next Admin Tool release. Cheers, Bautista Link to comment Share on other sites More sharing options...
AndyGilly Posted March 30, 2020 Author Share Posted March 30, 2020 thanks @Anakin @Steve G @Ricky error found is below are you able to propose when access is failing is this the SIS server to AD?? Link to comment Share on other sites More sharing options...
Ricky Posted March 30, 2020 Share Posted March 30, 2020 @AndyGillythe issue looks to be related to the Admin Credentials that were supplied can you confirm if any were supplied and where your SIS has been installed? Link to comment Share on other sites More sharing options...
AndyGilly Posted March 31, 2020 Author Share Posted March 31, 2020 morning @Ricky the SIS server is installed on-prem & I have created a key safe credential that is being used for this action where the user has the same AD permissions as our service desk staff looks like the username was domain qualified , so will take that out and try again Link to comment Share on other sites More sharing options...
Ricky Posted March 31, 2020 Share Posted March 31, 2020 Morning @AndyGilly Looks like the issue is with the deployment of the package to the target machine. The credentials used do not have admin rights for the target. You will be able to see the details within the EspSisService.log which will be located at the following path: C:\ProgramData\Hornbill\Site Integration Server\log\ The following snippet shows the failure: 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4460] Processing job: 622, type=package 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Executing package job: 622 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Executer filename: \\?\C:\Program Files\Hornbill\Site Integration Server\exec\win\x86\EspSisExec.exe 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Package filename: \\?\C:\ProgramData\Hornbill\Site Integration Server\packages\6f1364b1c97e53c56bd704da91ab56693443d562.pkg 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Computer: W2K12R2-DC01 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Protocol: 2 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Package: Active Directory User Management 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Operation: Create 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Callback context: zEmgs7Gp31vYr23mB4kYjIXvYis_uEMG51ke4_KbXAx8MWKJORKBIh9faqQ8-6QZ9gAStYQpeveDemPQAVNc43aDJVxiZZsfzWR3xjTTIlsxBLxMfsmH4lcUKqIZgri8gpYAvH18106iU5pLA3R3e26PxlK1ZEE18mlo_EBV3as0nS67I-bYNKva_CFZvR8ZGIRIiZdui5T5sPpG6EV8wAye768_inxDW_4h7ZR7Hmz4IkujyXC1GsBMkkwwweWvKK6Z96djk-8MGuAH_AAxYoTCvBzigV3UHkiH0GqgsKFQY8EW0jwlgQFbS7MUApYSGOiGQ8tSLTUOOZ-sjtZWF870YMdG0_dKLXGYi13H2Vzk_T8dxA 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Timeout: 60 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Encoded parameters: okpfR9fnZEwMovC0_-G_42TYE2Mo5b75u0qQUTTgsa6mx5GSj7HFkit8--pAYT5phA0eaL4rLSF7-3SCmrveB88s8xKb5-G-lMfA5y2V-CdapUpkX4bwldOXzDn0SgOyzFAjd8DAHUU8rhKIWHn6DE22FPLgD_HOQPhwLo7myjPyUF_gNAuuO5HS5k19nTslErhplqAMptJ0U0rmqns3f71wLQRX1DVMKdyX0lpc2aMLGZBUhI80qmKhYgGjfC2f8c6JvDhqHR2c7oDEVBqduoXChDnB1dgxcqdfMMbL3G86WHeux3U0clcNdtn9Y9IeHet89jRi4eQRP7vaOjLeJ9JIQOrDzRg1WviYlCL6qnsu2Pw4SUpdtWgUR4JOQvfMymzVVv7MQerpGVPNznYsyV46_cno8KbKBbeHWOGbRrCWrG7ERV4PAUxvKjnuXDwvW3d1F3ilbRDoEfGfs5zUcuVRglSGImaTKO7dasBRN0DZHrBPGsM5jix9M-DxKXAoTQ0yqVwE4_6_f9FAMB7lRvpKFVLv3DbIM8dIy9o9o4unQ2LIrIJwVREdQ4QZEenuOOtltCNGbvV1PXbgocC4s3M8zsLmOBvkcGiZwIoETqFyHP7nJF0KznOzD0OA8iY4QrDB8Jgg3gfA6rxbtFOuJisFLryQjG42H3n2QMdv5-XTvMP-3hPjeOPGHD4jb4ejDLx8VsAS4cTetNdBQEuoy7qJD4EfkcW133DO4_4wYNKbCWb2QonOSCiYmM7l_Yu8YMskT8-iP7j5HPCEKGumOWZ-j35A6LWx_YeVhvZ52DvFrW1RYChQerZUltMDURuAz106uTbkgJSjc2eYyMxjtfJMFzPaO5nHnXM5VvugCjKCsJ6TGibgTw8AKbIYobq2R5blOS3eq55EkHDykoAeX1J4KLwy5noBCj4VljuuMpwM7ARjerE5x3Yr8LXduPjpovBZxwlb-gbqjI7pdZM-Bd5HTEPL38rZVGcPJkZMiOixN_-T0afWccCmGoXQztJMdkfLl_fnSqmjMRgAAgxUMsT6-iDQC9v5WSM5KwxezLYLN_8Vr8VB7vfxL3N-KTvFFZi_La38pfs2aieH0ey_YsA-IHvNxAJDg7dkSE-ZuB88IDbQCzio6mIUudl750LcmmsuodqvQQ--wT1fxinYWnxvAZgEgNZbMboLERv66fFxcWRqxLOI49aVLtVLWEZIc9smuOo1LwDFePdm3ts9ajPmUJ3ZzygQuWGqec-QO-OEYVNoxDSu2arrgXliIPcRpZMSAgoTZe3q1HslWA59C7aRe3GzeRJymtEE6_c4M-v0csNwYdlSGnTP20HHLjF5tVGYdnmY8JmgXDKTHloYN3NL5ykR9xYRibOx8oWS9DNL3GkngRcruG-N5o0nH1i4MLu4q8ll7qjurX_Jc7tHrCU-c44qKzOwWyxgd7zu0B4l3Acm8NV4Z_SmNfSmxLYc0AGd2zweKxjgBwPKBVwxQ6DG8IVnbB1VlPMyqbrL5per7TYJH6FjmBuSZ3EwAP2IP3AyEvsX8ZRCKvEIBXiubgFP3QCmAubDnlaEAid-4PiVMsNyCGmu8_P4OdcAT6NWwDwpan5V2TpKjuqNNSlEIQ6XfEM2rXsW1cqqXk6faraHJsZhjzTYtXrj6dmrvF6or8jsnoUYvnOqjTEef1e4t0mFU2vLsUaan7Bpcjz1Q-qTm0GKWIBhzPAFT4uq5mrAE4qyAraBmDBUk00ZdaS0sugaVCicd6Ug1xF8jz42oJsjtQDEbgjv0AyjANntf9O91zgt6tyAsz_5N3Jc3tqyzQcZ68MW-JTcqd-lQtany8yg7SWd0g0OXverfEriJ-zqlyF8DsJU0sKkjaZyQ5wgyxRlj0D5RGUi9qonWEI6VvlF0mWRhvzUhCwO23J1IXH8U9mafAG-ifvPtgAknJGxHAHfPuHZuBlFJEY5hcOlmrJuMefqVhr_pIe8dFsbxlk3Xa9KpbVhyo3QE0a86INrcAuBBLXgGdg7uwfmsEcrHaYcwtf1GdTRb8l25bcBXD8edXFBOnko4TswI2PC2dTV2a8YGsOk7Yxp3rVwvFWVRWJBHX4ceTgAJZXHQoEyfdMh4QbTHPvLCo8gl7oO6eS-RwNooA-YBTse61XZ2ur7GJNwVE71UWKFinvkUVBk5PWYecQLQjX7Weg-yTKcIFeewphWX1uN7x1ZJ2sfz91576xqDdaK72aCMhb2tl4LUQXBf7TJ-9LQvys6g2ef6juZghf_7XkFfg2xglijtLFKdUDWKZl0qKSl7TrasH9iiKyjHvIZo68SOYUPZj1vgbHeIO5mm1KPtLQjCxuJeJv65KKiEbL2OlyiE6N_LJq_br-AMFrnQ1z_T3j-PlaWN71w5MM7AWjtqRUYyPE2Col3Xa0gV-UzJNsjtSbTAwUdHGmzUeBwXhaS-B7halcimyFXzz8uhtrLBpKzM8uV3z-zW72OSDqtMKDR3RI--bYO7rzT5wovoZwnQMTXfNTtI2Fn_YrW499Ph7t2eFpjOPPCUk-EW9e0aE3rsPxSpVqO4U15nTPgLoxdTk81Y6dMo-Y9KvxCAq4Lbn6lFnN57Jn9ZTCMXQHEAQ7EVExV_gaX2Rczcw6asqpJFSdcn2LJtTrBXPIZh4Npacx0wISU-m466h1l2eWQpI4j4JHv4HkW-wOGGBrjjIePWg261_oczeRoaJZ7UqmPMTVWLNV6EATZedlNt3ryMSkIGB5jh0BX4XVg7kZJtDVCau5zDXtwgNSwKkh9BSi8w7-VN6w4QOO6sKVpeRTZW0qCYa8hJNGASXJKzBbCzSvx8_Jsve36JTZ2Rr7RwqN28CWeMcS95BTLqNai2t4Xvu7Gy8B8J9ikhxPrPqk_8kZ6f1sZq2zkb1iJ7BVojEyquI6Endb4HZRNmFjASjI5KVQZ_gFu0cuVK4SkM5SXfHZAcfuXjmVxP29papJ47eCYgIoJyzu3R-Ds99O4bjCMiOo2k7fcTKWBDHJqEbe_Q7GVpCt6Pb2Z4pZI4hjWyA1PBRQ7JQBZngWNuFCumxX_dxFI660F7dASLduAiHCpnjdWl2DA_8CiddRxgnd0i141xY_ebG6UFoUrBrqNNnYrRjpwqPormmS03RnLsdqhzAUWZye0RVdxEeQmfa33NtDZya-0MMxj8C3JEFg4__CuCLch6Bt551WzW75Q0lT63QNEFGIY7olUL5MAwVEPTVMkLR1uyDUiQfkn6Ep5wQe-ZTljAM-UR92QZHhijZutxgiVwtNQlwqO98BLHy2rFwIC30MPNxKl6xZOWjaKYcTMPatimGHZq8tChmWI5F1hf5VMC_a4hAquI6ZPZpFCcTadTJ6wjO5djeqIL1ikbXFHK98RcdLNQkq17JjPNP6z21lQcRuYIVXub3LYBOszs6oJ_QmAoVFXWTiRkGWgLiAIJ194lbu1gFudGcYnmcoAkh6G5wXxAdmEbOP6uUaYmot8gY9o1zwlw0hdDyzR9q7HU_x-O5MRizuZqW3ZreXu4ch1vUT1GT6L1M8ORTQOmVEqW7dr37Qm-iwL_9fLyjMC23YWf2qlRg 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Encoded credentials: RMFrQFMVdXvfl5MRvBNLUrH8QwNHF3CeioK1TGCfUO-TsWEwS2TMFuHY3OOAs3M7Mgq8vdFJC19IEKGpWoIEkcw2JDIsnFwU9TT61iUm-Ro 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Impersonating TEST\administrator against W2K12R2-DC01. 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] XML Result document: 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Result: Failure 2020-03-31 08:52:32Z [INFO]:[GENERAL]:[4744] Setting job 622 status to failed Link to comment Share on other sites More sharing options...
AndyGilly Posted March 31, 2020 Author Share Posted March 31, 2020 @Ricky thank you, really helpful. Next step over come, now get a new error. shall we walk through this on Thursday? Or if you think I can push this along before then? I have requested access to the server log at our end Link to comment Share on other sites More sharing options...
Ricky Posted March 31, 2020 Share Posted March 31, 2020 @AndyGilly looks like the job failed while processing the output, was there any output in the Debug Log tab? If not then we will have to wait for the server log to see exactly where the failure has taken place. I am happy to run through this on Thursday if we are not able to solve the issue after reviewing the log information. Link to comment Share on other sites More sharing options...
AndyGilly Posted April 3, 2020 Author Share Posted April 3, 2020 Afternoon @Ricky, just an update that we have been able to prove that that account can authenticate into AD Tools and add/remove members from groups. job 13 in ITOM shows the latest error Link to comment Share on other sites More sharing options...
Ricky Posted April 3, 2020 Share Posted April 3, 2020 Thanks for the reply @AndyGilly did you receive the Powershell script that I sent you via Daniel Riley? If so would it be possible to execute the script on the SIS server? If this script executes correctly then it would finally prove that the issue is with the deployment. Also could you send me a copy of the error message, if it differs from that which we experienced yesterday. Cheers Link to comment Share on other sites More sharing options...
AndyGilly Posted April 3, 2020 Author Share Posted April 3, 2020 HI @Ricky new error message is Link to comment Share on other sites More sharing options...
Ricky Posted April 3, 2020 Share Posted April 3, 2020 @AndyGilly that looks like the issue is with the server that’s hosting SIS, does not have the Remote Server Administration Tools (RSAT) installed. They can be installed from Server Manager, Add Roles and Features. Ricky Link to comment Share on other sites More sharing options...
AndyGilly Posted April 4, 2020 Author Share Posted April 4, 2020 thanks @Ricky, appreciated Link to comment Share on other sites More sharing options...
AndyGilly Posted April 6, 2020 Author Share Posted April 6, 2020 Hi @Ricky We have been able to run the supplied PS1 file as the account we are using, using the same parameter statement, and it works but still each time we run from Hornbill it fails with the inability to import the PowerShell module thanks Andy Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now