I had a client where Adobe Acrobat XI Standard, on Windows 10, worked flawlessly for several years, but recently documents would open and then after a couple of seconds close with no warning. Reinstallation and reactivating did not solve the problem nor did many Internet search results such as registry edits.
What did work was to open Adobe and very quickly, before it closed, click “Help” on the menu bar and then select “Check for updates”. It did find an update, download, and install. It worked fine after that. I suspect a compatibility issue with a recent Windows update may have caused the problem.
A client had a 4 hour power outage today. Though the Hyper-V host, which was connected to a business class UPS, rebooted as it should, none of the VMs came back on line. The Hyper-V management console showed “No virtual machines were found on this server”.
After researching several solutions before simply recreating the virtual machines I restarted the “Hyper-V Virtual Machine Management service”, which was already running. Instantly all VM’s reappeared and started up. Perhaps this may assist others down the road.
This is a must have pdf reference file:
An amazing, free, current, searchable, compilation of hundreds Windows commands with explanations, syntax, and examples of their use. And, it’s free !
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.