So I wanted to use my old XBox 360 Kinect as a WebCam for conference calls using either Skype or Microsoft Teams. Lots online about how this is possible but most posts didn't work as so old. Here is how I managed to get it working.
This forum had all the details (1st Post):
However I noticed you cannot use the latest SDK v2 to register the KinectCam.ax. You needed V1:
Once you install this version (uninstall all other versions first) you can then register the KinectCam.ax and the camera is now accessible in Skype.
However Microsoft Teams would still not see the camera. So for this I installed ManyCam and which used the Kinect Cam and was now usable in MS Teams and all other apps.
You can also adjust the angle of the camera using the file located at (hidden folder) config.ini:
Just change the [CameraElevationAngle]
e.g. I have it at CameraElevationAngle=9
Fresh install of Windows 10 with latest update on a new workstation and I couldn't get SQL Server 2016 Developer to install as it kept showing error:-
There was an error generating the XML document.
Error code 0x84B10001
Thought this was a bit strange as never noticed this before. I wondered if it was a permission issue, but all was fine as I was local admin. As I work remotely I checked and noticed my VPN to work was not connected. So I reconnected it and the install completed correctly. Therefore it looked like it was an issue due to not being able to contact the domain Active Directory (wish it would have just said that).
As a remote worker I needed to join my newly built Windows 10 PC to the domain using Windows VPN.
- First login to the machine as a local admin
- Setup a VPN to the company and connect
- Join the PC to the domain
- Log back in as local administator
- Connect VPN again, switch account
- Try logging on with your domain account and you will probably see this error:-
The Group Policy Client service failed the sign-in. The universal unique identifier (UUID) type is not supported.
If you log back into the local administator account you will notice the VPN has been disconnected which did not happen in Windows 7. The fix is simply to create a VPN that stays connected when you switch account.
So login again as the local administrator and run powershell as administator, then enter:-
Add-VpnConnection -Name NAMEOFVPN -ServerAddress VPNADDRESS -AllUserConnection $true -SplitTunneling $true -AuthenticationMethod MSChapv2 -TunnelType Automatic -EncryptionLevel Required -PassThru
Connect to the VPN which using NAMEOFVPN you used in the PS Script.
Switch accounts and try to login as a domain user and you will not see the error again.
On my HP Windows 10 Laptop I was using Hyper-V and WiFi and the host Windows 10 PC was crashing with:-
The Windows 10 Laptop has been find so it seemed to be something to do with Hyper-V. Looking online it seemed related to either to Memory (built-in memory on this laptop so unlikely) or driver issues (more likely).
I guessed it might be the WiFi driver which was an Intel Dual Band Wireless-AC 3160. So I updated the driver and now no more crashes, phew.
To do this fix.
- Open Control Panel
- Security and Maintenance
- Administrative Tools
- Computer Management
- Open "System Tools" and select "Device Manager"
- Open "Network Adapters"
- Select the Wireless adapter, in my case "Intel(R) Dual Band Wireless-AC3160"
- Right click "Properties"
- Click "Driver" tab
- Click "Update Driver"
- Click "Search automatically for updated driver software" and let it download a new driver if it finds one
- Restart and all should be well
So setting up a new home server using latest Windows Server 2012 R2 Essentials. Tried to connect to the domain using the Server Web Connect e.g. http://[ServerName]/Connect and I can see the webpage and download the connection exe e.g. ComputerConnect[ServerName].exe but I get the following error when running it:
Windows Server Essentials Connector Configuration Wizard
An Unexpected error has occurred. To resolve this issue, contact the person responsible for you network.
Seems like the Web Connect doesn't yet work for Windows 10. So you need to install the KB from Microsoft and install it on your Windows 10.
Windows Server Essentials Connector for Windows Server 2012 R2
Once installed in Windows 10 you have a new App.
Click Start, All Apps
Scroll down to "Windows Server Essentials" and run "Windows Server Essentials Connector Configuration Wizard". Then run through the setup and all should be good.