Options
Questions from a new guy
Service_Desk2
Member IT Monkey ✭
Hi,
We have some questions regarding settings for the portal.
1: We use SCOM and from SCOM Alerts we create Incidents that are sent to SCSM. If i´m to create an alert i put my username as owner in SCOM and then i change the resolution state so the magic happens.
The thing is that even if i from SCOM assign the incident to a different group all incidents i create this way is shown in "Team Work" since i'm the "Primary Owner".
Is there anyway to make that "Primary Owner" doesn't affect "My Work" and "Team Work"?
2: We have a hard time to figure out how put everything assigned to my group in "Team Work" view.
Now all incidents assigned to my group is shown there. And if i assign a CR# or a SR# to me, those will show up there. But if someone just assigns a Service Request to my group, it will not show up in "Team Work".
3: New Page, Assigned AD Group.
I have created two custom pages and assigned different AD groups to them, the problem is that they see both pages.
For analysts we are using a AD group called "SCSM_Analysts". This group have "SCSM_Helpdesk" and "SCSM_NET" as members. Different users are members of the helpdesk and net group.
The page for Helpdesk i have assigned to SCSM_Helpdesk and the page for NET i have assigned to SCSM_Net.
But still users in the net group see the Helpdesk page and users in the helpdesk group see the NET page.
Why is it so?
4: Even though we are very few users in the portal (still testing and setting things up) we feel that the portal can be very slow and unresponsive from time to time.
Is there any IIS settings or app settings that are best practice to change?
5: We also get this alert:
A process serving application pool 'CiresonPortal' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3632'. The data field contains the error number.
Anyone knows anything about this?
All this is things we feel we need to solve before we can use the portal in production.
We have some questions regarding settings for the portal.
1: We use SCOM and from SCOM Alerts we create Incidents that are sent to SCSM. If i´m to create an alert i put my username as owner in SCOM and then i change the resolution state so the magic happens.
The thing is that even if i from SCOM assign the incident to a different group all incidents i create this way is shown in "Team Work" since i'm the "Primary Owner".
Is there anyway to make that "Primary Owner" doesn't affect "My Work" and "Team Work"?
2: We have a hard time to figure out how put everything assigned to my group in "Team Work" view.
Now all incidents assigned to my group is shown there. And if i assign a CR# or a SR# to me, those will show up there. But if someone just assigns a Service Request to my group, it will not show up in "Team Work".
3: New Page, Assigned AD Group.
I have created two custom pages and assigned different AD groups to them, the problem is that they see both pages.
For analysts we are using a AD group called "SCSM_Analysts". This group have "SCSM_Helpdesk" and "SCSM_NET" as members. Different users are members of the helpdesk and net group.
The page for Helpdesk i have assigned to SCSM_Helpdesk and the page for NET i have assigned to SCSM_Net.
But still users in the net group see the Helpdesk page and users in the helpdesk group see the NET page.
Why is it so?
4: Even though we are very few users in the portal (still testing and setting things up) we feel that the portal can be very slow and unresponsive from time to time.
Is there any IIS settings or app settings that are best practice to change?
5: We also get this alert:
A process serving application pool 'CiresonPortal' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3632'. The data field contains the error number.
Anyone knows anything about this?
All this is things we feel we need to solve before we can use the portal in production.
0
Best Answers
-
Options
Geoff_Ross
Cireson Consultant O.G.
Hi @Service_Desk2
We love questions from new guys, keep them coming. Some hopefully helpful answers.
1) I'm afraid the criteria for these views is set but you could maybe try applying a template that sets someone else (not a real person eg SCOM) as the Primary Owner on these Incidents to stop them showing up in your view.
2) I think this sounds like your groups are not mapped up properly. This is done in the SCSM Console, under Administration, Settings, Cireson Portal Group Mapping Settings. Remeber you have to map all the groups for each Work Item type, even if your Teams are identical across Work Item types as they are in fact different lists with different values.
3) It appears you have done everything correctly so I'm not sure why this is happening. We would need to look into this one further. Can you provide some screnshots etc.
4) The following article is worth checking out. https://support.cireson.com/KnowledgeBase/View/1173#/ Also, what version are you running as some very recent work as been done to improve loading times?
5) Where are you seeing that error? Do you have any errors in the WebConsole.log at the same time?
Geoff5 -
OptionsGeoff_Ross
Cireson Consultant O.G.
1. Good news.
2. Changes yes, Problems no. You need to add a custom Support Group property on CRs and then choose it in the bottom section of the Group Mapping Settings. Then upon reopening the Settings, you can map your groups. We have MPs you can import for this for CR and MA here: https://github.com/Cireson/Community_AddSupportGroupFieldToMA but Problem is not supported.
NB: you can ignore the java-script etc in there as thats all legacy, you just need to import the MP.
3. You are probably seeing them as you created them. Creator will always have permission. If you want to 'clean-up' your view, you can edit the SQL for those navigation nodes and set the creator to NULL.
4. You are running the latest version so see how you get on with those suggestions. If still slow, you may need to raise a ticket with us.
5. Still unsure what is causing that, again, you may need a support ticket so it can be investigated fully.
Geoff
5 -
OptionsGeoff_Ross
Cireson Consultant O.G.
Hey,
That is a very good question. That is not possible hence the follow feature request I created. Please go and up-vote and we might get this into the product soon.
https://community.cireson.com/discussion/1608/multi-edit-tasks-available-on-promoted-and-widget-grid-pages
Geoff5
This discussion has been closed.
Answers
We love questions from new guys, keep them coming. Some hopefully helpful answers.
1) I'm afraid the criteria for these views is set but you could maybe try applying a template that sets someone else (not a real person eg SCOM) as the Primary Owner on these Incidents to stop them showing up in your view.
2) I think this sounds like your groups are not mapped up properly. This is done in the SCSM Console, under Administration, Settings, Cireson Portal Group Mapping Settings. Remeber you have to map all the groups for each Work Item type, even if your Teams are identical across Work Item types as they are in fact different lists with different values.
3) It appears you have done everything correctly so I'm not sure why this is happening. We would need to look into this one further. Can you provide some screnshots etc.
4) The following article is worth checking out. https://support.cireson.com/KnowledgeBase/View/1173#/ Also, what version are you running as some very recent work as been done to improve loading times?
5) Where are you seeing that error? Do you have any errors in the WebConsole.log at the same time?
Geoff
1: After some discussion over here we disabled the "set primary owner" step in Orchestrator, so this is not an issue anymore.
2: I had totally missed to edit those settings for SR.
Is there any way to map Changes and Problems the same way?
3: False alarm. I created several screenshots and then when i wanted the users to take screenshot of their view they don't see each others dashboards anymore. maybe it was just during the setup this happened.
BUT, I do see every dashboard even though i'm not a member of those specific groups. But i'm admin, maybe that is why i see them?
4: Thank you, i will read this and see if we get any improvement.
5: This is an alert we get from SCOM and the IIS management pack.
I dont see any error in the WebConsole.log during this time. but we do only track errors in the log, i have changed that to include WARN now.
2. Changes yes, Problems no. You need to add a custom Support Group property on CRs and then choose it in the bottom section of the Group Mapping Settings. Then upon reopening the Settings, you can map your groups. We have MPs you can import for this for CR and MA here: https://github.com/Cireson/Community_AddSupportGroupFieldToMA but Problem is not supported.
NB: you can ignore the java-script etc in there as thats all legacy, you just need to import the MP.
3. You are probably seeing them as you created them. Creator will always have permission. If you want to 'clean-up' your view, you can edit the SQL for those navigation nodes and set the creator to NULL.
4. You are running the latest version so see how you get on with those suggestions. If still slow, you may need to raise a ticket with us.
5. Still unsure what is causing that, again, you may need a support ticket so it can be investigated fully.
Geoff
1-2 is completed, thanks for the help.
4-5 i have done the changes and now we wait and see. If i get any more issues i will create a ticket.
3: my colleague who is admin too also see these new pages even though he did not create them nor belongs to the specified AD group. So maybe it is because we are admins.
I have another question.
When i create a custom page with an SQL query for specific work items i loose the functionality like Edit and Tasks. Is there anyway to get this in this scenario?
That is a very good question. That is not possible hence the follow feature request I created. Please go and up-vote and we might get this into the product soon.
https://community.cireson.com/discussion/1608/multi-edit-tasks-available-on-promoted-and-widget-grid-pages
Geoff
This could open up a lot of exciting use cases if it received enough votes!
The sync seem to be really slow.
2 days ago i added a new user to a scsm role and to the cireson analysts group. late yesterday afternoon she got access to the portal. that took nearly 24 hours.
yesterday afternoon we found that she had only read rights, so she could not edit any work items. so i added her to another group.
Now this morning she still couldn't edit work items. and that is like 18h after i added her to the group and ran the AD connectors.
so i did this:
First stop the Cache Builder service and then run the following commands against the ServiceManagement DB:
- TRUNCATE TABLE CI$User
- TRUNCATE TABLE CI$DomainGroup
- TRUNCATE TABLE LastModified
- Restart the IIS app pool
- Restart the website
What i found out now is that all new pages i have created and assigned to a specific AD group have been overwritten. before it was only one AD group per page. now after the sync 2 pages have 4 ad groups assigned to them and 1 page have 8 groups assigned to it...all of the groups is a member of our Cireson_Analysts group.
so, really slow sync and settings being overwritten. what is happening?
Because these are new issues, i've opened a new thread for you and will help you there. This makes things easier to find for other users.
https://community.cireson.com/discussion/4616/sync-issues