If you’re a user of those right-click “Command Prompt Here” context menu utilities… I just updated my Command Prompt Here Generator with a developer prompt for Visual Studio 2015. Head over there to get an installer for “VS2015 Prompt Here” (or any other prompts you might be interested in).
UPDATE 7/8/2015 - All current documentation for my media center and home network is at illigmediacenter.readthedocs.io.
Way back in 2008 I put up an overview of my media server solution based on the various requirements I had at the time - what I wanted out of it, what I wasn’t so interested in.
I’ve tried to keep that up to date somewhat, but I figured it was time to provide a nice, clean update with everything I’ve got set up thus far and a little info on where I’m planning on taking it. Some of my requirements have changed, some of the ideas about what I want out of it have changed.
My hardware footprint has changed a bit since I started, but I’m in a pretty comfortable spot with my current setup and I think it has a good way forward.
I use a fairly sizable combination of software to manage my media collection, organize the files, and convert things into compatible formats.
VIDEO_TS images in the past. It works really well for that. These rips easily feed into Handbrake for getting MP4s.Videos are organized using the Plex recommendations: I have a share on the Synology DS1010+ called “video” and in there I have “Movies,” “TV,” and “Home Movies” folders. I have Plex associating the appropriate data scrapers for each folder.
/videos
/Home Movies
/2013
/2014
/20140210 Concert 01.mp4
/20140210 Concert 02.mp4
/Movies
/Avatar (2009).mp4
/Batman Begins (2014).mp4
/TV
/Heroes
/Season 01
/Heroes.s01e01.mp4
/Heroes.s01e02.mp4
You can read about the Plex media naming recommendations here:
Audio is kept auto-organized in iTunes: I just checked the box in iTunes to keep media automatically organized and left it at that. The media itself is on a mapped network drive on the HP MediaSmart server and that works reasonably enough, though at times the iTunes UI hangs as it transfers data over the network.
Photos are organized in folders by year and major event: I’ve not found a good auto-organization method that isn’t just “a giant folder that dumps randomly named pictures into folders by year.” I want it a little more organized than that, though it means manual work on my part. If I have a large number of photos corresponding to an event, I put those in a separate folder. For “one-off photos” I keep a separate monthly folder. Files generally have the date and time in YYYYMMDD_HHMMSS format so it’s sortable.
/photos
/2012
/2013
/2014
/20140101 Random Pictures
/20140104_142345 Lunch at McMenamins.jpg
/20140117_093542 Traffic Jam.jpg
/20140307 Birthday Party
/20140307_112033.jpg
/20140307_112219.jpg
Picasa works well with this sort of folder structure and it appears nicely in DLNA clients when they browse the photos by folder via Plex.
My main router is a Netgear WNDR3700v2 and I love it. I’ve been through a few routers and wireless access points in the past but this thing has been solid and flexible enough with the out-of-the-box firmware such that I don’t have to tweak with it to get things working. It just works.
I have wired network downstairs between the office/servers and the main TV/PS3/Xbox 360/HTPC. This works well and is pretty much zero maintenance. I have two D-Link switches (one in the office, one in the TV room) to reach all the devices. (Here’s the updated version of the ones I use.)
The router provides simultaneous dual-band 2.4GHz and 5GHz wireless-N through the house which covers almost everywhere except a few corners. I’ve just recently added some Netgear powerline adapters to start getting wired networking upstairs into places where the wireless won’t reach.
This setup works pretty well so far. I’m really enjoying the accessibility of my media collection and I find I’m using it even more often than I previously was. So where do I go next?
A few months back Cory Doctorow stopped by the local library and did a great talk on security and copyright issues. Very cool stuff which inspired me to look into how to secure my public/open wifi usage.
I have a Synology DS1010+ with a ton of helpful packages and features on it, so that seemed like the best place to start. It took a while, but I got it. I’m going to show you how.
Truly, Synology has made this super easy. I’m not sure this would have been something I could have done nearly as easily without that device and the amazing Diskstation Manager “OS” they have on it. If you haven’t got one of their NAS devices, just go get one. I’ve loved mine since I got it and it just keeps getting more features with every DSM release they put out.
So, with that, the general steps are:
I’ll walk you through each step.
Don’t skim and skip steps. I can’t stress this enough. Getting this up and running requires some virtual “planets to align” as it were, so if you skip something, the process will break down and it is kind of tough to troubleshoot.
You need to set up user accounts for people accessing the VPN. Chances are if you have your NAS set up already, you have these accounts - these are the same accounts you use to grant access to NAS files and other resources. There is a nice detailed walkthrough on the Synology site showing how to do this.
Now you need to set up your Synology NAS so you can access it from outside your home network. This is accomplished through a service called “dynamic DNS” or “DDNS.” But you don’t really need to know too much about that because, built right into the DSM interface, is a program called “EZ-Internet” that will do all the work for you. For the easiest solution, you’ll need to set up a user account with Synology, but that’s free… and if you use their DDNS system (a “synology.me” domain name) then that’s also free. They have a really super tutorial on getting this set up. Focus specifically on the EZ-Internet part of the tutorial - the QuickConnect stuff is neat and good to set up, but it won’t work for VPN usage.
It took me something like (seriously) five minutes to get this part working from start to finish. Some of the steps may seem “scary” if you’ve not set it up before, but Synology has made this really painless and if you don’t know what to do, accept the defaults. They’re good defaults.
When that’s done, you’ll see your DDNS setup in the Synology control panel under “External Access.”
Next, install the Proxy Server and VPN Server packages using the DSM Package Station package manager. Installing packages is a point-and-click sort of thing - just select them from the list of available packages and click “Install.” Make sure you set them as “Running” if they don’t automatically start up. Once they’re installed, you’ll see them in the list of installed packages.
Let’s configure the proxy server. From the application manager (the top-left corner icon in the DSM admin panel) select the “Proxy Server” application. There isn’t much to this. Just go to the main “Settings” tab and…
You can optionally disable caching on the proxy server if you’re not interested in your Synology doing caching for you. I didn’t want that - I wanted fresh data every time - so I unchecked that box. You can also optionally change the proxy server port but I left it as the default value provided.
Done with the proxy server! Close that out.
Now let’s configure the VPN server. This is a bit more complex than the proxy server, but not too bad.
Again from the application manager (the top-left corner icon in the DSM admin panel) select the “VPN Server” application.
On the “Overview” pane in the VPN server you you will start out showing no VPNs listed. Once you’ve finished configuring the VPN, you’ll see what I see - the NAS running the VPN and the VPN showing as enabled.
The VPN Server application offers several different VPN types to choose from. You can read about the differences on this article. I chose to use PPTP for my VPN for compatibility reasons - it was the easiest to get set up and running and I had some challenges trying to get different devices hooked up using the others. I am not specifically recommending you use PPTP, that’s just what I’m using. The steps here show how to set up PPTP but it isn’t too different to set up the other VPN types.
On the PPTP tab, check the “Enable PPTP VPN server” option. That’s pretty much it. That gets it working.
That’s it for the VPN configuration.
To allow people to connect to the VPN on the NAS, we need to set up the firewall on the NAS. In the Synology DSM control panel, go to the “Security” tab on the left, then select “Firewall” at the top. Click the “Create” button to create a new firewall rule.
When prompted, choose the “Select from a list of built-in applications” option on the “Create Firewall Rules” page. This makes it super easy - the DSM already knows which ports to open for the VPN server.
Scroll through the list of applications and check the box next to “VPN Server (PPTP)” to open the firewall ports for the VPN.
The firewall settings will be applied and you’ll see it in the list of rules.
The last thing to do on the NAS is to set up the router port forwarding configuration. DSM can automatically configure your router right from the NAS to enable the VPN connection to come through.
In the DSM Control Panel, go to the “External Access” tab on the left and choose “Router Configuration” from the top. This is almost identical to the firewall configuration process. Click the “Create” button to add a new rule and you’ll be prompted to choose from a list of existing applications. Do that, and select the VPN server from the list.
Once it’s configured, the DSM will issue some commands to your router and the rule will show up in the list.
That’s it for your server configuration! Now you have to connect your clients to it.
The rest of this walkthrough shows how I got my Android 4 phone connected to the VPN. I don’t have walkthroughs for other devices. Sorry.
Go to the main settings screen. From here, you’re going to choose “More settings.”
Scroll down to the VPN settings and click that.
For a PPTP VPN, select “Basic VPN” from the list.
Give your VPN a memorable name and put the DDNS name for your server in the “Server address” box.
When you connect to the VPN you’ll be asked for a username and password. Use the username and password from your user account on the Synology NAS. (Remember that first step of setting up user accounts? This is why.)
The last configuration step is to set the proxy server. Android 4 has this hidden inside the wifi configuration for each wifi hotspot. For the hotspot you’re connected to, edit the settings and check the “Show advanced options” box. Fill in the proxy details using the local machine name of your NAS (not the DDNS name) and the proxy server port you have configured.
Now connect to the VPN and the wifi hotspot at the same time. Go back through the Settings => More settings => VPN path to find the VPN you configured. Connect to it and if you haven’t previously set up credentials you’ll be prompted. Connect to the wifi hotspot as well so it’s using the proxy server.
When you’re connected to both the VPN and the hotspot with the proxy settings, things work! You will see a little “key” at the top of the phone showing you’re connected to a VPN. You can pull up some VPN details from there.
And here’s a screen shot of me surfing my blog through my VPN and proxy server, securely from an open wifi hotspot. Note the key at the top!
I’m still working out a few things and may change my setup as time goes on, but this is the easiest DIY VPN/proxy setup I’ve seen.
Stuff I’d like to do next…
And, finally, again - thanks to Cory Doctorow for prodding me into researching this; and thanks to Synology for making it easy. Part of what Doctorow was saying at his visit is that Security is Hard, particularly the implementation of decent security for the lay person. Synology is as close to point-and-click easy setup as I’ve ever seen for this.
If you’re looking for one of these devices, the Synology DS214se is pretty budget-friendly right now, though the Synology DS414j might give you a little room to grow. I have the DS1010+, which is basically the previous model of the Synology DS1513+, which is more spendy but is super extensible. All of the Synology products run the DSM so you really can’t go wrong.
UPDATE 8/14/2015: I’ve moved to an OpenVPN-based VPN (still hosted by my Synology Diskstation) and no longer need the proxy. I’ve added some instructions on how to get that working as well as how to make your Android device auto-connect to it when not on a trusted network.
We have a nice TeamCity build server at work and we somewhat-recently updated it to use a MySQL database instead of XML for the data storage (like for the VCS roots).
We have a number of service accounts we use for interacting with the version control systems and they periodically need their passwords changed. It used to be that we could modify the XML document search-and-replace style, but now it’s hidden in the database somewhere and is less straightforward to update.
Thankfully, TeamCity offers a REST API you can work with, so I decided to play with PowerShell and the Invoke-RestMethod command to automate the drudgery of going through the something-like-50 VCS roots we have defined and updating the passwords for selected accounts.
Here’s the code for a small one-function module:
<#
.Synopsis
Updates the password for a user account in TeamCity associated with VCS root entries.
.DESCRIPTION
Iterates through the VCS roots defined in TeamCity and updates the password associated with the specified user for all VCS roots.
.EXAMPLE
$credential = Get-Credential
Update-TeamCityVcsAccount -TeamCityUrl "http://your-teamcity-dash/" -TeamCityCredential $credential -VcsUserName "serviceaccount" -VcsPassword "TheNewPassword"
.NOTES
This command uses the TeamCity REST API to iterate through the VCS roots and update the password for matching accounts.
#>
function Update-TeamCityVcsAccount
{
[CmdletBinding()]
Param
(
# The URL to the TeamCity dashboard.
[Parameter(Mandatory=$true,
ValueFromPipeline=$false)]
[ValidateNotNull()]
[ValidateNotNullOrEmpty()]
[Uri]
$TeamCityUrl,
# The credentials of the TeamCity administrator account to make changes.
[Parameter(Mandatory=$true,
ValueFromPipeline=$false)]
[ValidateNotNull()]
[ValidateNotNullOrEmpty()]
[PSCredential]
$TeamCityCredential,
# The username of the VCS user that should be updated.
[Parameter(Mandatory=$true,
ValueFromPipeline=$false)]
[ValidateNotNull()]
[ValidateNotNullOrEmpty()]
[String]
$VcsUserName,
# The new password for the VCS user.
[Parameter(Mandatory=$true,
ValueFromPipeline=$false)]
[ValidateNotNull()]
[ValidateNotNullOrEmpty()]
[String]
$VcsPassword
)
Begin
{
$updated = @()
$progressActivity = "Updating VCS root passwords for $VcsUserName..."
}
Process
{
$vcsRootsUri = New-Object -TypeName System.Uri -ArgumentList $TeamCityUrl, "/httpAuth/app/rest/vcs-roots"
$allRoots = Invoke-RestMethod -Uri $vcsRootsUri -Method Get -Credential $credential
foreach($href in $allRoots.'vcs-roots'.'vcs-root'.href)
{
$rootHref = New-Object -TypeName System.Uri -ArgumentList $TeamCityUrl, $href
$vcsRoot = Invoke-RestMethod -Uri $rootHref -Method Get -Credential $credential
$currentVcsUserName = $vcsRoot.'vcs-root'.properties.property | Where-Object { $_.name -eq "user" } | Select-Object -ExpandProperty "value"
if($currentVcsUserName -ne $VcsUserName)
{
continue;
}
# secure:svn-password == Subversion Repo
# secure:tfs-password == TFS Repo
# Making the assumption all the password fields have this
# name format...
$propToChange = $vcsRoot.'vcs-root'.properties.property | Where-Object { ($_.name -like 'secure:*') -and ($_.name -like '*-password') } | Select-Object -ExpandProperty "name"
$propHref = New-Object -TypeName System.Uri -ArgumentList $rootHref, "$href/properties/$propToChange"
Write-Progress -Activity $progressActivity -Status "VCS root: $href"
Invoke-RestMethod -Uri $propHref -Method Put -Credential $credential -Body $VcsPassword | Out-Null
$updated += $propHref;
}
}
End
{
Write-Progress -Activity $progressActivity -Completed -Status "VCS roots updated."
return $updated
}
}
Export-ModuleMember -Function Update-TeamCityVcsAccount
Save that as TeamCity.psm1 and then you can do this:
Import-Module .\TeamCity.psm1
$credential = Get-Credential
Update-TeamCityVcsAccount -TeamCityUrl "http://your-teamcity-dash/" -TeamCityCredential $credential -VcsUserName "serviceaccount" -VcsPassword "TheNewPassword"
When you run Get-Credential you’ll be prompted for some credentials. Enter your TeamCity username and password. Fill in the appropriate values for the parameters and you’ll see progress rolling by for the password updates. The return value is the list of VCS root URLs that got updated.
Now that I have a reasonably-working pattern for this, it should be easy enough to use the REST API on TeamCity to automate other common admin tasks we do. Neat!
I have an MSDN subscription at work which comes with some Azure services like virtual machines. I’m using one of these VMs to explore the VS 14 CTP.
The problem is… port 3389 isn’t open through the firewall at work, so using the default port for Terminal Services doesn’t work for me.
Luckily, you can change the port your VM uses for Terminal Services. Knowing I won’t be hosting a web site here, changing to port 80 makes it easy.
First, open up the VM in the Azure Portal and click the “Settings” button.
Now click the “Endpoints” entry on the list of settings.
We want the public port for Terminal Services to be port 80. Click the Terminal Services entry to edit it.
Update the public port to 80 and click the Save button at the top.
Now go back to the main VM dashboard and click the “Connect” button.
A small .rdp file will download. If you open it in a text editor it will look like this:
full address:s:yourmachine.cloudapp.net:3389
prompt for credentials:i:1
Change that port at the end to 80.
full address:s:yourmachine.cloudapp.net:80
prompt for credentials:i:1
Save that and double-click the file to start a Terminal Service session. Boom! Done.