Jump to content


Search the Community

Showing results for tags 'CMDB'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hi, I'm new here and also to SCCM. My objective is to provide a clean standardized source of software product information that can be loaded into a Configuration Management Database (CMDB). More specifically I'm looking to collect, and automatically maintain the following information: For each licensed software item, i.e. a product / version / edition that may be purchased e.g. Microsoft Visio 2013 Standard, I need a Standardized Publisher Name, Standardized Product Name and Standardized Version. The latest revision - this might include a build / patch number and more specific version e.g. 32 vs 64 bit. I'm envisaging that the standardized product and version I'm referring to above might have several updates and minor revisions over its life. The devices where this application has run, including the last run date, and the username of the person using it. I intended to use the SQL views provided in SCCM to build a view or views containing the information required which will then be presented to the CMDB tool. The environment where I'm working has SCCM 2012 R2 SP1 running, with the client deployed to servers and workstations. Most applications at this site are installed through add/remove programs so appear in the hardware / asset intelligence views returned by SCCM. The following inventory classes are turned on: SMS_InstalledSoftware, SMS_SystemConsoleUsage, SMS_SystemConsoleUser, SMS_AutoStartSotware, Win32_USBDevice, SMS_InstalledExecutable. A number of applications use their own installers and are installed outside of the Program Files and (x86) folder structure, so these are not seen by the hardware inventory functionality as far as I'm aware. From the Technet I found the best information so far in the views: v_GS_INSTALLED_SOFTWARE_CATEGORIZED, v_LU_SoftwareList_Editable from the hardware inventory side, and on the software side from v_SoftwareProduct and v_GS_SoftwareProduct. The benefit of the two former views, is that SCCM is doing some name normalization and categorization. Anyone who has had a look at this problem will realize there are challenges in standardization of publisher, product and version information even at a high level. Furthermore, from a high or medium level perspective, there's also the challenge of aggregating the many minor variants / versions / patches of software back to their parent software packages that might be of interest in a CMDB as a "licensable product". The queries I have are: I am not sure that SCCM is configured exactly as it should be to return the data required? I have tried to match data between the hardware inventory side of the product and the software inventory side. There does not appear to be a common key and there does not appear to be sufficient standardization in publisher / product / version information to join the data. Am I missing something or is there any best practice here? In other forum posts I've read, there have been comments to the effect that software inventory is of little value. However if that is the case, how is it possible to include software products, that are installed outside of the Windows add / remove programs functionality? Assuming that SCCM is configured correctly to ensure the appropriate data is being collected, and that the Out Of The Box standardization and classification is working optimally, what additional manual configuration is required to ensure standardized publisher / product / version information is being collected / generated? I'm thinking of one smaller publisher, probably unknown to SCCM's classification database, where I've seen three or four variations in their name> Thanks very much in advance.
  2. Now that we have the Service Manager Management Server installed, we can move onto the Data Warehouse. Install PrerequisitesTo start, before we will actually be able to install Service Manager Management Server, we have to install a few prerequisites. § .NET Framework 3.5 SP1 § Microsoft SQL Server Analysis Management Objects § Microsoft SQL Server Native Client Install SCSM-WS (Warehouse Server)Start by either extracting the DVD contents, or mounting the ISO (the TechNet ISO is currently labelled as mu_system_center_2012_service_manager_with_sp1_x64_dvd_1348926). Start by opening your DVD drive, navigating to the corresponding architecture (i.e. x86 or amd64), and run the Setup.exe. On the splash screen click the Service Manager Data Warehouse Management Server install link. On the Product Registration screen, enter a Name, Organization, and Product Key. Also read the License Terms and check the ‘I agree’ checkbox, then click Next. On the Installation Location screen, you can either accept the default location, or change it according to your needs. Then click Next. The Prerequisite checker will run and indicate if there are any issues preventing the installation from continuing. If there are any identified issues, resolve the issue(s) until all checks are green and/or if there are only Warnings left. Then click Next. The next screen is to configure the Data Warehouse databases. You may encounter this Warning message. This is the same message from when we installed the Management Server for Service Manager. Click OK. This will return you to the Data Warehouse database screen. It may take some time but once it has connected to the instance successfully, click Next. When you click Next on the Data Warehouse database screen, you will be presented with the Data Warehouse Datamarts screen. This is where Service Manager collects the data from Operations Manager (OM), and Configuration Manager (CM). You will encounter this Warning message again, just click OK. This will return you to the Data Warehouse Datamarts screen. It may take some time but once it has connected to the instance successfully, click Next. On the Data Warehouse Management Group screen, provide a group name. Note that this should be different from other Management Groups (i.e. SCCM, SCOM). Also add a user or group as the Administrator. In a Production environment, it is best to use an Active Directory Security Group as it is easier to add/remove individuals. On the Reporting Server screen, you will have to wait for the validation to complete, then click Next. Next you need to either specify to use a Local Account, or specify a Domain Account for the Service Manager services. This can be the same domain account used for the services on the Management Server. You will not be able to click Next until the credentials are tested successfully. Once it is, then click Next. On the Reporting Account screen, provide an account and click the Test Credentials button. Then click Next. On the Analysis Services screen, we will accept the defaults in our lab example, and click Next. You next need to provide an Analysis Services service account. Provide the credentials and click the Test Credentials button. You will not be able to click Next until you do. Once tested, then click Next. On the CEIP screen, choose whether you will join the program, and then click Next. New to System Center 2012, you can choose to include the System Center product in Microsoft Updates. Make your applicable choice and then click Next. On the Summary screen, review the selections made, and then click Install. Once the installation is complete, ensure that the ‘Open the Encryption Backup or Restore Wizard’ checkbox is selected. Then click Close. Encryption Key BackupWhen the Encryption Key Backup wizard launches, read the Introduction information and then click Next. On the Backup or Restore screen, select ‘Backup the Encryption Key’ and click Next. On the Provide A Location screen, it is recommended to store the Encryption Key backup in a secure location (i.e. a file server that is regularly backed up). Enter an applicable UNC path, along with a filename, and then click Next. On the Provide A Password screen, provide a password for security purposes (and keep it in a secure location), and click Next. Once the backup is complete, click Finish. That completes the installation of Service Manager’s Warehouse Server. We now need to install the SharePoint / Self-Service Portal.
×
×
  • Create New...