Tuesday, November 23, 2021

Updating Dell servers using DSU (Dell System Update)

  • Search for latest Dell System Update for the server you are working on. Use the service tag on the Dell support site and then search for DSU in the downloads section.
  • Install package by double clicking the downloaded file
  • After install, run an administrative command prompt. Browse to c:\program files\Dell\DELL EMC System Update.
  • Type .\dsu.exe
  • The server will be inspected, and after some time applicable updates will be displayed
  • To select all updates, type the letter "a" and press "enter"
  • To commit the updates, type the letter "c" and press "enter"
    • To select only certain updates, look through the list and determine which ones are needed (check which ones are upgrades). Enter the number for each upgrade needed and hit enter. When all the updates have been selected, type the letter "c" and press enter.

This takes quite a while, so be prepared.


How to move DHCP server to new server, how to clear stale leases from DHCP server database

  1.  On old server, open an administrative command prompt and run "netsh dhcp server export c:\temp\dhcp.txt all"
  2. Install the DHCP server role on new server. Do not make any configuration changes after the install, and make sure the DHCP server service is running.
  3. Copy the exported dhcp configuration file from the old server to the c:\temp folder of the new server.
  4. Open an administrative command prompt on the new server and run "netsh dhcp server import c:\temp\dhcp.txt all"
  5. Open the DHCP management console on the new server, right click on the server name, and click "authorize". Make sure that all the settings have imported properly.
  6. Go back to the old server and deauthorize the server. You can then remove the DHCP server role, or just disable the DHCP service permanently.
  7. If you have moved DHCP to a server that will also be a DNS server, remember to include the new server in the DHCP Scope options.


DELETE STALE LEASES FROM DATABASE

  1. Right click IPv4 and choose "reconcile all scopes"
  2. Click "verify" at the bottom
  3. If it lists IP addresses, click "reconcile" at the bottom
  4. Check your active leases. You will see a bunch of them appear which all have the same bogus MAC address. Sort them so they are all in a row, highlight them all, right click and choose "delete".
  5. Your usage statistics should now match the actual amount of IP's that are leased.

Friday, April 9, 2021

How to configure File Server Resource Manager

  1. Go to Quota Templates and create a new template for each drive letter you are monitoring. 
    • Create a descriptive name for the template (ie. Drive C: almost full - company name)
    • Change the space limit to match the amount of space on the drive you are monitoring
    • Change settings to soft quota and choose "add"
    • Enter the email address you will be using for the email notifications (ie. rob@neverdownsystems.com)
    • Choose "OK" to save. You will receive notice regarding SMTP server setup. You can ignore this for now.
  2.  Go to Quotas and create a new Quota.
    • For Quota path, click "browse" and then browse to the drive letter you are monitoring
    • Under "how do you want to configure quota properties", click the down arrow and choose the quota template you set up in the previous step.
    • Click "create"
  3. Set up your SMTP server
    • Right click on "File Server Resource Manager (Local) and choose "configure options"
    • Under SMTP server name or IP address, enter the SMTP server you will be using
      • For Office 365 customers, you can use the MX record for Office 365. Make sure you have created a non-licensed user to send the reports (ie. fsrm@companyname.com) in Office 365. Also make sure you have a connector set up to allow the public IP address of the customer to send email via SMTP relay.
    • Under "Default Administrator recipients", enter the destination email address (ie. rob@neverdownsystems.com)
    • Under "Default From email address", enter the sending address (ie. fsrm@companyname.com)
    • Click "Send Test E-mail" to make sure email is delivered. If it does not get delivered, check the following:
      • Did you set up the connector in Office 365 to allow the public IP address of the customer?
      • Is the customer's firewall set to block SMTP traffic outbound? If so, did you allow an exception for the server(s) you are monitoring?