I ran into this issue at a client where we were forced to use an iSCSI connection for their backup. After upgrading to ESXI v6, the connection started showing as Normal / Degraded.
After doing a number of troubleshooting items, I found an obscure forum post where it was claimed that ESXI will flag it as degraded if there is only one connection (ie. the connection is not redundent).
I ended up un-bonding my NAS’s two NICs, added the “new” second NIC as a target for ESXI, rescanned the storage devices on ESXI, and voila… my degradation was resolved!
I am in the process of decommissioning several DNS and Active Directory servers and wanted to make sure there were no undocumented devices on the LAN that were statically set to use one of the soon-to-be-decommissioned DNS servers. I figured the best way to do this would be to record all requests for DNS from the specific servers and it is fairly straight forward to do.
1. Open the Domain Name System Microsoft Management Console (DNS MMC) snap-in by going to Start, Programs, Administrative Tools,
and then DNS Manager
2. From the DNS Server, right-click the server and select Properties
3. The Properties pop-window will appear on your screen.
4. Select the Debug Logging tab and the Log packets debugging check box, respectively.
5. Ensure that the Incoming, UDP, Queries/Transfers, and Request check boxes are selected.
To ensure that the server’s drive does not exceed capacity, make sure you set an appropriate file size limit!
6. Click the OK button.
That is it! Your text file will start logging items for you. This will work on:
- Windows Server 2003
- Windows Server 2003 R2
- Windows Server 2008
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
I had a user complain of some weird issues in RDP, the biggest one being that they couldn’t right-click in the taskbar. I found a few other reports of such issues and found the solution was to turn off hardware acceleration in the Options menu. Once I did that and restart Firefox, everything was working!
Ran into this one today… and it is nothing you want to see happen on an Exchange server! I was re-assigning services to a new SSL certificate when I started getting this error. After doing some searching, I found the easy fix from Microsoft. Under Server Config > Client Access, you can click Reset Virtual Directories on the far right. From there, you can choose which directories to rebuild (OWA, Autodiscover, etc.) Doing that fixed my issue for OWA!
More info can be found in Microsoft’s Technet Article: https://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
I am currently building a Remote Desktop Server paired with a Remote Desktop Gateway and I ran into this error:
“Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable.”
After troubleshooting a bit, I found that the error occurs if you have multiple sites binded in IIS to your Port 443. Make sure you have ONE site binded to 443 and you’ll be good to go!