I tested successfully with Linux by using Avahi(Bonjour) and Netatalk(AFP) to provide network storage to Mac OS X seamlessly (as like Time Capsule).
I want to make one another question for Windows 7. As I searched Windows 7 uses PnP-X and UPnP to provide Bonjour like zero configuration experience. What I want to achieve is:
Use Samba on Linux to share one folder
Publish this shared folder as NAS service by using PnP-X and UPnP
If a Windows 7 PC attached to the LAN which have the Linux it will discover the NAS service on Linux
Windows 7 automatically initiate PnP install process and new disk volume will be appeared on Explorer without any user intervention. This new volume is actually Samba shared folder from Linux
Do you think this scenario is achievable by using PnP-X and how can I do this?
Best Regards
I checked about it by myself.
PnP-X uses SSDP (Simple Service Discovery Protocol) of UPnP to publish network attached device to Windows clients in local network. By using XML configuration file of SSDP, device can let client knows PnP H/W ID.
From Windows 7, user can see PnP-X enabled device from network explorer. User can select install context menu to initiate device driver installation of PnP-X device.
PnP driver installation depends on H/W ID which is known by SSDP XML configuration file.
To implement this scenario on Linux O.S., I can use GUPnP library to support SSDP notify.
Also, I need to implement proper INF file and device driver.
BR,
Wonil.
Related
We have a Windows iot core device on a network that doesn´t have internet.
We want to update the software running on this device, we have another computer running Windows 10 on the same network, is there some service or software we can install on the Windows 10 computer, so that we can update the application running on iot device.
It should be possible to do the update through code.
Thanks
Anders
At the moment, we can update applications on Windows IoT Core via following ways.
Using Microsoft Store
Using Device Update Center
Using Azure IoT Device Management
Using OMA-DM
More details please see this document. The first three ways in above list need internet.Using OMA-DM seems an option in your scenario, the OMA-DM interface is supported in Windows 10 IoT Core and any OMA-DM compliant management solution can be used to install and update applications. You may not need a connection to the internet to use license. In this way, you need to configure a OMA DM server.
In addition, you can also create a custom service for updating the application. You can serve the application package in your server, the devices can load the package's url. And then use PackageManager to update the app.
Here is a topic about how to update the app from USB drive. You can refer to the implement. The difference is packageLocation, in that scenario it is a removable storage, while in your scenario you need to use network share instead.
I'm developing a website in VS on a Windows Server Azure VM, and remoting in to do my work through Microsoft Remote Desktop for Mac.
The website needs to access a webcam, but I don't have any webcam on the remote windows server!
Is there any way to allow the remote windows server where I'm developing to see my local webcam through Microsoft Remote Desktop, as my local machine is a Macbook Air?
Maybe there's another remote tool for Mac that will allow this? One I have to pay for?
Looking at the settings for Microsoft remote destop for Mac version 10.2.4 how can I set the local resources for USB connections? I don't even see a option for Usb device, just printers, clipboard and Smart cards.
All I see is this below with no options for USB connections
as of Dec 2018:
no, it is simply not possible with the latest Mac beta RDP Client
and a still open demand from user voice
The feature of USB redirection is part of so called RemoteFX and a feature of RDS.
From server side it is possible since Windows Server 2012, newer Versions improved it.
Windows Client (mstsc.exe or remote desktop client) support the USB and Video mapping for since ages, but of course negotiating with the server which features are possible and allowed.
this link gives a nice overview mosty without covering non-Windows:
https://workspot.zendesk.com/hc/en-us/articles/214248563-Configuring-USB-Redirection-with-RemoteFX-in-Workspot
to be afraid, the MS Mac client only supports the usual redirections like audio, printer, clipboard and drive mappings.
there are obviously other RDP clients out there, with experimental USB and webcam redirecting:
at least there is freeRDP which may also run on a Mac
does anybody know if a SNMP service exists for Windows 10 IoT Core (running on RaspberryPi3, preferred a C# source), so that I can query the Device like a PC/Server?
Normally I would say that WMI is the technology you should use if you want SNMP-like functionality from Windows, but WMI doesn't exist on Windows 10 IoT Core.
SNMP also doesn't exist on Windows 10 IoT Core.
There are open source SNMP servers and clients written in C#, and I don't know how easy these will be to port to UWP. Might be easy, might not be.
Yes on windows 10 SNMP agent exits.
By default that service is not installed, we need to install manually SNMP service on windows 10.
Please visit settings of your computer to install SNMP service on windows 10
Source:
http://www.bytesofgigabytes.com/snmp-protocol/how-to-install-snmp-service-in-windows-10/
I'm manufacturing a device that connects to my computer using Bluetooth and then a desktop Java app uses the Bluetooth connection to send serial data to the device which is then displayed.
When I try to connect my device to windows 7 it successfully finds and pairs with it creating a Bluetooth link on a COM port. This link can then be used by a serial prompt (used for testing) or my Java application. It works initially however soon after windows drops the connection and the only way to reconnect is to delete the device within devices and printers and then reconnect.
This seems to be a known problem with windows bluetooth so I decieded to use a third party Bluetooth application. I downloaded and tried Toshiba's Bluetooth Stack and it was able to add a Bluetooth device and keep a stable connection which works great however this only works for Toshiba computers without getting a cracked version.
This device is commercial and can't be sold with cracked versions of software. Has anybody experienced the same problems or not in other operating systems and has any solutions of advice as that would be a tremendous help.
This is not a good idea/method to use the COM ports generated by Windows, it's not working fine and not reliable in any scenario ; you should use Bluetooth Sockets instead.
Using Toshiba or Widcomm or BleuSoleil won't help: under Win7, all dongles are now trying to use the Microsoft Stack, not their own implementation.
We develop a custom Windows CE-based device. To connect this to the PC via ActiveSync / Mobile Device Center, we have to set up entries so that the WCE USB Serial Host (wceusbsh.sys) recognises our Vendor ID (Vid) and Product ID (Pid).
To do this, to date, we have distributed a modified version of wceusbsh.inf and wceusbsh.sys: when the user first connects the device then ActiveSync basically says it does not recognise the device, and the user is asked to identify a driver for it. If they now point at the location where they've stored our wceusbsh.* files then all is well. However this is pretty clunky.
What we really want is a slick way to do this, preferably by running an installer which just gets everything ready, so that as soon as the device is plugged in it is recognised by wceusbsh.sys.
Any clues how to do this? There seem to be a ton of registry entries which relate to WCEUSBSH, and it's not clear how these are set: just "installing" the .INF file doesn't seem to allow for setting them all, so it does look like ActiveSync reads the .INF file and then adds some more information before appending the new info to the Registry.
Thanks
Well, in case anyone else comes looking for an answer to this, we managed to do it via this link from MSDN WinUSB (Windows Driver Kit). We now have a driver install program which sets up USB / Mobile Device Center so that when you plug in the CE device it is recognised correctly.