Installing Dell Open Manage 7.1 on Hyper-V R2 Servers

Posted on Leave a commentPosted in 2008, 2008 R2, 2012, dell, hyper-v, openmanage, osma, server administrator, server core, windows server

This set of instructions goes through the process for installing Dell Open Manager on Windows Server 2008 R2 and Windows Server 2012.

  1. Download both the 6.5 and 7.1 versions of Dell Open Manage
    • You need to install 6.5 first, or you will get errors about “omchecks has stopped working” failing during the RunPreReqChecks process and an error about “Failed to load OMIL Library” when running the actual installer.

image

image

  1. On the server run Dism /online /enable-feature /featurename:SNMP-SC to install SNMP
  2. After downloading 6.5 expand the zip to c:\OpenManage65 and if needed copy to the server you are installing on, or burn a DVD and insert it into the server in question.
  3. Install Open Manage 6.5 with the following steps
    1. cd c:\OpenManage65\windows\prereqchecker
    2. runprereqchecks /s
    3. echo Return Code = %ERRORLEVEL%
    4. Check the Return Code with the codes listed at http://support.dell.com/support/edocs/software/smsom/6.1/en/ug/HTML/prereqch.htm#wp1053477
    5. Fix any errors listed. You should get a 2 as the Return Code. You might need to view the prereqchecker HTML file that it creates. This is made in your temp directory. Cd %TEMP% to see what this is. It will be something like c:\Users\username\AppData\Local\Temp\2. To open the HTML output file connect to this temp folder from a machine with IE installed on it and open omprereq.htm. Fix any listed errors.
    6. cd c:\OpenManage65\windows\SystemsManagement
    7. msiexec /i SysMgmt.msi
    8. Choose Custom and add the Remote Enablement option.
  4. Allow remote access to TCP port 1311 (the Open Manage web server port) using netsh advfirewall firewall add rule name="Dell OpenManage Server Administrator Web GUI" dir=in action=allow protocol=TCP localport=1311
  5. Install Open Manage 7.1. The steps here are similar, just from the directory containing version 7.1 instead.
    1. cd c:\OpenManage71\windows\prereqchecker
    2. runprereqchecks /s
    3. echo Return Code = %ERRORLEVEL%
    4. Check the Return Code with the codes listed at http://support.dell.com/support/edocs/software/smsom/6.1/en/ug/HTML/prereqch.htm#wp1053477
    5. Fix any errors listed. You should get a 2 as the Return Code. You might need to view the prereqchecker HTML file that it creates. This is made in your temp directory. Cd %TEMP% to see what this is. It will be something like c:\Users\username\AppData\Local\Temp\2. To open the HTML output file connect to this temp folder from a machine with IE installed on it and open omprereq.htm. Fix any listed errors.
    6. cd c:\OpenManage71\windows\SystemsManagement
    7. msiexec /i SysMgmt.msi
    8. Choose Custom and add the Remote Enablement option (though as this is now an upgrade it should already be selected).
  6. Finish by browsing to https://remoteserver:1311 not forgetting the s in https. You will get a certificate error and once connected you can replace this if you wish or are required to by corporate policies.
  7. With thanks to the following two blogs:

    Hyper-V and VSS Backups Cause Bluescreen

    Posted on Leave a commentPosted in 2008, backup, server core

    I found the other week that my Hyper-V server, running Server Core and nothing else was restarting all of its own accord. As this is just a server at home, and the monitor is switched off 99% of the time I had not noticed it blue screening.

    So looking in the event log (remotely of course, as it was running Server Core) to see why, I noticed it had done the same thing every day at a few minutes past 1pm – one of my scheduled backup times during the day.

    I was getting Event ID 1001 at about 1:03pm each day. So I changed the time of the backup (using Windows Server Backup, command line) to 11pm and I got 1001 bugchecks at 11:03pm each day.

    There was nothing else recorded in the event log, apart from the usual system start/TCP-IP etc messages and no clue as to the reason for the failure. All I had was the BugCheck, an example being 0x0000007e (0xffffffffc0000047, 0xfffff80003676b48, 0xfffffa60019ff5c0, 0xfffffa60019ff660.

    A bit of research later, and ignoring most of the posts regards VSS and Hyper-V I came across http://support.microsoft.com/kb/958662/en-us and http://support.microsoft.com/kb/960038/en-us (the latter of these is a hotfix) which I applied and solved the problem.

    It would seem that Hyper-V and VSS based backups have an issue with some backups if a virtual machine is in a running state. It is possible to save the Hyper-V guest machine and then back it up without issue, but of course this kicks people of the virtual machine – a bit pointless really unless its a development machine. To turn off backup for a Hyper-V machine, so that the server does not bluescreen then either disable the Backup (volume snapshot) option in the guest machine settings, under Integration Services or install the hotfix and reboot once.

    Enabling Previous Versions on Windows 2008 Server Core

    Posted on Leave a commentPosted in server core

    Enabling Previous Versions for file shares on Windows 2008 when you have the full graphic’s interface is easy to do – but what about if all you have is the command line as you get in Server Core.

    To turn on Previous Versions (shadow copies) via the command line follow these steps:

    1. From the command line on the server type:
      vssadmin add shadowstorage /for=c: /on=c: /MaxSize=5GB
    2. This will enable shadow copies on the volume, and this might be enabled already (esp. if you have already run a backup on the server). This particular command will do copies for the shares on the C: drive, with the storage for the copies also on the C: drive, and limiting that storage to 5Gb. Any of these options can be changed.
    3. Enable remote management on the Server Core firewall (again this might have already been done):
      Netsh firewall set service RemoteAdmin
      Netsh advfirewall set currentprofile settings remotemanagement enable
      Netsh advfirewall firewall set rule group=”File and Printer Sharing” new enable=yes
      Netsh advfirewall firewall set rule group=”Windows Firewall Remote Management” new enable=yes
    4. Then from a remote machine with the Task Scheduler MMC snap-in enabled, connect to the Server Core machine as an administrator level account and add the following scheduled task – 1 for each disk on the server:
      General>Name: Shadow Volume Copy
      General>User Account: Administrator level account (run whether logged in or not)
      Triggers>New: Weekly, 7am, Mon-Fri and Weekly, 12pm, Mon-Fri
      Actions>Start a program: %systemroot%\system32\vssadmin.exe
      Actions>Start a program>Arguments: Create Shadow /AutoRetry=15 /For=c: (changing C: if you have a different drive)
    5. Click OK and right-click the task and choose Run.
    6. Open a file share that is held on the Server Core machine and see if the Previous Versions tab shows a previous version having just been created.