IT Archive - Pixelfriedhof

Workaround: Error message “An internal error has occurred” on RDP Remote Desktop Connection

megaadmin — Wed, 18 Sep 2019 18:15:28 +0000

Description of a workaround if the error message “An internal error has occurred” appears when opening an RDP connection.

Symptom:

When you open a Remote Desktop connection from a client to Windows Server 2012, you receive an “Internal error occurred” error message.

The connection setup is neither possible via IP address nor via the DNS name of the server.
The connection is interrupted before authentication.

The connection to the server can either not be established by a single client or not by a group of clients.

Assumption/Background:

The Remote Desktop Session Service (Termservice.exe) is in a non-regular state.
The Remote Desktop Session Port is used by another program.
A self-signed RDP certificate is corrupt.
A self-signed RDP certificate is not provided by the server during connection establishment.

Workaround:

Restart the service for the terminal service if there is still access to the server.

If there is no more access to the server, restart the entire server or the VM.

Links:

https://docs.microsoft.com/de-de/azure/virtual-machines/troubleshooting/troubleshoot-rdp-internal-error

Now something to laugh at for the admin…

Keine Produkte gefunden.

All the links in this text are Amazon Affiliate Links, and by clicking on an affiliate link I will earn a percentage of your subsequent Amazon purchases. However, this circumstance does not influence the background of my product recommendation. This product recommendation is independent, honest and sincere.

Bei allen genannten Links handelt es sich um Amazon-Affiliate-Links. Durch einen Klick auf einen Affiliate-Link werde ich prozentual an Euren darauf folgenden Amazon-Einkäufen beteiligt. Dieser Umstand beeinflusst aber nicht die Hintergründe meiner Produktempfehlung. Diese Produktempfehlung erfolgt unabhängig, ehrlich und aufrichtig.

Der Beitrag Workaround: Error message “An internal error has occurred” on RDP Remote Desktop Connection erschien zuerst auf Pixelfriedhof.

How to: The IT-Departments advent wreath

megaadmin — Sat, 25 Nov 2017 13:11:00 +0000

A few years ago I came across an Advent wreath made of old RAM bars on 9gag. I found the idea quite nice, the implementation was rather moderately detailed. Reason enough to take matters into your own hands.

First of all, we need memory. I recommend to buy relatively large modules, so that we can use the maximum amount of memory per bar to reach the maximum amount of memory in the final result. 8 GB per bar should be the undersize.
You should also pay attention to the timings, so that each bar is timed the same, otherwise you will have performance problems later on. Buy at least DDR4-2800, CL 17 is recommended. You will need about 30 bars, I recommend this one here http://amzn.to/2jmpl6U.

Bullshit. Just buy some old rubbish from Craigslist / ebay.

To make sure that everything is nicely connected in a ring-shaped way “knot” the bars in a ring-shaped way with flexible wire, see blue circle. All in all, you knot three circles that vary slightly in size.

You then lay these three circles on top of each other and interleave them a little bit into each other and solder the rings to each other (pink circle in the first picture). Also tie them within the same ring with strong wire, for example from ground wires. If you are not sure how often you should solder the bars together, then listen to my wise words:”A lot helps a lot” and “more is always better” – this does not apply to Tinder acquaintances.

When this is done, tie a colorful LAN cable to a nice loop and attach it with cable ties at the top (or anywhere else) to the RAM wreath. Now we glue the beautiful WAGO clamps with hot glue on the wreath. Here I have used the connectors in orange and yellow, which are pretty colorful and hold well on the bars.

WAGO 2273-203 orange: http://amzn.to/2Ac6DqQ
WAGO 2273-205 yellow: http://amzn.to/2k1Ttsx

We then hang our extremely high-quality mini Christmas tree balls into these clamps by attaching them to the connectors with a cable core.

Extremely high quality mini Christmas tree balls: http://amzn.to/2jV1Buy

Then we’ll get old keyboards. From this we take the keys for a nice Christmas message. Depending on how many keyboards you want to sacrifice, you have the following options:

MERRY XMAS – requires two keyboards (because of the bloody “R”)

MERRY CHRISTMAS – requires three keyboards (because of the bloody “R”)

MERRY CHRISTMAS YOU FILTHY ANIMAL – requires three keyboards (because of the bloody “R”, the Y, the I and because of M) This variant is characterized by the best ratio between usable keys per used keyboard, but may be NSFW.

Anyway, as a carrier for the keys we cut a piece of wood which we paint professionally so that it doesn’t look completely shitty when you look at the finished Christmas wreath from the side later on.

Then we glue our keys to it with hot glue. The complete carrier is glued to one of the RAM bars at the bottom of the wreath.

Finished – decorate beautifully, take kitschy photo and then off to Instagram with the thing:

Thank you for watching and a lot of fun when building. Next time, I’ll show you how to build a plug that can be used to quickly reset all electrical devices with a network connection to their factory settings:

Bei allen genannten Links in der Videobeschreibung handelt es sich um Amazon-Affiliate-Links.Durch einen Klick auf einen Affiliate-Link werde ich prozentual an Euren darauf folgenden Amazon-Einkäufen beteiligt. Dieser Umstand beeinflusst aber nicht die Hintergründe meiner Produktempfehlung. Diese Produktempfehlung erfolgt unabhängig, ehrlich und aufrichtig.

Der Beitrag How to: The IT-Departments advent wreath erschien zuerst auf Pixelfriedhof.

What is the difference between IUSR and IIS_IUSRS?

Daniel Beckemeier — Tue, 01 Dec 2015 18:28:45 +0000

Which user actually needs access to the directory from which a website is hosted for the IIS? The IUSR or IIS_IUSRS? Actually it is quite simple…

If requests from the Internet are forwarded to the IIS, they are usually made anonymously. This means that the server notices that someone wants to access a certain resource, but of course does not know exactly who. In order for these anonymous users to be able to access files within a site, they must of course have the appropriate rights. All anonymous requests are made within the IIS with the user IUSR.

However, there are other situations in which access to the contents of a site or application is necessary. For example, if the so-called application pools want to access a site or application. This is often the case with web portals or web applications. Application pools are quasi framework conditions for the execution of certain frameworks, such as .NET or ASP. And each application pool has its own user. Since it would now be very time-consuming administratively to consider each individual application pool user individually when assigning rights, the IIS_IUSRS group was created. Yes, that’s right, that’s a group, you can tell by the last letter “S”, which indicates the plural.

Microsoft IIS 10.0 Cookbook: Task-oriented recipes to manage your web server with ease (English Edition)*

Khan, Ashraf (Author)

If you want to know more about who is behind the group IIS_IUSRS, you can call the IIS_IUSRS in the node “Local Users and Groups”, in the submenu “Groups” and have the members displayed by taking a look at the computer administration.

Der Beitrag What is the difference between IUSR and IIS_IUSRS? erschien zuerst auf Pixelfriedhof.