- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2020 10:14 AM
Hi Guys,
I am facing weird situation for JEA.
We have enabled JEA by applying same changes suggested on the KB article given by servicenow. We have configured two mid server properties as well. Enabled JEA_disco endpoint ( tried using JEA_DISCO / jea_disco for case sensitivity)
I see the logs in the powershell transcript file. File attached. ( This was optional step but we did it ) Here is a discovery log,
We can see the same Windows server discovered through other MID server ( not JEA enabled / but admin ). That ends up failing Windows Server pattern as below,
Am I using identifier attributes wrong here? However, I did not modify any OOB identifiers.
Appreciate your help.
Thanks
Abhijeet Yadav
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2020 09:21 AM
Dear community,
I am replying to my question as we figured it out.
We made sure / checked below things
1. MID server powershell version / target powershell version ( 5.0 in our case )
2. MID server properties : modified 2 properties.
2.1 mid.windows.management_protocol : WinRM
2.2 mid.powershell.jea.endpoint : <<as you configured>>
3.Fllowing the instructions on KB article from ServiceNow to add JEA files and modifying given lines in code. Especially JEA user group.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0782125
4. Adding target host as a trusted host
https://docs.servicenow.com/bundle/madrid-servicenow-platform/page/product/mid-server/task/enable-winRM-MID-servers.html
5. Please add the transcript folder even if its optional, its helps a lot in debugging.
6. Add below lines to Session config file,
# Modules that will be imported
LanguageMode = 'FullLanguage'
# Initial state of this session configuration
SessionType = 'Default'
https://hi.service-now.com/kb_view.do?sysparm_article=KB0854392
Thanks,
Abhijeet

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-29-2020 01:55 AM
Hi,
I Suggest raise a HI ticket because we here dont have more insights on what is happeing and if you raise a HI ticket then you can see with ServiceNow Support what went wrong.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2020 09:21 AM
Dear community,
I am replying to my question as we figured it out.
We made sure / checked below things
1. MID server powershell version / target powershell version ( 5.0 in our case )
2. MID server properties : modified 2 properties.
2.1 mid.windows.management_protocol : WinRM
2.2 mid.powershell.jea.endpoint : <<as you configured>>
3.Fllowing the instructions on KB article from ServiceNow to add JEA files and modifying given lines in code. Especially JEA user group.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0782125
4. Adding target host as a trusted host
https://docs.servicenow.com/bundle/madrid-servicenow-platform/page/product/mid-server/task/enable-winRM-MID-servers.html
5. Please add the transcript folder even if its optional, its helps a lot in debugging.
6. Add below lines to Session config file,
# Modules that will be imported
LanguageMode = 'FullLanguage'
# Initial state of this session configuration
SessionType = 'Default'
https://hi.service-now.com/kb_view.do?sysparm_article=KB0854392
Thanks,
Abhijeet