It seems recently many users are receiving an error logging into Remote Desktop Servers (Terminal Servers) from off-site. The error reads:
An authentication error has occurred.
The function request is not supported.
Remote computer <ServerName>
This could be due to CredSSP encryption oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660
This is a result of a March 13th update. The previous error message was shorter, but an Apr 17 update elaborated the error message to read as above.
The link explains how to resolve using group policy but the simple fix, as of May 8th, is to apply the KM4103725 monthly rollup update. This will require a reboot on most servers, but should resolve the problem once complete.
It seems Windows 10 Update fails sometimes, especially with the Fall Creators Update. It continuously wants to install, you approve, it runs, and fails, often with error code 0xc1900208.
In troubleshooting I have found most of the time it will install if you click the “Update now” button form the Creators Update Web page. It seems to check for compatibility, make any adjustments, then Install.https://www.microsoft.com/en-us/software-download/windows10
Should that fail to work, you can download the Windows 10 Update Troubleshooter, which will troubleshoot, and offer to repair any issues found. There is also a troubleshooter for Win 7 and 8.https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter
However, I also recently read about an issue with attached USB drives oddly causing the update to fail. Recently, on a PC on which I tried all of the aforementioned options, and had no attached USB devices, I discovered a DVD in the drive. Once ejected the update installed without a problem. This strikes me as very bizarre, but perhaps the update searches other available drives for some reason.
Therefore; I recommend if having issues with Windows updates, try disconnecting any USB devices such as external drives, thumb drives, phones which may be charging, and possibly even USB printers, and don’t forget to check the DVD tray, just in case.
Have you ever opened an Adobe document and been surprised to see hieroglyphic-like, unrecognizable, characters?
Having seen this a few times and having found dozens of solutions on the internet, some of which seem rather complex, I did a little tinkering. It seems the common denominator is one simple change; allowing “document fonts”. I confess I have not run across this with Adobe Acrobat Reader, but if Adobe Standard or Pro, there will be an Adobe “Printer”. To resolve the problem……….
- Windows 7/8: Open Control Panel and then Devices and Printers Right click on the Adobe “printer” and choose Printer properties.
- Windows 10: In the Cortana Search box type printers and click enter, which should open the Printers and Scanners window. Click on the Adobe “printer” and 3 buttons should appear, click manage, then Printer Properties
- Click the “Preferences” button near the bottom
- Choose the “Adobe PDF Settings” tab
- Uncheck the box “rely on system fonts only, do not use document fonts”
- Click Apply, OK, and close all windows
- This requires a restart to take effect.
On several systems over the past year I have seen the C:\Windows\Temp folder filling up with large .cab files generated by the system, on a semi-regular bases. This continues until there is no available drive space and the system becomes unusable.
The short term solution is to just delete all of the files but the problem returns after weeks or months, depending on the initial free drive space.
It seems this is caused by a large log file within the C:\Windows\Logs\CBS folder. To resolve I created a folder C:\Windows\Logs\CBS_Archive and moved all CbsPersist_file_number.log files, older than 10 days, to the archive folder. This seems to have resolved the issue.
I was asked to look into a beeping in a server room which no one could find.
It was understandably difficult as there were three server racks with modems, routers, switches, servers, PCs, UPSs, CCTV, and audio equipment. To add to that they were single beeps, quite wide spread apart, and within a noisy, concrete room. I determine after a little while they were single beeps and exactly 15 minutes apart. Typically first suspicions are the UPS units, but 15 minutes is not typical of APC UPS devices. To make a long story short, it turns out in a far corner where 2 fiber internet connections entered there were small UPSs units supplied by the service provider. One of the UPS units showed a failed battery. Being behind the open steel door, no one had seen the light.
This seems like a trivial post and an obvious solution but I am posting as there are many forums on the Internet with people not being able to locate a device creating a beep every 15 minutes. This is common with FIOS, Verizon, and Bell equipment. One story goes as far as to explain a fellow turning everything off in the server room, one device at a time, every 15 minutes, till everything was shut down and unplugged, but could still hear the beeps.
For simplicity there are many reasons you may want a single URL or FQDN to access a resource internal or external to your corporate domain. If the internal and external domain names are the same it can sometimes cause DNS issues resolving the public domain name from the corporate network. I am often asked about this in reference to web sites; “why is our website accessible from anywhere but our buisiness network””?” For example you want to access www.net-works.ca from a network that uses the internal domain net-works.local. The internal DNS server manages DNS for net-works so it doesn’t pass on the request to the forwarder, but it also doesn’t have a DNS record for the www Host. The simple solution is to create an internal zone for the host name you are trying to access. SBS 2008/2011 did this automatically for “remote” so that the same URL could be used internally and externally. This technique can be used for access ing websites, dvr systems, or anything you like that uses a FQDN.
To do so open the DNS management console, expand the folders under your server name, right click on the “Forward Lookup Zones folder, and select New Zone. A wizard starts, click next and you can select the zone type. Accept the defaults, Primary Zone and next.
Select “To all DNS servers running on domain controllers in this domain”.
In this case I am going to set up a universal URL for access to a DVR system, so I will enter dvr.net-works.ca This could be www, remote, or what ever meets your needs. Keep in mind for external access you must set up the DVR, or matching, Host record with whichever service manages DNS for your public domain.
Again accept defaults, and click next, and finish.
Now right click on the new zone folder and choose “New Host (A or AAAA)” record. Finally, again accept defaults except insert the IP address. In this case it is an internal IP. There should be no need for a PTR record creation.
When complete it should look similar to this:
It seems Server Essentials and possibly others will often show in the daily report a DFSR Event ID: 2147485861 error. There is also a corresponding Warning Event logged in the DFS Replication log (sub-folder of Applications and Services Logs) of the event viewer with Source DFSR and Event ID 2013, followed by an Event ID 2212. This is most often caused by a dirty shutdown.
There are numerous articles on the Internet explaining how to resolve this, but I was told they were not clear to some readers. So, hopefully to clarify:
Firstly open Regedit and locate the key below, and verify it is set to 1. If not change it to 1. (Note: you should always backup the registry before making any changes)
Then in the error message within the report locate the command as highlighted in the image above, but cut and past it from your server report as it will have the correct volume GUID. Make sure it is all one line. You may want to use Notepad to reassemble if broken in the report. You need to use an elevated command prompt to run this.
If you run the command with the wrong GUID it will display; “No Instance(s) Available”.
If successful your command window should look similar to this:
This should resolve the problem, but it may return at some point in the future. The Windows Server 2012 Essentials Build document (wiki article) suggests to prevent this in the future, after running the command successfully, change the aforementioned registry key from 1 to 0. Doing so enables DFS Replication automatic recovery.
Recently after installing a new Linksys (Cisco) EA6300 router we received a “502 – Bad Gateway” error message when trying to access the web management page.
(Note: the IP in the image is correct for this site, but the default of course is 192.168.1.1)
Installation of the router and configuring went as expected, and internet access by client machines was fine, but after completion and reboot the Bad Gateway message appeared when trying to log back into the router. This seems to be a common issue with numerous models not just the EA6300, but also the EA6500, EA4500, EA2700, E4200, E1200, and more. There are numerous posts about this issue on many blogs and message boards, all of which suggest starting to resolve by pressing the reset button. If you have a detailed configuration with custom IP configurations, port forwards, DDNS and more, that would be quite a nuisance and time consuming.
We discovered simply disconnecting the WAN / Internet connection to the router and refreshing the web management page allowed access and log in. Once logged on the WAN connection could be reconnected. Logging out and back in reproduced the problem. The solution was to gain access as described and then using the built-in utility update the router’s firmware. Once updated there were no further problems.
There are numerous 3rd party applications that require .NET 3.5 and/or .NET 2.0 such as QuickBooks, Profile, and more. Normally you simply go to: Control Panel, Programs and Features, Turn Windows Features On and Off, select .NET Framework 3.5 (includes .NET 2.0 and 3.0) and install.
However with Windows 10 it will want to “Download files from Windows Update” and then fail, primarily when joined to a domain that has WSUS (Windows Server Update Services) enabled, resulting in an Error code: 0x800F081F.
The problem also exists on Windows 8 and 8.1, with numerous suggestions to resolve including removing specific updates. These updates do not exist on Win 10, but if they relate to your problem see: http://www.askvg.com/fix-0x800f0906-and-0x800f081f-error-messages-while-installing-net-framework-3-5-in-windows-8/
To give credit where credit is due, Microsoft’s solutions to the Windows 10 problem are outlined in the following article: https://support.microsoft.com/en-us/kb/2734782
From that I was able to resolve using the following steps. :
- Attach a Windows 10 install ISO, either by inserting the install CD, USB, or a path to an ISO file on the network. The latter can be achieved by using the USB/ISO creation tool which downloads the files from Microsoft and creates the ISO from Microsoft: https://www.microsoft.com/en-us/software-download/windows10
- If you are using an ISO file you can mount it so that it can be accessed using a drive letter within Windows 8/10 by highlighting the ISO file and choose manage then mount, from the menu bar in Windows Explorer.
- Edit local group policy to look for your ISO when Microsoft Update cannot be accessed. Open group Policy by entering gpedit.msc in the search box or from an elevated command line.
- Locate the following policy: Computer Configuration | Administrative Templates | System
- In the right hand window, scroll down past the folders and locate the specific policy: “Specify settings for optional component installation and component repair”.
- Double click on the policy to open it, click the radio button “Enable”, and in the box “Alternate source path” enter the path to the necessary files. They are located in the \sources\sxs folder of the ISO. In my case this would be E:\sources\sxs
- Note: there is an option in the policy to “contact Windows Update directly” but this did not work for me or others.
- Force group policy to update by rebooting or from an elevated command prompt enter gpupdate /force
- Now you can return to: Control Panel, Programs and Features, Turn Windows Features On and Off, select “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” and install. It should locate the files and install without a problem.
- I recommend a reboot after doing so.
NOTE: WINDOWS 10
– I recently had difficulties applying this method to a Windows 10 machine. I believe it may be related to it being an upgrade from 8.1, but I had to download the Windows 10 trial .ISO file from TechNet, mount it, and run the following command from an elevated command prompt. (Substitute your drive letter for ‘D:’, and path if necessary)
dism /online /add-package /packagepath:E:\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab
I have had 2 clients unable to print from Internet Explorer 11 during the past month. After some digging it seems there is a temp folder used in the printing process.
This folder had no changes for several months and had a corrupt user ID (SID) within the security permissions. Adding the user account to the security (NTFS) permissions of this folder and granting them “Full Control” resolved the issue. A reboot is required.
I should have tracked down sooner as when printing, the page was blank with only C:///C:/Users/%UserName%/AppData/Local/Temp/Low/<random doc name>.htm printed at the bottom