The Windows Servicing Guy

Features on Demand (Part 2)

2013-03-29T15:09:08Z

In part 1, I talked about how to remove a Role/Feature using Features on Demand. In this blog, I will be talking about how to add a feature back after it has been removed.

Adding previously removed Features back to a computer using Features on Demand

As I mentioned in part 1 there are three available sources for adding roles and features back to a computer after their payloads have been removed using the Features on Demand option.

· Installation Media

· Network location of install.wim from media

· Windows Update (if configured)

To add features back into an image, administrators will need to use DISM.exe from an elevated command prompt, the Windows PowerShell cmdlets for DISM or Server Manager and path to the Windows Image file (.WIM) that holds the necessary payload for the feature to be restored. Source paths are not required if GPO’s have been defined for the environment. I’ll talk about that later.

To restore features using DISM.exe

1. Locate the .WIM file that contains the payload for the restore operation. This can be located on locally attached storage or a network share.

2. Run the command: DISM /online /enable-feature /featurename:WindowsServerBackup /source:wim:c:\install.wim:2 /limitaccess (where the WIM index is the image in the WIM file that contains the source of the feature payload)

a. The limitaccess switch will prevent the installation from attempting to contact Windows Update/WSUS Servers.

You can get the WIM index using the following command:

If you didn’t specify the source path you would get the following:

When restoring Roles/Features using the Server Manger GUI interface you will get the following notifications if the GPO is not configured.

Group Policy for Features on Demand

As I mentioned earlier there is a new Group Policy option in Windows Server 2012 allows for the configuration of an installation source for domain joined clients. The Group Policy is located in the Group Policy Editor in the Administrative Templates\System node and named "Specify settings for optional component installation and component repair".

Available policy settings include the following:

· Alternate source file path: Specifies the network location for use in installation operations. This must be a fully qualified path and can be either a folder location or WIM file. You can specify multiple paths by using ";" between the paths. Valid syntax is wim:<path to wim>:<index>

· Never attempt to download payload from Windows Update: Disables the use of Windows Update as an installation source

Note:

Windows Server Update Services (WSUS) is not configurable as a recovery source for Features on Demand

Values for this policy are in the registry under the following key:

HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Servicing

"LocalSourcePath"

"RepairContentServerSource"

"UseWindowsUpdate"

Possible registry values include:

• LocalSourcePath – Specifies location to use for installation source. Can specify more than one source when separated with a “;”. Valid sources include a network folder path or a WIM file (using the syntax wim:<path to wim>:<index>)

• UseWindowsUpdate – Enables use of Windows Update as an installation source

Note:

If the Never attempt to download payload from Windows Update checkbox is not checked, or if you do not use the /limitaccess switch using dism or powershell, features on demand will always attempt to use Windows Update first for the payload files.

How to troubleshoot error 0x800F081F when installing roles and features

2012-11-30T15:33:14Z

I’ve seen a couple of issues now where customers are having issues installing roles and features, particularly the .Net Framework 3.5, in Windows 8 and Server 2012. The general process is that you’ll have an application that needs the older .Net Framework and run through the UI wizard in an attempt to download the files from Windows Update. If this fails, you’ll see the error with exit code 0x800F081F. The means that we cant find a source for the files we need to install the feature you’re requesting. So, how do you troubleshoot this?

Make sure the source you’re using isn't corrupted. If you have a download ISO from MSDN/TechNet/VL/etc, make sure that the ISO is good or try another source just to make sure.
Make sure the component store isn't corrupted. I’ve spoken in the past about the Inbox Corruption Repair feature (aka in-box CheckSUR) and it usually resolves a lot of these problems. You can check your system for problems by running the command: DISM /Online /Cleanup-Image /RestoreHealth from an Internet connected machine. Any corruption and repair operations will be logged to the CBS.log
If you have a WSUS server on your network, use the /LimitAccess switch from DISM and install the component that way. For example, for the .Net Framework, this command is: DISM /Online /Enable-Feature /Featurename:NetFX3 /Source:G:\sources\sxs /LimitAccess (where G: is the appropriate letter for the location of the DVD/ISO)
Update your source media. I reference how to do this in this prior post
If all else fails, open a support ticket with us so we can take a look at your logs and determine what’s going on.

Most of the time, I’ve seen steps 1-4 (or a combination of them) resolve these types of issues.

Hope that helps, let me know if you have questions.

--Joseph

Features on Demand in Windows 8 and Windows Server 2012

2012-11-20T15:27:04Z

This was written by a co-worker of mine, Jim Collins.

Features on Demand is a new feature in Windows 8 and Windows Server 2012 that will allow you to remove files associated with specific roles and features, typically referred to as payload files. The major benefit of this feature is to conserve disk space. Once removed, these binaries will need to be added back from a valid installation source before the feature can be used again. Unlike the stage and un-stage process used by the component store, Features on Demand removal results in a permanent removal of those binaries. Available sources include Windows 8/Windows Server 2012 WIM files, an expanded Windows 8/Windows Server 2012 DVD (flat), an available network location with Windows 8/Windows Server 2012 installation files and Windows Update.

Removing Roles/Features from a computer using Features on Demand

First let’s talk about removing Roles and Features from an installed Operating System. Features on Demand is exposed via the DISM command line interface as well as the new DISM and Server Manager Windows PowerShell cmdlets. Below are examples of the new DISM and Server Manager Windows PowerShell cmdlets.

DISM PowerShell Cmdlet

Server Manager PowerShell Cmdlet

It’s important to note that in Windows 8 features on demand is only exposed via DISM and DISM PowerShell cmdlets. This is important because DISM does not understand the parental dependencies. So DISM will only remove the packages you specify and will not remove any dependent packages, if they exist. For this reason it is highly recommended to only use the Server Manager PowerShell cmdlets to remove features in Windows Server 2012.

Below I will give an example of how you would remove the payload for the Windows Server Backup feature using all three methods:

DISM:

DISM.exe /Online /Disable-Feature /Featurename:WindowsServerBackup /Remove

To verify the payload has actually been removed you would run the following:

You can see from the above screenshot, that the State is Disabled with Payload Removed

DISM PowerShell Cmdlet:

Disable-WindowsOptionalFeature –Online –FeatureName WindowsServerBackup –Remove

To verify the payload has actually been removed you would run the following:

You can see from the above screenshot that the State is DisabledWithPayloadRemoved

Server Manager PowerShell Cmdlet:

Remove-WindowsFeature Windows-Server-Backup –Remove

To verify the payload has actually been removed you would run the following:

You can see from the above screenshot, that the Install State is Removed

To get a list of all Roles/Features that have been Removed you can run the following command

Get-windowsfeature | Where-Object {$_.InstallState -eq "Removed"}

Removing Roles/Features from an installation source

An administrator can also remove Roles and Features from an installation source so that they can reduce the size of their image as well as limit the Roles and Feature a specific group will have available to them. In this scenario, administrators must consider some factors to ensure the removal does not inversely effect the environment. First you will need to know what type of installation source will be used when adding roles or features back to the image. You will also need to take into account how much disk space will be needed for the addition of Roles and Features. Administrators will want to keep at least 10 GB of space free for potential component store growth.

Below are the steps to remove the Windows Server Backup feature from an installation source

1. Copy the installation WIM to a local directory (in this example C:\)

2. Create a mount directory to mount the WIM to (in this example C:\image)

3. Find the index of the image you will be editing:

DISM /get-imageinfo /imagefile:c:\install.wim

4. Mount the image to the folder created in step #2:

DISM /mount-image /imagefile:c:\install.wim /index:3 /mountdir:c:\image

5. Remove the Feature from the image:

DISM /image:c:\image /disable-feature /featurename:WindowServerBackup /remove

6. Verify the state of the feature is removed:

DISM /image:c:\image /get-featureinfo /featurename:WindowsServerBackup

7. Commit the changes to the WIM:

DISM /unmounts-image /mountdir:c:\image /commit

8. Prepare the image for deployment by adding it to a WDS or MDT deployment point.

--Joseph

How to update local source media to add roles and features

2012-11-14T16:29:00Z

I’ve talked in the past about the new Features on Demand option in Windows 8 and Windows Server 2012. However, let’s say you build out an image, remove some roles and features and then patch the overall install. If you attempt to add back in roles and features previously removed, the operation will fail because it needs updated source files (RTM+patch level) to complete this operation.

My colleague Ben Herila from the Server Core team has some information about this on their team blog: http://blogs.technet.com/b/server_core/archive/2012/11/05/using-features-on-demand-with-updated-systems-and-patched-images.aspx

This post is to show you how you can update a recovery source to match that of your environment so it can successfully be used later to install roles and features. For the purposes of this discussion, I’ll use KB2756872 (http://support.microsoft.com/kb/2756872) as most people received this package during the initial Windows 8 release.

First, you want to download the contents of the needed updated from the Microsoft Update Catalog (http://catalog.update.microsoft.com/v7/site/Home.aspx). In this case, you’d just type in the KB number and get the following results:

Choose the appropriate downloads needed for your environment to a local computer, in this case we’ll use the 2012 update. When the updates are downloaded, they will look like this in explorer. These are the files we’ll need to use to update the source

Once you have the files downloaded, mount an install.wim for the operating system you need to update as a source. On a Windows 8 or Windows Server 2012 machine, this can all be done from an elevated command prompt using the IMAGEX commands. In the commands below, we’ll walk through the steps to mounting the install.wim to a temporary location and updating it to be a new source directory.

Copy install.wim from DVD to a temp directory

copy d:\sources\install.wim z:\install.wim

Make a mount directory for the install.wim

mkdir c:\mountdir

Remove the Read-Only attribute from the copied file so we can modify its contents

attrib.exe -r z:\install.wim

Get index information from the WIM file so we can verify the proper source index we wish to modify

dism.exe /get-wiminfo /wimfile:z:\install.wim

Mount the ‘2’ index of install.wim to our mount location

dism.exe /mount-wim /WimFile:z:\install.wim /index:2 /mountDir:c:\mountdir

I highlighted the image index above because you’ll want to ensure you’re updating the proper index when performing these operations. The Server WIM contains 4 indexes (typically) and indexes 2 and 4 contain the full operating system binaries where indexes 1 and 3 contain only the Server Core binaries. We’ll also need to make sure we know which index we updated so we can later use it for adding the roles and features back to the OS.

With the WIM mounted, you’ll need to use DISM to add the package to the index you’d previously mounted. The command for this if you’d downloaded the files above to your C:\ folder would be:

dism.exe "/Image:c:\mountdir" /Add-Package "/PackagePath:C:\2756872\Update for Windows Server 2012 (KB2756872)"

NOTE: We use the source folder for this command and not an individual MSU inside the folder

Once this step is completed, commit the changes you’ve made to the WIM and unmount it:

dism.exe /Unmount-Wim /MountDir:c:\mountdir /commit

Now you have a new source directory that can be used to add roles and features back to your patched images. So, if you were on Server Core and wanted to add back the shell components using your updated index 2 source, the command would be:

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Source:wim:z:\install.wim:2

Organizations will need to determine how often they need to update their source recovery media. Any time an update is released, the source is potentially invalid for reinstallation or repair operations.

Hope that helps.

--Joseph

More on Minimal Server Interface

2012-10-09T21:29:13Z

Quick post today following up on my prior post about Features on Demand and role persistence:http://blogs.technet.com/b/joscon/archive/2012/08/20/understanding-features-on-demand-and-role-persistence-in-windows-server-2012.aspx

I've noticed people on the forums and other places have clicked through the setup process on Windows Server 2012 and ended up in Server Core (as expected btw). I've seen several people mention they'd need to rebuild their machines to get back to a user interface, which was the case in Server 2008/2008 R2 but isn't true in Server 2012. My colleague Mike Stephens recently authored an excellent post on how to manipulate the shell in Server 2012 using Features on Demand. It's located here and I think its a worthwhile read for those of you interested in the servicing of Windows: http://blogs.technet.com/b/askds/archive/2012/09/20/windows-server-2012-shell-game.aspx

--Joseph

Fixing component store corruption in Windows 8 and Windows Server 2012

2012-09-26T17:13:00Z

One of the most used tools when fixing corruption for Windows Vista, 7, 2008 and 2008 R2 was the System Update and Readiness Tool (KB947821), commonly called CheckSUR. The CheckSUR tool was an excellent way for most people to see what corruption had happened on their store, and potentially fix that corruption if the tool contained the payload to do so. I’ve written in the past how to use this mechanism to also fix corruption when the CheckSUR utility doesn’t include the payload for your files to “fool” CheckSUR into resolving the problem without needing to do all sorts of whacky permission changes (http://blogs.technet.com/b/joscon/archive/2010/05/26/using-checksur-and-update-packages-to-fix-corruption.aspx).

The way this works in Windows 8 and Windows Server 2012 is different, in a fantastic way. It’s called Inbox Corruption Repair and it brings the functionality of CheckSUR into Windows rather than requiring a separate download to get the utility like you do now. This is exposed in two ways, the first is really unseen by the end user and happens when we detect a corrupted state when attempting to install fixes via Windows Update. When this happens, we'll fix the corruption silently and then re-install the prior packages. The manual way to use this tool is via DISM. The way this is exposed is via the DISM /Cleanup-Image functionality. Here’s what the available switches do:

/CheckHealth: This checks to see if a component corruption marker is already present in the registry. We’ll inform the user if there is corruption but nothing is fixed or logged anywhere. This is merely a quick way to see if corruption currently exists. Think of it as a read-only CHKDSK. This operation should be almost instantaneous.

/ScanHealth: This checks for component store corruption and records that corruption to the C:\Windows\Logs\CBS\CBS.log but no corruption is fixed using this switch. This is useful for logging what, if any, corruption exists. This operation takes ~5-10mins.

/RestoreHealth: This checks for component store corruption, records the corruption to C:\Windows\Logs\CBS\CBS.log and FIXES the corruption using Windows Update. This operation takes ~10-15mins or more depending on the level of corruption.

As an example, if you wanted to run this utility against your local component store to check for corruption and you wanted it to repair everything as it found it you would run the following command: DISM /Online /Cleanup-Image /RestoreHealth

So a couple of things of note here:

CheckSUR.log is not created using Inbox Corruption Repair, this logging has now been rolled into CBS.log
I would typically recommend you run /RestoreHealth if you suspect corruption as it will record and fix issues and takes about the same time as /ScanHealth.
This functionality is also present in Windows PowerShell and can be scripted across an environment
Windows Update or a network available WIM are valid recovery sources but WSUS installations are not. This is important because if you have WSUS enabled in your environment, there is a chance that your repair operations may be captured by the WSUS Servers and not be properly serviced. You can control this behavior using Group Policy or the /LimitAccess switch
If you decide to block Windows Update and use a local source WIM, the WIM will only be able to recover payloads present in that WIM. This means that you’ll need to update your WIM files accordingly to match the patch level of your environment or you wont successfully recover.
CheckSUR will continue to be available for down-level operating systems prior to Windows 8 and Windows Server 2012 and will continue to get updated

These changes are really fantastic in my opinion because you no longer need to attempt to move files from other servers, manipulate permissions or “hack” other utilities to get corruption resolved. Windows Update is updated frequently so that it contains all of the payloads necessary to repair corruption. And above all else, Inbox Corruption Repair can repair both payload files and manifests (CheckSUR only did manifests) which is a HUGE win for you and I as customers.

As always, ask questions here.

--Joseph

Remote Server Administration Tools (RSAT) for Windows 8 are now available

2012-09-14T14:44:49Z

The RTM version of the Remote Server Administration Tools for Windows 8 is now available here: http://www.microsoft.com/en-us/download/details.aspx?id=28972

Please take a moment to download them and update any prior RC versions that you might have in your environment. For those of you who aren't aware, the RSAT tools are a tools management suite that can be used to remotely manage Windows Server 2012 servers from a Windows 8 client installation. Let me know if you encounter any issues with using them.

--Joseph

Understanding Features on Demand and role persistence in Windows Server 2012

2012-08-21T00:28:00Z

A new option in Windows Server 2012, Features on Demand, allows for the removal of unwanted feature payloads from a Windows Server 2012 image before or after deployment. The way Features on Demand works is that it takes the payload (binaries for all components and permissions, registry settings, etc. for previously installed and configured components) defined by the component and feature manifests and it removes them from the file system. What this means is that unwanted role and feature payloads can now be permanently removed from an online or offline Server 2012 image. In a typical Server 2012 with Gui installation, roles and features that are not installed are in a state known as staged or disabled. I've spoken about this in the past but this basically means that the files are not installed but are still cached locally on the disk in the component store (%Windows%\winsxs) and therefore are taking up disk space. When a feature is removed using Features on Demand, the payload is actually removed from the file system and that space is reclaimed. This is a great option for administrators looking to cut down on virtual disk space usage as it allows you to customize your images exactly how you want them. Features which have had their payload removed are shown as “disabled with payload removed” or “removed” in DISM and Windows PowerShell.

But how does this work in relation to features and roles installed on the system already? The answer here is, it depends. There is also a new interface option called Minimal Server Interface. This lives between Server Core and Server with GUI and offers administrators the ability to remove the shell while still administering the server with some user interface functionalities. So, here's what happens to roles and features as you move through the various stages of user interface.

Server Core

In Server Core, when installed from Setup, everything has been removed aside from the role and features supported by Core. This list can be found here: http://technet.microsoft.com/en-us/library/jj574158.aspx . Inside of Server Core, you can further remove the roles and features that it supports to continue to optimize the size of the image but everything else has already been removed.

Minimal Server Interface

Minimal Server Interface installs a lot of dependency features that are needed in order to support various user interface elements, with the exception of Desktop and Shell features. It gives you virtually all of the functionality available in the Server with GUI option, but without the patching cost of the Shell and Desktop features. The disk space savings is not as noticeable as with Server Core. With Minimal Server Interface, you benefit from a reduction in servicing and surface area. Minimal Server Interface is a great compatibility option if you are running legacy server applications that don’t support Server Core, but also don’t require the Shell. You also can’t install Minimal Server Interface directly; you must build up to it from Server Core or down from Server with GUI.

For information on configuring Minimal Server Interface, see Configuring the Minimal Server Interface.

Server with Gui

In Server with Gui, formerly called "Full Server", pretty much everything is either staged or installed. This has the largest of the three footprints, and similar to Minimal Server Interface, roles and features can be removed from the image to reduce the footprint.

With that out of the way, what happens to an installed role that is configured in Server with GUI but then I convert to Server Core using Features on Demand to reduce my footprint? Again, the answer is it depends. If the role is part of the Server Core role listing, nothing happens. The role stays installed but configuration options will obviously not include a user interface. If the role was NOT a part of the Server Core role listing, that role is removed via Features on Demand because it cannot exist in Server Core.

Here's an example, I install Server with Gui and then install the Active Directory Domain Services role and the Windows Deployment Services role. I later decide I would like to have a much smaller footprint for my Windows installation because I want to virtualize it. So I convert to Server Core using the –remove option to remove the binaries completely using Features on Demand. The AD-DS role continues to stay installed but the WDS role is removed as part of the transition to Server Core. If I were to later change my mind again and move to Minimal Server Interface or Server with GUI, the role will NOT be reinstalled, it will need to be reinstalled and (and possibly re- configured).

NOTE: You can also use the Windows PowerShell –WhatIf cmdlet to see what will be added/removed in an operation without actually doing the operation against the image

The main point to take away is this, when you're planning your Server 2012 infrastructure and you're considering space optimization, look over the various user interface options first and then pare back the roles and features accordingly. Server Core is a fantastic option for core infrastructure roles and you can make a virtual machine with a very small footprint using it. However if you want to use roles outside of the Server Core role listing, Minimal Server Interface is the best option and then features and roles should be removed from there. Only use Server with a GUI when you absolutely have to because of a dependency on the shell.

--Joseph

Now that we've RTM'd, what you can expect from the blog

2012-08-02T17:23:02Z

As many of you probably heard, we RTM'd Windows 8, Windows Server 2012 and Windows RT yesterday. In the event that you've been under a rock, you can read the release about RTM here: http://windowsteamblog.com/windows/b/bloggingwindows/archive/2012/08/01/windows-8-has-reached-the-rtm-milestone.aspx

Now that we have hit RTM and bits will soon be available for some of you, I wanted to give an update as to how things will occur here on the blog with regards to the changes in servicing. First, I've taken a new role here at Microsoft and am no longer in support. That means that I don't know how much time I will have for super regular posts, but I will do my best. I really enjoy servicing and I like the little corner of the world I've built here, so I think I'll stay a while. With that out of the way, some things I plan on talking about in the future here include the following, if you have other things you'd like to talk about, please post in the comments and we'll go from there:

Using Features on Demand to minimize image footprint
Feature and Role persistence when working with Features on Demand
Using In-Box corruption repair and how it's NOT CheckSUR
Determining offline capability of updates to make better decisions for future downtime planning

Those are a couple of things I have at the top of my mind for right now. I'll start writing on them shortly after release.

--Joseph

A dying breed

2012-05-07T11:47:00Z

Recently, I interviewed for a new role within Microsoft. As is the norm here, the last 15 minutes of the interview allows the interviewee to ask questions of the interviewer. I usually ask the same two questions of each interviewer:

1. What do you think makes a good <insert position name here>?

2. Why did you choose to work for this group and what are your most and least favorite things about the group?

I was having a conversation about how my interviews were going with a co-worker and they asked me what my answers to those two questions would be. I thought it might make an interesting blog post as I am regularly asked by the high school and college students I speak to at Microsoft events about what they can do to "get into Microsoft" or the skills required to do my job. Many people think you need a ton of fancy degrees and certifications or loads of external work experience, and all of those definitely help.

But as I thought about how I would answer the two questions though, it became clear to me that question number one is an easy answer that's becoming increasingly hard to find in potential candidates I speak with. So anyways, here are my answers to the question one above. Keep in mind this is MY opinion and doesn't have any bearing on the way groups inside of Microsoft hire.

What do you think makes a good support engineer?

For me, this is relatively simple, it comes down to two traits and I think one trait begets the other. You must have a passion for technology first and foremost. I'm not talking about someone who "likes" technology and buys a lot of gadgets, although that's not a bad start. I'm speaking of someone who lives and breaths technology. Someone who looks for interesting ways to make technology more a part of their lives or even define solutions for problems in their lives with technological answers. Does this mean that the person doesn't interact with humans? Hardly. You still need to be able to speak to people (respectfully I might add), but I want you to be as comfortable speaking to a machine as a person. And I would prefer that you're comfortable doing that with any machine and not just a computer. As an example, we recently got new phones here at work and I spent the better part of my lunch hour just trying to reprogram the ringtones (harder than it sounds) so that it would be annoying to the co-worker that sits across from me - sorry Scott. It should have been as easy as adding that dog whistle ringtone to the list, but once it wasn't, I dug into the phone and its software and tried to modify the WAV file to match the bitrate that the phone application was looking for in an attempt to get it to work. It's a small, childish example, but many people are prone to just get their phone, plug it in and make calls on it. I want someone who wants to play with the device to see how it works, even if for nefarious means.

The second trait is the ability to troubleshoot. As I said, I think an interest in technology begets an interest in troubleshooting and vice versa. However this is becoming increasingly rare to find in candidates that I speak to. There are plenty of brilliant people out there, most much more so than me, but if you cant troubleshoot, you cant do my job no matter how intelligently gifted you are. Microsoft, like many tech companies, we're fairly notorious for asking questions about manhole covers, light bulbs and moving Mt. Fuji. While we don't really ask questions like that any longer (it's a shame if you ask me), but we do still test your ability to troubleshoot. I recently did a round of interviews of college candidates and the skill I am usually assigned to interview on is "problem solving". A question I love for this is an oldie but goody: "How do you troubleshoot a keyboard?". I love this question because of the possibilities of it and it does give you information on how much a particular person has "played" with computers throughout their lives. Do they even think about PS2? Do they try other devices, computers or combinations? How do they test the keyboard they have in the scenario is good by itself? I get all sorts of answers but rarely does someone give me more than 3-4 attempts before saying it must be a hardware problem and to buy a new keyboard. While I agree, that's a fine answer, I really want someone who is going to exhaust every possibility they can (and maybe the aforementioned candidates are), especially if its to the point where I cant think of anything else they could have done. Now that's a great candidate for the work I do.

Sadly, that's a rare and dying breed. If you're interested in critical thinking type questions, I highly recommend the book "How would you move Mt. Fuji?". Its a classic from 2003/2004: http://www.amazon.com/How-Would-Move-Mount-Fuji/dp/0316778494/ref=sr_1_3?ie=UTF8&qid=1336390776&sr=8-3

Although I haven't read all of it, I hear that the authors book on Google hiring is equally interesting: http://www.amazon.com/Are-Smart-Enough-Work-Google/dp/031609997X/ref=sr_1_2?ie=UTF8&qid=1336390776&sr=8-2

--Joseph