Tag Archives: cmdb

How are User Locations, Departments, Inventory, and Services populated in ServiceDesk?

Reposted from here.

Question

When making a ServiceDesk advanced incident, there are fields for the User’s Location, Department, Inventory, and Services. These may be empty or are not populated correctly. You want to know how to populate these fields in order to use them.

Answer

ServiceDesk does not manage data for the User’s Location, Department, Inventory, or Services fields*. These fields come from the CMDB Solution product in the Symantec Management Console and must be populated there first to be later used in ServiceDesk. Then, when a primary contact is selected for an advanced ticket in ServiceDesk, these fields are automatically populated with their CMDB data. Also, ServiceDesk does not sync this data from CMDB into ServiceDesk’s database, but copies CMDB data to tickets when a user is selected.

* The Location field is also an actual field in ServiceDesk for its users. This is not imported from Active Directory in the ServiceDesk AD sync as there is no out of the box Location field in AD. If this field is manually populated, and no Location field has been assigned to the user in CMDB, this field can then be entered automatically when selecting a primary contact in an advanced ticket. However, it is recommended that the Location be populated in CMDB for the users instead of doing this in ServiceDesk.

CMDB can populate data into its fields by one of the following:

1.The Symantec Management Platform’s Active Directory (AD) sync. This is found at Settings > All Settings > Notification Server > Microsoft Active Directory Import.
2.A Data Connector Solution product Import Rule. This is found at Settings > All Settings > Notification Server > Connector > Import/Explort Rules. A Data Connector rule can connect to an external non-Symantec database or use files, such as an Excel .xls file, to import data into CMDB.
3.Data imported in from Altiris Basic and Inventory Solution Agents.
4.Manual entry into CMDB. (The areas for manual CMDB entry are described below.)
Locations and Departments

Locations and Departments can be accessed by ServiceDesk by adding data to CMDB’s Location and Department areas.

1.In the Symantec Management Console, go to Home > Service and Asset Management > Manage Configuration Items.
2.Click on Organizational Types > Location, or > Department.
Inventory (i.e., resources, assets, computers, monitors, etc.)

Inventory can be accessed by ServiceDesk by adding an associated user to a resource in CMDB.

1.In the Symantec Management Console, go to Home > Service and Asset Management > Manage Configuration Items.
2.Click on Computers and Peripherals > Computer.
3.Select a computer and right click and choose Edit.
4.Add a user to the Asset Owners field.
5.Click on the Save changes button.
6.Click on the Done button.
Services

Services can be accessed by ServiceDesk by adding data to CMDB’s Service area.

1.In the Symantec Management Console, go to Home > Service and Asset Management > Manage Configuration Items.
2.Click on Datacenter Types > Service.
Related Field: Office Name

ServiceDesk users have a field called Office Name. This can be populated by ServiceDesk’s AD sync, or manually. However, this field is not available on an advanced ticket.

Troubleshooting

•If recent changes to CMDB fields are not appearing in ServiceDesk, reset server extensions and then reset IIS on the ServiceDesk server. Otherwise, after IIS next refreshes automatically, these fields will be updated with their current data. For example, if a Location is removed, it may still appear in ServiceDesk until the next IIS refresh occurs. Also, if IIS has been modified to increase the amount of time that it peforms an automatic check, it may be necessary to perform this procedure to force the CMDB fields to be seen by ServiceDesk, even if the values have been present in CMDB for some time. Likewise, if there is an issue with IIS updating correctly, or, its cache timeout has been extended, this may impact CMDB data being able to be seen by ServiceDesk. Verify that the default cache timers are set correctly, which can be found by reviewing the following article:

How to increase the page cache times for ServiceDesk and Workflow
http://www.symantec.com/business/support/index?page=content&id=HOWTO9818
 
•Verify that the user that is picked for the primary contact is the same user that has populated data in CMDB. Compare the NT ID (domain\username) and email address in both locations to establish if a different user was selected by accident in ServiceDesk.
•If no CMDB data is being found, verify that “Use CMDB7” was selected during the ServiceDesk install and that IsUsingAMS is enabled. If not, this will result in CMDB data not being used in ServiceDesk.

 
1.In ServiceDesk, go to Admin > Data > Application Properties.
2.Click on the action button and then click on Display Definition Values, for the ServiceDeskSettings entry. Note: If no ServiceDesk settings are present, this indicates a failed installation. Try performing an Upgrade install to reinstall ServiceDesk. If this fails, a new install will likely be needed. For more information on how to perform a new install, refer to the following article:

How to Install and run ServiceDesk 7.0 MR2 with a domain account instead of
local system account
http://www.symantec.com/business/support/index?page=content&id=HOWTO31346
 
3.Click on the action button and then on Edit Values.
4.Verify that IsUsingAMS is enabled. This is located under the Services category. If it is not enabled, click to enable it.
5.If changes were made, click on the Save button.
•Run the ServiceDeskDataServices.asmx file directly on the ServiceDesk server to find what CMDB data is able to be accessed.
1.Open a web browser on the ServiceDesk server.
2.Enter the following URL:

http://localhost/SD.DataServices/ServiceDeskDataServices.asmx
 
3.Select the data type to test. For example, click on SearchLocations.
4.Click on the Invoke button.
5.A new page will open with HTML code. In this, the data, for example Locations, should appear. If not, then CMDB data is not able to be accessed by the ServiceDesk server.
 
•Verify that the Notification Server that is being used by ServiceDesk for licensing is where the CMDB data is stored at.
1.In Windows, click on the Start button > Altiris > Workflow Designer > Workflow Designer.
2.Click on the Plugins menu > Notifcation Servers Credentials.
3.Verify that the NS Server Name value is the Notification Server where CMDB data is stored at. If not, either the data must be added at the other Notification Server listed, or, the ServiceDesk license must be transferred to the Notification Server that does have the data.
4.Remove and add in the correct server that has CMDB data and the ServiceDesk license as necessary.
5.If the listed server does have the CMDB data, however, remove the entry anyway, and then re-add it.
6.Close the window after making any changes. Note: It may take a minute or two for the window to close. This is normal.
7.Right click on the Task Tray Application and then click on Restart Server Extensions.
8.In Windows, click on the Start button > Run.
9.Type iisreset and then click on the OK button.
 
•Customizations to the SD.DataServices project may also result in issues even if these were working successfully earlier. If the SD.DataServices project has been customized, temporarily revert back to the out of box version to verify if the customizations are the issue. The following article describes how to backup and restore projects:

Optimizing SQL

Creating a maintenance plan in SQL Server 2005 or 2008 to optimize database performance

Article: HOWTO8589

Question
How can I create a maintenance plan in SQL Server 2005 or 2008 to optimize database performance?
Answer
A SQL maintenance plan for rebuilding indexes and setting the index free space percentage to 10% within the Symantec/Altiris databases should be scheduled to run at least monthly (preferably weekly). This maintenance plan should also be configured to update column statistics (index statistics are updated during the index rebuild process). It is recommended that this plan be scheduled to run at a time when database utilization by the Symantec applications is at its lowest. This could be on a Sunday during the day or a during a scheduled maintenance cycle, etc.

To build the SQL Maintenance plan for SQL 2005/2008:

  1. Make sure that the SQL Server Agent service is running.
  2. Open SQL Server Management Studio.
  3. Expand the Management folder.
  4. Right-click on Maintenance Plans and select Maintenance Plan Wizard.
  5. When the SQL Server Maintenance Plan Wizard info page opens up; click Next.
  6. Give the maintenance plan a name such as “Rebuild Indexes for Altiris Databases”.
  7. Leave the default option set to Single schedule for the entire plan… Click the Change button to put in the schedule for this plan.
  8. Enter in the chosen weekly time.
  9. Click OK.
  10. Click Next.
  11. Check the options to Rebuild Indexes and Update Statistics.
  12. Click Next.
  13. Make sure that “Rebuild Index” task is at the top.
  14. Click Next.
  15. Click the Database drop-down.
  16. In the These databases section, select all the databases you are trying to optimize, such as Altiris, Altiris_Incidents, eXpress, AeXRSdatabase, Symantec_CMDB and Symantec_CMDB_IntelAMT.
  17. Click OK.
  18. Select Change free space per page percentage to and set its value to 10% (20% if only rebuilding indexes monthly).
    • “Sort results in tempdb” should generally not be used; however, if SQL memory resources are low, then this will help, but it does cause rebuilding to take a lot longer.
    • Make sure that Keep index online while reindexing is unchecked.  Altiris databases uses ntext fields which prevent clustered indexes from being rebuilt while online for those tables that have an ntext column.
  19. Click Next.
  20. Chose the same databases as before.
  21. In the Update section, select Column Statistics Only.
  22. In the Scan Type section, select Full scan Click Next.
  23. Check the option to Write a report to a text file and allow it to write to the default location.
  24. Click Next.
  25. Click Finish.

Once the wizard is finished with creation, you can click Close. To execute the maintenance plan, right-click it in the left hand Object Browser pane and click Execute.

Additional Performance Considerations:

  • Make certain that the database files are not physically fragmented. Periodically check the fragmentation level on the volume where the database files are hosted and defragment when needed.
  • See KB49632: Optimizing SQL Server 2005 on Windows Server 2003 for more optimization information.


Article URL http://www.symantec.com/docs/HOWTO8589