Community Discussions and Support
Note on Pegasus Network Installation

Having just upgraded to V4.71, I noticed that the install exe, does not enable you to select a network location, either by mapped drive or Network Browsing.

I do not think that this is a Pegasus problem, but is more likely to be the problem with Network Browsing that has appeared since Microsoft's November Major update For Windows 10 (Version10586).

This problem has occurred before with Microsoft's lamentably untested updates, and is even more acute now with Windows 10, where you are not even told what it is updating, or have any choice whether you want the updates! If you have the Enterprise versions you have more control over how  the updates are delivered.

The solution that works for Pegasus Network Install is to use the explicit IP based locator for the resource when you are asked for the installation location. Do not use Browse as that is where the problem described above will prevent you from seeing your network device. Instead enter the URL in the form:

\\192.168.xxx.xxx\Network resource name\Pegasus Folder name\Programs

For example in our case this is:

\\192.168.1.21\SharedDocs\PegMail\Programs

This is why I always setup mapped shares to explicit  IP number based resources as problems have always existed with Microsoft's Master Browser service, (this is supposed to resolve the Network Names to devices). Mapping drives in this way avoids this problem.

I would be interested to know if others running network versions have the same problem, and, if so, under which versions of Windows.

For the record, we are running Windows 10 Pro x64 and we use ARM based NAS devices (QNAP).

<p>Having just upgraded to V4.71, I noticed that the install exe, does not enable you to select a network location, either by mapped drive or Network Browsing.</p><p>I do not think that this is a Pegasus problem, but is more likely to be the problem with Network Browsing that has appeared since Microsoft's November Major update For Windows 10 (Version10586).</p><p>This problem has occurred before with Microsoft's lamentably untested updates, and is even more acute now with Windows 10, where you are not even told what it is updating, or have any choice whether you want the updates! If you have the Enterprise versions you have more control over how  the updates are delivered.</p><p>The solution that works for Pegasus Network Install is to use the explicit IP based locator for the resource when you are asked for the installation location. Do not use Browse as that is where the problem described above will prevent you from seeing your network device. Instead enter the URL in the form:</p><p>\\192.168.xxx.xxx\Network resource name\Pegasus Folder name\Programs</p><p>For example in our case this is:</p><p>\\192.168.1.21\SharedDocs\PegMail\Programs</p><p>This is why I always setup mapped shares to explicit  IP number based resources as problems have always existed with Microsoft's Master Browser service, (this is supposed to resolve the Network Names to devices). Mapping drives in this way avoids this problem.</p><p>I would be interested to know if others running network versions have the same problem, and, if so, under which versions of Windows.</p><p>For the record, we are running Windows 10 Pro x64 and we use ARM based NAS devices (QNAP). </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft