Wednesday, December 16, 2015

Dell Server Management Pack with Agent-Free and SNMP Monitoring

This post gives instructions on how to setup the Agent-Free Monitoring with WSman and SMASH discovery and then SNMP Monitoring through the iDracs.  Some of this document I have copied from another document, but heavily modified to make corrections and added a good bit of instruction so that it will be a more complete guide.

Deploying the Dell Server Management Pack
Follow this procedure to deploy the Dell Server Management Pack (MP) for SCOM.

1.1 Network prerequisites
All iDRAC IPs must be accessible from the Management Console and routable to the management network.  From the Management Console ping the IP of each iDRAC to ensure it is reachable.

1.2 Hardware Prerequisites
Validate on each iDRAC that its Alerts are set to Enabled and Alerts set to go to the OpsMgr server.

NOTE: If you have a lot of iDracs and want to programmatically set this on all at once, you can either use OpenManage Essentials, or I will post a script or link to one soon to do this.

1. Login to each iDrac and go to Alerts.  Set Alerts to Enabled and then click the Apply button in the same box.

2. Set Alerts and Remote System Log Configuration.  The SNMP Trap needs to be set on all 19 pages.  Select SNMP Trap box from the title bar which will check all boxes for SNMP traps on that page.  Then click the right arrow to advance to the next page and select the SNMP Trap box from the title bar again to mark all on that page.  Continue doing this on each page until all 19 pages are done and then click the Apply button. 

3. Next, click over to the SNMP and Email Settings page.  Under IP Destination List, add your OpsMgr server IP, and enable the State box.  The Community String will be used to create a Run As Account in OpsMgr in section 1.7 below.

1.3 Install Steps for Configuring the WS-Management and SMASH Device Template
Download the System Center Monitoring Pack for WS-Management and SMASH Device Discovery:

1. Launch the WS-ManagementAndSMASHDeviceDiscoveryTemplate.msi file.
2. Click Next.
The license agreement is displayed.
3. To continue the installation, accept the license terms after reading them, and click Next.
4. Click Change (if necessary) to change the default installation folder and click Next.
5. Click Install.
6. Log on to OpsMgr 2012 R2 as an administrator for the OpsMgr Management group, preferably by right clicking and selecting Run As Admin.
7. On the OpsMgr console, click Administration, and then click on Import Management Packs under Actions.

8. Add from Disk.  Select No for Online Catalog Collection.
9. Select Management Packs to Import.  Import the MPB file from the extracted location.
“C:\Program Files(x86)\System Center Management Packs\WSManagementAndDeviceDiscoveryTemplate\
10. Click Install.

11. Once completed Select Close
12. On the OpsMgr console, click Authoring.
13. Expand Management Pack Templates.
14. Once that is done you should see 'WS-Management and SMASH Device Discovery".

15. At the bottom of the left navigation pane, click Add Monitoring Wizard.
16. The Add Monitoring Wizard screen appears.
17. On the Select Monitoring Type screen, select WS-Management and SMASH Device Discovery and click Next.
19. On the General Properties screen, enter a friendly name and description.  In the Name field provide a name for the wizard.
20. Under Management Pack, click New.
21. The Create a Management Pack screen appears.  Provide a name for the management pack in the Name field, such as Dell OOB MP, and click Next.
For information on creating a management pack, see the OpsMgr documentation at
22. Click Create.
23. The management pack you created is selected in the Management pack drop-down box. Dell OOB MP

24. Click Next.
25. On the Specify the target drop-down menu, select a resource pool for monitoring out-of-band
Devices.  If you have created a resource pool with a limited set of management servers, use that.  Otherwise, use All Management Servers Resource Pool and click Next.
26. On the Specify the account to be used to run discovery screen, click New and create a Simple Authentication RunAs Account.  This Simple Authentication RunAs Account will be the credentials used to access the iDRAC.

27. For Display Name use iDRAC ACCOUNT
28. On the Credentials page, enter your iDrac credentials.  Click Next.

29. On the Distribution Security page, select Less Secure – I want the credentials to be distributed automatically to all managed computers.
30. Select Create then Select Close.
31. On the Credentials Screen, select the RunAs Account you created from the RunAs Account drop-down menu and click Next.

32. On the Devices page, specify the devices you want to monitor. Here you will add your iDRAC IPs. Click Add.
33. On the Add Devices screen specify the iDRAC IP address of the systems you want to monitor using the Server (out-of-band) monitoring feature.  You can specify the iDRAC IP address of the systems by:
• Scanning the IP Subnet that you provided.
• Scanning a specified IP Range.
• Importing a text file containing the list of iDRAC IP addresses.  If you list contains more than 100 IPs, please split it into multiple files with less than 100 in each test file.
34. Click Advanced Options, select the Skip CA Check and Skip CN Check option and click OK.

35. Click Scan for Devices to search for Dell PowerEdge 13G systems on your network. Depending on the number of devices it may take quite a while.
36. The IP addresses that were able to be communicated with are listed under Available Devices. Highlight the devices click Add to add the list of IP addresses you want to monitor and click OK.

38. Back on the Specify the devices you want to monitor screen click Next and then on the Summary screen click Create.
40. On the OpsMgr console, click Monitoring.
41. Expand → WS-Management and SMASH Monitoring → WS-Management Device State.
The Dell servers will appear here after the automatically triggered SMASH discovery is completed by the OpsMgr.  NOTE: This may take between 5 and 20 minutes.  NOTE: do not proceed past this section if SMASH Device State is not populated.
42. Continue if the SMASH Device State is populated

1.4 Install steps for Dell Server Management Pack Suite

***NOTE:  A newer version has been released and should be used instead of 6.1.1.***

Download the Dell Server Management Pack Suite for Microsoft System Center Operations Manager v6.1.1:

Open an administrative command prompt window and run Dell_Server_Management_Pack_Suite_v6.1.1_A00.exe
The following MPs are automatically imported after the installation of Dell Server Management Pack
• Agent-based monitoring feature.
• Agent-free monitoring feature.
• Dell Feature Management Pack. The Feature Management Dashboard is displayed under
Monitoring → Dell on the OpsMgr console. Refer to the individual monitoring sections in the User Guide for importing the monitoring features.

NOTE: It can take 15-30 minutes before the Feature Management State Dashboard is populated.

1.5 Set the Agent-Free Monitoring Level
1. Go to the navigation pane and select Monitoring. Select Dell Feature Management Dashboard.
2. Select Server and Rack Agent-Free Monitoring
3. From Task Pane, use either "Set to Agent-free Detailed Feature" or "Set to Agent-free Scalable Feature" depending on the unit monitors you want to be available.  See link in Note below.
4. Do not close the task window until it has finished.

NOTE: Keep in mind that many of the unit monitors are not enabled by default.

1.6 Install iDRAC Monitoring Feature
From the Dell Feature Management State Dashboard install the iDRAC Monitoring Feature.

1. Go to the navigation pane and select Monitoring. Select Dell Feature Management Dashboard.
2. Select DRAC Monitoring
3. From Task Pane select Import DRAC Monitoring Feature.
4. Do not close the task window until it has finished.

1.7 Discovering iDRAC Devices
The DRAC devices must be discovered as network devices under the Administration section of the
OpsMgr console.

Create a Community String Run As Account:
1. Log on to the management server as an OpsMgr administrator, preferably by right clicking and selecting Run as Admin.
2. On the OpsMgr console, click Administration.
3. Right click on Run As Configuration -> Accounts and select Create Run As Account.
4. Change the Run As account type to Community String, give it a name in Display name, and click Next.
5. On the Credentials page, type in the community string exactly as it was on the iDrac SNMP and Email Settings page.  This is essentially a password and is case sensitive.  Click Next.
6. Select Less secure on the Distribution Security page and click Create.

Associate the Community String account with the SNMP Monitoring Profile:
1. Click on Run As Configuration -> Profiles.
2. Find SNMP Monitoring Account, right click on it and select Properties.
3. On the General page click Next.
4. On the Add Run As account page, click Add.
5. In the Run As account drop down box, select the Community String account we just created.  Leave it targeted to All target objects.
6. Click Save and then Close.

To discover DRAC devices:
1. At the bottom of the navigation pane, click Discovery Wizard.
2. Run the Discovery Wizard, select Network devices and follow the instructions on the screen.
3. On the Default Accounts page, click the Create Account button.
4. The Create Run As Account Wizard will open with the type already selected on CommunityString.
5. In Display name field, enter a name for the account and click Next.
6. On the Provide account credentials page, in the Community string field, type in the same community string that was on the SNMP and Email Settings page in the iDrac from section 1.2 above and then click Create.
7. Back in the Specify the default Run As account for discovery page, select the Run As Accounts you want to use for your iDracs.
8. On the Specify devices page click Add or Import.  With Add, you will type in a single iDrac IP at a time and you can specify specific Run As Accounts if they are different on some iDracs.  Import will let you use a text file.  The Access Mode can stay on ICMP and SNMP.
9. On the Schedule the network discovery page, select Run the discovery rule manually.
10. Finish creating the discovery rule and select the box to Run the discovery after the wizard is closed.
11. Once the iDracs have been discovered they will show up under Monitoring → Dell → State Views →DRAC.

1.8 Monitoring
After you install the Dell Server Management Pack Suite, you can use the Monitoring pane of the
OpsMgr to select views that provide complete health information of the discovered Dell DRAC devices.
The DRAC monitoring feature discovers and monitors the health of the Dell DRAC devices. It includes monitoring health of Dell DRAC devices, both at regular intervals and on occurrence of events.

1.9 Validate Alerts and SNMP traps
Send a Test Alert from the iDRAC console.

The Alert will show up under Dell -> Alerts Views -> RemoteAccess Alerts

2.0 SNMP Monitoring Account Options
If you want to the SNMP Monitoring Account to be targeted more tightly, you can target specific classes instead of leaving it targeted to “all targeted objects”.  The specific classes you may want to use include:
Dell Modular Chassis
Dell CMC
Dell Server
Dell iDRAC
Dell Remote Access Controller Group

You may not need all of these.  I put them here because I have all of them mainly for the troubleshooting that I do to cover my bases.

Wednesday, October 21, 2015

Del DTK 5.2 released doesn't work with ADK10

What I ran into is that the Dell DTK 5.2 will not import into Configuration Manager with Dell Server Deployment Pack (DSDP) if you already have ADK10 installed.  DTK 5.2 is not compatible with ADK10.  So if you want to import DTK5.2, you will have to uninstall ADK10, reinstall ADK8.1, then install DTK5.2.  I suppose that after that you could try to reinstall ADK10, but your boot images created with DTK5.2 will not have the ADK10 components.

Wednesday, September 2, 2015

Dell Operations Manager MP Suite 6.1.1 Released

I'm a little behind on this but Dell released the Dell SCOM Mp Suite 6.1.1 in early August to add support for a couple of new servers and to resolve an issue with the 6.1 installer.

Here is the link for the wiki:

Here is the direct link for the 6.1.1 download page.

The 6.1 installer was an msi that had to be run from an elevated command prompt.  If you didn't run the 6.1 from an elevated cmd, you are most likely missing the Dell Device Helper COM+ Object.  A simple repair install from an elevated cmd will resolve that or you can download and upgrade to 6.1.1.

Friday, July 17, 2015

Dell OpsMgr MP Suite Unit Monitors

If you have installed the Dell SCOM MP Suite and are wondering why some of the columns may not be lighting up, this post may help.

Here is the link to the Dell Server Management Pack Suite v6.1 for System Center Operations Manager User's Guide because I will reference it several times in this post.'s%20Guide_en-us.pdf

First I will give you some page numbers to see charts for the different monitoring features so you can see and make decisions on what you want to monitor and view.

Comparison of Scalable and Detailed on page 10.
Discoveries by the Agent-based Monitoring Feature (Scalable & Detailed) starting on page 11.
Monitored hardware components (Scalable vs. Detailed) starting on page 12.
Unit Monitors (Scalable vs. Detailed) starting the bottom of page 19.

Comparison of Scalable and Detailed on page 33.
Discoveries by the Agent-free Monitoring Feature  page 35.
Monitored hardware components (Scalable vs. Detailed) starting on page 36.
Unit Monitors (Scalable vs. Detailed) starting the bottom of page 41.

Discoveries by the DRAC Monitoring Feature on page 50.
Unit Monitors starting the bottom of page 52.

Chassis Monitoring Feature:
Discoveries by the Dell Chassis Monitoring Feature on page 58.
Monitored hardware components (Scalable vs. Detailed) starting on page 58.
Unit Monitors starting the bottom of page 62.

***The rest of this post will focus on the Agent-free monitoring.***

Once you install the MP Suite and you have your Agent-free devices discovered, the next thing to do will be to right click on the column headers and click on Personalize View.  Then there will be several options here you can select to see more info about your servers in the main view.

Check the items you want.  Some may have the same information as others so you may have to play with it a little to see which ones you want and which you don't.  

Depending on whether you enabled the Scalable or Detailed discoveries on the Dell Feature Management Dashboard, some items may or may not be running discoveries already.  Those are described in the charts listed above.

But to see the unit monitors light up, you still have some work to do.  As you can see in the first picture above, the Dell Server Memory Group says Not Monitored.

There are 2 types of Unit Monitors to be aware of (Event and Periodic).
  • Event - triggered by the event that the Dell instrumentation logs in the Windows event log, indicating the health of the corresponding object.
  • Periodic - triggered by a periodic poll configured as Interval Seconds.
Next, go to Authoring, Management Pack Objects, Monitors.  Use the Look For search box and type in "Dell Server".

Find the Unit Monitors that you chose from the charts listed above, that you want to enable.  For example, we will look at the Dell Server Memory Group.  Find the Dell Server Memory Group\Entity Health\Availability\Dell Server Memory Group.  Right click on it and select Overrides\Override the Monitor\For all object of class: Dell Server Memory Group.

On the Override Properties screen, you have several items you can change.  To enable the item, you need to check the Enabled line and change it to True.  And check the Generates Alert option and change it to True if you want alerts from this component.  Other items I suggest you look at include:

Alert on State - do you want an alert only in critical state or in both warning and critical states.
Alert Priority - depending on the component you may want to increase the priority of the alert.
Alert Severity - again, depending on the component and how important it is you might want to change this too.
Auto-Resolve Alert - do you want the alert to auto-resolve when it sees the condition change back to healthy or do you want to have to acknowledge the alert and close it in OpsMgr.
Interval Seconds - depending on the component and its importnace, I wouldn't change this one too much.  The lower the time, the more polling the OpsMgr server will do of that component, which increases load and traffic.
Log Level - is more for troubleshooting.  If necessary, change this from 0 to 1 and you should get a log at the interval seconds time, in a sub-folder at C:\Windows\Temp.

Once you have your options set, save this to a management pack, but don't use the default management pack.

Give it some time and possibly hit refresh and then your monitors will light up.  Do this for all of the unit monitors that you want to get alerts for.

Monday, June 15, 2015

Dell ToolKit 5.1 with DSDP Set RAID envout issue

If you are using the Dell Server Deployment Pack with the Dell ToolKit (DTK) 5.1, you may see an error when trying to use the Set RAID function in an OSD task sequence.

Look in the SMSTS.log and find the section where raidcfg.exe is being called.  Near the end you may see errors saying "File is not writeable!" or "Could not find the raid output file you specified (envout.txt). Please check the path."

This turned out to be a permissions problem in DTK and possibly back in DTK 4.4 also.  This issue has been resolved and a new version of DTK A01 was released today (6/15/2015).

1. Download the latest version of DTK at the link above.  Then in ConfigMgr, go to Software Library\Application Management\Packages and right click on Dell PowerEdge Deployment.  Select Dell PowerEdge Server Deployment -> Launch Deployment Toolkit Configuration Wizard.

When the wizard opens, point the zip location to the DTK zip you just downloaded.  If you already had the previous version of DTK 5.1 installed, the bottom part of the wizard will look the same on both sides.  They will both show Version 5.1.  Don't worry, it will update.

On the next screen you can select your previous boot image that you were using or let it create a new one from the Windows ADK.  Let this run to completion and you will have a new boot image with all the necessary drivers to boot the last couple of generations of Dell servers.

2. Next, you will need to update the 3 PowerEdge packages.  PowerEdge Custom Reboot Script, Deployment Toolkit Integration, and Startup Network Setting.  If you had already distributed them to your distribution point, just right click on them and select Update Distribution Points and then make sure the Content Status at the bottom turns green and has the current date and time.  This may take a couple minutes depending on your environment.

3. Once all 3 of those are updated, do one last check.  Look at the PackageID of the PowerEdge Deployment Toolkit Integration package.  Go to the path of where your distribution share packages are (Drive:\SMSPKGDrive$\) and find the folder with that PackageID and open it.  Find the Version.txt file and open that.  It should tell you Build 1658 which confirms that you have updated DTK and distributed it successfully.

4. And the last thing that needs to be done is to make sure your new boot image is the one that your task sequence uses and the target machine boots to.  I have instructions on how to do all of that in the following post.  Look down where it says "1. Boot Image".

Now you should be able to run your OSD task sequence and have the Set RAID step work correctly.

Dell DSDPv3.0 with ConfigMgr 2012 R2 SP1

I have confirmed through testing that the Dell Server Deployment Pack v3.0 does work with ConfigMgr 2012 R2 SP1.  No need for a new version just to work with SP1.

I tested the Set Boot Order, Set BIOS config, Set iDrac config, and Set RAID config, and Driver import from SMTD and they all work.

A couple of things to keep in mind:

1. If you are trying to deploy Server 2012 R2, you will need your ConfigMgr host to be running Server 2012 R2, or may have to copy the boot image to a Server 2012 R2 machine to manually inject drivers.  This is due to a downlevel DISM issue described here:

2. If you are trying to deploy Windows 8.1, Server 2012 or Server 2012 R2, I suggest you update your version of DTK (Dell ToolKit) to the latest version which was just released today (6/15/2015).  The latest version is A01 at this link  This is because of a permissions issue in the previous version of DTK that we just resolved.  I explain that in another post.

Monday, June 8, 2015

Upgrade to Dell OpsMgr MP Suite 6.1

The new Dell OpsMgr Management Pack Suite resolves a couple of bugs that I identified.  The annoying Usage Information Alerts, and a problem with the Dell Connections License Manager in particular.  If you are using the MP Suite v5.2 or 6, I suggest you update to the new v6.1.  I went back and forth from 5.2 to 6.0 to 6.1 and back down and up again several times in 2 separate labs to confirm that these instructions worked each time for me.

1. Download the published release of the Dell OpsMgr Management Pack v6.1.  Here.

***Edit 6/23/2015
In #2 below, the best way to run the installer is to open an elevated command prompt and use "msiexec /i ".  If you are not logged in specifically as the local admin, the COM+ object will not be created.  This is a permissions issue with the MSI installer that will be resolved soon.  Logging in as the Domain Admin or any other user, even if a member of the local administrators group, will not install correctly unless you have lowered your UAC security profile.

If you already ran the installer, open dcomcnfg and look under Component Services\Computers\My Computer\COM+ Applications and see if the Dell Device Helper is there.  If not, open an elevated cmd and run the installer again and chose the repair option.

2. Extract and run the installer Dell_Server_Management_Pack_x64.msi, and I suggest unchecking the box at the end to open the OpsMgr console.

3. Right click on the OpsMgr console and Run As Admin.  This is usually the best way to open any of the System Center consoles.

4. Go to Monitoring\Dell\Feature Management Dashboard.  After a little while the FMP (dashboard) will update and show Available Versions as 6.1.

***On each one of the 5 features that you update, do not close the Task Status window until you have read through it to make sure it is successful because it will almost always show Success for Status even when there was an error running it.  That Success Status is just a success that the function ran.  Not that it completed successfully.  Read through the Task Output and you are looking for something similar to:

INFO: Dell.Chassis.Modular.Server.Correlation imported successfully

Once you see that, you can close the window.***

5. Start at the top and select "Chassis Modular Server Correlation" and then in the task pane run the "Upgrade Chassis Modular Server Correlation Feature" task.

6. Next, is the Chassis Monitoring.  Highlight it and then run the task "Set to Chassis (either Detailed or Scalable) Monitoring Feature" task.

7. DRAC Monitoring.  Highlight it and run the "Upgrade DRAC Monitoring Feature" task.  Don't close until you are sure it was successful.  For me, this one was not successful on the first run.  I had to run it again and set an override to Auto Resolve Warning/Errors set to true in the task as seen below.

8. Server and Rack Workstation Agent-based Monitoring is next up.  Select it and run the "Set to Agent-based (Detailed or Scalable) Feature" task.

9. Last, is the Server and Rack Workstation Agent-free Monitoring.  Select it and run the "Set to Agent-free (Detailed or Scalable) Feature" task.

After a short while you should see the In Use Version column for each feature change to 6.1.0.

10. Now, go to Administrator\Management Packs.  Look at all of the Dell MPs and make sure they are all 6.1.0.x, where x could be any of multiple numbers, except for Dell Base Hardware Library which will still be  Very specifically, look at Dell Feature Management and see what version it is.  If it is not, it hasn't updated and it may be held up by other MPs that are dependent on that one.  Open the properties of the Dell Feature Management MP and look on the Dependencies tab in the bottom half to see which ones.  Most likely will be Dell.FeatureManagement.Override version and Dell.FeatureManagement.TaskRefresher version  If there are others, make note of them also for the next step.

You can find those 2 MPs and export them if you like, and then you will need to delete them.  Delete both the Dell.FeatureManagement.Override and the Dell.FeatureManagement.TaskRefresher.

11. Once they are gone the next step is to import the new Dell Feature Management MP since it didn't update before.  Select Import Management Pack.  Select from Disk and No for searching for dependencies.  Browse to "C:\Program Files\Dell Management Packs\Server Mgmt Suite\6.1" and select the  It should show the new version  Click Install.  When it finishes, you should see that new version number for Dell Feature Management after the MPs list refreshes.

12. Go to Authoring\Management Pack objects\Object Discoveries.  In the Look for box, type "Dell Feature" and hit Find Now.  Select "Dell Feature Management Host Discovery".  Right click on it and select Overrides->Override the Object Discovery->For all objects of class: Management Server.

On the Override Properties you are going to put a check next to FMPHostFqdn and set that to the FQDN of your OpsMgr server.  Then put a check next to Interval Seconds and change the value to 600 seconds.  If you want a log of this, you can also check the Log level and change it from a 0 to a 1.  This log will be located at C:\Windows\Temp\DellFeatureMonitoring_Logs.  At the bottom of Override Properties, create a new Management pack.  Give it a name and then save it.

13. After the specified time period (600 seconds) the Dell Feature Management Dashboard will update to the new version.  You will no longer see the annoying Usage Informational Alerts and some of the column headers will change.  The Total Node Licenses column will change to Total Node Count, and the License in Use column will change to Required License Count.  And if you select the Server and Rack Workstation Agent-free Monitoring feature you will see a new task on the right side called Associate Run-As Account.  Once you see these things you will need to go back to step 12 above and uncheck the Interval Seconds so that it will go back to the default of once per day.  If you do not do this, the discovery cycle will run every 10 minutes appending the log file which will continue to grow (about 0.5MB/Day).

The Usage Information Alerts can be closed.  The Associate Run-As Account task associates the Run As account used for SMASH discovery with all Dell Server objects, required for health monitoring.

14. And lastly, you will see a new Information alert that should only appear one time.  The name is Dell FMP: License Information - Dell Server and Rack workstation Agent-free Monitoring and it gives you information about the license tiers and requirements.

Now you have updated to the new Dell OpsMgr Management Pack Suite v6.1.  If you have multiple OpsMgr management servers, you will need to run the installer for this MP Suite on each mgmt server to update the files and com+ object on each one and that should be all you need to do.

Friday, June 5, 2015

Set RAID Config not working with Dell Server Deployment Pack

Dell Server Deployment Pack 3.0 with Dell Toolkit 5.1 will have problems running the set RAIDcfg command.  We found that there was a security permissions change starting in DTK 5.1 for sure; and possibly as far back as DTK 4.4 because I had the same error there as well.

The permissions change created a situation where the envout.txt file could not be created by the script in the downloaded package folder.  The default location is "X:\Windows\Temp\SMSTSLog\PackageID\Tools\AMD64".

You would see an error in the SMSTS.log saying "File is not writable!" in the "Output from command execution" block immediately after the "Starting execution of ArrayBuilder script" block.  Then in the "StdOut output from the command:" block you will see "EXITCODE=204", which means the same thing "File is not writable".  Then just a little further down you will see something like this:


DESCRIPTION: Could not find the raid output file you specified (envout.txt). Please check the path.


As a work-around, you could create a new script to make an empty envout.txt in the AMD64 folder.  Attach that script to your task sequence to run before the Set RAID step.

The resolution to this will be in a new version of DTK that will hopefully be out in the next week or two (from June 5, 2015).

And please remember that anytime you update DTK in ConfigMgr, you will need to re-distribute the Application Management\Packages\Dell PowerEdge Deployment\PowerEdge Deployment Toolkit Integration package in ConfigMgr.

Wednesday, May 27, 2015

Annoying Dell FMP: Feature Management Usage Information Alerts

If you have the Dell OpsMgr Management Pack 6.0 imported and OpsMgr is integrated with System Center Virtual Machine Manager, you may see some annoying "Dell FMP: Feature Management Usage Information" alerts every 6 hours.

Open the alerts and on the Alert Context tab you will see information related to the "StorageObjectsDiscovery.DS.ps1".

Most cases that I have seen involve 4 alerts.  The first one in the Alert Context Data says "Storage Discovery: started."  The second alert says "Storage Discovery: Got VMMServer. Module imported."  Third alert says "Missing Value in Property Id: {78FCB9D8-AFF4-785C-CAC3-1C9B8BAAA561}."  And the fourth and last alert says "Storage Discovery: Complete!".

These then repeat every 6 hours.

You can either ignore these and delete them as often as you want.  Or you can set an override by right-clicking on the alert and select Overrides -> Override the Rule -> For all objects of class: Health Service.  Check the Enabled parameter and change the override value to False.  Save to a new management pack.  That will stop you from seeing the alerts for now.

When the new version of the MP Suite comes out, these annoying alerts are supposed to be removed.

Tuesday, May 26, 2015

Fix for Dell Server Deployment Pack Driver Package where it is required to distribute to DP share multiple times.

If you have the issue I talked about in these two previous posts, listed below, where you import Dell Server Driver Packages and then you have to run Distribute Content and then a second Update Distribution Points to get the driver package to fully distribute, there is a fix now.

After updating to ConfigMgr 2012 R2 SP1, I found that the above issue was resolved if you manually import driver packages when I was importing packages from other vendors, but not if you use the Dell Server Deployment Pack v3.0.  With some research into the issue I found that the "RefreshDPs value" was set to "false" in DSDPv3.0.  In the new SP1 for ConfigMgr 2012 R2, that box was removed in the Driver Import Wizard and checked by default.

The initial fix was just to check that box for the DSDP wizard.  This then caused another issue which caused the driver import to refresh the DPs after every driver.  That made the import take a very long time.  From a normal import time of a couple minutes to nearly an hour.  So we made another change and now it all works correctly.  Driver Package import time is back to normal, driver package is created on the DPs the beginning of the import process and then refreshed once at the very end of the import.  So you will see a driver package version of 2 in the Distmgr.log at the end of the import.

Then you can check the box in the properties of the driver package to "Copy the content in this package to a package share on distribution points".  Then you can right click and Distribute Content one time and your package will show up fully on your DP in the SMSPKGDrive$ folder.

This fix will not help with Driver Packages that have already been imported because they were imported with the RefreshDPs box unchecked.  Those already imported driver packages will still have to be distributed to the DP share twice.  But any new driver package that is imported after installing the new DLLs will be able to be distributed once.

Since this is not a major issue and can be worked around, this patch will be included in the next version of DSDP.  If you need it before the next version is available, please call Dell and open a case.  Tell them you need the Configuration Manger DSDP Driver Package Import fix.  Your call should be transferred by the call director to the high complexity team, who you can then tell to contact me, Brad Goodman, directly for the patch.