Add Second NIC to Ubuntu Server

1) Type- dmesg | grep enp

2) Look for your network adapters, you'll see you're primary one (enp1s0) - look for the second one.  In my case in was enp2s0.

3) Type- sudo nano /etc/network/interfaces and add the following (using the name of your adapter you found in step 2)
For DHCP-
auto enp2s0
iface enp2s0 inet dhcp

For Static ip-
auto enp2s0
iface enp2s0 inet static
        address 192.168.0.3
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.1
        dns-search example.com
        dns-nameservers 8.8.8.8 4.2.2.2

Ubuntu Server Command-line black screen instead of login, Intel Graphics Media Accelerator (GMA) 3600

I bought this cool little MITXP D2500CCE, basically a tiny little Intel Atom PC with dual nics with the intention on loading Debian on it.  All I got was a black screen after the initial boot.  I loaded Ubuntu Server (16.04) and same thing.  Since I installed SSH, I SSH'd in and dug around.

It took me a near eternity to figure out the solution.  So in the interest in saving you an eternity, here's what fixed it-

Type-
sudo nano /etc/default/grub

Change-
GRUB_CMDLINE_LINUX_DEFAULT=""
to
GRUB_CMDLINE_LINUX_DEFAULT="video=LVDS-1:d"

Hit Control X, save the file.

Type-

sudo update-grub

sudo update-grub2

sudo reboot

That's it!  :)

Troubleshooting Windows Server Account Lockouts when the Security Log Fails You

Many times, you may encounter a windows domain account that rapidly locks out.  You've enabled auditing and used tools to evaluate the security log.  And you come up with something like-

The computer attempted to validate the credentials for an account.

Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account: adam1115
Source Workstation:
Error Code: 0xC0000234


Great!  I'll head right over to the blank source workstation and check it out.  One option is to find out what domain controller is locking it out and enable verbose logging of the netlogon service.

Open up the command prompt as administrator and run the following-

nltest /dbflag:0x2080ffff

Then once the account locks out again, open the log file as administrator (I do it from the same command prompt)-

notepad c:\windows\debug\netlogon.log 

You will see each logon attempt and which machine is generating them.  To turn off the debuging, type the following-

nltest /dbflag:0x0

In Exchange, you can check the IIS logs and device statistics-

Get-ActiveSyncDeviceStatistics -Mailbox <Mailbox Name> | ft DeviceType, DeviceUserAgent, LastSuccessSync

Using PSCP.EXE to transfer files from/to ASA on Windows

Lately I've been utilizing PSCP.EXE instead of TFTP on windows system to transfer files.

To enable-

ciscoasa(config)# ssh scopy enable

Then from your windows box-
pscp.exe asa921-k8.bin admin@192.168.0.1:disk0:/asa921-k8.bin

You can backup the config by doing-

copy running-config disk0:ASA112316.txt

pscp.exe admin@192.168.0.1:disk0:/ASA112316.txt ASA112316.txt

You get the added benefit of storing a copy on the device for future review.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

How to upgrade Dell Server to latest Bios and Firmware with ISO for VMware or other non-windows servers

Dell keeps an up-to-date linux ISO image that you can boot with CD, USB, or Virtual CD.  Just go to-

https://dell.app.box.com/bootabler620

Note- simply replace the "620" with the appropriate model of your server.  620 would be for a PowerEdge R620.

Exchange 2013 in EMC you get he WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota.

I use a powersehell command to give a certain mailbox full control of all mailboxes.  In Exchange 2013's EMC, I started getting the following error-

Sending data to a remote command failed with the following error message: The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota.

I found some info on-line related to Exchange 2010, but to resolve this in 2013 with Windows 2012 was slightly different.

In a command line (not powershell)-
winrm get winrm/config

Look for this-
MaxEnvelopeSizekb = 2000

I upped it to 8000-  (Note, I had to use quotation marks)
winrm set winrm/config @{MaxEnvelopeSizekb="8000"}

              ୍୎

                                                                                                                     

How to update file attachment size in Exchange 2013

To check-
get-transportconfig | ft maxsendsize, maxreceivesize
get-receiveconnector | ft name, maxmessagesize
get-sendconnector | ft name, maxmessagesize
get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize

To Fix-
Set-TransportConfig -MaxSendSize 50MB -MaxReceiveSize 50MB
Get-Mailbox | Set-Mailbox -MaxSendSize 50MB -MaxReceiveSize 50MB
get-transportconfig | Set-TransportConfig -maxsendsize 50MB -maxreceivesize 50MB; get-receiveconnector | set-receiveconnector -maxmessagesize 50MB; get-sendconnector | set-sendconnector -maxmessagesize 50MB; get-mailbox | Set-Mailbox -Maxsendsize 50MB -maxreceivesize 50MB