netstat -lnptu | grep :<port#>

This will give you the PID of the service, and then you can run

kill <PID>

or

kill -9 <PID>

if just a regular kill doesn't work.

1 http://pss.united.com/web/en-US/content/mileageplus/awards/upgrade/default.aspx

2 http://www.united.com/web/en-US/content/booking/flight/fareClass.aspx

1. Ensure that your worker process (what the AppPool runs under) has the ability to create a database if you check the box Create database if it doesn't exist.
2. How to access the installation page.  You need to browse to http://site/views/install/default.aspx

There are other OWASP and scalability best practices that I may go into later if I really dig down further, but three that immediately come out:

1. Unencrypted DB Connection string info
2. compilation debug="true" being set in the web.config
3. Single DB

Currently reading: 

This is because the crontab service needs to be recycled in order to grab the new jobs (also, don't update your DSM, because that seems to blow it away).  As this is a non-standard linux distro, you need to restart crontab the following way:

/usr/syno/etc.defaults/rc.d/S04crond.sh stop
/usr/syno/etc.defaults/rc.d/S04crond.sh start

Steps for the Server:

1. Grab the spk from http://www.plexapp.com/linux/linux-pms-download.php.
2. Log into DSM and in Package Installer, install the downloaded spk.
3. After it is installed, visit the website at http://<nas-server>:32400.  It doesn't look like the shortcut that is created works.
4. Add in the locations to your media.

The steps for the Client on a Samsung TV with SmartHub is broken up into two options: installer hosted on your own server, or on someone elses.  It doesn't matter where you get the installer from, as you can specify the Plex Server after the application is installed.

Hosted on your NAS:

1. In Control Panel, enable web station under web services
2. Copy the installer (link) to the web share that was created in step 1
3. Copy the widgetlist.xml (link) to the web share that was created in step 1
4. Edit the widgetlist.xml to contain the IP of your NAS (or the URL where the installer is located)
5. On the TV, open the Smart Hub
6. Log in as a different user (A/red button)
• User: develop
• Password: 123456
7. Click the Settings button (D/blue button)
8. Select Development
9. Set the Server IP to that of your NAS
10. Select User Application Synchronisation
11. Once the installation is finished, restart your TV
12. Visit SmartHub and Plex is installed.
13. Point Plex at your Plex Media server.

Hosted by someone else:

1. On the TV, open the Smart Hub
2. Log in as a different user (A/red button)
• User: develop
• Password: 123456
3. Click the Settings button (D/blue button)
4. Select Development
5. Set the Server IP to 92.50.72.58
6. Select User Application Synchronisation
7. Once the installation is finished, restart your TV
8. Visit SmartHub and Plex is installed.
9. Point Plex at your Plex Media server.

These install instructions were taken from the Plex forums.

Update 1/6/2012: The crawler has completed, and it does actually work!  I also found out that it only supports TV shows right now, and not music or photos.  Looking into it, it's just a webpage with a lot of javascript.  If I have time, I may look to add music in, as having one solution for everything is a lot better than both this and DLNA!

The first one, which is something we just noticed was that the User Profile Sync jobs were constantly failing.  Unfortunately, there isn't really a good way to know without going into the MIISClient program to look at the errors.  Basically, if you think, for whatever reason, profile sync is not working, open up the MIISClient.exe (Program Files\Microsoft Office Servers\14.0\14.0\Synchronization Service\UIShell) as the farm account and take a look to see if everything is a success.

For us, we were seeing all the MOSS-{guid} jobs failing with the error stopped-extension-dll-exception as you can see below.

Based on the lovely error message, I'm still amazed that I was able to isolate this issue (event logs reported that CA was being accessed via a non-registered name).  However, it turns out it is because of alternate access mappings (AAMs) for the central admin (CA) website.  Normally, SharePoint sets up the AAM for CA as the machine name you first install SharePoint on to.  However, we changed the AAM to be a more friendly name.

When you update the "Public URL for Zone" for the CA website, it does not propagate the change into the MIISClient.  This causes the MIISClient to not correctly access the CA APIs for the user profile sync (or at least I am imagining this is the case).

Fix it with the following steps:

1. MIISClient.exe as the farm account.
2. Tools > Management Agents (or click the Management Agents in the bar)
3. Right-click on the MOSS-{guid} management agent and select Properties
4. Go to the Configure Connection Information section in the left-hand pane
5. In the connection information box, change the Connect To URL to be the same URL as listed as the "Public URL for Zone" for your CA in the AAM configuration.
6. Re-enter the farm account username and password for good measure
7. Save the configuration
8. Run a full profile sync from CA

1. Download the latest release of the Linux Crashplan Client from Crashplan website along with the client for your operating system if you use another operating system then Linux
2. Upload the Linux client to the NAS and login to your NAS as root using SSH.
3. You need to installe ipkg in order to do so. If haven't done so already you can follow this guide: http://forum.synology.com/wiki/index.php/Overview_on_modifying_the_Synology_Server,_bootstrap,_ipkg_etc#What_is_a_Synology_Server
4. You will need to install a few extra packages at your NAS from the command line:
1. ipkg update
2. ipkg install nano
3. ipkg install cpio
4. ipkg install bash
5. ipkg install coreutils
5. Move the uploaded client package to /opt
6. Unpack the crashplan client: tar -xvf name_of_downloaded_archive_file
7. Modify the install.sh script in the newly created directory to use bash as your shell. The first line in the script should be replaced with this one: #!/opt/bin/bash
8. Install the crashplan using the options below. When asked about java allow it to be downloaded:
• CrashPlan will install to: /opt/crashplan
• And put links to binaries in: /opt/bin
• And store datas in: /opt/crashplan/manifest
• Your init.d dir is: /etc/init.d
• Your current runlevel directory is: /usr/syno/etc/rc.d
9. Modify the /opt/crashplan/bin/run.conf by adding  -Djava.net.preferIPv4Stack=trueas an additional option at the end of the two confiurations (This was already added when I did the install)
10. Remove commandline options for the ps process in the /opt/crashplan/bin/CrashPlanEngine file since ps doesnt accept parameters at the synology NAS: sed -i 's/ps -eo /ps /'  CrashPlanEngine;sed -i 's/ps -p /ps /'  CrashPlanEngine
11. Modify the /usr/syno/etc/rc.d/S99crashplan file line 1 to : #!/opt/bin/bash
12. Modify the /opt/crashplan/bin/CrashPlanEngine file line 1 to: #!/opt/bin/bash
13. Modify the /opt/crashplan/bin/CrashPlanEngine file line 14 with a full path for nice to: /opt/bin/nice
14. Start your crashplan service /usr/syno/etc/rc.d/S99crashplan start
15. Validate that your service is running: netstat -an | grep ':424.' should give to listeners:
• tcp        0      0 0.0.0.0:4242            0.0.0.0:*               LISTEN
• tcp        0      0 127.0.0.1:4243          0.0.0.0:*               LISTEN
16. Edit /etc/rc.local and add "/usr/syno/etc/rc.d/S99crashplan start" without quotes, it seems to load after restart.
17. Install your desktop client and point it towards the headless service you just installed. Follow the instructions in the crashplan website for this (http://support.crashplan.com/doku.php/how_to/configure_a_headless_client)

Instead, I picked up a Synology DS1511+ NAS.  This little appliance is pretty darn slick.  It can pretty much do everything I was doing, in a smaller, quieter, and cooler form factor.  Since it uses an Atom processor, it runs a fairly familiar flavor of Linux, so you can do quite a bit with it.  Plus, a lot of the default stuff it comes with is quite nice!

I'll be throwing up a few copy/pastes on the site so that I can quickly re-reference.  Oh, and there's another SharePoint article in the works too.  Busy, busy!

General idea came from a few places for the upload, and locally for the file creation.

#USER Defined Variables
#Specify the extension type of files you want uploaded
$strDocTypes = @(".docx",".xlsx", ".pptx", ".pdf")
#The max amount of data generated in MB
$maxSize = 50
#The max size one file could be in MB
$maxFileSize = 10
#Intermediate folder where the test data is placed
$fileSource = "F:\TestData"
#New Content Database (for easy removal)
$dbName = "Portal_ContentDB2"
#New Site collection template
$template = "SPSPORTAL#0"
#Account owner
$siteOwner = "TEST\Administrator"
#Web Application address
$webApp = "https://portal"
#Site Collection Address
$siteCollection = "/sites/1"
# DO not edit anything beyond this line

#Create all the test data using FSUTIL

$rand = New-Object system.random
do {
	$guid = [guid]::NewGuid()
	$guid =  $guid.ToString()
	$fileName = $guid+$strDocTypes[$rand.next(0,$strDocTypes.length)]
	$rand1 = $rand.nextdouble()
	$rand2 = $rand.nextdouble()
	$rand3 = $rand.nextdouble()
	[int]$fileSize = 1048576*$rand1*$rand2*$rand3*$maxFileSize
	FSUTIL FILE CREATENEW $fileName $fileSize
	$fileTotalBytes = $fileTotalBytes + $fileSize
	$fileTotal = $fileTotalBytes/1024/1024
}
#Data generation keeps going until the amount of data is > $maxSize
while ($fileTotal -le $maxSize)

#Creation of the new content database and site collection
$siteCollectionURL = $webApp + $siteCollection
New-SPContentDatabase $dbName -WebApplication $webApp
New-SPSite -url $siteCollectionURL -OwnerAlias $siteOwner -Name "Test Doc Library" -Template $template -ContentDatabase $dbName

#uploading of all the generated data into the $siteCollectionURL/Documents folder
$spWeb = Get-SPWeb -Identity $siteCollectionURL
$listTemplate = [Microsoft.SharePoint.SPListTemplateType]::DocumentLibrary
$spFolder = $spWeb.GetFolder("Documents")
$spFileCollection = $spFolder.Files
Get-ChildItem $fileSource | ForEach {
	$spFileCollection.Add("Documents/$($_.Name)",$_.OpenRead(),$true)
}

There appears to be a lot of dependencies though:

• Migration from 2007 to 2010
• As it collects info from your log files, you'll need to have everything migrated for the scripts to work
• Data
• Apps
• Site Collections
• Etc.

Could be hot though!