Do you manage multiple KODI boxes? For family or a few in your house. Annoying and of my own making I manage them for all my family. The biggest problem is if their is a update usually a ADDON will stop working. If your streaming or just simply updating this becomes a massive pain. 

I usually try to setup KODI using s specific theme so I can walk each family member through navigation etc if they have problems. 

Want them all the same? And updated from a single source here is how. 

KODI and SYNCTHING your centralized solution.

​

STEP 1: 
Download the SCP driver packaged here. You can get it elsewhere I don't really care where. The link is from my one drive. 

STEP 2: 
Under program files, least this is where I placed mine, you can place the extracted folder anywhere. 
I create a folder called PS3  c:\Program Files\PS3 

Place the extracted zip file in that folder - the default extracted name is "SCPServer"

STEP 3: 
Before proceeding plug in your PS3 into the USB port on your computer. This is needed to install the device drivers for it.

​Go into the "BIN" sub folder and you will see several files and exe's like so.

First EXE you want to run is "SCPDriver.exe"

STEP 4:  Once you open SCPDriver click on install (NOTE click forced install if everything doesn't install). You should get a UAC popup or "Trust Applicatio" pop up. Say yes to everything and continue.  It should show both USB driver and few other packages installed.  Most important it should include the bluetooth driver in the install. 

STEP 5: FINAL step when you remove the PS3 from USB it should auto sync with your bluetooth. Please note this converts your bluetooth into a dedicated connection, other blue tooth devices will no longer work. You must then uninstall using the application again to remove drivers. Hope this helps. Happy gaming. 

It beings here asking for the IP address or hostname of the remote computer, you can even use "localhost" if you want to test it on your local system.

Next it gather some WMIC info on the machine your removing it from, current user, make, model, serial number etc. This helps you keep track and know you are running it on the correct machine. You can still exit at this point before it runs the uninstall command. 

After it gets the WMIC product installation ID for "Symantec Endpoint Protection" it runs the MSIEXEC with the install string to uninstall the software. Once complete it does another WMIC get to see if the product is still listed as installed, then prompts you to try again if it still shows as installed or exit. 

I have included a download link here

Any questions please feel free to contact me. 

My first attempt at setting up a migration from exchange 2003 to office 365.
Once you get your account setup within Office 365, you begin the migration portion. 

I followed this guide which help quite a bit. 

MIGRATE FROM EXCHANGE TO OFFICE 365 
I ran into a few hiccups that caused some issues. 
First being that most mailboxes during the BATCH (You run this to sync exchange with office 365)
failed, would not sync. 

Using Microsoft support - for the migration I used the local administrator account which had its own exchange mailbox and was local domain admin. Microsoft explained this is why mailboxes are failing and had me choose a domain user with domain admin and exchange admin privileges. My test user account I added to both domain and exchange full access privileges. 
We deleted the batch and started a new one using my "Test User"

Again the batch failed even with the change to "Test User" even with Microsoft tech support on this I found the issue on my own. Some older mailboxes contained white space in their Alias in AD. I went through and cleaned up the mailboxes, trashed the BATCH job on office 365 and started over. 

This time the batch move more mailboxes then the first time around but still several that were important failed. Using Microsoft support yet again. We connected to the 2003 exchange server and started checking user accounts on the ones that failed. 

ADSI EDIT - we connected to the server and dived into the users. Under public delegates and BK delegates, we found disabled users - once we removed them and restarted the batch it moved further users over.  

In the end I had to do some manual moving of users email as couple users would not move, Microsoft unfortunately washed there hands of it and I had to move on as the migration was taking way too long. 

Currently I manually moving sub folders within the inbox of the old exchange mailbox. 
The rest went well and I am glad to be off the old exchange server, however I found the support from Microsoft lacking in knowledge as they tried to figure out why the migrations were failing.

The one mailbox I wanted to move without issues was of course the owners mailbox. In the end I had to move 140 sub folders in his old inbox. This took better part of a hour which could be better served setting up the remaining users.