# Node-Red installation fail Windows Server 2019 via RDP

**URL:** <https://discourse.nodered.org/t/node-red-installation-fail-windows-server-2019-via-rdp/58899>\
**Category:** General\
**Created:** [23 February 2022 23:11 UTC](https://discourse.nodered.org/t/node-red-installation-fail-windows-server-2019-via-rdp/58899 "2022-02-23T23:11:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hardillb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hardillb/32/12373_2.png) [@hardillb](https://discourse.nodered.org/u/hardillb)\
**Post date:** [24 February 2022 15:29 UTC](https://discourse.nodered.org/t/node-red-installation-fail-windows-server-2019-via-rdp/58899/4 "2022-02-24T15:29:01Z")

</div>

No, nothing on npm will help you here.

Best I can do is suggest you do a local (not global) npm install into a known directory

```auto
mkdir temp
cd temp
npm install node-red

```

Then zip up the temp directory copy it over to the unconnected machine and unzip it.

You can then try starting it by running:

```auto
cd temp
node_modules\.bin\node-red.bat

```

But you are going to have other problems, once installed it will be hard to install any extra nodes as the catalogue manager will not work.

You will need a connected machine to install the modules then zip up the content of the userDir and copy that over as well.

I believe others have got this sort of thing to work, but it would be a lot easier if you could set the machine up with it connected to the internet first, then move it to the air-gapped network.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-installation-fail-windows-server-2019-via-rdp/58899)._