Daily IT Matters [DIM]

Daily IT Matters, this is the place where I post my daily findings on IT.

Monday, December 01, 2014

Install Kodi on Google Nexus Player the easy way.

Yesterday I received my Google Nexus Player.



And after the inititial setup I checked the Google Play Store I installed the usual Netflix, TED, Pandorra. But I wanted to install Kodi formerly known as XBMC. I initially searched on the Internet and saw some tutorials with using USB devices, OTG cables, enabling Developer mode and Enabling ADB debugging and I thought this can be done easier, below are the steps I took to install Kodi on the Nexus Player.

  1. Enable Unknown Sources on the Google Nexus Player
  2. Install ES File Explorer on the Google Nexus Player through a web browser.
  3. Start the FTP Server in ES File Explorer on the Google Nexus Player.
  4. Download Kodi [Kodi 14.0 “Helix” – RC 1] copy the downloaded file to the Google Nexus Player.
  5. Start the install on the nexus player through the ES File Explorer.
Below in more detail.

  1. On the Nexus Player you need to enable "Unknown Sources" since Kodi is still not in the google play store.
     
    1. Go to settings.
    2. Scroll down and click on Security.
    3. Enable "Unknown sources" to allow installation of apps from sources other than the Google Play store note: This will also side load Kodi once installed)
       
  2. We are now going to install ES File Explorer on the Google Nexus player, we will do this from another device because the Play Store on the Nexus Player is crippled and does not have all the applications.
     
    1. Now on any device that has a browser and where you are logged in with the same account as on the Google Nexus Player click this link (this link will take you directly to ES File Explorer)
    2. Click Install or Installed
    3. From the drop down "Choose a Device" select "No carrier Asus Nexus Player"
    4. On the congratulations screen click OK.
       
  3. We are now going to start ES File Explorer and Enable FTP in it your Nexus Player will now be an FTP server on which we can put files.
     
    1. On the Google Nexus Player go to Settings | Device | Downloaded | Apps
    2. Click "ES File Explorer"
    3. Go to Network | Remote Manager
    4. Click "Turn On"
    5. You will now see an url like this: ftp://192.168.0.6:3721
       
  4. Now we are going to download Kodi and move the file to the Google Nexus Player.
     
    1. Go to Kodi.tv and go to Dev builds and Choose Android "x86"
    2. Save it to any download location of course remember it.
    3. In explorer not (interner explorer) type in the url you had in step 3.5  
      .
       
    4. Copy the downloaded Kodi apk file to the download folder.
       
  5. Now we are going to install the Kodi apk file on the Google Nexus Player.
     
    1. On the Google Nexus Player in the ES File Explorer app go to the download folder.
      Local | Home | Download
    2. Click the file "kodi-14.0-Helix_rc1-x86.apk" and select "install"
    3. You will be prompted again and you should choose "install" again.
    4. Once completed you will be prompted to choose done or open the app.
    5. That's it we've successfully installed Kodi on the Google Nexus Player.

Wednesday, July 30, 2014

Find user accounts who do not require Kerberos PreAuthentication

This is just a simple one.

I had to find users who did not had the preauthentication option checked.
Read more here: http://technet.microsoft.com/en-us/library/bb742516.aspx

Please note that I use samAccountType instead of the less efficient
(&(objectClass=user)(objectCategory=person))

Get-ADUser -LDAPFilter "(&(samAccountType=805306368)(useraccountcontrol:1.2.840.113556.1.4.803:=4194304))"

Thursday, February 14, 2013

How to stay ahead with your home pc security

This article is about security and how to minimize your exposure to malware / virusses / trojans.
Keep in mind that this article is written for the home user and not for the large companies with for example Checkpoint Firewalls with IPS blades, and with SCCM 2012 with integrated CSI, forefront etc....

This is about the average joe who wants to stay secure while browsing the World Wide (War) Web.

The first thing to achieve the above goal, is to keep you off from malicious sites who deploy trojans, try to run botnets etc etc.... for this I use OpenDNS.

  • Speed up your Internet experience
    OpenDNS’s 12 global data centers are strategically located at the most well-connected intersections of the Internet. Unlike other providers, OpenDNS’s network uses sophisticated Anycast routing technology, which means no matter where you are in the world, your DNS requests are answered by the datacenter closest to you. Combined with the largest DNS caches in the industry, OpenDNS provides you with DNS responses faster than anyone else.
  • Make your Internet more reliable
    With our extensive data center footprint and use of Anycast technology, the OpenDNS network has built-in redundancy ensuring zero downtime. SmartCache technology, an OpenDNS innovation, enables you to access sites that may otherwise be inaccessible due to authoritative DNS outages, providing you with the most reliable Internet possible.
  • Improve your security
    OpenDNS owns and operates PhishTank, the largest clearinghouse of phishing information on the Internet. OpenDNS incorporates PhishTank into its services to protect you from fraudulent websites that attempt to steal your personal information and money. In addition, OpenDNS provides protection against two of the most pervasive Internet security threats that continue to infect millions of users — Conficker, the largest botnet, and Internet Explorer exploits.
  • Gain visibility into your network usage
    OpenDNS’s reports provide you with visibility on your networks' Internet activity, giving you needed insight into how your Internet resources are being used.


RDP Authentication issues Windows 2008 R2

Today we had a nasty encounter with sudden access denied on RDP connection to our Terminal Server Farms.

The day started that users could not connect to our Navision environment, this environment constists of an Terminal Server farm with an SQL 2008 Cluster. After analyzing first symptoms we saw that the SQL Cluster had failed over but that the quorum disk was stil on the Node that had "sudden" issues.

Thus we gracefully brought the faulty node down through Cluster Manager and started it up again.
In the meantime we were notified that there were still issues, then we saw profile redirection errors caused by a faulty location and permissions of the user profile location. We left the profiles at default location and focussed on the permissions we fixed them, and users started to report that they could log in again.

But now problems started to appear out of now where users could not connect to our other Terminal Servers farms for other application, we where now more then 3 hours after the initial problems appeared.
While trying to find several causes for these issues we focused on the first symptoms that were reported, we should not have done that but that is with hindsight.


We focussed on Kerberos issues because we have a mixed 2003 and 2008 forest and 50 domains, we sometimes run into the infamous KDC ticket being to large. We now set it to 48000 as per microsoft recommendation for windows 2012 with its base http encoding that it no longer can be set at its largest dword value it can take.
Read this for Kerberos changes in 2012 it will save you in large environments.
http://technet.microsoft.com/en-us/library/hh831747.aspx

But we came to the conclusion it was not the rootcause, simultaniously we started to suspect group policy changes but checking the change date for all applied policies ruled that out rather quickly.

After pinpointing the problems to a single datacenter we realized what just had happened, it was the BlueCoat that was causing the problems, the day before it was put back in service after former issues.

Bypassing the Bluecoat solved the issues.....

pwhmmmmwwwwweeh.. what a day in the office

How to Upload to multiple stocksites at once for free with Adobe Lightroom [Part 1 of 2]

Ever since I've starting to upload my photo's to some microstock sites I always have been looking for the easiest and fastest way possible to upload them to the microstock sites I'm on.

The reason I upload my photo's to multiple microstock sites lies in the fact that you only can make some money if you upload either a lot photo's or some photo's to a lot of microstock sites. Since I don't have a lot of photo's to upload to microstock sites I choose the latter, I upload to a lot of microstock sites.

When you do the math it becomes obvious. Lets say I have 20 photo's that are good enough to upload to microstock sites and I upload them to 25 microstock sites I have effectively the same exposure as with 500 photo's But do it with 500 photo's and you reach a whopping 12500 photo's online. So in order to put in a year 12500 photo's online you only have to shoot 5 decent pictures in a weekend that you can upload to a microstock site.

I almost forgot to tell you how I came by the number 5, A year has 365 days divide that by 7 weekdays ~ 52 multiply that number by the days of a weekend 2 and you get 104 days. In 104 days you have to shoot 500 pictures to get 12500 pictures online. In fact you have to shoot 5 every weekend. That is more manageable than the sheer amount of 12500.

Requirements:

Photoshop Lightroom
Photoshop Lightroom Development Kit
Export Manager

Stocksites:







Tuesday, May 15, 2012

[Solved] Avira keeps it quiete about the mess they made...

Solution below

I was having some problem since yesterday that my DllHost.exe process was blocked by Avira.
I suspected that I was infected with some kind of worm, which is odd since I run several layers of security to prevent this.

Today I had enough and sought after a solution on the internet, I was dumbfounded to find this.

Please Note its in German and it published 10:44 +1 GMT (DST)


Sehr geehrter Avira Nutzer,

nach dem Produktupdate der Avira Software werden diverse Anwendungen als gefaehrlich eingestuft und von der Komponente ProActiv blockiert. Unsere Entwicklung arbeitet derzeit mit Hochdruck an einem automatischen Update zur Beseitigung des Fehlers. Damit Sie Ihren Computer wieder wie gewohnt benutzen koennen haben wir 2 Loesungsvorschlaege die wir Ihnen im Moment anbieten koennen:

Loesung A: ProActiv deaktivieren

1. oeffnen Sie das Avira Control Center
2. druecken Sie die Taste "F8" um die Konfiguration zu oeffnen
3. aktivieren Sie links oben den Expertenmodus falls dieser noch nicht aktiv ist
4. oeffnen Sie die Option "Echtzeit Scanner -> ProActiv
5. entfernen Sie den Haken bei "ProActiv aktivieren"
6. schliessen Sie das Fenster mit dem "OK" Button
7. starten Sie den Computer neu


Loesung B: ProActiv Ausnahmen erstellen

Hierzu haben wir bereits einen Eintrag in unserer Wissensdatenbank der die Vorgehensweise beschreibt:

http://www.avira.com/de/support-for-home…etail/kbid/1257

Wir werden Sie informieren sobald das automatische Update verfügbar ist um die Erkennung zu korrigieren. Danach können Sie ProActiv wieder über den selben Weg wie oben beschrieben aktivieren. Die Ausnahmen sind danach nicht mehr notwendig.
Stefan Berka
Avira Operations GmbH & Co. KG

Es werden keine unangeforderten Supportanfragen per PN beantwortet. Bitte nutzen Sie den ihrem Produkt entsprechenden Bereich im Forum.
There is no support for unsolicited PM requests available. Please use the board section which accords to your product.


*************************************

Solution is to manually update Avira (via the control center) and then do reboot.
I have no clue why Avira keeps playing the silent game here.




Friday, May 11, 2012


Const ForReading = 1

Dim arrTapes()
Redim arrTapes(1)
strPrevTapeNumber = "xxxx"

Dim objDictionary
Set objDictionary = CreateObject("Scripting.Dictionary")

'Reading Arguments from the commandline
Set args = WScript.Arguments
argTapesExportFile = args.Item(0)
argPoolName = args.Item(1)

Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objTextFile = objFSO.OpenTextFile(argTapesExportFile, ForReading)

Do While objTextFile.AtEndOfStream <> True
  strLine = objtextFile.ReadLine
  If inStr(strLine, argPoolName) Then
    strTapeNumber = Mid(strLine,InStr(strLine,argPoolName) - 7,7)
      if not inArray(arrTapes,strTapeNumber) then
        redim preserve arrTapes(ubound(arrTapes)+1)
        arrTapes(ubound(arrTapes)) = strTapeNumber
        wscript.echo arrTapes(ubound(arrTapes))
      end if
   End If
   strPrevTapeNumber = strTapeNumber
Loop

function inArray(a,value)
  for each v in a
    if v = value then
     inarray = true
     exit function
   end if
 next
end function

Restore Exchange 2003 Database from Dirty Shutdown

Friday, normally a very quiet day, today was going to be different than I had anticipated.

I got in the in office and overheard a collegue, talking with a sysadmin from a subdivision about an exchange server. Damn I knew it immediately it was the one from yesterday that wend down 30 times in 12 hours.
They had replaced the systemboard, and where now knocking on our doors for help because the Mailbox database wouldn't mount, and before I even got a cup of coffee I was on the phone and started the rdp session to the server. Our exchange environment consists of about 135 exchange 2003 servers. But the one I now needed to rdp to I knew the hostname already.

On the phone with the sysadmin I started the needed actions, and I've written them down so it maybe helps someone in the future.

This article explains all the steps you need to take to be a bring a exchange 2003 mailbox store that is in a "Dirty" Shutdown state back to life.


Actions performed for exchange 2003 dirty shutdown restore.


1. Bring the server gracefully down.

This to let exchange try to automatically forward the logs
into the store after the clean reboot.

2. Ran the following command to check the state of both mailbox store database and public folder database.

eseutil /mh "E:\Exchsrvr\FirstStorageGroup\PFStore1\PFStore1.edb"
eseutil /mh "E:\Exchsrvr\FirstStorageGroup\MBStore1\MBStore1.edb"

Output from the MBStore1 was mailbox state was "Dirty Shutdown"

And the Repair Count was 0 and the last fullbackup was from 5/9/2012 21:30:14

3. Ran the following command on the logs, to check if the log files are all ok, this to make sure a soft repair will work.

eseutil /ml "D:\Exchsrvr\FirstStorageGroup\Logs\E00"

Output was ok logs are valid, so we can start with a "soft repair"

4. Eseutil /r E00 /l "D:\Exchsrvr\FirstStorageGroup\Logs" /d "E:\Exchsrvr\FirstStorageGroup\MbxStore1\MbxStore1.edb"

Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after 44.62 seconds


5. Due to the error above I had to ignore streaming errors by adding the /i switch.

Eseutil /r E00 /l "D:\Exchsrvr\FirstStorageGroup\Logs" /d "E:\Exchsrvr\FirstStorageGroup\MbxStore1\MbxStore1.edb" /i

After this I started ESM and mounted both the mailbox store en public folder store without errors.

Wednesday, April 11, 2012

How to save your work from a system drive with Bitlocker

This is real small tip but a very crucial one.
When you have bitlocker on your systemdrive and somehow your windows installation becomes corrupt then this is the procedure on how to access your data still on the systemdrive.

1. Get the system drive physically out of your system.
2. Attach the drive to another system running windows.
3. When you want to access your data browse to the drive and access it like your reguraly do.
4. You will be prompted to type your PIN.

You can see that this only will work when you know your PIN.

Wednesday, January 27, 2010

New Virus causes Havoc!

http://www.eset.eu/download/ezimuse-remover

the reason I show you the below commands is that the remover executes these commands.
However there is an Error it doesn't stop the Service MStart first therefor sc delete will fail.

I hope this will help you


sc stop UnzipService
sc stop Mseu
sc stop MStart
sc delete UnzipService
sc delete Mseu
sc delete MStart
ren C:\Windows\System32\Mseus.exe Mseus.exe.vir
del /Q /F C:\Windows\System32\Drivers\Mseu.sys
del /Q /F C:\Windows\System32\Drivers\Mstart.sys
del /Q /F C:\Windows\System32\ainf.inf
del /Q /F C:\Windows\System32\tokset.dll
del /Q /F "C:\Program Files\Dump\Dump.exe"
Google