Windows 8.1 OSD supported with SCCM 2012 ?

Windows 8.1 OSD supported with SCCM 2012

CU3 only supports the following for 8.1
‘This update adds support for Windows 8.1-based client computers in Microsoft System Center 2012 Configuration Manager Service Pack 1. Windows 8.1 is added to the supported platform list for the following features:
Software distribution
Software update management
Compliance Settings’
For complete OSD support you must be running R2. Here's a great starter guide.
http://www.scconfigmgr.com/2013/10/19/deploy-windows-8-1-with-configmgr-2012-r2/
Cheers
Paul | sccmentor.wordpress.com
OSD of Windows 8.1 is fully supported on SCCM 2012 SP1 CU3.
More info: http://blogs.technet.com/b/configmgrteam/archive/2013/10/21/how-to-enable-windows-8.1-deployment-in-sc-2012-configmgr-sp1-cu3.aspx
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Similar Messages

How to prompt for OU during OSD Task with SCCM 2012 R2?

How to prompt for OU during OSD Task with SCCM 2012 R2?

Hi,
Here is an example on how to do it using a Variable prompt in Configuration Manager, It works the same way in SCCM 2007,
http://www.the-d-spot.org/wordpress/2013/04/01/dynamically-join-computer-to-ad-ou-during-osd-with-sccm/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

WinPE 5 802.1x Support with SCCM 2012 R2

Please see updated information a few posts down.
I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012. I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties. I am trying to follow the guide on the deploymentguys.
I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line. doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2"
does work. I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2" All i get is error setting
user data for interface ethernet2, the operation is not supported.
How does one get 802.1x working in WinPE 4.0?
Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:
So here's the current situation and hopefully someone has seen it before.
My boot image has the prestart command set to x:\8021x\configure8021x.cmd. If i make a USB boot media this command will run and work with an 8021x wire plugged in. If I PXE boot with a non8021x
wire plugged in this command will run. If I PXE Boot with an 8021x
wire plugged in it does not run the command. If the boot image gets staged from the windows software center it
also will not run my command.
Does anyone know why the staged boot image and booting from PXE are not running my prestart command? It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?

Well progress on this issue has been made. So why I was getting the operation not supported is because I was exporting our corporate 8021x LAN profile which gets put in place by group policy, which i assumed would work. So i unjoined the windows
7 machine from the domain and was then able to modify the LAN profile to be what is exactly in the documentation with images.
Then the above command works and I no longer get the operation is not supported and I am able to move on to the next steps which is to create a script file which contains the net start and the netsh commands i was using above to test it. Great!
Now my next issue comes up when the instructions tell me to modify the winpeshl.ini file which it says is located at X:\windows\System32\Winpeshl.ini. So I mount the boot.wim file that I did earlier and I browse to the location in question however
the first thing I notice is that when I open the winpeshl.ini file to go to modify it I expect to see:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Instead what I find is it says:
[LAUNCHAPPS]
%Windir%\system32\netstart.exe, -prompt%SYSTEMDRIVE%\sources\recovery\recenv.exe
So I thought ok I will create a copy of this file and rename it to winpeshl.ini.bak and then modify it to say what It says it should be in the instructions which is:
[LAUNCHAPPS]
winpeinit.exe
%SYSTEMDRIVE%\Windows\System32\wscript.exe, %SYSTEMDRIVE%\8021x\Configure8021xUser.wsf
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Next I unmount the boot.wim file and overwrite the copy I had. Next I update the distribution points and PXE boot a test machine. What I see next is
what I dont understand. Upon booting and hiting F8 to get to a command line I cd into x:\windows\system32\ and notice that I do indeed still have my winpeshl.ini.bak file so I open the winpeshl.ini file I had thought I modified earlier and low and behold
it contains this which is different when I look at it when I mounted the wim file:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
So something is modifying this file and setting it this way effectively overwriting what I put in so that my script can run and configure the 8021x user settings.
Is there some updated documentation somewhere, how do I proceed from here??
The next steps after this would be to modify the unattend.xml file at a certain location to run the Configure8021xUserWindows.wsf script which does the winpe script just instead
of running from X: it runs from C: as it says in the documentation. But I can't move on to test this yet without getting the winpe part working.

Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1

Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)

MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua

AMT 3.2.10 Clients with SCCM 2012 on Windows 2012

Hey
I have a couple of HP dc7800 computers with Intel's AMT/vPro that I'd like to provision with SCCM 2012. The installed firmware version is 3.2.10 which is a supported version according to the documentation [1]. Provisioning of newer clients (5.2.x upwards)
is successful, so I can rule out all the usual suspects like the provisioning certificate from GoDaddy, our internal CA, DHCP options, etc. Provisioning with SCCM 2007 of both 3.2.x and 5.x AMT devices is also still successful.
The amtopmgr.log repeatedly shows the following entries:
Provision target is indicated with SMS resource id. (MachineId = 16777325 WS45.mydomain.ch)
Found valid basic machine property for machine id = 16777325.
Warning: Currently we don't support mutual auth. Change to TLS server auth mode.
The provision mode for device WS45.mydomain.ch is 1.
The IP addresses of the host WS45.mydomain.ch are x.x.x.x.
Root hash of provisioning certificate is 2796BAE63F1801E277261BA0D77770028F20EEE4.
Attempting to establish connection with target device using SOAP.
Create provisionHelper with (Hash: 74B7792EDBD64EBB01E2E3A0B27FAFA04C2D3BCB)
Set credential on provisionHelper...
Try to use provisioning account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioning account #0.
Try to use default factory account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using default factory account.
Try to use provisioned account (random generated password) to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioned account (random generated password).
Error: Device internal error. This may be caused by: 1. blabla...
Error: Can NOT establish connection with target device. (MachineId = 16777325)
After some investigation with Wireshark, I've found out that SCCM tries connect with TLSv1 to the AMT device. The response from the device is immediately an SSL alert (internal error). Using OpenSSL, I could connect to the device if I explicitly told it
to use SSLv3. This leads me to believe that the 3.2.x firmware cannot handle TLSv1 correctly and SCCM never tries to connect with SSLv3 after a failure.
So the question is: How can I get SCCM 2012 to provision these devices?
Regards,
Ingo
[1]
http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigOOB

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Windows Intune with SCCM 2012 R2.

Windows Intune with SCCM 2012 R2.
I am able to download Certificate Signing Request (CSR).
When I submit CSR file to Apple Push Certificates Portal I get following prompt:
Do you want to open or save create02fe592d.json (132 bytes) from identity.apple.com?
I am unable to get the APN Certificate.

That is a known issue with Internet Explorer and the Apple Website. If you just go back to the main page where all your certificate are located you can download it from there.
Jon L. - MSFT - This posting is provided "AS IS" with no warranties and confers no rights.

Deploying CC Enterprise Applications With SCCM 2012

Hi all,
We are using CC Packager to package up individual applications (Photoshop, InDesign etc) and are having trouble deploying the applications once packaged. To deploy, we are using SCCM 2012 and are deploying to Windows 7 x64 clients. It appears that the install begins on the client, then hangs, never to finish.
We are running the MSI with the REBOOT=ReallySuppress and MSIRESTARTMANAGERCONTROL=Disable commands, but with no luck.
This has us really stumped. The applications seem to package fine, yet just won't install. If we manually run the installer, we can see it begin installing, then the progress bar goes backwards and the installation ends without displaying any sort of message.
Also, as an FYI, we have followed this guide closely in our attempts: http://helpx.adobe.com/creative-cloud/packager/deploying-packages-sccm.html
Has anyone experienced a similar problem? Any ideas?
Thank you in advance.
Ryan

Windows 7 x64 Clients
Deploying with SCCM 2012
I have called Adobe before and was told that the application package needs to be on a local drive on the computer. The package cannot be installed if the package is sitting on the network. My installation for a adobe creative cloud package fails to install when I try to install the application from the software center. At some moment the installation searches to ensure it is on a local disk. Not sure how this happends. If you place the installation package on a drive on your computer the package will install, although it will take time depending on how many applications you have packaged.
Another problem that you might have is having users log out of the applications without admin previlages.
I have yet to find a solution for these two problems, I could really use some help from someone who has sucessfully deployed a creative cloud package to a user.
Thank you

Deploymen fix with sccm 2012 R2

Hello Guys
I need deployment a patch in 235 windows 7 x86 and x64. I was created the package and also create a .bat file with the following contents
wusa.exe <fix.msu> /quit /norestart
The package is distributed but when is running appears a windows with the parameters of wusa
Who I can distributed this patch with SCCM 2012.
Thanks for your help
Regards

Hello
I running .bat file with the parameters
wusa.exe <fix.msu> /quit /norestart
In the station of user appears a messages with options of parameters wusa.
Exist other method?
Regards

Will SCOM 2012 R2 co-exist with SCCM 2012 SP1

Hi. Sorry if the answer is obvious, but I need to ask...
Will SCOM 2012 R2 coexist with SCCM 2012 SP1?
We currently have SCOM 2007 R2 installed and we'd like to upgrade.
We installed SCCM 2012 close to 2 years ago and upgraded to SP1 last summer.
We had SCOM 2007 R2 integrated with SCVMM 2008 R2, but have upgraded to SCVMM 2012 SP1 recently - so there is nothing setup between SCOM and SCVMM.
There is currently nothing setup between SCOM and SCCM.
We're a single forest, single domain shop. Ideally, we'd like or System Center products to "work together", thus the question about the 2012 SP1 and R2 mix.
Thanks for any input. I appreciate your time and expertize. Joe.

Hi,
I concur with Alexey, a side note SCCM and SCOM do not use the same SQL Server.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Does Powershell 3.0 / Wmf 3 runs flawlessly with SCCM 2012 SP1

Hi the title says it all:
Does Powershell 3.0 / Wmf 3 runs flawlessly with SCCM 2012
SP1?
Thanks, Rob

Hi Rob,
WMF3 is required for ConfigMgr 2012 SP1:
http://support.microsoft.com/kb/2801416
(I posted the same link in your thread in the PowerShell forum).
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing)

Remote WSUS integration with SCCM 2012

Hi,
We are currently having WSUS already in place for Patching , but not used at all its just installed.
can remote WSUS be integrated with SCCM 2012 server which is on different server ? what is the best practice ? is it to have WSUS on same server as Primary server?
or I decommission it and install a new WSUS on same server as SCCM server.
what steps have to be taken care if remote WSUS is integrated ? any documents or steps to be taken care .
Thanks in Advance

When you install SUPs, they automatically configure the underlying WSUS instance to sync from an upstream server based upon your ConfigMgr hierarchy.
A couple of notes here though:
- You generally shouldn't use an existing instance of WSUS for ConfigMgr. Once integrated into ConfigMgr, WSUS should no longer manage approvals, update binary downloads, or update binary distribution as these are all handled by ConfigMgr separate from WSUS.
Using an existing WSUS instance where this was the case can be problematic at best and will cause unexpected behavior and results.
- Clients do not choose SUPs based upon boundaries or location so using a remote SUP is typically not beneficial and in many cases will cause additional network load. The exception to this is if the SUP is within a secondary site.
Jason | http://blog.configmgrftw.com | @jasonsandys

I heard some promote use of "Terminal Services(RDS)", rather than App-V application with SCCM 2012 even if you have SCCM licens.

Hi,
I heard some promote use of "Terminal Services(RDS)", rather than App-V application with SCCM 2012 even if you have SCCM licens. The reason you dont need to repackage\test the application on an client OS...
I don't agree and I have not Heard this Before, just that you use TS for some scenario.
Or is it more likely that "Terminal Services(RDS)", take over the applikation administration?
/SaiTech

Surely this all depends on your environment. There's nothing wrong with creating RemoteApps to push to client devices. Maybe you have an environment where RDS is widely used.
Why not leverage both solutions and target App-V's at RDS servers and then create App-V based RemoteApps that users can run at home as part of a home working solution via RDWeb.
Creating apps via RDS will be an admin overhead yes but then so is creating App-V packages in SCCM.
I don't agree with the arguement re: 'you dont need to repackage\test the application on an client OS...' as
App-V allows you to run on multple O/S types.
To be honest both technologies have their pros and cons.
Cheers
Paul | sccmentor.wordpress.com

How to find using SQL query application deployed on win 7 machines with SCCM 2012 server or user installed manually.

Hi,
how to find using SCCM SQL query, application deployed on win 7 machines with SCCM 2012 server or user/technician installed manually. Please let me know.

Thanks, is it not possible via any script also?
Like Torsten said, how can you tell the difference between CM12 installed applications and locally installed? Once you can answer that, then you can write report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

How to manage Forefront Endpoint Prorection Security Client 2010 with SCCM 2012

Hi
I've sucessfully installed System Center Configuration Manager 2012
and now I 'd like to push/deploy Forefront Endpoint Protection Client 2010 on client machines.I also know that Microsoft embedded Forefront Endpoint Protection in SCCM 2012 so that you can manage FEP from single SCCM 2012 console.Now
when I try to push FEP client on client machines using Default Client Settings
then I've found that all Endpoint Protection settings are greyed out !
Do I need to install Forefront Endpoint Protection 2010 or 2012 Server (which is beta) with SCCM 2012, in order to deploy FEP client or is there a workaround or solution to resolve this ?
Thanks
Sohail

Hi,
Endpoint Protection 2012 is builtin in SCCM 2012, you simply add the Site Role called Endpoint Protection either on your CAS if you have one of those or on your Primary site Server. FEP is no longer a standalone installer and it is a released product and
no longer Beta.
Then the Endpoint Protection Client Settings will no longer be greyed out and you can deploy the System Center 2012 Endpoint Protection client.
http://technet.microsoft.com/en-us/library/hh508760.aspx
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

How to reduce configuration cache file Quota size located in ( C:\Windows\ccmcache ) for all client from SCCM 2012 server

How to reduce configuration cache file Quota size located in ( C:\Windows\ccmcache ) for all client from SCCM 2012 server
Thanks in Advance
NTRao

Hi,
There are numerous ways to change the cache size.
You could deploy a vbscript to a collection of the devices.
On Error Resume Next
Dim UIResManager
Dim Cache
Dim CacheSize
CacheSize=20000
Set UIResManager = createobject("UIResource.UIResourceMgr")
Set Cache=UIResManager.GetCacheInfo()
Cache.TotalSize=CacheSize
Or you could use a configuration item.
http://blog.coretech.dk/heh/configuration-items-and-baselines-using-scripts-powershell-example/
You can also use the right click tools by Now Micro on a collection, if all the servers are on this would be the easiest / quickest way.
http://www.nowmicro.com/recast/right-click-tools/
http://www.david-obrien.net/2013/02/how-to-configure-the-configmgr-client/
select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like '%6.2%'
https://msdn.microsoft.com/en-us/library/windows/desktop/ms724832%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

Windows 8.1 OSD supported with SCCM 2012 ?

Similar Messages

Maybe you are looking for