Ok, check it, you want to upgrade your Nexus 5 to Lollipop 5.0 (apparently this work with the Nexus 7 and 9 as well).
First, you will need Nexus Root Toolkit tool for your desktop – I’m running windows 8.1 for my sins but it may work elsewhere – other OSs are available. You can download the tool for windows here: http://www.wugfresh.com/nrt/
Once you’ve got the Nexus Root Toolkit install it! What am I? Your dad?
Ok, once you have the root kit installed. You need to put your phone into ‘developer mode’. Settings -> about phone -> tab ‘Build number’ a bunch of times and it will pop up and say you’re a developer. Now when you go to settings you’ll see Developer options. Go in here and enable USB Debugging. Ok you’re all set.
Open the Root toolkit on your desktop and plug your device in.
Follow the order.
1. You need to backup. Failure to do so may result in the loss of cat pictures!
2. Then unlock
3. The flash the device. You will have to download the Lollipop software here.
And that’s pretty much it. If you need more help check out this guys video tutorial: here
I haven’t blogged for a while. It’s been a bit hectic at this end. I’m no longer working as a sysadmin. I’m now working as a project manager for UC and SCCM solutions.
Anyway, just moved house and am in the process of configuring SabNZDB and NZBDrone. Rather that having to remember the ports for all of these different services e.g. http://domainname.com:8989 I’d like to just remember a short name for each service e.g http://domainname.com/sab or http://domainname.com/drone
Right, lets get started:
1. Setup SAB and Drone as you usually would but rather than opening up ports 8080 and 8989 (Default SAB and Drone ports ) only open up port 80 to the server.
2. Download and install XAMPP. I’m running this on a little Windows 7 box. Here is the link: https://www.apachefriends.org/download_success.html
3. Once its installed and is up and running stop the Apache service from the application tool.
4. Once you’ve done this go to the config location for Apache (Default is: C:\xampp\apache\conf) now find the httpd.conf file and open it with notepad.
5. Ive added these two sections at the bottom of the file:
deny from all
allow from all
deny from all
allow from all
6. Once you’ve done this and save the files you should be able to get to Sab and Drone from outside your firewall.
E.g http://mydomain.com/sab and http://mydomain.com/drone.
One additional note with NZBDrone
You may see just NZBDrone Ver. If you do, do this:
- Go to Settings -> General
- Set URL Base to desired path
- Save settings
- Restart (Restart as administrator on Windows)
- Donate ❤
Let me know if you need further details
Exporting Mailboxes with Exchange Server 2010 SP1
Exchange Server 2010 Service Pack 1 introduced a new method for exporting mailboxes called Mailbox Export Requests. This new method replaces the previous Export-Mailbox command.
Before we look at how to create a new mailbox export request in Exchange 2010 SP1 there are a few things that you should understand.
Firstly, no accounts are granted the rights to export mailboxes by default. You need to explicitly grant these rights, even to accounts that are organization administrators.
Secondly, the mailbox export request is processed by the Client Access server role. Because multiple Client Access servers can exist in a site the request could be processed by any one of them. To ensure that the path to the export PST file is valid for any Client Access server it has to be a UNC path to network share, not a local path.
Granting User Rights for Mailbox Exports in Exchange 2010 SP1
The first step is to grant the right to export mailboxes to an account in your organization. In the Exchange Management Shell run the following command.
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User Administrator
If you’re logged with that user already simply restart your Exchange Management Shell session to be granted access to the new cmdlets.
Creating a Network Share for Mailbox Exports in Exchange 2010 SP1
Next we need to create the network share that will be used as the file path for the exported PST files. All that is required here is a network share that the Exchange Trusted Subsystem group has read/write permission to.
Exporting a Mailbox with an Exchange Server SP1 Mailbox Export Request
With everything configured properly we can now use New-MailboxExportRequest to start the mailbox export. The only two required parameters for the command are the file path to the export PST file, and the name of the mailbox to export.
[PS] C:\>New-MailboxExportRequest -Mailbox “adrian.chatto1” -FilePath \\dserver\pst\davelister.pst
To view the status of the request uses the Get-MailboxExportRequest cmdlet.
Name Mailbox Status
—- ——- ——
MailboxExport KPS/Company/Users/Head of… InProgress
You can also see more detail about the mailbox export request with Get-MailboxExportRequest.
An easy way to see the progress of all mailbox export requests is to pipe Get-MailboxExportRequest into the Get-MailboxExportRequestStatistics cmdlet.
[PS] C:\>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
Name Status SourceAlias PercentComplete
—- —— ———– —————
MailboxExport InProgress Adrian.chatto1 20
Exporting an Archive Mailbox with Exchange Server SP1 Mailbox Export Request
You can also export a user’s Personal Archive using mailbox export requests simply by adding the -IsArchive parameter to the command.
[PS] C:\>New-MailboxExportRequest -Mailbox davelister -FilePath \\dubbur-fs01\pst\davelister.pst -IsArchive
For a few weeks, my Business Intelligence Architect has been complaining that the SQL Reporting server has been running slowly.
At first, we thought that the services seem to “go to sleep” and need awakening once a day. However, it seems to run slow more than once a day. After reading this article:
it seems that the idle processes “goes to sleep” after 20 minutes. After the service has gone to sleep, the time consuming handshake has to take place again next time the report it run. This can take up to 60 seconds and gives the impression to the user that the system is slow.
It is possible to increase this “idle time out” limit. We have increased it to 120 minutes (someone should run the report at least once every 2 hours, keeping the service alive). We didn’t want to increase it further than this as we are not sure what effect this may have on the server.
Here is how we made the change on IIS 6:
Restart the Windows Server 2008 computer, and log in to a Windows Server 2008 computer Administrator account. Click “Start,” and select the “Search” box. Enter “%WINDIR%\system32\lserver” in the “Search” box, and press “Enter.” The “Lserver” window will appear.
Right-click on the “TSLIC.edb” file, and click “Rename” in the menu that appears. Enter “tslic.prior” in the name box, press “Enter” and then reboot the computer.
Read more: How to Reset a 120-Day Terminal Server Timeout | eHow.com http://www.ehow.com/how_7543547_reset-120day-terminal-server-timeout.html#ixzz2Ihve2dXT
The photo must be 96×96 and less than 10k. Photoshop can do this
Import-RecipientDataProperty -Identity “USERNAME” -Picture -FileData ([Byte]$(Get-Content -Path “C:\temp\PICTURENAME.jpg” -Encoding Byte -ReadCount 0))