About a month ago I had to quickly provision and prepare a new domain controller for a remote site, this went smooth and quite fast they had a new DC for logon/DNS and also acting as DHCP. One thing we had noticed before the upgrade was that if we tried to use Active Directory Users and Computers from the Remote Server Administration Tools package against the domain controller, then we were getting a “RPC Server is unavailable”. Since we have multiple sites and this was the only site we’ve noticed this issue, then when we started having other issues regarding replication and so on, we were quite quick to determine that the server needed to be replaced.
After the new server was brought up and was prepared, I tried again to use the remote tools to administer the server, but to my “horror” I was still getting this error… Now with the upgrade, I went for a 2012R2 version where the old was 2008R2, so I started thinking if there could be an issue with this for the new server. At the time I didn’t have other remote 2012R2 domain controllers, so for a while I settled with this and decided to come back and try to resolve it when I got some spare time – the DC was running perfectly on all other measures.
Today, a little over a month later, I got this extra time on my hands and decided to give it another look. Now, since last month, I’ve got a brand new site that holds a 2012R2 DC and of course this works fine with the remote tools – so something had to be messed up on the other site. I tried a quick search for RPC and RSAT tools and got some old Windows Vista KB that didn’t help me much, but then the second result took me in the direction, that some antivirus clients(or rather the Realtime-scan part) had a tendency to block RPC calls – so I tried to unload the Officescan client and voila -> The connection in ADUC switched over to the server that it couldn’t connect to previously…
Now this is all fine and dandy, but what I cannot get around is – how can it work against the other site’s DC without any issues???
The only thing I see different between the 2 sites is that the brand new site is VPN connected through Cisco ASA, and the other site that needs me to turn of Officescan is connected through our company MPLS…
If anyone can explain this to me – please do so in the comments below!
It seems that if a user set an Out of office from their Outlook client, before the update was applied, it cannot be turned off using their Outlook client. They are simply asked again and again, without success.
This can be handled through the Exchange Control Panel website, where an admin can turn it off for the specific users.
Having used Windows 10 for what seems a long time, and having upgraded whatever I could get my fingers on, issues sometimes appear. One of these have been going on through almost the entire lifespan of Windows 10, from the earliest builds. Depending on how/what I am doing on the PC, then a few times a day I’ve seen a 5-10 second stop in everything and then an error message, saying something like “Intel HD display driver for Windows 8 has crashed” – I’ve been blaming it on me running the insider build, but still I was annoyed that Intel/Microsoft did not fix at least the error message to show Windows 10.
But now mom has been upgraded, and she really only uses Microsoft Solitaire collection, 1 game-site online with Java-games and occasionally browse the net. She found that when playing the Spider solitaire game, she could force the crash message and her game needed to be restarted, but she could never get a game done.
Having this to search from, I quickly found that a lot of other people are playing these games 🙂 and they have seen many issues with these since Windows 10 came along. But in November, Intel finally stepped up at least on the beta channel – and provided what seems to be a fixed display driver, still though on the release notes, there are quite a few games that have issues, so be careful to read this.
Find the Intel beta download here: https://downloadcenter.intel.com/download/25541/Intel-Beta-Graphics-Driver-for-Windows-7-8-1-10-15-40-
This driver seems to work for most Intel current display adapters, but check the list below:
Intel® Iris™ Pro Graphics 5200 for 4th Generation Intel® Core™ Processors
Intel® Iris™ Graphics 5100 for 4th Generation Intel® Core™ Processors
Intel® HD Graphics 5000 for 4th Generation Intel® Core™ Processors
Intel® HD Graphics 4600 for 4th Generation Intel® Core™ Processors
Intel® HD Graphics 4400 for 4th Generation Intel® Core™ Processors
Intel® HD Graphics 4200 for 4th Generation Intel® Core™ Processors
Intel® HD Graphics 5300 for Intel® Core™ M Processors
Intel® Iris™ Graphics 6100 for 5th Generation Intel® Core™ Processors
Intel® HD Graphics 5500 for 5th Generation Intel® Core™ Processors
Intel® HD Graphics 6000 for 5th Generation Intel® Core™ Processors
Intel® HD Graphics 530 for 6th Generation Intel® Core™ Processors
Intel® HD Graphics 515 for 6th Generation Intel® Core™ M Processors
Intel® HD Graphics 520 for 6th Generation Intel® Core™ Processors
Intel® Iris™ Pro Graphics 580 for 6th Generation Intel® Core™ Processors
Intel® Iris™ Graphics 540 for 6th Generation Intel® Core™ Processors
Intel® Iris™ Graphics 550 for 6th Generation Intel® Core™ Processors
Intel® Iris™ Pro Graphics 6200 for 5th Generation Intel® Core™ Processors